Time to the first credible scenario matters
The first useful outcome in Orgonaut is not a completed transformation programme. It is a scenario that a leadership team can inspect. You can import or model the current organisation, confirm that the Live view is accurate enough for the decision, and clone it. The proposed future structure then has its own boundary, metrics, and change record.
That boundary changes the planning conversation. A spreadsheet usually mixes today, the preferred plan, and several discarded ideas. A drawing can show the future state but often loses allocations, vacant positions, compensation context, and the reason a number changed. In Orgonaut, the current state stays current while the proposal remains editable. Reviewers can ask about a concrete delta instead of trying to reconstruct one.
Transparent pricing changes who can start
Orgonaut publishes the price and the included limits. The Team plan is €199 per month or €1,990 per year for up to 75 actors and three active scenarios. The Business plan is €499 per month or €4,990 per year for up to 250 actors and ten active scenarios. Both include scenario creation and cloning, and both can begin with a 14-day trial without a card.
That does not make the products equivalent. It makes the buying decision legible. A VP Engineering, COO, founder, or people leader can decide whether a small model is worth trying without opening a procurement project. Enterprise and Agency options remain available when SAML, custom role controls, unlimited actors, or multiple client workspaces become necessary.
Org data can participate in technical workflows
Orgonaut treats the organisation as structured operational data. The same model appears through the web application, a tenant-scoped REST API, a command-line interface, remote MCP access, and OrgSpec. OrgSpec is a portable YAML representation of units, actors, positions, placements, and related organisational facts.
This is useful when the people shaping the organisation include engineers and AI-enabled operators. A scenario can be inspected in the application, reported through the CLI, or proposed through an agent-accessible surface while the human review and promotion boundary remains in place. The intent is not to automate judgement. It is to make the evidence and the proposed mutation available through controlled tools.
The product is built for continuous, smaller changes too
Many organisation decisions are too consequential for an ad hoc spreadsheet and too small for a transformation office. A squad split, a manager change, a revised hiring plan, or the introduction of agent capacity can still alter cost, coverage, and review load. Those decisions benefit from the same baseline, scenario, delta, and history discipline as a larger reorganisation.
Orgonaut keeps that loop compact enough to repeat. Live remains the shared source of truth. Scenarios hold alternatives. Snapshots preserve important historical states. Promotion lineage records how an accepted proposal became the next version of the organisation. The model can evolve with the operating cadence rather than appearing only when a major programme begins.
