RECON
Aug 25 to 26
Detection: 2,932 companies scanned for a signal that is an absence
- YC companies loaded
- 2,932
- Scored above zero, the deliverable
- 909
GTM engineering case studies
The map ends where this work starts.
Circuit racing runs on a map every driver shares. Rally runs on pace notes the driver wrote during recon. I build go-to-market systems for the second kind of market: buyers no enrichment tool can see, signals that only exist as an absence, and claims I will only publish once two independent sources agree.
Everything below is one continuous three-week build against a single audience, Stripe's startup partnerships pool over the YC company universe. 2,932 companies loaded. 909 scored. 12 emails sent, each signed with my real name. The failures are reported in the same voice as the wins, because catching a wrong number before it ships is worth more than the pipeline the wrong number would have produced.
Source: working sessionNumbers marked with a dot come from the working session and its published posts. Unmarked numbers are stated in the build artifacts on disk, with file and line.
One build, three stages, in the order it happened.
RECON
Aug 25 to 26
PACE NOTES
Aug 27
Segments need a clock to operate on
THE STAGE
Aug 30 to 31
Nothing audits a pipeline like having to sign your name to it
Every build in this arc contains the same shape of finding: a thing that did not happen presenting as a thing that did. A null read as a zero. An absence read as unset. A blind instrument read as a market signal. The work is telling those apart, and that part is mine rather than the tool's.