And whether the story still matches every quarter after.
Zamski conducts technical due diligence from the target company's operating history, not the snapshot assembled in a data room. Code, messages, tickets, calendars, AI sessions. Zamski reads what the company created without knowing anyone would one day examine it.
Separately, they are noise. Read together, they become a record.
Six engineers, 129 merged changes in a month, a demo that closes rooms. 16% of capacity touches the product customers pay for. An F that photographs like an A.
Facts sealed 2026-07-06 · window 2026-06-08 to 07-05 · every figure resolves to a record. GIT fct_m1a204CRM fct_m1e05bGIT fct_m1f930
Negative space. ticketing and runtime telemetry not connected. The questions this grade cannot answer are stated on the card, with who can. An honest gap beats a confident guess.
Sample report card on a synthetic demonstration. The grade is computed, not judged. How the grade is computed · See more specimens →
Findings arrive while price and terms can still move.
Start a pre-close reportDPA day one. Read-only. Delete after 30 days, or sooner if you ask.
Why now
AI drafts the model, polishes the CIM, prepares the CTO, and reads the data room. Diligence materials agree with each other because the same tools wrote them all.
Missing operating evidence is not a gap. It is a finding.
Negative space. What we could not see, stated rather than filled.
From the Commit Up
Talent
Cross-tool cohort calendar-density drop before the retention risk crystallizes. Team-level bands, never individual signals. Surfaced in the brief.
Read on the Commit Up →AI spend
Total spend climbed three quarters in a row. License count rose. Throughput per engineer flat. The brief surfaces the cohort lines the CFO pack actually needs.
Read on the Commit Up →Governance
Three of them. Cited. Mapped to the strategic priorities they quietly displaced. Independent of the management narrative.
Read on the Commit Up →DEAL PARTNER
The deck says the team ships. Diligence gets two weeks and a data room. The report reads the target's operating record before the wire and every week after it.
Term sheet diligence. IC memo. Reps and warranty defense. Post-close day one.
OPERATING PARTNER
You inherit the target after close. The plan assumes engineering delivers three initiatives on the CIM's schedule. The report tells you which two are actually moving and which one needs an intervention this week.
First hundred days. QBR with the CEO. Milestone review. Bolt-on scoping.
FUND CFO
LPs ask what the engineering line is worth. The mark relies on the story management tells and the number management projects. The report gives you both, cited to the operating record on every portfolio company.
LP letter. Fair value marks. Fund review. Exit preparation.
01 · Provenance
A data room is assembled for the deal. The operating record accumulated for years before anyone knew it would be examined. Nobody prepared it for you, which is exactly why you can trust it.
02 · Substrate
Code, messages, tickets, calendars, AI sessions, identity-resolved into one record. A survey asks people to describe the work. The record is the work.
03 · Two artifacts
Deal teams and evaluators buy the R&D GRADE, a sealed diligence read on a target. Operators who install Zamski on their own org get the Monday Brief. Same record, two readers.
Three mock companies, three deal moments. Open one to read the full sealed report the deal team, the fund operating team, or the underwriter would receive. All numbers illustrative; none of these are real companies.
Founder-written. No sales pitch. Unsubscribe in one click.
One sealed report, from a target's operating record or from your own. Real data. One page. Delete after 30 days, or sooner if you ask.
Start a pre-close reportRunning your own org? Start a 30-Day Finding.
DPA day one. Read-only. Delete after 30 days, or sooner if you ask.