Enterprise DNA

Instead of DealRoom

Stop renting DealRoom. Own your diligence system.

We build your version around the requests, review steps and handover work your acquisitions need. We map your DealRoom exports, bring the agreed records across and run it for you.

DealRoom quotes an annual subscription based on deal volume, with unlimited users. Its current pricing page does not publish an amount.

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

An annual platform commitment around each acquisition

DealRoom combines diligence, a document room, integration planning and reporting. Decide which of that work belongs in a system built around your own acquisition process.

paid

Pricing follows deal volume

The subscription scales with the number of deals you run. Compare that commitment with owning the request and decision records behind your acquisitions.

schedule

An annual commitment

The vendor quotes an annual subscription. Your acquisition timetable and your subscription renewal are separate decisions.

groups

Unlimited users are already included

DealRoom does not charge another seat for every adviser. The case for switching is ownership and a process built for you, not an invented per-seat saving.

folder

A hosted document room

Permissions and shared document handling are part of the platform. We scope the controlled document storage and external access your installed version needs.

checklist

Diligence and integration tracking

Requests, reviews and progress reports sit alongside integration planning. Your version connects those records to your own signing and handover rules.

extension

Optional document analysis

The pricing page identifies document analysis and organisation as an add-on. Choose the review work you want automated when we scope your version.

What you own instead

From unanswered requests to an accountable handover

Request review

Know what still needs an answer

Keep each request with its workstream, owner, due date and supporting evidence. Submission and approval are different steps.

  • check Rank unanswered requests by days overdue
  • check Find responses waiting for a separate reviewer
  • check Reopen a response when the evidence changes
  • check Compare approval backlogs across workstreams

Signing decision

Keep unresolved risks in the decision pack

See major findings beside the requests your team has not approved. Record the decision and the person who made it.

  • check Identify unresolved high and critical findings
  • check Require reviewed requests before internal signoff
  • check Record how each finding was resolved
  • check Keep integration actions open after signoff

Your records

Bring the request register with you

Start from a request-level export, check the mapping and keep the source values alongside your local review.

  • check Test the import before saving records
  • check Keep original source status for reference
  • check Skip identical repeat imports
  • check Keep document locations and privacy review dates together

Your weekly work

Build the review around your acquisition process

Generate private decision packs and handover plans from the same records. Add your own fields and rules as your investment process changes.

  • check Compare request workload by owner
  • check Find requests untouched for thirty days
  • check Review access and retention reminders with cited sources
  • check Ask a new question across your records without buying another report package

Make it yours

Design your own DealRoom replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Due Diligence for Claude Code

Connected to your own database

Which requests, findings and handover actions need attention?

request

Deal
Project Kauri
Name
Customer concentration schedule
Owner
Mere
Due
2026-10-04

finding

Deal
Project Kauri
Name
Key client termination clause
Owner
Alex
Due
2026-10-09

handover

Deal
Project Kauri
Name
Confirm client handover owner
Owner
Mere
Due
2026-10-11

Ask it anything

Questions your diligence records can answer

These examples run on fictional records in the free version. DealRoom also offers reporting. Your own fields and review rules determine the questions your version answers.

chat_bubble Which unanswered requests are furthest overdue?
chat_bubble Which responses still need independent review?
chat_bubble Which deals combine unapproved requests and major findings?
chat_bubble Which high-risk findings need a decision before signing?
chat_bubble Which owners carry the most overdue requests?
chat_bubble Which workstreams have the biggest approval backlog?
chat_bubble Which handover actions are overdue after signoff?
chat_bubble Which requests have gone untouched for thirty days?
chat_bubble Which personal documents need a purpose or retention review?
chat_bubble Who reopened a request and why?

Switching

How to switch from DealRoom

A move is less about copying request rows than agreeing what history and review rules to bring, then testing the mapped import before you change over.

  1. 1

    Export your request report

    DealRoom documents Excel exports for request reports. Export the request-level report your account allows, then save it as CSV. If you cannot find the report or are unsure what your account can export, check with DealRoom. The free base brings across request records, not every part of your DealRoom workspace.

  2. 2

    Test the import first

    Use the import’s test-run option before loading records. The guidance is to work from an empty database and create the deal record before importing its requests. Check the report columns and decide which headings match the new register. This gives you a chance to spot mapping issues without treating source completion labels as local approvals.

  3. 3

    Map and load requests

    Match the headings in your report to the fields in the new register, then load the request records. The free base preserves source values, including completion labels as source history. Those labels do not count as local approval. Files, comments, permissions and historical approvals need separate migration work, so identify any you still need before you leave DealRoom.

  4. 4

    Review import flags

    Check the import results for records that need attention. Identical imports are skipped, while changed source rows need explicit reconciliation. Malformed batches roll back. Confirm that the requests and source values you expected are present, and resolve any differences before relying on the new register for live diligence work.

  5. 5

    Run both, then switch

    Keep DealRoom available while you use the new register alongside it for a short period. Check that your team can find the requests it needs and follow its review process, and confirm that any files or collaboration activities you still need have a separate plan. Once you are satisfied with the move and agreed migration scope, switch off DealRoom.

construction

Where the real effort goes

The real work is usually mapping your own field names and review rules, then deciding which history to bring. Requests are supported, but files, comments, permissions and historical approvals need separate migration work. If you have Enterprise DNA run the system, they handle the mapping and migration scope with you before switching.

Not ready for a call?

Get your DealRoom switch plan by email

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

Choose who sets it up and keeps it running

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo with Claude Code, Codex, OpenCode or Cursor
  3. 3 Ask for /request-chase, /review-queue and /closing-readiness
  4. 4 Save your DealRoom request export as CSV, map its headings and run import dealroom --dry-run
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your workstreams, evidence requirements and signing rules
  • check Your DealRoom exports mapped and reconciled
  • check A web front end and controlled file sharing for the people who need them
  • check A different technical foundation where your business needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated inside Omni by Enterprise DNA
  • check Connected to the business records you agree to include
  • check Access controls, document storage and backups scoped for your team
  • check Weekly decision packs and ongoing changes covered by the agreed service
Book a call

Questions

Instead of DealRoom, answered

Does this replace the whole DealRoom platform? expand_more

The free base covers the diligence request register, evidence review, findings and integration actions. DealRoom also provides hosted document sharing and collaboration. Enterprise DNA scopes your shared workspace, controlled storage and adviser access into the installed version before you move those activities.

Can we bring our existing requests and evidence across? expand_more

DealRoom documents Excel exports for request reports. Save a request-level report as CSV and check the headings against the import mapping. The free base imports request records and preserves source values. Files, comments, permissions and historical approvals need separate migration work. We reconcile the agreed scope with you before switching.

What happens when somebody marks a request complete? expand_more

Imported completion labels remain source history. A local request needs a response and evidence before another person reviews it. Internal signoff requires all requests approved and no unresolved high or critical findings. Your team still makes the acquisition decision and obtains the required professional advice.

Can we trust the privacy checks? expand_more

The checks flag missing purpose, access-review and retention-review records, with links to New Zealand privacy principles. Your team sets the review dates. These reminders do not certify compliance or enforce permissions on the original documents. We design those controls as part of your installed version.

What do we pay Enterprise DNA, and who owns the result? expand_more

You own the database and the customised system. The free base has no licence fee, while hosting and agent usage are your costs. We agree one setup fee, then a retainer for the ongoing work and operation you choose. DealRoom has its own reporting too; the difference here is that you can change the records and workflow you own.

Bring the acquisition you are working on

Book 30 minutes with Sam. Bring your DealRoom renewal and a sample request list. We will agree what moves across, how evidence gets reviewed and what your team needs for the first handover.

Book a call Get the free version

Due Diligence for Claude Code is free and open source, published by Enterprise DNA.

Done paying for DealRoom?

Get your version built