Moonshot recon: pain log
Founder greenlit this on 2026-11-02 at 16:23 ET. The idea is to treat the phData seat as reconnaissance. From every deal or call, harvest three things:
- Pain: a problem that keeps coming up that nobody sells a fix for
- Buyer: the kind of person who would pay directly for the fix
- Builder: a person he would want to build it with
Boundary: record public-safe patterns only. No client names, no deal figures, no internal phData or partner detail, and nothing copied from client artifacts. Write the pattern ("mid-market insurer, claims team re-keys PDFs into Snowflake"), not the account. Builder entries are first names or roles. Reference a contact note only if the person is already in 03-contacts.
Intake: the founder voice-dumps or texts after a call (e.g. "pain: ..."). Ray strips identifying detail, appends a row and tags any repeat. A pain that shows up 3+ times gets promoted to the Repeats section.
Review: every quarter, check whether all three lists are filling up. If they stay thin after a year, the seat is "just helping others build." If they are full, the seat is customer discovery for the moonshot. See [[2026-11-02-platform-partner-ground-game-economics]] and [[project_ambition_bigger_problem_network]].
Repeats (3+ sightings)
none yet
Log
| Date | Pain (pattern) | Buyer (role/segment) | Builder | Sightings | Notes |
|---|
Related
- [[2026-11-02-platform-partner-ground-game-economics]]
- [[2026-09-29-nov30-credibility-targets]]