PAUL WINGFIELD / 6 MIN READ

Winning Scenarios

From the Earn the Right to Scale article series.

In this articleWhy early SaaS businesses should master 3 to 4 scenarios rather than build huge generic playbooksThe mistake is confusing documentation with repeatabilityMore information does not automatically create better sellersYour salesperson does not need an encyclopaediaWhat exactly is a Winning Scenario?Why three or four?The Scale Hack Winning Scenario Canvas

Why early SaaS businesses should master 3 to 4 scenarios rather than build huge generic playbooks

Early-stage SaaS companies love building playbooks.

ICP definitions. Personas. Discovery frameworks. Objection handling. Battlecards. Competitor matrices. Demo scripts. Qualification criteria. Email templates. Negotiation guidance. Closing techniques.

Before long, there is a 70-page document explaining how the company sells.

There is only one problem.

Nobody actually sells like that.

And worse, much of what has been documented has never really been proven.

It is not a sales playbook.

It is a collection of theories about how the company thinks it might sell.

I think early-stage SaaS businesses should take almost the opposite approach.

Do not try to teach your sales team how to win every conceivable deal.

Teach them how to recognise and repeatedly win the three or four situations where you have the strongest evidence that you can.

I call these Winning Scenarios.

And I think they are one of the missing links between founder-led sales and a genuinely repeatable GTM motion.



The mistake is confusing documentation with repeatability

There is a fairly predictable moment in a SaaS company's development.

The founder has closed some customers.

A salesperson or two have joined.

Perhaps a VP Sales has arrived.

Someone quite reasonably says:

"We need to document the sales process."

So the business tries to capture everything.

Every buyer.

Every persona.

Every objection.

Every competitor.

Every use case.

Every route through discovery.

Every possible demo.

Every conceivable reason someone might buy.

It feels mature.

But comprehensiveness and repeatability are not the same thing.

In fact, at an early stage, they can work against each other.

The company has taken a relatively small amount of market evidence and extrapolated it into a system designed to cover a much larger universe.

The result is usually breadth without depth.

Reps technically know 14 use cases but have mastered none.

They can recite six personas but struggle to recognise which one really matters.

They have 30 objection responses but cannot tell the difference between an objection and a fundamental lack of need.

They know the sales stages but not what actually causes a buyer to move between them.

The playbook gets bigger while the evidence underneath it stays exactly the same size.

That is the problem.



More information does not automatically create better sellers

There is a useful parallel in the research on learning and expertise.

Cognitive Load Theory is built around a fairly simple idea: our ability to process multiple interacting pieces of new information at once is limited. Research into worked examples has repeatedly found that people learning complex tasks can often learn more effectively by studying concrete examples of successful execution before being expected to solve the full problem independently.

That research is not about SaaS sales, so I am not suggesting it proves that a three-scenario sales playbook will outperform a ten-scenario one.

But the mechanism matters.

A new salesperson does not become effective because we expose them to every possible situation.

They become effective by learning to recognise important patterns, understanding what tends to work within those patterns, executing it, receiving feedback and gradually developing judgement.

Research into expert decision-making tells a similar story. Recognition-primed decision models describe how experienced operators in uncertain environments frequently make decisions by recognising familiar situations and matching them with patterns learned through experience.

Put simply:

Experts do not necessarily know more rules. They recognise more patterns.

That distinction should completely change how we think about sales enablement.



Your salesperson does not need an encyclopaedia

Imagine your AE is 20 minutes into a discovery call.

The prospect mentions that their existing provider renews in four months, adoption has dropped, the CFO has challenged the renewal cost and the internal champion has been asked to investigate alternatives.

That salesperson does not need access to 70 pages of enablement.

They need their brain to say:

"I know this situation."

They recognise the buying trigger.

They know which questions matter.

They understand who will probably become involved.

They know where the deal is likely to stall.

They know which proof points resonate.

They know which customer story to use.

They know how to shape the evaluation.

They recognise the pattern because they have seen it before, trained for it before and ideally won it before.

That is a Winning Scenario.

A traditional playbook tries to answer:

"How do we sell our product?"

A Winning Scenario asks:

"When this specific situation exists, what have we learned about how we win?"

They sound similar.

They are not.



What exactly is a Winning Scenario?

A Winning Scenario is not simply an industry, persona or use case.

"Financial services" is not a scenario.

"CTO" is not a scenario.

"Enterprise" is not a scenario.

"Companies needing automation" definitely is not a scenario.

A scenario combines context.

For example:

A 500 to 2,000 employee business is approaching renewal with an incumbent platform. Usage is declining, costs have increased and a senior operational leader has been asked to assess alternatives before the next budget cycle.

Now we have something useful.

There is a recognisable environment.

There is a trigger.

There is pressure.

There is likely to be a defined buying window.

There are predictable stakeholders.

There is an existing alternative to displace.

There will probably be recurring objections.

And, if we have won enough similar opportunities, there may be a repeatable way to navigate it.

That is something a salesperson can learn to recognise.



Why three or four?

There is nothing scientifically magical about the number four.

This is an operating constraint, not a neurological law.

The point is concentration.

If you have four sellers, limited pipeline and 12 different plays, each salesperson gets relatively few opportunities to practise each situation.

If instead the business deliberately concentrates demand generation and sales execution around three or four high-potential scenarios, something different happens.

Pattern density increases.

Reps encounter similar conversations more frequently.

Managers coach similar situations more often.

Marketing creates sharper proof.

Discovery gets better.

Demos become more relevant.

Objection handling develops from actual conversations.

Win/loss data starts becoming comparable.

Customer stories become reusable.

And eventually the team begins recognising what is happening before the buyer has fully articulated it.

You are compressing the learning loop.

This matters enormously in an early company because your scarcest resource is not documentation.

It is repetitions.



The Scale Hack Winning Scenario Canvas

I would define each Winning Scenario through six things. I call it the 6P Winning Scenario Canvas:

  1. Profile: Who does this scenario occur within? Not a giant TAM definition, but the characteristics that genuinely matter to the sale.
  2. Pressure: Why is something happening now? Renewal, regulation, growth, cost reduction, new leadership, consolidation, failure, strategic change or another identifiable trigger.
  3. Problem: What specific problem becomes important because of that pressure? What happens if the customer does nothing?
  4. Promise: What outcome are we really selling in this scenario? This should be expressed in the buyer's terms, not product functionality.
  5. Proof: What evidence makes the promise believable? Customer evidence, quantified results, product demonstration, POC, reference call, benchmark or business case.
  6. Path: How does this type of customer typically move from problem recognition to purchase? Who becomes involved, what decisions need to happen and where do these deals commonly fail?

That is the play.

Not a 70-page PDF.

One scenario.

One page.

Something a seller can actually internalise.


Written by Paul Wingfield.

View the original on LinkedIn ↗
← All insights
LET’S TALK

What’s standing between
you and your next stage?

Let’s work it out ↗