What this is
This page gives one practical onboarding path so you can move from zero to useful action without technical setup confusion.
Why I built this
I built this ecosystem because most teams are forced to jump between disconnected tools, and that creates delays, confusion, and missed handoffs. In real work, people do not need ten dashboards. They need one clear path to choose the right app, finish the task, and move on with confidence. The result is a practical ecosystem where each app has a clear job, and the documentation helps people use that job without technical friction.
Who should use this
- New users entering the Cumulus ecosystem for the first time.
- Team leads who need a clear map of which app solves which job.
- Operators who want step-by-step guidance without technical language.
What you can do today
- Choose your first product based on role and priority.
- Complete one successful first-run workflow in a controlled scope.
- Know exactly where to continue after your first success.
Quick start
By the end of this page, you will have a clear and repeatable first outcome in Getting Started in the Ecosystem.
- Pick one product only for day one. Do not start with multiple products at once.
- Use that product quick-start guide and complete all steps in order.
- After completion, open FAQ or Troubleshooting only if you hit a blocker.
Known limits and maturity
- This onboarding path is intentionally simple and not optimized for advanced customization.
- If your role is unclear, start with ecosystem map before any product action.
- Some advanced options are intentionally left out to keep first use reliable.
- Current maturity: active.