A prospect loves your product. They said so on the call, they asked good questions, they even used the word “finally.” Then the deal goes quiet. No objection, no rejection, just silence. Three follow-ups later you’re not sure if you lost, or if you’re still in it.
The instinct is to blame the pitch, the price, or the timing. Often the real answer is simpler and less comfortable: you pitched the person who’ll use the product, and never built the case for the person who has to pay for it. They’re frequently not the same person, and founder-led B2B SaaS sales tends to optimise entirely for the one who’s easier to talk to.
Why this happens more in founder-led sales, not less
Founders assume role-mismatch is an enterprise problem, something that shows up once you’re selling six-figure contracts with procurement teams and multi-person buying committees. It isn’t. It shows up the moment your champion has anyone to answer to, which for most B2B SaaS companies is almost immediately.
Founder-led sales makes this worse in a specific way: founders are naturally drawn to the most engaged, most enthusiastic person in the room, usually whoever will actually use the product day to day. That person gives the best signal in the call. They ask the sharpest questions, they get visibly excited, they feel like the deal. So the founder optimises the whole pitch around them: the workflow pain, the daily friction, the “this will save you hours a week” story.
That story is often true and it’s rarely enough. The user’s pain justifies wanting the product. It doesn’t justify spending money on it, that’s a different question, answered by a different person, using a different set of criteria the founder never addressed because the most engaged person on the call wasn’t the one asking it.
The three roles hiding inside almost every deal
Most B2B SaaS deals, even small ones, involve some version of three roles. They can overlap in one person at the earliest stage, but treat them as genuinely separate questions:
The user. Feels the pain directly. Cares whether the product actually works, fits their existing workflow, and doesn’t create new friction. Their objection sounds like “this doesn’t do X” or “our current process is different.”
The buyer (economic buyer). Controls or approves the spend. Cares about cost relative to the status quo, what happens if they don’t buy, and whether this is the best use of a limited budget this quarter. Their objection rarely gets said out loud on your call; it happens internally, after you’ve left the room.
The blocker. Doesn’t have to say yes, but can say no. Often IT, security, finance, or simply a co-founder who wasn’t on the call and doesn’t share the enthusiasm. Their objection is usually about risk, not value: “why this vendor,” “what happens if it doesn’t work out,” “who else is using this.”
A deal that stalls silently after a strong first call has almost always been pitched to one of these three and never reached the other two in a form they’d actually respond to.
A three-question buyer map (run this before your third call)
You don’t need a formal buying-committee framework to catch this. Before any deal goes past a second conversation, answer three questions honestly, on paper, per deal:
- Who feels the pain right now, in their daily work? This is usually obvious, it’s whoever you’re already talking to.
- Whose budget does this come out of, and what do they need to see to approve it? If you don’t know, that’s the gap. Ask directly: “If we move forward, whose budget is this, and what would they want to see?” It feels presumptuous early on. It’s far cheaper than finding out three weeks into a stalled deal.
- Who could kill this even if they love the product? Often unnamed until late, this is the person whose silent “no” ends deals that otherwise looked closed. Ask your champion directly: “Is there anyone else who’d need to be comfortable with this before it moves forward?”
If your answer to questions 2 and 3 is “I don’t know” past a second call, that’s not a minor gap, it’s the most likely reason the deal is about to go quiet.
A composite example: selling to the rep instead of the manager
A pattern we’ve seen repeat across multiple founder-led sales teams, shown here as a single anonymised composite: a founder selling a sales-outbound tool kept closing enthusiastic first calls with individual sales reps. The reps loved it, the demos went well, trials had strong usage. Win rate on those trials was close to zero.
The product had been pitched entirely around the rep’s daily pain: manual list-building, tedious follow-up tracking, hours lost to admin. All true, and all irrelevant to the person who actually approved new tools, the sales manager, who wasn’t on any of the calls and had a completely different question: does this make the team more predictable and reportable, not does it save one rep time. The founder was closing the user every time and never reaching the buyer, because the buyer was never in the room and nobody had asked whose budget this came out of.
The fix wasn’t a better demo. It was retargeting the pitch itself: keep the individual-rep story for the user conversation, but build a separate, explicit business case, team-level visibility, forecast accuracy, ramp time for new reps, for the manager conversation, and get that person on a call before treating the deal as real. Trial usage stayed the same. Close rate didn’t, because the right person finally heard a case built for their actual job.
Common mistakes
Assuming the most enthusiastic person on the call is the decision-maker. Enthusiasm and budget authority are unrelated. The person most excited to talk to you is often the one with the least power to say yes.
Never asking who else needs to be comfortable. Founders avoid this question because it feels like inviting friction into a good conversation. It doesn’t invite the friction, it just reveals friction that already exists and was going to surface anyway, later and more expensively.
Running one pitch for every role. The user wants to hear about their daily workflow. The buyer wants a business case relative to the status quo cost. The same fifteen slides rarely serve both; the user’s excitement doesn’t automatically translate into the buyer’s approval unless someone builds that translation on purpose.
Treating “let me check with my manager” as a soft yes. It’s a signal the buyer conversation hasn’t happened yet, not a formality on the way to signing. Treat it as the start of the real sales process, not the end of it.
Giving up on a deal that stalls instead of diagnosing which role went quiet. Most founders read silence as rejection and move on. Often it’s simpler: the champion is genuinely trying, but has nothing to bring to their own boss because nobody gave them a business case, only a product demo.
The takeaway
A B2B SaaS deal doesn’t usually stall because the product was wrong. It stalls because it was pitched to the person who was easiest to excite instead of the person who had to say yes, or the person who could quietly say no. Before your next serious deal goes past a second call, map the three roles, user, buyer, blocker, and make sure each has heard a version of the pitch built for what they actually care about. This diagnostic pairs with a documented discovery framework you can eventually hand off and it works best once your ICP is defined by buying mindset, not job title, since a fuzzy ICP usually means a fuzzy buyer map too.
If your pipeline has a pattern of strong first calls and quiet endings, that’s exactly the kind of stall a fractional CMO or senior GTM lead can help you diagnose before you write off the deals as lost.