Know your R&D numbers before a buyer does.
For founders, boards and PE operating partners. A buyer's technical due diligence will measure your engineering cost, delivery and key-person risk, and test every AI claim in your materials. We measure it first, from your own systems, with scripts your team can re-run.
The questions a buyer's diligence will ask
| Buyer's question | What we measure | Source |
|---|---|---|
| Is engineering spend efficient? | R&D cost as % of revenue, split into keeping the lights on vs new product; capitalisable share | payroll, Jira |
| Is the AI real? | Each AI claim in your materials, checked against what runs in production | code, deck |
| Is delivery predictable? | Lead time, release frequency, change failure rate, planned vs delivered | Jira, Git, CI |
| Who is the company dependent on? | Bus factor per system, from how concentrated commits and reviews are | Git |
| How much debt are we buying? | Tech-debt hotspots: churn × complexity × incidents, with a € estimate | Git, incidents |
| Is there licence or security risk in the code? | Open-source licences in shipped code (copyleft flagged), known vulnerabilities by severity, how out of date dependencies are | code, SBOM |
| What does it cost to run? | Hosting and third-party costs as % of revenue and of gross margin, per product | cloud bills |
Timeline
Weeks 1–6
The baseline, €16,000. Every number above, with the scripts that produced it. Half when we start, half when the report and the scripts are handed over. You decide what to fix.
Months 2–9
Fix what matters, quoted per fix. Your leads make the changes, with us alongside. Improvements need two or more clean quarters to show in diligence.
6 months before
The re-run, included. Same scripts, same definitions. Your team hands the buyer's diligence firm a method it can reproduce.
How we work before a sale
Confidential. Inside your company it runs as a delivery review. Your leads don't need to know a sale is planned.
Reproducible or left out. If a number can't be reproduced from your own systems, it doesn't go in the report. Buyers check, and so do we.
If a number doesn't hold. For 6 months after the re-run, if the buyer's diligence firm can't reproduce a number from our baseline with our scripts on the snapshot you keep, we correct it within 10 working days at our cost.
The snapshot is yours. At the re-run we hand you the data snapshot and the scripts, signed for, so every number can be reproduced without us.
Messy Jira. Where tickets aren't tagged well, we classify work from Git and pull requests, and mark every estimated number as an estimate.
Accounting calls. Capitalisation and cost splits are your finance team's and auditors' decision. We give them engineering data they can trace to tickets and commits.
During diligence. When the buyer's diligence firm has questions about our baseline, we answer within 2 working days, billed by the day and written into the contract.
No key-person risk. Scripts and documents your team owns. Nothing depends on us after handover.
Contracts. NDA and DPA first, read-only access, removed at handover. Professional liability insurance on request. Security summary
A confidential call about your timeline.
A rough sale date is enough to start. On the call we'll tell you which of a buyer's questions your current data can already answer, and which it can't.