Logo
Resources · Technical Due Diligence
For Founders Preparing for Exit · 25–40 min Self-Audit

The complete checklist acquirers actually use.

52 items. 8 sections. The same diagnostic V2STech ran before three SaaS exits — QFix → Pinelabs (unicorn), Carebeans → QCS, Fissara → McAuliffe. Now built into a live tool you can score in real time.

No email required to startAuto-saves your progressFree PDF gap report
Pre-Acquisition TDD Audit
52-Point Checklist
Codebase under version control with branching strategy
Commits attributed to real people with real history
Code review process documented and enforced before merge
CI/CD pipeline blocks deploys on test failures
Third-party penetration test in last 12 months
Documented incident response plan, tested
Items Checked28/52
What's covered

Eight sections. Mapped to how acquirers actually inspect.

The 52 items are organized exactly the way a real technical due diligence team works through a target company over 14–21 days. Each section answers a specific buyer concern.

01

Code Quality & Architecture Fundamentals

8 ITEMS
02

System Architecture & Scalability

7 ITEMS
03

Security & Compliance Posture

8 ITEMS
04

Data Governance & Privacy

6 ITEMS
05

Documentation & Knowledge Transfer

6 ITEMS
06

Team Continuity & Key Person Risk

5 ITEMS
07

Operations, DevOps & Production Health

7 ITEMS
08

IP, Legal & Contractual Cleanliness

5 ITEMS
How items are weighted

Not all 52 items carry equal risk.

🔥

Deal-Killers

Failure here typically ends the conversation. Address before any buyer outreach.

19 items
⚠️

Valuation Discounts

Buyers don't walk, but they re-price. Typically 5–15% off valuation per major issue.

23 items
✓

Hygiene Items

Won't kill a deal alone, but multiple gaps signal an immature engineering org.

10 items
Ready when you are

Score yourself against the same framework acquirers use.

25 minutes if you're focused. Up to 40 if you stop to think. Auto-saves as you go — pick it up later if you need to.

No credit cardNo email to startFree PDF gap report at the end
V2STech
0 of 52 checked
Exit

Check what's true today.

Be honest. If you're between yes and no, leave it unchecked — that's a gap to investigate, not a free point. Your progress saves automatically as you go.

View
Click to toggle  Header collapses a section
✓ Section Complete!
01
Code Quality & Architecture Fundamentals
0 / 8
Acquirer's Question“Will their team be able to ship on this codebase?”
🔥
Is your codebase under version control with a clear branching strategy (e.g., trunk-based, GitFlow)?
About 1 in 8 SaaS companies have one repo with no branching strategy — and that signals chaos to acquirers.
#01
🔥
Are commits attributed to real people with real history (not bulk migrations or anonymous bots)?
Acquirers do a git log on day one. They want to see authorship that matches your team.
#02
⚠️
Is your codebase free of TODO comments older than 6 months without resolution?
Stale TODOs signal accumulated tech debt that nobody owns. Buyers count them — literally.
#03
⚠️
Do you have a documented and enforced code review process before merge?
Required: PR templates, mandatory reviewers, no direct-to-main pushes.
#04
✓
Are linting and code style enforced automatically (e.g., ESLint, Prettier, Black)?
Inconsistent style isn't a deal-killer but adds friction to onboarding cost estimates.
#05
⚠️
Is your test coverage above 50% on business-critical paths (auth, billing, core workflow)?
Below 50% on critical paths is the threshold where buyers start questioning whether they can ship safely.
#06
🔥
Do you have a CI/CD pipeline that blocks deploys on test failures?
Manual deploys are a deal-killer for buyers planning fast integration.
#07
✓
Is your build reproducible from a clean checkout in under 30 minutes?
If it takes more than half a day to get the codebase running locally, the onboarding cost spirals.
#08
All 8 items complete in Code Quality & Architecture Fundamentals — well done.
✓ Section Complete!
02
System Architecture & Scalability
0 / 7
Acquirer's Question“Can this scale into our infrastructure?”
🔥
Can you produce an up-to-date architecture diagram showing services, data flows, and external dependencies?
If you can't draw it, you don't really know what you have. Acquirers ask for this on day 2.
#09
⚠️
Are services or modules independently deployable, or does every change require a full system deploy?
Tightly coupled deploys are an integration risk multiplier visible on the deploy timeline.
#10
⚠️
Do you have clearly defined API boundaries between major components, with versioning?
API versioning shows you've thought about backwards compatibility.
#11
✓
Is your application stateless where possible, with state externalized to dedicated stores?
Stateless apps scale horizontally. Stateful apps don't. Buyers planning to scale care.
#12
⚠️
Have you load-tested your critical paths to at least 2x your current peak traffic?
Buyers want evidence the system survives growth. Show them the test reports.
#13
✓
Do you use managed services for infrastructure where reasonable (database, queue, cache)?
Self-managed infrastructure adds operational debt the buyer inherits.
#14
🔥
Are you free of hardcoded credentials, IPs, or environment-specific values in production code?
Hardcoded secrets are an immediate red flag. Use a secrets manager.
#15
All 7 items complete in System Architecture & Scalability — well done.
✓ Section Complete!
03
Security & Compliance Posture
0 / 8
Acquirer's Question“Are we inheriting a security incident?”
🔥
Have you completed a third-party penetration test in the last 12 months?
Self-attestation isn't enough. Buyers want a real third-party report from a recognized firm.
#16
🔥
Do you have a documented incident response plan, with at least one tested run-through?
Untested plans don't count. Show evidence of a tabletop exercise or real incident review.
#17
⚠️
Are you SOC 2 Type II certified, or actively in the audit window?
Below $5M ARR you can sometimes get away without SOC 2. Above that, it's table stakes.
#18
🔥
Are all production credentials stored in a dedicated secrets manager (AWS Secrets Manager, Vault, etc.)?
Credentials in code or shared docs = automatic deal-killer.
#19
⚠️
Do you enforce MFA on all production access, including third-party tools?
MFA gaps are findable and embarrassing. Audit your tool stack.
#20
⚠️
Do you have role-based access control (RBAC) on production systems, with regular access reviews?
Stale access (former employees still in systems) is a major red flag.
#21
✓
Are dependencies regularly scanned for known vulnerabilities (Snyk, Dependabot, etc.)?
Old, vulnerable dependencies surface in due diligence scans within hours.
#22
🔥
Do you have evidence of compliance with applicable regulations (GDPR, HIPAA, PCI, etc.) for your market?
Regulatory compliance is a yes/no gate. There's no 'working on it' credit.
#23
All 8 items complete in Security & Compliance Posture — well done.
✓ Section Complete!
04
Data Governance & Privacy
0 / 6
Acquirer's Question“Whose data is this and can we use it?”
🔥
Do your customer contracts grant you the right to retain and use customer data, including post-acquisition?
Some customer contracts terminate or require renegotiation on change-of-control.
#24
🔥
Do you know where your customer data is stored geographically, and is it compliant with each customer's jurisdiction?
Data residency is a compliance issue that buyers must inherit cleanly.
#25
⚠️
Is your database schema documented, with field-level descriptions for sensitive data?
Acquirers want to know what's PII, what's PHI, what's PCI before they touch the data.
#26
⚠️
Do you have a documented data retention and deletion policy, applied automatically?
GDPR right-to-erasure compliance is a yes/no question. Non-compliance kills enterprise deals.
#27
✓
Are backups encrypted, tested, and stored geographically separate from production?
Untested backups aren't backups. Buyers ask when you last restored from one.
#28
⚠️
Do you have audit logs for sensitive data access, retained for at least 12 months?
Required for most compliance frameworks, useful evidence in disputes.
#29
All 6 items complete in Data Governance & Privacy — well done.
✓ Section Complete!
05
Documentation & Knowledge Transfer
0 / 6
Acquirer's Question“Can we operate this without their team?”
🔥
Do you have current architecture documentation, updated within the last 90 days?
Architecture docs older than 90 days are usually wrong. Buyers know this.
#30
⚠️
Is your API documented (OpenAPI/Swagger), with examples and authentication flows?
Internal APIs included. The buyer's integration team needs this on day one.
#31
🔥
Are deployment procedures documented as runbooks (not as tribal knowledge)?
If only one person knows how to deploy, you have a key-person liability.
#32
⚠️
Do you have onboarding documentation that gets a new engineer productive in under 1 week?
Acquirers will ask: if you hired an engineer tomorrow, what would they read?
#33
⚠️
Are major architectural decisions captured in ADRs (Architecture Decision Records)?
Why did you choose Postgres over Mongo? ADRs answer this.
#34
✓
Is post-incident learning captured in postmortems with documented action items?
Postmortems show operational maturity. Buyers want a culture that learns from incidents.
#35
All 6 items complete in Documentation & Knowledge Transfer — well done.
✓ Section Complete!
06
Team Continuity & Key Person Risk
0 / 5
Acquirer's Question“What happens if the founders leave?”
🔥
If your CTO disappeared for 30 days, would the system continue to operate normally?
Test this honestly. If the answer is no, you have a key-person liability that costs valuation.
#36
🔥
Is critical knowledge documented or distributed across at least 2 engineers per major system?
Bus factor of 1 = walking away from the deal. Bus factor of 3+ = healthy.
#37
⚠️
Do you have written employment agreements with all key engineers, including IP assignment?
Verbal agreements aren't enforceable. Get IP assignment in writing for everyone who's touched the code.
#38
⚠️
Are key engineering roles backed up with named succession candidates (internal or recruitable)?
Acquirers want to know what happens if the engineering lead leaves.
#39
✓
Do you have non-compete or non-solicitation agreements appropriate to your jurisdiction?
Limited in some US states; standard in most other jurisdictions.
#40
All 5 items complete in Team Continuity & Key Person Risk — well done.
✓ Section Complete!
07
Operations, DevOps & Production Health
0 / 7
Acquirer's Question“Will it stay up after we own it?”
⚠️
Do you have application monitoring with alerts tied to user impact (not just CPU/memory)?
Datadog, New Relic, Honeycomb, etc. Show buyers your dashboards.
#41
⚠️
Do you have logs centralized and searchable, retained for at least 30 days?
Distributed logs across servers = operational debt. Centralize them.
#42
🔥
Do you have an SLA or uptime commitment with customers, and do you measure against it?
Enterprise customers will have SLA in their contracts. Buyers want to see your real uptime numbers.
#43
⚠️
Do you have an on-call rotation with documented escalation procedures?
On-call by the founder = unsustainable. Show a real rotation.
#44
✓
Is your infrastructure provisioned via code (Terraform, Pulumi, CloudFormation)?
Click-ops infrastructure is impossible to inherit cleanly. IaC is the standard.
#45
✓
Do you have automated database backups with documented restore procedures, tested in the last 6 months?
Backups untested are not backups. Restore once a quarter, document it.
#46
⚠️
Do you have disaster recovery procedures documented and tested?
What happens if your primary region goes down? Show the buyer your DR plan.
#47
All 7 items complete in Operations, DevOps & Production Health — well done.
✓ Section Complete!
08
IP, Legal & Contractual Cleanliness
0 / 5
Acquirer's Question“Is this actually theirs to sell?”
🔥
Do you have signed IP assignment from every developer who has ever contributed to the codebase?
Including former employees, contractors, freelancers, interns. No exceptions.
#48
🔥
Are you free of code dependencies on copyleft licenses (GPL, AGPL) that would compromise your IP?
Run a license audit (FOSSA, Snyk License). Copyleft contamination kills deals instantly.
#49
🔥
Do you have signed contracts with all customers, including standard data, IP, and limitation-of-liability terms?
Verbal customer agreements or unsigned MSAs are deal-killers.
#50
⚠️
Are your trademarks registered in jurisdictions where you operate?
Unregistered trademarks weaken the buyer's brand portfolio acquisition.
#51
⚠️
Are you free of pending litigation, IP disputes, or regulatory investigations?
Disclose everything. Hidden litigation discovered post-LOI ends deals.
#52
All 5 items complete in IP, Legal & Contractual Cleanliness — well done.
Your TDD Checklist Results

You have significant gaps to close.

You've made some progress, but if a serious acquirer started technical due diligence tomorrow, the conversation wouldn't get past the first week. The good news: every gap on this list is fixable, and the sequence is clear — start with the deal-killers.

0/52
ITEMS CHECKED
BEGINNER
Tier
Beginner
Estimated Timeline to Acquisition-Ready
6–12 months
Top Recommended Move
Fix the deal-killers first
Your gap summary

What you're carrying into a buyer conversation.

19
🔥 Deal-Killer Gaps
Could end a deal entirely
23
⚠️ Discount Gaps
5–15% off valuation each
10
✓ Hygiene Gaps
Signals immature engineering
Where to focus

The gaps you need to close, ranked by impact.

🔥
Deal-Killers — Address before any buyer outreach
19 gaps
#01
Is your codebase under version control with a clear branching strategy (e.g., trunk-based, GitFlow)?
#02
Are commits attributed to real people with real history (not bulk migrations or anonymous bots)?
#07
Do you have a CI/CD pipeline that blocks deploys on test failures?
#09
Can you produce an up-to-date architecture diagram showing services, data flows, and external dependencies?
#15
Are you free of hardcoded credentials, IPs, or environment-specific values in production code?
#16
Have you completed a third-party penetration test in the last 12 months?
#17
Do you have a documented incident response plan, with at least one tested run-through?
#19
Are all production credentials stored in a dedicated secrets manager (AWS Secrets Manager, Vault, etc.)?
#23
Do you have evidence of compliance with applicable regulations (GDPR, HIPAA, PCI, etc.) for your market?
#24
Do your customer contracts grant you the right to retain and use customer data, including post-acquisition?
#25
Do you know where your customer data is stored geographically, and is it compliant with each customer's jurisdiction?
#30
Do you have current architecture documentation, updated within the last 90 days?
#32
Are deployment procedures documented as runbooks (not as tribal knowledge)?
#36
If your CTO disappeared for 30 days, would the system continue to operate normally?
#37
Is critical knowledge documented or distributed across at least 2 engineers per major system?
#43
Do you have an SLA or uptime commitment with customers, and do you measure against it?
#48
Do you have signed IP assignment from every developer who has ever contributed to the codebase?
#49
Are you free of code dependencies on copyleft licenses (GPL, AGPL) that would compromise your IP?
#50
Do you have signed contracts with all customers, including standard data, IP, and limitation-of-liability terms?
⚠️
Valuation Discounts — Each costs 5–15% on deal value
23 gaps
#03
Is your codebase free of TODO comments older than 6 months without resolution?
#04
Do you have a documented and enforced code review process before merge?
#06
Is your test coverage above 50% on business-critical paths (auth, billing, core workflow)?
#10
Are services or modules independently deployable, or does every change require a full system deploy?
#11
Do you have clearly defined API boundaries between major components, with versioning?
#13
Have you load-tested your critical paths to at least 2x your current peak traffic?
#18
Are you SOC 2 Type II certified, or actively in the audit window?
#20
Do you enforce MFA on all production access, including third-party tools?
#21
Do you have role-based access control (RBAC) on production systems, with regular access reviews?
#26
Is your database schema documented, with field-level descriptions for sensitive data?
#27
Do you have a documented data retention and deletion policy, applied automatically?
#29
Do you have audit logs for sensitive data access, retained for at least 12 months?
#31
Is your API documented (OpenAPI/Swagger), with examples and authentication flows?
#33
Do you have onboarding documentation that gets a new engineer productive in under 1 week?
#34
Are major architectural decisions captured in ADRs (Architecture Decision Records)?
#38
Do you have written employment agreements with all key engineers, including IP assignment?
#39
Are key engineering roles backed up with named succession candidates (internal or recruitable)?
#41
Do you have application monitoring with alerts tied to user impact (not just CPU/memory)?
#42
Do you have logs centralized and searchable, retained for at least 30 days?
#44
Do you have an on-call rotation with documented escalation procedures?
#47
Do you have disaster recovery procedures documented and tested?
#51
Are your trademarks registered in jurisdictions where you operate?
#52
Are you free of pending litigation, IP disputes, or regulatory investigations?
✓
Hygiene — Multiple gaps here signal immaturity
10 gaps
#05
Are linting and code style enforced automatically (e.g., ESLint, Prettier, Black)?
#08
Is your build reproducible from a clean checkout in under 30 minutes?
#12
Is your application stateless where possible, with state externalized to dedicated stores?
#14
Do you use managed services for infrastructure where reasonable (database, queue, cache)?
#22
Are dependencies regularly scanned for known vulnerabilities (Snyk, Dependabot, etc.)?
#28
Are backups encrypted, tested, and stored geographically separate from production?
#35
Is post-incident learning captured in postmortems with documented action items?
#40
Do you have non-compete or non-solicitation agreements appropriate to your jurisdiction?
#45
Is your infrastructure provisioned via code (Terraform, Pulumi, CloudFormation)?
#46
Do you have automated database backups with documented restore procedures, tested in the last 6 months?
Recommended next step

Built for where you are.

Recommended for Beginner Tier
MVP Clarity Sprint
$100
60–90 minute working session with a senior V2STech architect. We'll triage your top 5 gaps, give you a written 90-day plan, and tell you exactly which engineer or vendor to hire to close them.
Take this with you

Save your gap report.

Download a branded PDF of your full gap analysis, send a copy to your inbox, or share with your team.