Grasp 路 Diligence
The Grasp Diligence Report
Acquiring a software company, auditing your own codebase, or losing a senior
engineer? The paid engagement goes far beyond the free scan.
What you receive, in five business days
- Two Grasp Scores, not one. The churn view (where risk is accumulating now) and
the windowless survivorship view (git-blame attribution of every surviving line: what fraction of
the asset you're buying or running has a living author).
- Dark-code inventory. Every module ranked by comprehension risk, with the specific
freeze-and-document candidates named.
- Key-person concentration table. Who holds what share of the living code; the
succession, retention-package, and offboarding picture.
- Full-coverage review forensics. Every attributable merge analyzed rather than sampled:
unreviewed merges, AI-only review, approval latency versus change size.
- The evidence bundle. Raw JSON behind every figure, so your analysts can independently
re-derive each number. That is what makes it diligence-grade rather than an opinion.
- A written findings memo. A plain-language executive summary at the front of the
report: what the scan found, what it means for your decision, and what I would do about it.
- 30 days of written Q&A. Questions answered in writing within two business days.
Everything is delivered in writing by policy, so every answer is precise, referenced to the
evidence bundle, and shareable with your deal team.
Access, your choice: grant read-only repo access and
I run it, or run the engine inside your own network and send back only the metadata bundle.
Code never crosses your wall, which is the usual path for M&A targets under NDA.
Fixed fees.
See a real sample diligence
report before you spend a dollar.