Use cases

Org scenario planning software for reorgs

Resorcerer is org scenario planning software: a scenario is a full copy of your organization that you change freely, compare against today by positions and cost, and merge back change by change once it wins. Draft "Flatten engineering", "Open the Berlin office" and "Freeze hiring until Q3" side by side, and let the numbers, not the deck, settle which one you run.

  1. 01 / 05

    Protect today's organization

    Mark the model of your real organization as protected. Nobody edits it by accident; it changes only through a reviewed merge.

  2. 02 / 05

    Branch into options

    Copy it once per option, such as a new Platform Team or two more hires in Backend. Each copy is a full organization of its own.

  3. 03 / 05

    Change each one freely

    Add teams, positions and people to each option. None of it touches the real organization.

  4. 04 / 05

    Weigh them against today

    Compare each option with the current organization on positions and cost, and see exactly what it adds.

  5. 05 / 05

    Bring back the one you pick

    Merge the winning option into the real organization, reviewing each change on its way in.

A scenario is a copy of your org, not a spreadsheet tab

Every scenario in Resorcerer is a model: the same tree of units, positions, reporting lines and people as the real organization, held separately. Copy the real organization with everyone assigned for "next quarter, starting from today", or without assignments when the shape is the question and the names aren't yet. Because scenarios are independent, you can keep three competing restructures open at once and none of them touches the live org. A Basic workspace holds up to 10 models, Pro up to 25, and Enterprise has no limit.

Compare scenarios by headcount and cost

Open a scenario's Compare view against the real organization and every difference is classified as added, removed or changed, for units and positions alike, with the before and after of each attribute that moved: role, level, location, reporting line. Above the list sit the numbers a decision turns on: total positions, filled positions and total cost for each model, and the delta between them. Costs come from cost profiles that price positions by shape, so a scenario that adds eight engineers is costed the moment you add them, and a problems report flags any position no rule covers.

Lay scenarios out on a timeline

Some what-ifs are about sequence, not alternatives. Give models effective dates and place them on a timeline: today, end of Q2, end of year. The analysis views then show headcount and cost side by side across every snapshot, and each position carries its own history along the way, so you can see which roles are new, which are going away and which were quietly re-levelled. Positions can carry start and end dates too, for the contractor who rolls off in August inside the plan that starts in June.

Choose one and merge it, change by change

When a scenario wins, open the real organization's Merge view and select it. Resorcerer works out the operations needed, add, remove or update, and presents each one for review. Accept the new unit, reject the second hire that isn't funded yet, and resolve any item both models changed with an explicit choice. The real organization's model stays protected throughout: direct edits are blocked, and a reviewed merge is the only way in. Keep working in the scenario afterwards and the next merge shows only what changed since, so a long plan can land in stages. The full workflow is in Compare and merge.

Keep sensitive scenarios private

A restructure that names people isn't ready for the whole company. Mark a scenario private and only organization admins and the people you grant access to can open it. When it's approved, the merge is what everyone sees.

Built for the planning conversation

Ask an AI assistant "what would this scenario cost?" and it answers from the real model over MCP. Export the result, or read it through the REST API. For the wider design workflow see the organizational design tool page, and for plans built around positions and budget see headcount planning.

Start with a worked example

The free preview gives you an example organization to explore, read-only until you upgrade: org chart, diagram and matrix views, costs, breakdowns and problem checks. Paid plans start with a 14-day free trial; see pricing.

Model a scenario free

Questions people ask

How do I compare two org structure scenarios side by side?

Open one scenario's Compare view and pick the other, or today's organization. Every unit and position is classified as added, removed or changed, with the before and after of each attribute, and the totals for positions, filled positions and cost sit above the list with the difference.

How can I plan a reorg without a spreadsheet?

Draft the reorg on a copy of the real organization instead of in a sheet. Cost profiles price every position by rule, so the plan's cost updates as you change it, and a reviewed merge lands it on the real organization in one step or in stages.

Can I see what an org change costs before committing to it?

Yes. Make the change on a copy, compare the copy with today, and read the cost delta before anything is merged. The real organization's model stays protected, so it changes only when you merge.

Can I merge only part of a scenario?

Yes. Merging lists every change for review: accept the ones you want and reject the rest. Keep working in the scenario afterwards and the next merge shows only what changed since. See compare and merge.

How many scenarios can I keep at once?

Each scenario is a model. Basic holds up to 10 models, Pro up to 25, and Enterprise has no limit. Archived models count toward the limit; snapshots and models in the trash don't.