Product
Six modules. One decision loop.
Each module answers a question a deal team has to answer before signing — and hands its answer to the next step with the evidence attached.
Revenue and SaaS metrics
Pactlab rebuilds recurring revenue from invoice lines rather than from the data book, so every metric traces to the transactions behind it.
“Is the ARR in the deck the ARR in the ledger?”
Read more →- Revenue ledger. MRR and ARR rebuilt from billing records, with currency conversion at recorded rates.
- Retention. Gross and net revenue retention, expansion, contraction, churn and reactivation.
- Cohorts. Revenue and logo cohorts by start month, so a strong year cannot hide a weak vintage.
- Concentration. Share of revenue held by the largest customers, and how it has moved.
- Reconciliation. Management ARR set against billed ARR. A reviewer approves the difference, or it stays open.
- Explanations. Every figure shows its formula, time basis, inclusion rules and the source rows behind it.
Technology and code
Pactlab reads commit metadata and scan results, never keeps the source, and ties every technical finding to the exact commit and tool version that produced it.
“Who really built this, and what comes with it?”
Read more →- Commit provenance. Every finding resolves to a full commit hash, the tool that produced it and that tool’s version.
- Unattributed commits. Work by identities missing from the identity map, or committed after a recorded departure.
- Key-person concentration. Subsystems that depend on one contributor, reported as aggregates and never as a ranking of people.
- Licence exposure. Components and licences from a software bill of materials, checked against a licence policy.
- Scanner findings. Security and quality signals from isolated, short-lived scans.
- Source never kept. Scan workspaces are destroyed on success, failure, timeout or cancellation. Paths and hashes remain; code does not.
Delivery health
Pactlab reads sprints and issues from the delivery tracker and surfaces the trends a roadmap slide leaves out. It reads delivery facts only, not names, comments or descriptions.
“Can this team ship what the plan assumes?”
Read more →- Completion against commitment. Points committed and completed, sprint by sprint.
- Defect backlog. Open bugs by priority and age, and which way the backlog is moving.
- Reopened work. Fixes that came back — a signal estimates and burndown charts miss.
- Gaps, not guesses. Unestimated work, open-ended sprints and unreadable projects are reported, never filled in.
Documents and contracts
Pactlab extracts parties, dates and clauses from deal documents and answers questions about them. Every statement points to the exact passage it came from.
“What did they actually sign?”
Read more →- Exact citations. Each answer quotes the page it relies on. A claim whose quote cannot be found is rejected.
- Clause extraction. Change of control, assignment, termination, exclusivity and other terms, drafted for review.
- Injection-aware. Instructions hidden inside documents are treated as data. Answers that cite them are blocked.
- Secure uploads. Malware-scanned, tenant-scoped storage with retention classes and legal hold.
- AI exclusion. HR, compensation and performance documents are never sent to a model.
Findings and review
Analysts, scanners and models can draft findings. Only people decide them. Every decision is recorded with who made it and why.
“Which risks are real, and what are they worth?”
Read more →- Evidence links. A finding cannot be accepted until its evidence resolves to a source record.
- Priced risk. Price reductions, escrows, indemnities and remediation costs as decimal ranges with a stated basis.
- Human decisions. Submit, accept, reject or ask for support — each with a rationale and a named reviewer.
- Append-only history. Reviews and earlier evidence are never overwritten, so the decision trail stays complete.
Valuation and deal terms
Pactlab turns accepted risks into explicit adjustments and runs deterministic valuation scenarios. Change a risk and every scenario that depends on it is marked stale.
“What should we pay, and on what terms?”
Read more →- Methods. ARR multiples and discounted cash flow, with LBO returns for take-private deals.
- Sensitivities. Two-way tables on the inputs that move value most.
- Purchase-price bridge. From enterprise value to equity price: cash, debt, debt-like items, working capital and risk adjustments.
- Stale on change. Re-price or reject an accepted risk and dependent results are flagged until they are re-run.
- Frozen submissions. A submitted scenario is stored byte for byte with its digest and never rewritten.
- Four eyes. The person who submits a valuation cannot approve it.
Pilots with acquirers of software companies
We are working with a small number of design partners on live deals. If you buy or invest in software businesses, talk to us.