Enterprise DNA

Instead of Orgvue

Stop renting Orgvue. Own your organisation design system.

We build your version around the way you review positions, capacity and costs. We map your agreed Orgvue history, prepare your review documents and run the system for you through Omni by Enterprise DNA.

Orgvue subscriptions are privately quoted and invoiced annually in advance. Professional services are billed separately under the agreed terms.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Before the next renewal

What is the Orgvue subscription doing for your review?

Orgvue provides workforce planning and scenario analysis. If your recurring job is a position review, compare that job with a system built around the records and evidence you actually use. Ask for your current renewal quote before making a cost comparison.

paid

An annual subscription

Orgvue invoices subscriptions annually in advance. Your agreed scope determines the price, so there is no single public tariff to compare with your business.

support_agent

Services alongside the software

The commercial terms distinguish subscription charges from professional services. Check the scope and fee for the changes you need.

account_tree

A view of the structure

Reporting relationships are part of the planning job. Keep stable position identifiers and parent links when you bring that structure across.

compare_arrows

Options for the next plan

Orgvue supports workforce scenarios. Decide which comparisons your review needs and retain the assumptions behind each option.

database

Data transfers between systems

Orgvue describes CSV, connector and API transfers. A complete position export is the starting point for this free version.

fact_check

Your review process

Ownership, source checks and decisions still need a home. In your version, those records sit beside the position assumptions they explain.

Your own planning system

Keep the structure, the numbers and the review in one place

Positions

See where capacity sits

Ask for positions by department, reporting manager or occupancy. Keep part-time capacity visible instead of treating every position as one full-time person.

  • check Stable position references and reporting parents
  • check Capacity fractions for part-time positions
  • check Vacant capacity by department
  • check Reporting spans and layers from the same records

Scenarios

Compare with the baseline you actually reviewed

Create an option from a dated snapshot. Its saved baseline stays fixed even if the original snapshot is corrected later.

  • check A separate option for each planning assumption
  • check Annual full-time budget rates adjusted for capacity
  • check Currency totals kept separate
  • check Changed assumptions beside before-and-after values

Evidence

Bring your review rules into the comparison

The free version joins planning assumptions with dated source reviews and follow-up evidence. Extend those checks around the questions your business needs to answer.

  • check Owners and due dates for review actions
  • check Overdue accuracy and retention reviews
  • check A different named reviewer for approval
  • check A reason and history entry when an option is reopened

Review pack

Take a clear record into the meeting

Produce a branded scenario pack and a planning decision record from the same database. Your documents keep source dates and unresolved checks visible.

  • check Department capacity and annual cost summaries
  • check A position list for the review meeting
  • check A record of review status and supporting evidence
  • check Local read-only reports in your business name

Make it yours

Design your own Orgvue replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Orgvue. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Orgvue replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Orgvue data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Organisation Design for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Organisation Design for Claude Code

Connected to your own database

Which manager positions have the most direct reports?

P01

Title
General manager
Direct_reports
3
Report_fte
2.600

P02

Title
Delivery lead
Direct_reports
2
Report_fte
1.800

Ask it anything

Ten questions the free version answers

These are real questions answered by the demo. Orgvue also offers scenario analysis. Your advantage here is owning and changing the records and review rules.

chat_bubble What annual cost does each currency carry?
chat_bubble Which departments hold vacant capacity?
chat_bubble Which planned positions are vacant?
chat_bubble How many direct reports does each manager position have?
chat_bubble How many reporting layers sit above each position?
chat_bubble What annual cost changes against the saved baseline?
chat_bubble Which position assumptions changed?
chat_bubble Which source snapshots need an accuracy or retention review?
chat_bubble Which review actions are late, and who owns them?
chat_bubble Who changed an assumption and what was there before?

Switching

How to switch from Orgvue

A move usually involves exporting a complete position snapshot, mapping your fields and cost rules, checking the imported data, and running both systems side by side before you switch.

  1. 1

    Export your position snapshot

    Export a complete positions worksheet from Orgvue, including the fields and assumptions you need for position structures, capacity and annual costs. Orgvue properties vary by organisation, and the export options available depend on your account. Check with Orgvue what you can export, usually CSV or Excel, and make sure you have the required position fields.

  2. 2

    Map fields and test the import

    Match your Orgvue property headings to the fields the new system expects, including your capacity and cost definitions. Create a dated scenario for the imported snapshot. Run the import test first and review its results before loading the data. If a heading or definition does not match, correct the mapping rather than assuming the imported value means the same thing.

  3. 3

    Reconcile the imported records

    Review anything the import flags, then check the position count against your Orgvue worksheet. Reconcile capacity and annual cost totals separately for each currency, since currencies are not combined. Confirm that reporting relationships and key assumptions look right. The importer carries positions and assumptions, not people records, permissions, saved visual layouts or live connections.

  4. 4

    Run both systems side by side

    Keep Orgvue available for a short period while you use the new system for the planning work you intend to move. Compare the structures, capacity and annual planning costs, and check that your review evidence is recorded as expected. Use the period to catch mapping gaps or differences in your rules before relying on the new system for that work.

  5. 5

    Switch off Orgvue

    When the records and planning outputs have been checked and the people responsible for the work are ready, make the new system your source for the work you moved. Keep in mind that other datasets, permissions and saved visual layouts need separate migration work. Switch off Orgvue only after deciding those items are no longer needed there or have another agreed home.

construction

Where the real effort goes

The main work is usually mapping your own Orgvue fields and cost definitions, then reconciling position counts, capacity and totals by currency. You also need to decide which history to bring across. Revised snapshots use a new scenario rather than overwriting history. When you have Enterprise DNA run it, they map the agreed history and build your planning rules and paperwork.

Not ready for a call?

Get your Orgvue switch plan by email

We will send you the step-by-step plan for moving your business off Orgvue, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free version, or have yours built and run

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo and inspect the fictional review
  3. 3 Open the folder in Claude Code, Codex, OpenCode or Cursor
  4. 4 Map your Orgvue position CSV, test the import and reconcile the result
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your position fields, capacity rules and review steps
  • check Your agreed Orgvue history mapped and reconciled
  • check Your own review documents and business branding
  • check A web view or a different technology setup when agreed
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Agreed connections to your existing business records
  • check Source updates, review documents and ongoing care
  • check Your operating rules maintained as the business changes
Book a call with Sam

Questions

Instead of Orgvue, answered

Will this replace everything we use in Orgvue? expand_more

Start with the work you need to replace. The free version covers position snapshots, reporting structures, capacity, annual budget costs and recorded reviews. Enterprise DNA scopes your visual planning, access controls and connections into the version we build for you.

Can we bring our Orgvue data across? expand_more

Yes, for a complete position export with the required fields mapped. Orgvue properties vary by organisation, so we check your headings and cost definitions, then reconcile position counts, capacity and each currency total. Other datasets, permissions and saved visual layouts need separate migration work.

Does a lower scenario cost mean we have saved that money? expand_more

No. The comparison shows annual planning costs based on your recorded full-time rates and capacity assumptions. It is not a payroll calculation or realised saving. Review timing, employment obligations and implementation costs before making a business decision.

Who can approve a change, and does this make us compliant? expand_more

The free version records review evidence, requires a different named reviewer and locks the reviewed scenario. Names are operator-entered records, not verified signatures. Its privacy and accuracy checks prompt review, and do not certify compliance or authorise an employment change. We build agreed access controls into your managed version.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer, agreed around your migration, customisation and ongoing operation. The free version has no licence charge. Hosting and the assistant you use have their own costs. Your Orgvue subscription is privately quoted, so compare against your actual renewal offer.

Bring your Orgvue renewal and one position review

Book 30 minutes with Sam. Show him the structure you review, the comparisons you need and the records behind them. He will help define the version Enterprise DNA can build and run for your business.

Book 30 minutes with Sam Get the free version

Organisation Design for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Orgvue?

Get your version built