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.

New organisations start with a generated name such as "Nova 3027". Owners see a What is your organisation called? field at the top of /onboarding until they add data. Name it there first so the top of your org chart uses your real name; you can rename it later in Settings → Account.

If you choose Start empty during onboarding, Orgonaut keeps those settings defaults, creates the Live company root, sends you straight to /live, and shows a confirmation toast there. While Live has no people, teams or departments, /live shows how to add data instead of empty charts.

If you choose Load demo data during onboarding, Orgonaut seeds a sample organisation with four departments, six teams, about 30 people with positions, placements and salaries, and AI agents with monthly running costs, so cost totals are realistic. Each team is linked to the Work activities it does, so Work shows who does what. Orgonaut then rebuilds Live rollups and takes you to /live, with a toast pointing to the next step: creating a scenario. 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.

Account owners can use Remove demo data in Settings → System even after adding their own organisation data. Cleanup removes demo-marked records from Live and keeps your own people, positions, placements, and other records. Shared demo teams, departments, or other records needed by your own data are kept, with their demo marker removed, so nobody is moved. Existing scenarios and snapshots, including their sample records and history, remain unchanged. If Live still contains organisation data, you return to Live; otherwise you return to onboarding. Records without a demo marker are always preserved, including placements generated by older versions of the demo loader.

Once data exists, /onboarding shows a Next step panel: Create a scenario until you have one, then a button that opens your latest scenario so you can make your first change. The Onboarding checklist in the sidebar links each unfinished step to the same actions.

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, Robots, 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

On /onboarding, choose Open CSV importer in the spreadsheet card or Continue to HRIS setup in the HR system card, when available. The primary actions sit side by side on larger screens, with Download CSV template below the importer button; the cards stack on smaller screens.

Start from the Orgonaut CSV template and include at least:

  • email
  • first_name and last_name
  • department_name
  • job_title
  • manager_email

If you have team, location, and FTE fields, include them. See Import your org (CSV) for details.

0-10 minutes: import Live data

  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