ORGONAUT
Login Signup
Docs
Quickstart: first 30 minutes

Quickstart: first 30 minutes

This guide gets you from a new workspace to a decision-ready first scenario.

The goal is not perfect data. The goal is a reliable first pass you can iterate on.

Every new workspace starts with the same tenant-scoped defaults used by the seeded demo tenants: team types, department types, role types, currencies, and AI model pricing are ready in Settings before onboarding begins.

If you choose Start empty during onboarding, Orgonaut keeps those settings defaults, creates the baseline company root, sends you straight to /live, and shows a confirmation toast there so you can start building immediately.

If you choose Load demo data during onboarding, Orgonaut seeds sample people, AI agents, teams, departments, positions, and placements, then immediately rebuilds baseline rollups so the dashboard and sidebar counts are ready on reload. While that demo set is active, both /onboarding and /live show a Demo data is active banner with a shortcut to /settings/system, and Settings shows a Demo Data entry for the same page. You can remove the demo set there and return to onboarding with a clean account.

If you are on the organisation picker (/organisations), use the profile menu in the top-right to sign out. If you are on /login and need a different workspace, use the Switch Workspace link beside the login helper text. Inside the main app and public auth pages, use the profile menu or footer links to open Help Docs (/docs), API Reference (/docs/api), or the public Change Log (/updates). Until your organisation onboarding is complete, the profile menu in the top-right also includes an Onboarding shortcut back to /onboarding. On smaller screens, the top-right overflow menu holds Import, Scenarios, and Snapshots, and the header collapses to the Orgonaut mark to preserve width. Across People, Agents, Positions, Teams, Departments, and Scenarios, compact Edit actions switch to a filled pencil icon on small screens and return to text-only on larger screens.

Before you start

Prepare a CSV with at least:

  • email
  • full_name
  • department
  • job_title
  • manager_email

If you have team, location, and FTE fields, include them.

0-10 minutes: import baseline

  1. Open the import flow.
  2. Upload your CSV.
  3. Run validation.
  4. Fix blocking issues and rerun.
  5. Complete import.

Outcome: you have a usable structure in Live.

10-20 minutes: clean critical records

Prioritize high-impact cleanup only:

  • Confirm top-level departments and core teams.
  • Fix obvious manager/reference mismatches.
  • Ensure key leaders have correct primary placement.
  • Validate 3-5 representative positions.

Outcome: Live is clean enough for scenario modeling.

20-30 minutes: create first scenario

  1. Create a scenario from Live.
  2. Apply one meaningful structural change.
  3. Review cost and velocity deltas.
  4. Save and share the scenario for review.

Examples of first changes:

  • Move one team under a different department.
  • Reallocate one shared role across two teams.
  • Add an agent-supported operating pattern to a target team.

Outcome: your team can now compare current vs proposed structure with evidence.

End-of-quickstart checklist

  • Live view exists and is reviewable.
  • At least one scenario exists.
  • At least one structural change is modeled.
  • Deltas are visible and can be discussed with stakeholders.

What to do next