Concepts
GTM hypothesis
A GTM hypothesis is a written bet about a motion, not a vibe about a market. The sentence from the session:
We believe [this customer] has [this problem], will respond to [this message] through [this channel], and will take [this action] because [this proof].
Example as given: homeowners have a maintenance problem, will respond to insurance or discount messaging on Facebook, and will start a trial because 45% of the relevant Florida homeowners live in a named group and have already complained about the problem there.
Why it matters
Section titled “Why it matters”Without the because, you are renting someone else’s playbook.
From the room
Section titled “From the room”You need to have a very specific framework for deciding why you wanna do something, and it can’t be based on somebody else’s success.
Even the same category and the same software should not share a motion if you are trying to leave the sea of sameness. Depth, not “who is my target customer”: who feels the pain (often the user), who buys (CFO, procurement, department head), company stage and size, and the trigger that makes it now — hired fast, raised, lost a customer, missed a deadline, new exec, reorg, regulatory change. A tracker on LinkedIn company updates and financial releases is enough to start showing up on time.
This is not the XYZ hypothesis. XYZ is a demand test before you build: X% of market Y will pay $Z. The GTM hypothesis assumes you have something to sell and asks how a specific person will hear about it and act.
Where founders get it wrong
Section titled “Where founders get it wrong”- Copying an adjacent company’s channel.
- Stopping at a persona.
- A channel with no proof.
- Mixing this up with the pre-build demand test.
Go deeper
Section titled “Go deeper”- GTM as a system has the symptom checker that tells you which part of this sentence is wrong.
- Validate demand before you build is the XYZ test that should already have passed.
- Related concepts: Blue ocean, Buying committee, XYZ hypothesis.