Introducing Orgonaut

How software gets built has changed dramatically in the last six months.

Not in the abstract, and not as a distant future trend. The change is already visible in real engineering teams: agents in the terminal, AI-assisted workflows moving from novelty to operating rhythm, and product teams starting to ask what a smaller, faster, more automated organisation should look like.

What is happening this year is bigger than most people expected. Even people who were already bullish on AI are having to recalibrate.

And now, the way we build companies is changing too.

AI has changed how work is done and how quickly organisations need to adapt.

That is why we built Orgonaut.

Orgonaut began as a practical experiment in agentic software development: could we build a real SaaS product with AI deeply involved in the engineering process, while still keeping the architecture understandable, testable, and maintainable?

The useful lesson was not that one model or one framework was magic. It was that AI works best when the system around it has structure: clear domain models, explicit permissions, repeatable workflows, strong conventions, and good operational boundaries.

That lesson ended up shaping the product itself.

Because while we were building with AI, we were also watching organisations change under the same pressure.

Teams are restructuring more frequently. Role ratios are shifting. Some functions are shrinking while others expand. People are starting to work alongside software agents, automation systems, and increasingly autonomous tools.

Most companies still manage this with static org charts, spreadsheets, slide decks, HR systems, and planning meetings.

That feels increasingly outdated.

What would an organisation design platform look like if it was built for the AI era from the start?

That question became Orgonaut.

What Orgonaut is

Orgonaut is an AI-first organisation design and planning platform.

It is built for the people who actively shape organisations: founders, CEOs, CTOs, engineering leaders, operations, finance, HR, and transformation teams.

We also believe AI consultants will be central to Orgonaut’s early success.

They are the people already helping companies rethink roles, workflows, operating models, and delivery structures around AI. In many cases, they are the ones turning AI adoption from a tooling conversation into an organisational change programme.

For those consultants, Orgonaut can be more than a system of record. It can become a system of action alongside the engagement: a place to model the current organisation, design future scenarios, agree recommendations, and keep the approved structure alive after the consulting work is done.

That is why we are building a white-label agency plan for AI consultants who want to sell Orgonaut as part of their own package to customers. The consultant owns the relationship and the advisory work. Orgonaut provides the modelling layer, scenario workflow, and operating record behind it.

It is not trying to replace your HRIS.

It is the planning layer above it: a place to understand the current organisation, test possible changes, compare trade-offs, and make better decisions before anything changes in the live business.

The core idea behind Orgonaut is simple:

AI should be able to work with organisational structure safely.

Today, you can export an org chart into an LLM and ask questions about it.

But that is temporary. It is detached from the source model. It does not understand live versus planned structure. It cannot safely model change over time. It cannot produce governed proposals your team can review, approve, and execute.

Orgonaut changes that by making scenarios central.

Scenarios are the heart of the system

Scenarios are isolated organisational sandboxes. They let you model changes to structure, staffing, placements, positions, cost, and capacity before anything reaches Live.

That matters because AI is becoming very good at proposing change.

In software, it is already reaching the point where many code changes need much less human-in-the-loop involvement. The codebase is there. The tests are there. The interfaces are explicit. The context is increasingly legible to the machine.

Organisations are different.

Not all of the important context is written down. Humans are complex. The relationships, trust, judgement, history, informal leadership, and “right stuff” that make great teams work are often hard to define, document, or model.

So organisational change still needs human judgement.

That is why Orgonaut is built around a human-in-the-loop model from the beginning.

Astro, the embedded assistant inside Orgonaut, can answer questions, inspect teams and departments, compare scenarios, surface risks, draft proposal bundles, and help break larger restructures into phased programmes.

But humans stay in control.

AI-originated changes are staged as reviewable proposals. Scenario writes require confirmation. Live changes, promotion, and snapshots remain protected by hard guardrails.

That separation between exploration and execution is one of the most important architectural decisions in the platform.

Built for humans and agents

Orgonaut is designed to be usable by humans and agents.

The platform includes a web app, REST API, tenant-scoped OAuth, a remote MCP server, a first-party CLI, companion agent skills, and Astro for teams who want a conversational interface directly inside the product.

That matters because organisational planning should not be trapped inside one UI.

A leader might use the web app. An analyst might use the API. An agent might use MCP. A technical operator might use the CLI. The same underlying model and guardrails should apply across all of them.

Orgonaut also does not assume organisations are made up entirely of people anymore.

The platform models people, agents, and robots as first-class organisational actors.

That sounds futuristic until you realise it is already starting to happen.

Companies are beginning to work with AI coding agents, autonomous support agents, workflow automation systems, and robotics systems that operate as part of real teams.

Organisational software needs to reflect that reality.

Why systems of record need to change

We think the systems of record inside companies are going to evolve significantly over the next few years.

Historically, they mostly recorded what already happened.

AI systems need something more structured. They need systems they can read, reason over, simulate against, and use to propose safe action.

That is where Orgonaut fits.

Not as another HR platform.

Not as another org chart tool.

But as AI-native infrastructure for organisational design.

Right now, we are using Orgonaut ourselves while continuing to shape the platform in public.

The immediate goal is straightforward: build a genuinely useful system for modelling and managing organisations in an AI world.

Longer term, we think organisational structure becomes more dynamic. Teams will change more frequently. AI participation in organisations will increase. Scenario planning will become continuous instead of occasional. Organisational design will become something companies actively optimise, not something they revisit only during periodic reorganisations.

The tooling around that shift barely exists today.

So we are building it.

Welcome to Orgonaut.