gtm system, seed-stage ai infrastructure (airtable) →
Read-only. Accounts and deals are labelled by segment rather than named, and the stages, tiers and dates are illustrative rather than the live engagement.
problem
The brief was a prospect list. A long list of generic AI companies would have been easy to produce and useless to work, because every name on it needs a specific buyer and a reason that company would care.
role
Freelance GTM contractor. Spec build.
did
First, who actually counts as a prospect. Technical teams from pre-seed to Series A, roughly 5 to 50 people, whose own knowledge is scattered across Slack, GitHub, docs, and old incidents, and who have recently done something that suggests they are about to feel it: raised, hired, or shipped.
Then thirty accounts instead of three hundred, split into four groups. Each group is a different guess about who the product is really for, which makes the outreach a test rather than a queue.
Then the Airtable underneath it. Opportunities for where a deal stands and what happens next, accounts for whether a company fits, leads for the individual buyer and how they were reached, owners for who is responsible. The rules say what has to be known about a company before anyone contacts it, and what gets written down after every conversation.
result
Delivered as a spec build. Because each of the four groups tests a different guess, the outreach comes back with something useful about the market whether or not it comes back with meetings.
- accounts selected
- 30
- groups tested
- 4
- airtable tables
- 4