Technical due diligence for private equity
Technical due diligence for private equity deals
Know what you are buying before you sign. We review the software, infrastructure and engineering team of a company you plan to buy, and tell you in writing what will break after close and what fixing it will cost.

- Time
- 5 business days
- Fee
- $15,000 fixed
- Output
- A written report
- Credit
- Counts in full toward a bigger engagement
Why it matters
In most mid-market deals the software is part of what you pay for
It is also a risk you take on. A good demo and a tidy pitch deck say very little about how the platform will cope with the growth in your model.
The problems are expensive and easy to miss. We regularly see re-platforming that nobody budgeted for, security gaps that surface a few months after close, and systems that only one engineer understands. Technical debt can also lower the multiple you get at exit. None of this shows up in an architecture diagram supplied by the seller.
A checklist report full of green ticks will not catch it. You need someone to read the code, rank the problems by severity and put a cost on each one, so the risk is in the price before exclusivity runs out.

When sponsors call us
When to bring us in
How deep we go depends on where the deal is and how much time you have.
Before the LOI. A quick check before you commit, so you know about the technical risk before exclusivity starts.
48 to 72 hours
Between LOI and close. A full review of the code and the team, sized to the investment thesis and your timeline.
5 business days
Just after you buy. A baseline on the platform you now own, with the fixes in order and the cost of each.
Scoped to the platform
Add-ons and roll-ups. A check of how the targets' systems will fit together, so the savings in your model are realistic.
7 to 10 business days
What we review
What we review
Architecture and code
The real state of the platform behind the demo, and how much of the roadmap it can support as built.
Security and data
Access rights, stored secrets, third-party risk, compliance and the data model the business depends on.
Scalability and cost
Whether the platform can handle the growth in your investment case, and what running it will cost during the hold.
The team and delivery
Who the business depends on, how fast the team ships, and whether the roadmap in the deal materials is realistic.
A cost on every finding
Each serious finding gets a severity rating and a cost estimate, so the numbers in your model rest on evidence.
How the five days run
From data room to committee in five days
- 1
Kickoff and data room
We agree the thesis and the risks that matter for this deal, and get access to the code, the cloud accounts and the documentation.
Day 1
- 2
Technical review
We assess the code, architecture, security and infrastructure against what we have seen in hundreds of earlier deals.
Days 2 to 3
- 3
Team interviews
We talk to the engineering leaders about the roadmap, how fast they ship and who the business depends on.
Day 4
- 4
The written report
You get the findings, their severity and the cost of fixing them, ready for the investment committee.
Day 5
The written report
What the report contains
The operating team then uses the same report for the first 100 days.
| Section | What it tells the deal team |
|---|---|
| The verdict | Go ahead, go ahead with conditions, or walk away, with the three main reasons on one page |
| Findings by consequence | Each finding marked for the price, the deal structure (escrow, indemnity, closing conditions), the 100-day plan or the file |
| Severity and cost | A severity rating and a cost range for every serious finding |
| Key people | Who holds knowledge the business cannot lose, and how to keep them |
| Scalability against the model | Whether the platform can support the growth in the investment case, and what that will cost |
| The first 100 days | The technology part of the value creation plan, with owners, dates and costs |
Client notes
What clients say about working with us
“Mario bracketed the issues really quickly and then gave me project suggestions that I could understand.”
Paul MacMartinTechnical Writer, 25+ years of experience
“Mario is highly knowledgeable and has supported us in the growth of our business at two key junctures, giving us sound advice and guidance both times.”
James AshfordFounder of GoProposal & OverSuite
Red flags
Red flags to price into the deal
Most problems we find go into the 100-day plan. A few belong in the price or the deal structure, and those are why it pays to do this before you sign. You can tick the ones you have already seen. The ticks are saved in your browser only.
Timeline and fee
Timeline and fees
| Scope | Timeline | Fee |
|---|---|---|
| Pre-LOI technical check | 48 to 72 hours | $5,000, credited in full against the 5-day review |
| Single company with $1M to $20M EBITDA and one main platform | 5 business days | $15,000 fixed |
| Roll-ups, companies with several products, or several regulated markets | 7 to 10 business days | $25,000 to $40,000 |
The request list
What we ask the target for
We send this on the first day. Mario’s technical due diligence checklist for mid-market acquisitions lists the questions behind each item and which deal decision each one affects.
- To
- Management of the target
- From
- Growth Shuttle
- Re
- Technical due diligence information request
- 01Read access to the code repositories and the deployment pipeline.
- 02Read access to the cloud accounts, or 12 months of hosting bills and an architecture diagram.
- 03The last penetration test and the status of each finding.
- 04An org chart for engineering and product, with tenure and contractor status.
- 05The product roadmap and the delivery history against the previous one.
- 06Exports or screenshots of the CRM and billing configuration, and the KPI definitions used in reporting.
- 07Two hours with the CTO or head of engineering, and one hour each with two senior engineers.
How the review works
A review at the level of the code
Whether a review is useful depends on how deep it goes. Growth Shuttle assesses the code, the architecture and the infrastructure, and talks to the target's engineers instead of sending them a questionnaire.
Each finding is written up in the terms a sponsor uses, meaning its effect on the thesis, its cost and its effect on the exit. We judge severity against hundreds of earlier assessments, so every red flag has evidence behind it.
Our founder, Mario Peshev, has been on both sides of this kind of review, as a buyer and as a founder who sold.

Advice only
Hiring us never commits you to a build
Growth Shuttle advises and DevriX builds. They are separate companies on purpose.
If an adviser also sells the implementation, you can never be sure the advice is about you. Our only job is to get the answer right. You can hire us alone, DevriX alone, or both.

Our founder
Led by Mario Peshev
Mario Peshev is a value creation advisor to private equity firms and an active operator. He has founded six companies, exited two, acquired and integrated more than 40 businesses and digital properties, and advised over 500 companies since 2010.
He also founded DevriX, which builds technology, data and revenue systems, and he invests in early-stage startups. He has spent twenty years running engineering teams and the companies around them. His weekly briefing goes to more than 29,000 operators and investors.
Mario Peshev
- Advising since
- 2010
- Companies advised
- 500+
- Acquired and integrated
- 40+ businesses and properties
- Build firm, separate
- DevriX, which builds technology, data and revenue systems
- Advisory and training
- VMware · SAP · CERN · Saudi Aramco
- Coverage
- Forbes · BBC · Inc · Entrepreneur
Questions
Common questions
If your question is not here, send it through the contact form and we will reply in writing.
What exactly do I get?
A written report you can put in front of your investment committee, with the findings, how serious each one is and what it costs to fix. It is based on our own review of the code, not on a questionnaire the target filled in.
How long does it take?
Five business days for the standard review. A pre-LOI check is faster. A larger platform can take longer, and we agree the scope and price before we start.
How much is it?
The 5-Day Tech DD costs $15,000. We quote larger reviews based on the deal. The fee counts in full toward a bigger engagement if the deal goes ahead.
Who does the work?
The review is led by Mario Peshev, who reads code, has run acquisitions and has founded and sold companies.
Do you build the fixes afterwards?
Only if you want us to. DevriX, a separate company, would do that work. Hiring us for the review does not commit you to anything else.
What if we walk away from the deal?
Then you have spent $15,000 to avoid a much more expensive mistake. Walking away is a good result when the review gives you a reason to.
Is technical due diligence the same as IT due diligence?
In M&A the two names are often used for the same work. Our technical due diligence covers the code, architecture, infrastructure, security and the engineering team. That is wider than a review of IT systems alone.
What size deals do you work on?
PE-backed and mid-market companies, from lower mid-market platforms to larger assets. We adjust the scope to the deal.
Do you need access to the source code?
For a full review, yes. A pre-LOI check works from management calls, the product and its documentation, and tells you what the full review needs to confirm.
Is technical due diligence useful on the sell side?
Yes. If you run it 12 to 18 months before a sale, you find the problems a buyer would find while there is still time to fix them or disclose them yourself.
What happens after the report?
The items for the first 100 days become the technology part of your value creation plan. Growth Shuttle can stay on as a fractional CTO to run them.