Enterprise DNA

Instead of Midaxo

Stop renting Midaxo. Own your integration system.

We build your version around how you integrate acquisitions, map the agreed Midaxo exports and run it for you. Your workstreams, review rules and steering reports stay under your control.

Midaxo discusses pricing with sales and says it scales with deal volume. Bring your quote so we can compare the work your own version needs.

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

What the subscription covers

Compare the whole platform with the integration work you need

Midaxo spans the acquisition lifecycle. The free base here starts with integration delivery and benefit evidence. Your installed version is scoped around the work your business needs to keep.

paid

A sales-led subscription

The current vendor pages direct you to a pricing discussion. Use your actual quote rather than an assumed seat price.

account_tree

A wider acquisition process

Midaxo connects sourcing, diligence, integration and value tracking. Decide which parts belong in your own operating system.

checklist

Integration workstreams

Ownership, tasks and progress sit within the hosted platform. Your version keeps those records with the rules your integration manager uses.

trending_up

Benefit tracking

Midaxo tracks value alongside the work that delivers it. Your own version separates the monthly plan, reported claims and accepted evidence.

groups

Shared working arrangements

The platform supports collaboration across integration teams. We scope the access and shared working arrangements your installed version needs.

assessment

Leadership reporting

Progress and value reports help leaders review the integration. Your version produces a steering pack from the same records your team works on.

What you own instead

A decision record behind every reported result

Day-one readiness

Know which handover task is still open

Keep due dates, owners and supporting evidence beside the work.

  • check List the tasks marked for day one
  • check Find overdue work by function
  • check Call out tasks with no owner
  • check Require evidence before recording completion

Dependencies

Expose the work blocking the result

Link prerequisites so a completed label cannot hide unfinished work underneath it.

  • check See direct and indirect blockers
  • check Reject circular dependency chains
  • check Keep each acquisition dependency chain separate
  • check Flag a completed task when a prerequisite reopens

Benefit evidence

Separate a reported saving from an accepted one

Compare monthly plans with claims and the amounts a different reviewer has accepted.

  • check Keep costs separate from savings and revenue
  • check Compare each acquisition in its own currency
  • check Clear approval when a claim is corrected
  • check Hold accepted benefits when linked work reopens

Steering decisions

Bring the unresolved questions into the meeting

Prepare the review from risks, task progress, benefit evidence and recorded decisions.

  • check Show risk owners and decision dates
  • check Keep the evidence reference behind each claim
  • check Find missing purpose and overdue privacy reviews
  • check Produce branded steering and benefit review papers

Make it yours

Design your own Midaxo replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Midaxo 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 Midaxo 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 Integration Value for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Integration Value for Claude Code

Connected to your own database

Which handover tasks need attention?

Harbour Analytics acquisition

Name
Confirm supplier transfer
Workstream
Operations
Owner
Alex Morgan
Due date
2026-11-04
Status
doing
Blockers
0
Days overdue
10
Stale
true

Kowhai Services acquisition

Name
Prepare employee access list
Workstream
People
Due date
2026-11-16
Status
open
Blockers
0
Days overdue
0
Stale
true

Ask it anything

Questions your own integration records can answer

These examples run on the fictional demo records. Change the questions and rules for your business. Midaxo also supports reporting; the difference here is ownership of the records and definitions.

chat_bubble Which acquisition has overdue day-one tasks?
chat_bubble Which benefit claims are held by unfinished integration work?
chat_bubble Which completed tasks became blocked after a prerequisite reopened?
chat_bubble What accepted net benefit remains after transition costs?
chat_bubble Which claims changed after a reviewer accepted them?
chat_bubble Which workstreams have stale updates as well as overdue tasks?
chat_bubble Which future periods have plans but no reported actuals?
chat_bubble Which acquisitions need access or retention reviews?
chat_bubble Who recorded and reviewed the evidence behind each accepted amount?
chat_bubble Which source projects imported unchanged, and which would conflict?

Switching

How to switch from Midaxo

A move involves exporting the project records you need, mapping their headings and rules, then checking the imported records and workflows before you retire Midaxo.

  1. 1

    Export agreed project records

    Use Midaxo's Grid-to-Excel project export for the projects and records you have agreed to move. The available export can vary by tenant, so confirm what your account allows with Midaxo. The import preserves source project IDs and original rows, but task trees, documents and benefit history need separate mapping. Decide whether those records are in scope before you export.

  2. 2

    Map and import selected records

    Convert the Excel export to CSV and map its actual headings to fields in the new database. Start with a preview before importing, then load only the selected project records after you are satisfied with the mapping. Keep the scope clear: task trees, documents and benefit history need separate mapping rather than being assumed to come across with the project rows.

  3. 3

    Reconcile the import

    Review the preview and reconciliation before accepting the import. Check the counts and source project IDs against Midaxo, and inspect any conflicts or other items the import flags. Resolve mapping issues and repeat the preview until the records you selected are accounted for. Keep the original export so you can trace imported rows back to their source.

  4. 4

    Run both systems briefly

    For a short period, use both Midaxo and the new database for the agreed integration work. Check that the records you need are present, then compare how you handle tasks, dependencies, monthly benefit evidence and steering papers. Use the overlap to catch missing history or workflow gaps while Midaxo is still available, and note any changes needed before you make the new system your working source.

  5. 5

    Retire Midaxo after acceptance

    Switch off Midaxo only after the people responsible for the work accept the agreed records and workflows in the new system. Confirm any separately mapped task trees, documents and benefit history that you chose to bring across. If a required workflow or record is still missing, resolve that gap before you stop relying on Midaxo.

construction

Where the real effort goes

The main work is usually mapping your own fields and operating rules, then deciding how much task, document and benefit history to bring. The project rows can be imported after mapping and reconciliation, but the other records need separate handling. When Enterprise DNA runs the installation, it maps your exports and builds the agreed fields and rules as part of the scoped work.

Not ready for a call?

Get your Midaxo switch plan by email

We will send you the step-by-step plan for moving your business off Midaxo, 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

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and try /weekly-review
  3. 3 Convert your Midaxo project export to CSV, map its headings and preview the import
  4. 4 Reconcile your records and set up a private database before using live information
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your integration workstreams, review steps and decision rules
  • check Your agreed Midaxo exports mapped and reconciled
  • check A web front end or a different technology stack where your team needs it
  • check Your reporting, document storage and business systems connected
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access and backup arrangements agreed
  • check Weekly steering packs and evidence reviews prepared
  • check Your system maintained as the acquisition programme changes
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book a 30-minute integration review

Questions

Instead of Midaxo, answered

Does the free version replace everything in Midaxo? expand_more

It covers integration tasks, dependencies, risks, monthly benefit evidence and steering papers. Midaxo also covers the wider acquisition lifecycle. We agree which additional workflows, document controls and connections your version needs before a switch. DealRoom and Devensoft are other products to compare when reviewing the broader acquisition process.

Can we bring our existing acquisition records across? expand_more

The free import starts with a project export saved as a text-based spreadsheet file, with its headings mapped and counts checked. It preserves source project IDs and original rows. Task trees, documents, permissions and benefit history need separate mapping, which we scope with you before moving the agreed records.

How do we stop a claimed saving being treated as delivered? expand_more

Reported and accepted amounts are separate. Acceptance needs evidence, a different reviewer, a recorded acquisition close and completed linked work. Correcting the amount clears approval. Reopened prerequisite work puts the benefit on hold. Reviewer names in the free version are recorded labels; your installed version needs appropriate identity and access controls.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer for the agreed ongoing work. We review your integration process, exports, access needs and reporting before proposing the scope. Hosting and the tools you choose to use remain part of the operating cost.

Can we change the rules and keep ownership? expand_more

Yes. Your version can use your fields, workstreams and review rules. You keep the source and records, and can take a complete archive. The free base also flags missing purpose and overdue privacy reviews. Those checks support your review process; they do not certify legal compliance.

Bring the Midaxo quote and your next integration plan

In a 30-minute call, Sam will walk through the work you need to carry across, the evidence behind your benefit reports and what it takes to build and run your version.

Book a 30-minute call with Sam Get the free version

Integration Value for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Midaxo?

Get your version built