Skip to content

Technical due diligence: what you run, what each option costs, what to do first.

For companies in Europe, or entering it, about to commit a budget: a migration, a build, an acquisition. A fixed price of 2000 € to 3000 €, credited if work follows. The report is yours.

Book the assessment2 to 5 days, fixed priceNot ready to pay yet? The free twelve-question test

What is technical due diligence?

A short, paid assessment of the systems behind a decision you are about to make: what actually exists, where the technical, organizational and schedule risks sit, and what each option costs, doing nothing included. Some firms call it technology due diligence; the work is the same.

Two situations call for it. A decision you are about to make (modernize a system, migrate a platform, launch a build, take over a project that went wrong), where you need the ground truth before committing a budget. And an acquisition, where the posture is adversarial, the clock is short and the seller rarely opens everything: we prioritize what moves valuation and write down what we could not verify. A declared blind spot is worth more than a false certainty.

Same discipline in both: compare the system as described with the system as it actually is. For a target with European customers, that comparison includes where the personal data really runs and under which contracts. Not ready to pay for it? The free twelve-question test tells you whether this conversation is worth having.

Your report, section by section, and what you do with it.

Ten to fifteen pages and a half-hour readout, with editable sources. Usable by the vendor of your choice.

The five sections of the technical due diligence report, their content and their use
The five sections of the technical due diligence report, their content and their useWhat it containsWhat you do with it
Your systems and how they connectThe systems, the tools, the flows between them and who holds each oneSee the whole estate on one page, often for the first time
Risks, sorted by kindExposure sorted into technical, organizational and schedule riskKnow which risk to treat first, and which can wait
Costed options, doing nothing includedSeveral options with their cost, including leaving things as they areDecide on written numbers instead of instinct
An action plan, in orderStages in order, with what each one depends onBrief any vendor, us or another, on the same basis
The skills each stage needsWhat each stage needs: in-house, hired, or boughtBudget the people, not only the software

The one price we publish.

2000 € to 3000 €excluding VAT, fixed, credited in full if the work continues

Duration
2 to 5 days, with three to five of your people in sessions of thirty to forty-five minutes.
Deliverable
The report and its editable sources belong to you, whatever you decide next.
Credit
If an engagement follows, the fee is deducted from it in full.
Conclusion
It can say the project should not go ahead, or that the right vendor for the next stage is not us. It says so.
End
The assessment ends at the readout. A question a month later is a new piece of work.

How the days run, and what you have at the end of each.

  1. 20 minutes

    The decision and the scope, agreed.

    One call to name the decision you are trying to make. If a shorter conversation answers it, we tell you so.

  2. Interviews

    Your people heard, the real system seen.

    The sponsor, one or two operators, whoever runs the technology. We look at what runs, not at what the documentation claims.

  3. Analysis

    Options costed, risks sorted.

    Scenarios with their cost, doing nothing included, and the plan in order.

  4. Readout

    A report you can hand to anyone.

    Half an hour to walk through it, then the document and its sources are yours.

A pencil resting on a hand-drawn plan (illustration photo)

What the assessment will not do for you, stated up front.

A few days is enough to scope or enough to build, never both. Better to say it before you pay.

If the assessment shows you should not do the project, the report says so.

  • No code, no proof of concept.That is separate work, after the assessment, and only if it makes sense at all.
  • No disguised sales call.If the right vendor for the next stage is not us, the report says that too.
  • No open-ended follow-up.The assessment builds nothing: it produces a document that reads without us.

1 persontrained internally to change the business rules without us

Anonymized composite of several engagements, 2023 to 2025, case studies page

Industrial company, 15 to 30 people (anonymized composite)

One spreadsheet ran the company. Now a tool does.

The problem
Quotes, stock and scheduling in one file that one person understood, and a customer tool and an accounting system that did not talk to it. The same data was entered three times.
What was delivered
A connected tool in place of the spreadsheet, the customer and accounting systems wired together through their APIs, the history rebuilt during migration with a two-pass quality check.
Read the case studies

Who looks at your systems, and who writes your report.

The assessment is led and written by Laurent Tulpan, who started inside the IT departments of media, telecoms and banking companies, with Clairmont on infrastructure and integrations. A few days are enough because we look at what runs, not at what the documentation says.

Laurent Tulpan, in more detail
  • Laurent Tulpan, founder of Coeur du WebLaurent, founder and CTORuns the interviews, sets the priorities, writes the report and presents it.
  • Clairmont, technical leadClairmont, technical leadReads the infrastructure and the integrations, and what would not survive a rise in load.

Price, people, conclusions: before you book the assessment.

How much does technical due diligence cost?

2000 € to 3000 € excluding VAT (value-added tax), fixed before we start, for 2 to 5 days of work. The fee is credited in full against the engagement if you continue with us.

It is the only price we publish, because it is the only piece of work whose scope is the same from one company to the next.

What exactly is in the deliverable?

Four things you can act on:

  • A map of the systems and how they connect, often the first time anyone has seen it laid out.
  • A risk list separating technical, organizational and schedule exposure.
  • Several costed scenarios, including the scenario of doing nothing.
  • A sequenced action plan naming the skills each stage needs.

It ships with editable sources so you can reuse it.

Why is the assessment paid when others offer a free audit?

Because a free audit gets rushed, flatters, and steers toward whatever suits the person offering it.

A paid one buys the time to understand, and it buys conclusions that do not serve the vendor, including the conclusion that the project should not go ahead.

The fee is credited against the engagement if you continue, which makes it an entry point rather than a toll.

Who needs to be available during the assessment?

Three to five people, in sessions of thirty to forty-five minutes:

  • The sponsor, for the business stakes and the constraints.
  • One or two operators, to hear what the tools actually do to their day and what workarounds exist.
  • Whoever currently runs the technology, internal or external, for the real architecture.
  • If the subject calls for it, a business reference for the rules nobody has written down.
Can the assessment conclude that we should not proceed?

Yes, and it happens. The exercise compares the system as described with the system as it actually is, and the gap between the two is usually more informative than either on its own.

Sometimes it shows the problem is organizational rather than technical, or that the intended timeline cannot hold. A negative conclusion written down plainly saves far more than the assessment costs.

When is technical due diligence not worth it?

When the decision is already made and what you need is someone to build;
when the question fits in one call, which we answer in 20 minutes at no charge;
and when nobody on your side will carry the plan afterwards, in which case that missing function is the first problem to solve.

And once you know what to build?

The plan is yours to hand to anyone. If you want us to carry it out, the same people build it.

Build and automate

Software, automations and AI hosted in the EU, sources in your name.

Closer to your case

All services

Name the decision you are trying to make.

20 minutes to agree on the decision at stake and the scope of the assessment. If a shorter conversation is enough to answer your question, we will tell you that instead.

Book the assessment

2 to 5 days, fixed price