Builds · Side Quests
I design and build GTM systems that turn fragmented information into structured intelligence and workflows a person can use. The work joins enterprise sales, product thinking, and technical implementation, from competitive intelligence and customer feedback to security research, enablement, and account-based GTM.
Each project is a prototype, professional field system, design, or concept. The label is the implementation status, not a production claim.
Builder / Side Quests
Lifecycle stages are a second filter. A project can sit in more than one functional category. Revenue Intelligence is the Measure prototype. The other case studies still carry their own metrics. A hypothesis is not a measured outcome.
4 matching projects
Match partner account lists on domain, leave uncertain rows for a person, and show whitespace. Not deployed.
I designed this from channel work. The page shows one fictional match.
No product screenshot
This card links to the case study. It is not a running interface.
An editable planning year for a fictional company. Retention, expansion, and the new-ARR residual are formulas. The dollars are fixtures.
I built the planner in gtm-revenue-os. It is not embedded here, and it is not an employer plan.
No product screenshot
This card links to the case study. It is not a running interface.
Pipeline health from stage history, then planned new ARR against bookings and what is still required. The book is synthetic.
I wrote the SQL. Win rate comes from the close, not the current stage.
No product screenshot
This card links to the case study. It is not a running interface.
Territory coverage and AE capacity for the same fictional company. Potential is an estimate. Headcount does not create bookings.
I built the operating plan in gtm-revenue-os. The $25M view is capacity math, not a result.
No product screenshot
This card links to the case study. It is not a running interface.
From market intelligence to customer execution.
These projects cover different parts of the same motion. Selecting one shows its inputs and output. The lines are a map, not a data integration.
Dashed links are a conceptual map. These projects do not exchange data.
Ideas and operating models I am exploring next.
A scoring sheet for a short list of bets. Not designed past this note, and not software.
One segment, one message, and a readout of what to change. Not built.
A reviewed weekly note from a fixed list of public sources. The product is still an idea.