Why the consulting sales model is broken — and where the fix actually lives.

Something has shifted in how B2B buyers make decisions — and most consulting firms haven't caught up with it yet.

They're losing deals before they ever open a slide template. Not because their proposal was weak. Because the real work — diagnosing the right problem, mapping the right stakeholders, building the narrative that will survive a room they'll never be in — was never done properly in the first place.

The consulting sales model is obsessed with the proposal. Teams iterate decks, sharpen pricing, agonise over design. And then lose to someone scrappier with a fraction of the effort. The reason is almost always the same: they're solving a downstream problem that was created upstream.

Today's B2B buyers do most of the purchasing process without direct involvement from a vendor. They research independently, build internal consensus on their own terms, and engage consultants when they feel ready — often already misaligned internally, with unclear decision criteria and unresolved tensions between stakeholders. By the time a proposal arrives, the deal isn't just being evaluated against competitors. It's being evaluated against a buying group that hasn't agreed on what it wants. No proposal, however polished, can fix that after the fact.

The firms that understand this stop obsessing over packaging and start obsessing over shaping. We sat down with Kelston Smith —  founder and principal at Plantec Ventures, angel investor, and former SAP industry director with 10+ years across enterprise tech and SaaS — to understand what that shift looks like in practice.

About the expert

Kelston Smith is Founder and Principal at Plantec Ventures, a London-based venture studio and capital advisory platform that helps founders and leadership teams commercialise enterprise technology, sharpen strategic narrative, and execute fundraising and partnership mandates from Seed through growth. With over a decade in enterprise tech and SaaS including eight years at SAP managing £15M+ accounts across N.EMEA, Kelston now supports scaling businesses with GTM strategy, investor relations, and strategic transactions alongside VCs and family offices.

The Real Split: Upstream and Downstream

Every consulting deal has two phases, each with a completely different job.

Upstream is everything that happens before a proposal is drafted. It's where diagnosis happens, where hypotheses are formed and tested, where stakeholders are mapped and relationships are built, where the client's internal narrative starts to take shape. Done well, upstream work doesn't just inform the proposal — it renders most objections irrelevant before they can form.

Downstream is the proposal itself: its structure, design, pricing, and delivery. This phase matters — but its job is not to win the deal. Its job is to not lose what upstream has already secured.

Upstream is where you win. Downstream is a hygiene layer. If downstream is where your team's energy, anxiety, and senior time are concentrated, you have a structural problem — not a proposal problem.

"A lot of the groundwork is done in the meetings. The proposal is just you summarising all the meetings — making it so clear that when they're reading it, it's the story of what you've already gone through together."

What a Downstream-Heavy Model Looks Like

The symptoms are recognisable, even if the cause usually isn't named:

Beautiful, expensive proposals that lose to scrappier competitors with half the credentials. Procurement and legal friction appearing late in the cycle — a reliable signal that the buying group was never properly aligned in the first place. Senior consultants spending days on deck iterations while the core narrative — the strategic angle — remains weak, untested, and unchallenged.

The pattern compounds. Every lost deal burns time and money. Every downstream iteration that doesn't fix the underlying upstream problem trains the team to iterate more downstream next time. Meanwhile, the firm positions itself as an executor — a vendor that responds to briefs — rather than a strategic partner that shapes them.

Why Teams Don't See It

The reason this persists is partly structural and partly human.

Downstream work is measurable. You can look at a slide deck and say it's good or bad. You can redline a pricing model. You can critique a narrative arc. Upstream work — the quality of a diagnostic hypothesis, the accuracy of a stakeholder map, the strength of the framing before anyone opens a template — is much harder to review in a meeting. So it doesn't get reviewed. It gets assumed.

There's also a pressure dynamic. Clients want to see progress, and teams want to show momentum. The proposal gives everyone something tangible to point to. Early-stage conversations, by contrast, feel speculative — like work that hasn't produced anything yet. So teams rush through them to get to the part that feels like real work.

The result is that the most consequential decisions in a deal cycle — how to frame the problem, whose interests to prioritise, what narrative will resonate with people you haven't met — get made quickly, intuitively, and without scrutiny.

The Upstream Failure and Success in Practice

Theory is one thing. Here's what it looks like when it goes wrong.

"About two years ago we were brought in alongside a consumer agency to add value on the tech and design side for a wellness brand. We had five discovery meetings, brought in a strong design lead and a manufacturing specialist. Our thinking on the brand direction was solid.
But somewhere around meetings four and five, it became clear we'd started extending our scope beyond what we'd been asked to do — into the website, the ads, broader brand strategy. And I think the agency felt like they were losing control.
So by the time the proposal was being shaped, they were steering it in a direction they knew wouldn't land. Too many slides, too much copy, no clear narrative. And we lost.
The lesson was about stakeholder mapping, not proposal quality. We should have stayed in our lane — kept the incumbent agency feeling like they were in control, made them feel like they were sponsoring us rather than competing with us. That's the problem framing we missed from the start."

The second case is the reverse — a deal that was won precisely because the upstream work was done right.

"We delivered a CRM and AI workflow implementation for a concierge lifestyle brand serving family offices and HNWIs, reducing operational fragmentation while keeping executive judgement firmly in the loop. I was working closely with the COO, but there were two partners above her I never once met, even though we've now had a relationship for nearly a year.
What we did was focus entirely on making the COO look good. We hit all her proof points, showed how our work would make her operations less fragmented — without making it look like we were replacing her judgment or taking over her territory. That's how we won it.
The challenge now is that we're trying to expand the scope, and I need access to those partners. In a live call you can credit the COO for ideas in real time. In a proposal, that's much harder to do.”

Helping the Client Buy

The framing shift this requires is significant. The traditional consulting sales model is built around presenting a solution. The upstream model is built around something harder: helping the client buy.

That means doing the work to understand not just what the client says they need, but what's actually happening inside their organisation. What are the internal tensions? Who hasn't been consulted yet? Whose endorsement is quietly required? What does the decision look like from the perspective of someone who will never appear in a discovery call?

It means listening more than pitching in early conversations — a point Kelston returns to directly:

"Ask open questions and get them to tell you their problem. Just shut up for a good ten minutes and listen. That for me is so important." 

And it means recognising that the proposal, however good, cannot do this work retroactively. A proposal lands in front of stakeholders who weren't in the room. It has to speak to people you've never met, navigate political dynamics you may only half understand, and survive translation from the person who briefed you to the people who will actually decide. If the upstream work hasn't been done, no amount of downstream polish can compensate.

Two Phases, Two Sets of Metrics

The practical implication is that upstream and downstream need to be treated as separate functions — with separate owners, separate review processes, and separate definitions of success.

Upstream success means: the right problem has been diagnosed, the key stakeholders have been mapped and engaged, internal consensus is building, and the narrative is locked before anyone opens a slide template. Downstream success means: the proposal was assembled cleanly, the pricing held, procurement moved without friction, nothing was lost that upstream had secured. This is the part of the process that can be optimised with the right tools that make the process easily repeatable. 

Most firms currently have one review process for both — a proposal review — which means the upstream work never gets scrutinised at all.

The Rebalance

The audit is simple, even if acting on it isn't: track where your pre-deal time actually goes. Not where it's supposed to go — where it actually goes. How many hours went into slide design versus stakeholder mapping? How many into pricing iteration versus diagnostic conversations? How many senior hours were spent on a proposal that was strategically off from the start?

If the weight is downstream, the fix isn't to do downstream better. It's to invest in upstream — in the diagnostic rigour, the hypothesis testing, the consensus-building that determines whether any of the downstream work will matter.

Win upstream. Don't lose downstream. The firms that understand the difference are the ones that stop wondering why their best proposals keep losing.

While we’re at it…

The upstream phase is hard to systematise — but the downstream one doesn't have to be a black box either. Cognitive Alpha is a structured proposal workflow built specifically for boutique consulting firms: it captures your firm's expertise once, contextualises each opportunity, and produces client-ready proposals without burning senior time on deals that may never close.

If the problem this article describes sounds familiar, it's worth having a look.