Will it scale the way the deck says?
Find out before you commit.
Independent technical due diligence for VC, PE, family offices and corporate acquirers. We assess the technology, the team and the roadmap, and translate what we find into risk, cost and valuation impact your investment committee can act on.
Book an Intro Call View a Sample Report
Where are you in the deal?
First look at a target
A fast, structured screen of the core stack, architecture, security essentials and team.
→ Basic Tech DD · 5–7 business days
Term sheet on the table
Full assessment: code, AI claims, cloud & cost, DevOps maturity, roadmap validation.
→ Full Tech DD · 2–3 weeks
A specific question
AI real or wrapper? Security exposure? Codebase health? One question, answered thoroughly.
→ Tech Deep Dive
You've closed
Independent audit of what you bought + a 100-day technology roadmap for value creation.
→ Post-Acquisition Audit · 3–4 weeks
From kickoff to final report: under a month.
Most engagements complete in 2–3 weeks of active assessment, under a month start to finish when information flows on time. A Basic Tech DD moves faster still. Diligence shouldn't be the reason a deal slows down.
The timeline holds when the target responds on time, and if it slips, you hear it from us immediately, with the reason. Fast because the process is structured, not because corners are cut.
Twelve risks a Tech DD exposes, and protects against.
Every one of these has surfaced in our engagements. None of them appears in a P&L, and all of them surface after closing if nobody looks first. Click a card to see how the diligence catches it.
Messy Code
Hard to maintain, risky to change, slow to onboard into. Every feature costs more than it should, and velocity decays quarter by quarter.
Code walkthroughs and repository analysis size the debt in engineer months, so it is priced and planned instead of discovered after closing.
Legacy Technology
Aging stacks and frameworks engineers do not want to work on. Hiring drag, patches that stop coming, performance ceilings.
The assessment maps end-of-life components and the true cost of the oldest decision still in production.
Architecture at Its Limits
A platform that strains at today's load. Growth capital ends up funding firefighting and emergency rewrites instead of the roadmap.
We identify what fails first under 10x load and whether resilience is designed or merely assumed.
AI That Is More Pitch Than Product
A wrapper positioned as proprietary. The moat evaporates the first time a competitor gets the same API keys.
Models, training data rights, and evaluation evidence are tested against the claims in the deck, line by line.
Cowboy Releases
No review, no tests, no rollback. Every deploy is an experiment on customers, and one bad release can erase months of trust.
We reconstruct the path a change takes to production and what, if anything, stops a bad one.
Silent Security Exposure
Untested defenses and unmonitored access. One incident away from a headline, with the breach discovered by customers first.
We probe what a motivated attacker would find in a week, versus what the attestations claim.
High, Uncontrolled Tech Spend
Cloud costs nobody watches, growing faster than revenue. Often masking weak architecture or unoptimized code, compensated with more compute.
We rebuild the infrastructure unit economics and find which line item scales worse than revenue.
Knowledge That Lives in Heads
Undocumented systems and tribal knowledge. Onboarding drains senior engineers, and any departure erases capability.
We test whether a new senior engineer could ship safely in week two, using only what is written down.
Vendor Concentration
One provider's policy change can stop the product, or the roadmap. A terms-of-service page becomes an existential document.
We map the blast radius of every critical dependency and check whether the exits have ever been tested.
Key-Person Dependency
The product lives in one irreplaceable head. Continuity, delivery, and routine fixes hinge on a single person staying.
We probe who is irreplaceable, what survives their departure, and what the succession plan actually covers.
Roadmap Fiction
Promises never sized against the team that must build them. The slips surface after the capital is committed.
The forward plan is tested against six months of shipped-versus-promised history and the current bench.
IP the Company Does Not Own
Missing assignments, contractor code, unvetted open-source licenses. The chain of title breaks exactly at closing.
We trace ownership of the codebase, contributor by contributor, before the lawyers have to.
What your peers say
Your deal stays your deal. Full stop.
One rule, no exceptions: findings belong to whoever commissioned them. Everyone else, including the other side of the table, gets nothing. Not the report, not a summary, not confirmation we ever met.
No fund sees another fund's work
What we learn in your deal, your thesis, your target, our conclusions, is never available to another investor, fund or acquirer. Portfolio insight is not a shared resource.
A wall between every mandate
We may be assessing several deals at any time. Each engagement is sealed: need-to-know staffing, access-controlled files, and conclusions that are never recycled into anyone else's assessment.
The target doesn't see your read
The company we assess receives nothing from your engagement unless you choose to share it. And if they commissioned their own work with us, that file is equally invisible to you.
// NDA-FIRST · READ-ONLY ACCESS · NEED-TO-KNOW STAFFING · NO CONTACT OUTSIDE THE AGREED CIRCLE · GDPR-COMPLIANT BY DESIGN
Questions investors ask us
How long does a Tech DD take?
Most engagements complete in 2–3 weeks of active assessment, and under a month from kickoff to final report when information flows on time. A Basic Tech DD screen runs in about 5–7 business days.
What access do you need?
A read-only data room (architecture docs, security policies, key contracts), read-only repository access for code review, and a short list of engineers for deep-dive interviews. We work from what you can share and flag anything missing early.
How much of the target team's time is required?
Typically a few hours across the engagement — a kickoff, two or three focused technical sessions, and follow-up questions. The process is designed to minimise disruption to the founding and engineering team.
Do you work under our NDA or yours?
Either. We sign before anything else, NDA-first, and are comfortable working under your paper or ours. Findings belong solely to whoever commissioned the work.
What does it cost?
Fees are scoped to the depth of work and the size of the deal. A single-question Tech Deep Dive is a fixed fee; a Full Tech DD is scoped to the target. We give a firm quote before any work begins.
Can you start this week?
Often, yes. We hold capacity for live transactions — if you are mid-deal and on a clock, tell us and we prioritise accordingly.