Interpret
Signals create hypotheses, not pitches
A signal is not a reason to pitch. It is a reason to form a hypothesis. Get this one distinction right and you will already sell better than most of the market.
Here is the mistake that defines mediocre enterprise selling. A seller spots a signal, a new CTO, a funding round, a regulatory change, and immediately turns it into a pitch: “I saw you appointed a new CTO, our platform would be perfect.” The signal was real. The leap was lazy. And the buyer can feel the difference.
From signal to hypothesis
A hypothesis is a testable belief about the customer’s world, held loosely until evidence confirms it. It does not assume you are the answer. It asks a better question. The same new CTO signal becomes: “A new CTO often means a technology review in the first two quarters. If that is happening here, they may be reassessing platforms and integration risk. That is worth testing before assuming anything about fit.”
Signals create hypotheses, not pitches. The pitch, if it is ever justified, is earned much later.
Meridian’s three Coastline signals didn’t become “you need a customer data platform.” They became a hypothesis in the buyer’s language: the member-experience programme depends on consolidating fragmented data, and the new CCO owns that outcome without yet owning the data. Same signals, but now a problem worth a conversation rather than a product worth deleting.
- Generate multiple hypotheses from a signal
- Argue for and against each one
- Suggest what would confirm or kill it
- Resist jumping to your solution
- Judge which hypotheses are plausible
- Prioritise by evidence and relevance
- Decide which to test, and how
- Hold them loosely
Framing decides everything here. A hypothesis framed around the customer’s risk or opportunity earns a conversation; the same insight framed as your product earns a delete. Loss aversion is relevant too: buyers move faster to protect against a credible threat than to chase an abstract gain. The interpretation you take forward should be framed in the buyer’s terms, not yours.
I once watched a competitor win an account we had researched better, because we led with our solution and they led with a hypothesis about the customer’s real problem. Same facts. They sounded like they understood the business. We sounded like we wanted a deal. They told me afterwards it was not close.
Monday morning: turning the weekend’s signals into a plan
Load the signals. Bring the three signals from your Stage S pass to the teammate. Ask for two or three hypotheses per signal, each framed as the customer’s problem or opportunity, not your product.
Stress test. For each hypothesis ask: what would make this true, what would make it false, and how confident are you? Kill the weak ones now.
Prioritise. Choose the one or two hypotheses worth building a conversation around. These become the spine of everything from here to discovery.
Bank it. Write the chosen hypotheses in the buyer’s language. You now have a reason to reach out that is about them, not you.
Example ladder: from the same signal
“You have a new CTO, so you need our platform. Can we book a demo?” Assumes the answer, ignores the buyer’s world, invites a no.
“New CTOs often review the tech stack. Thought it might be timely to connect.” Relevant, but vague, and still faintly about wanting a meeting.
“A leadership change in engineering often puts integration risk and platform consolidation on the agenda. If that is on your mind, I have seen how peers in your sector handled it, happy to share what worked and what did not.” Frames the buyer’s likely problem, offers value, earns the conversation.
The teammate can generate ten plausible hypotheses in seconds. It cannot know which one is true for this buyer, this quarter. That judgement is yours, and it only gets confirmed in discovery. Do not let a well-written hypothesis harden into a conviction before the customer has said a word. More on holding evidence honestly in The Validation Approach →
Build it: convert your signals
Return here once you have run Stage S on a real account. Take the strongest signal and turn it into a hypothesis in the buyer’s language.
Want every stage’s worksheet in one document?The complete field guide has all six build exercises, ready to print or fill in on screen, plus the full appendix of prompts.
Download the Field GuideYou’ve now formed a SIGNAL Leading Hypothesis. Next, that hypothesis needs credibility behind it, because a good idea delivered cold is still cold.