Minimum Viable Repeatability: The Real Gate Before You Scale SaaS Sales

Minimum Viable Repeatability

The Real Gate Before You Scale SaaS Sales

£2 million ARR does not mean you are ready to scale sales.

Neither does raising a Series A.

Neither does having more pipeline than the founder can personally handle.

And neither does the board agreeing that next year’s number requires five more Account Executives.

All of those things may create a reason to want more sales capacity. None of them proves that the business has something ready to be scaled.

That distinction matters.

In my previous article, Revenue Is Not Repeatability, I argued that one of the most important jobs in an early-stage SaaS company is taking what works in founder-led sales and turning it into a commercial operating system that another capable person can execute.

The natural question that follows is:

When have you done enough?

At what point does a founder stop experimenting with sales and start scaling it?

I do not think the answer is an ARR number.

I think the better gate is what I call Minimum Viable Repeatability, or MVR.

Minimum Viable Repeatability is the point at which there is enough evidence that adding another salesperson primarily adds capacity to a working system, rather than another variable to an unfinished experiment.

That sounds like a subtle distinction.

Commercially, it is enormous.

Because if you scale before reaching it, you do not just scale headcount.

You scale every uncertainty that still exists inside the GTM model.

Why ARR is such a seductive scaling trigger

I understand why ARR becomes the default milestone.

It is visible. It is objective. Investors understand it. Boards can measure it. The SaaS ecosystem is full of benchmarks describing what companies should look like at £1m, £5m, £10m and £100m ARR.

ARR is exceptionally useful for measuring the size of a recurring revenue business.

The problem begins when we assume it also measures the maturity of the mechanism that created the revenue.

It does not.

Imagine two companies at exactly £2m ARR.

The first has grown through founder relationships, investor introductions, a strong partner, several referrals and a handful of inbound opportunities. The founder still joins most meaningful sales conversations and remains the person most capable of explaining the problem, handling senior stakeholders and getting deals over the line.

The second has acquired the majority of its recent customers through channels that do not depend upon the founder. Two salespeople can independently diagnose the customer problem, progress opportunities through an understood buying process and close business using broadly consistent positioning and methodology.

Same ARR.

Completely different commercial risk.

That is why I think founders and investors need to separate two ideas that are too often treated as one.

Revenue Validation proves that customers will buy.

GTM Validation proves that the organisation can repeatedly make that happen.

One tells you a market opportunity exists.

The other begins to tell you whether you have built a mechanism capable of exploiting it.

Early-stage SaaS guidance increasingly makes the same distinction in practical terms. Bessemer, for example, recommends that founders deliberately acquire customers outside their immediate network when validating the earliest sales motion, rather than treating former colleagues and warm relationships as representative of what a future sales team will experience.

That is not because warm revenue is somehow less valuable.

It is because warm revenue answers a different question.

The danger of scaling the result instead of the cause

Let’s say the founder has reached £1.5m ARR.

The board wants £3m next year.

One salesperson apparently helped get the company to £1.5m, so the spreadsheet says another three or four should get it to £3m.

This is where SaaS planning can become dangerously linear.

Revenue grew, therefore add capacity.

But before approving the hiring plan, I would want to understand what caused the revenue.

Was it generated by a repeatable outbound motion?

Was it one unusually productive partner?

Did two enterprise customers happen to arrive through the founder’s network?

Did one salesperson actually generate the revenue, or were they largely converting demand created elsewhere?

Is the ICP genuinely established?

Are win rates understood?

Do we know the normal sales cycle?

Are there specific problems that correlate with winning?

Can the team distinguish a genuine opportunity from an interested prospect?

And perhaps most importantly:

What happens when the founder is removed?

If those questions cannot yet be answered, hiring more salespeople may still be the right experiment.

But it should be understood as an experiment.

It should not be confused with scaling.

There is an important difference between hiring the next seller to help prove the model and hiring five sellers because you believe the model has already been proved.

One increases learning capacity.

The other assumes repeatability.

Scaling sales is expensive enough that this distinction matters

The cost of getting this wrong is not theoretical.

In SaaS Capital’s 2026 benchmarking of private B2B SaaS companies, the median business spent 15% of ARR on selling and another 8% on marketing. Commercial capacity is one of the largest investments a scaling SaaS business makes.

And people do not become productive the day their laptop arrives.

The Bridge Group’s 2026 benchmark across 158 B2B sales organisations found that average AE ramp time had reached 6.2 months, the highest point recorded in the study, while just 48% of AEs achieved annual quota. SaaS companies within the dataset reported a median annual AE quota of $875,000.

That dataset is broader than sub-£5m SaaS and should not be treated as a direct benchmark for every early-stage company. But the lesson is still useful.

Adding headcount and adding productive capacity are not the same event.

Every salesperson you hire creates salary, commission, recruitment, management, tooling, enablement and opportunity costs before you know whether that person can successfully reproduce the motion.

If the underlying GTM is unclear, every new rep also starts running their own version of the experiment.

One targets financial services.

Another likes manufacturing.

One leads with cost reduction.

Another leads with automation.

One qualifies aggressively.

Another fills the pipeline with anything willing to take a demo.

Three months later, the company has more activity, more CRM data, more pipeline and less certainty about what actually works.

The problem was not that the salespeople failed to scale the model.

There was not yet a model to scale.

Minimum Viable Repeatability

This is why I prefer MVR as the gate.

Minimum Viable Repeatability does not mean perfect predictability.

A £2m ARR company should not be expected to behave like Salesforce.

It does not mean every rep hits quota, every opportunity follows exactly the same journey or the ICP never changes again.

Early-stage GTM should continue evolving.

MVR simply means the business has moved far enough from intuition towards evidence that adding sales capacity has a reasonable probability of multiplying something real.

I think about it through a simple progression:

Discover → Codify → Transfer → Prove → Scale

Discovery asks what appears to work.

Codification turns those observations into explicit commercial hypotheses.

Transfer asks whether somebody else can learn them.

Proof establishes whether those people can reproduce the outcomes.

Only then does scale become the primary objective.

The mistake is jumping directly from Discover to Scale.

That produces:

Founder sells → Founder gets busy → Hire five people → Hope.

Hope is not a GTM strategy.

So what actually needs to be true?

I have built eight Scale Readiness Gates into the 6M Sales OS Assessment.

They are not universal SaaS benchmarks handed down by the industry. They are the practical tests I would use when sitting with a founder, CEO, board or investor deciding whether a business is ready to materially increase sales headcount.

You do not necessarily need perfection across all eight.

But if several are fundamentally unanswered, I would want to understand why before pressing the accelerator.

Gate 1: Can you define the market you intend to win now?

Not the investor TAM.

Not every organisation theoretically capable of purchasing the software.

The market your sales team is actually going to attack.

In my first article I called this the Executable Market: the intersection of customer fit, problem intensity, buying triggers, accessibility, product readiness and evidence that you can win.

This matters because scale magnifies focus.

If your first salesperson can sell to healthcare, financial services, retail, manufacturing, technology companies and professional services, that sounds exciting.

Give five salespeople that same brief and suddenly you have five people trying to become experts in six markets, across multiple personas, problems and buying journeys.

The messaging becomes broader.

The case studies become less relevant.

Outbound becomes generic.

Learning becomes fragmented.

Early-stage SaaS businesses rarely suffer because their theoretical market is too small.

More often, they suffer because their commercial focus is too broad.

Before scaling, I want to know where the company has deliberately chosen to become disproportionately good.

If the answer is “any company with more than 500 employees”, Gate 1 probably remains open.

Gate 2: Do you know the scenarios in which you win?

Knowing your ICP is useful.

Knowing why that ICP buys now is much more useful.

This is where Winning Scenarios become important.

A Winning Scenario combines a particular customer, a situation or trigger, a painful problem, the impact of that problem and a credible reason for your company to win.

For example, “professional services companies” is a segment.

“Multi-site professional services companies immediately following an acquisition, struggling to onboard hundreds of employees across fragmented systems” is a scenario.

The second gives Sales something to recognise.

It gives Marketing something to communicate.

It gives outbound something to target.

It gives discovery a hypothesis.

It gives Product context.

And it gives the company a pattern it can test.

Before scaling, I would want to see a small number of these patterns emerging repeatedly from actual customer behaviour.

Not twenty use cases.

Three or four situations the organisation understands incredibly well.

If every closed-won deal still has a completely different explanation, you may have revenue.

You may not yet have repeatability.

Gate 3: Can you create demand outside the founder’s network?

This is one of the most important tests for me.

Early founder-led revenue naturally comes through warm routes.

Former colleagues.

Existing industry relationships.

Investors.

Advisers.

Partners.

Customer referrals.

There is nothing wrong with any of them.

In fact, ignoring those routes to prove some point about cold outbound would be irrational.

But eventually, someone who has no idea who you are needs to care.

That is the moment the company begins testing whether the message stands independently of the founder’s reputation.

Can the team identify a prospect that fits the Executable Market?

Can it create a relevant reason for that person to engage?

Can it turn that engagement into a genuine commercial conversation?

If the answer is consistently yes, we have started validating distribution.

If all meaningful pipeline still arrives through founder relationships, I would be cautious about assuming that five AEs suddenly create five times the opportunity.

Bessemer makes precisely this point in its early-stage playbook, encouraging founders to test cold outreach and develop an intentionally narrow customer profile before expecting non-founder salespeople to reproduce the motion.

Gate 4: Does cold demand actually turn into customers?

This deserves its own gate because businesses often stop the experiment too early.

“We booked 50 meetings.”

Great.

“We generated £700k of pipeline.”

Also useful.

Neither proves repeatability.

I care about what happens at the bottom of the funnel.

Do people who had no prior relationship with the founder actually become paying customers?

Because GTM can appear healthy at the top while failing completely at conversion.

Cold outbound may generate meetings because the messaging is interesting but fail because the product is not sufficiently differentiated.

Marketing may generate pipeline that never reaches the right seniority.

An SDR team may fill Salesforce with opportunities that experienced founders would never have qualified.

The stronger test is:

Can strangers become customers?

Not once.

More than once.

Through a sufficiently similar route that the company can begin understanding why.

That is a much higher bar.

It is also much more valuable evidence.

Gate 5: Can somebody other than the founder run the commercial process?

This is where codification is tested.

The founder has intuition accumulated across hundreds of conversations.

The salesperson has whatever the organisation successfully transferred.

Can they run discovery?

Can they identify real pain?

Can they understand impact?

Can they recognise a weak opportunity?

Can they control a demo rather than defaulting to a product tour?

Can they navigate multiple stakeholders?

Can they build enough credibility to challenge the customer?

Can they create urgency without inventing it?

Can they progress commercial conversations?

The original research I used when building the 6M framework makes a useful distinction here: a codified sales process should move opportunities based on objective buyer evidence, not simply salesperson activity. A demo being completed is not progress if the buyer has not validated the problem or evaluation criteria.

This is exactly why methodology matters.

Not as corporate bureaucracy.

As a way of replacing what previously depended upon instinct with behaviours another person can learn and execute.

Gate 6: Can routine deals close without the founder?

This is different from Gate 5.

A salesperson may successfully run 80% of the sales process but still need the founder for the last 20%.

That may be perfectly acceptable early on.

But it is not the desired end state.

Founders often become embedded in deals because they are incredibly effective.

A senior prospect wants reassurance.

Bring in the founder.

The AE struggles with a technical question.

Bring in the founder.

A deal stalls.

Bring in the founder.

Commercial negotiation becomes difficult.

Bring in the founder.

The customer wants roadmap confidence.

Bring in the founder.

Every individual decision makes sense.

Collectively, they create a commercial organisation that has never learned to function independently.

The test I use is simple:

Is the founder useful, or required?

Those are completely different things.

A founder joining a strategically important enterprise deal as executive sponsor is useful.

A founder being required to close every £30k deal is dependency.

The ultimate goal is for the founder to spend virtually all of their time doing the things only they can do: shaping strategy, building the company, developing product, hiring exceptional people, raising capital and finding the next growth curve.

The Sales OS should sell today’s product.

The founder should be building tomorrow’s company.

Gate 7: Do the economics support the motion?

A sales process can be repeatable and still be commercially unattractive.

Suppose the company discovers that it can reliably close £8,000 ACV customers.

Excellent.

Now suppose every deal requires an AE, a solutions consultant, three months of sales activity, bespoke implementation and significant founder involvement.

That is a different problem.

Repeatability without viable economics does not create a scalable GTM model.

The acquisition motion has to make sense relative to:

ACV.

Gross margin.

Retention.

Expansion potential.

Sales-cycle length.

Implementation burden.

And the cost required to produce the revenue.

This is why blindly copying the GTM organisation of another SaaS company is so dangerous.

A £250k enterprise sale and a £10k SMB sale cannot economically support the same commercial architecture.

The market determines the motion.

The motion determines the cost.

The economics ultimately tell you whether the combination deserves to scale.

Recent SaaS benchmarking reinforces how material these costs become. SaaS Capital’s 2026 data puts median selling expenditure at 15% of ARR and marketing at another 8% across private B2B SaaS respondents.

That does not dictate what your number should be.

It does remind us that scaling sales is a capital allocation decision, not simply a recruitment decision.

Gate 8: Do you understand enough of the maths to know what another seller should produce?

This final gate sounds obvious.

It is frequently missing.

Before hiring another salesperson, I want to know the basic commercial hypothesis behind that hire.

How much qualified pipeline does a rep need?

Where will it come from?

How much must they self-source?

What percentage typically converts?

What is the expected ACV?

How long does it normally take to close?

How long should the rep take to ramp?

How much pipeline already exists?

When should the business realistically expect the hire to become revenue-positive?

The numbers do not need to be perfect.

At this stage, they almost certainly will not be.

But there should be a rational model.

Otherwise the hiring plan becomes:

Revenue target ÷ rep quota = number of AEs required.

That equation looks beautifully scientific in a board deck.

It can be completely detached from reality.

The Bridge Group’s latest benchmarking makes the risk particularly visible. Average AE ramp reached 6.2 months in its 2026 dataset, and only 48% of reps achieved annual quota.

Again, those figures should not simply be copied into an early-stage financial plan.

The point is that 100% quota attainment from 100% of your newly hired sellers is not an operating assumption. It is wishful thinking.

A credible scaling plan models reality.

Pass all eight and are you guaranteed success?

Of course not.

That is not how early-stage companies work.

Markets change.

Competitors appear.

Products disappoint.

People fail.

Customers behave irrationally.

The purpose of Minimum Viable Repeatability is not to create false certainty.

It is to reduce avoidable uncertainty before committing significant resources.

That distinction is important.

There will always be risks you cannot control.

The job of the Sales OS is to stop taking risks you could have understood before spending the money.

This is why I would treat the eight gates as an investment discussion rather than a compliance exercise.

If six are strong and two are still emerging, perhaps scaling carefully is entirely rational.

If three are strong and five remain assumptions, perhaps the next hire should be part of the codification experiment rather than the beginning of a 10-person sales build.

The assessment should inform judgement.

It should not replace it.

There is also a difference between adding a salesperson and scaling sales

I think this distinction is critical.

Early-stage companies should hire salespeople before everything is perfectly codified.

Otherwise you create a circular problem.

You cannot prove the motion transfers until you give it to somebody else.

The first one or two sellers therefore have an unusual job.

They are simultaneously:

Revenue producers.

Commercial researchers.

Playbook testers.

Knowledge-transfer experiments.

Sources of market feedback.

And evidence of founder independence.

This is very different from the tenth salesperson.

By the time you are truly scaling, the primary purpose of additional headcount should have shifted.

You are no longer asking:

“Can another person sell this?”

You are increasingly asking:

“How much more can we sell by adding another person to something we already understand?”

That is the moment capacity begins replacing uncertainty as the dominant variable.

That is Minimum Viable Repeatability.

Hiring ahead of MVR changes the person you need

There is another consequence here that affects recruitment.

If the Sales OS is not yet fully codified, the person you hire needs to be able to operate in that environment.

They need curiosity.

Commercial judgement.

Comfort with ambiguity.

The ability to self-source.

The ability to diagnose problems they have not been given a script for.

The ability to distinguish between the process failing and their own execution failing.

And perhaps most importantly, they need to turn what they learn into something the next person can use.

This is why I am wary of early businesses hiring entirely on logo pedigree.

A brilliant AE from Salesforce, Microsoft or another global SaaS company may be outstanding at operating a mature commercial machine.

The question is whether they have ever had to help build one.

At pre-MVR stage, that difference is enormous.

The role requires somebody capable of operating the machine while the machine is still being assembled.

After MVR, hiring begins to change.

You can increasingly recruit for specialisation.

Enterprise.

Mid-market.

Specific verticals.

Partners.

Management.

Geographies.

Because the organisation is no longer asking every new hire to rediscover the fundamental GTM model.

The company begins giving them leverage.

That is one of the hidden benefits of codification.

It does not just make existing sellers better.

It changes who you are capable of successfully hiring.

MVR is not a finish line

I want to be careful with the word “repeatability”.

It can imply the work is finished.

It never is.

The purpose of codifying a Sales OS is not to freeze GTM in place.

It is to give the organisation a common model from which it can learn.

Your Executable Market will expand.

Winning Scenarios will change.

Messaging will improve.

Competition will evolve.

New channels will work.

Old channels will stop working.

ACV may move.

Product-market fit may deepen in one segment and weaken in another.

The system therefore needs a continuous learning loop:

Hypothesis → Experiment → Evidence → Codification → Transfer → Measurement → Revision

This is what makes the Sales OS an operating system rather than a playbook.

A playbook tells somebody what worked yesterday.

A functioning Sales OS helps the company understand why, see whether it still works today, and change when the evidence says it should.

What I would ask before approving the next five sales hires

If I were sitting in the board meeting, I would not begin with:

“How many AEs do we need to hit the number?”

I would begin somewhere else.

Where are we winning repeatedly?

Which customer situations produce the greatest urgency?

How much of recent pipeline was created outside the founder’s network?

How much of that converted into paying customers?

Which parts of the sales process still require the founder?

Can our current sellers reproduce founder outcomes?

Do we understand the economics of the motion?

What evidence tells us another salesperson adds capacity rather than complexity?

If the answers are strong, brilliant.

Press the accelerator.

If the room suddenly becomes uncomfortable, that is useful too.

Because three months spent closing those evidence gaps may be infinitely cheaper than twelve months trying to diagnose why a newly built sales team is missing target.

And history is full of good companies that blamed the people before questioning the system.

Scale readiness is evidence, not a milestone

This is ultimately the point I want to make.

There is no magical ARR number at which sales becomes scalable.

A pre-revenue company may already have extremely strong market and problem validation but little revenue.

A £3m ARR company may still depend almost completely on founder relationships.

Another £1m business may already have two sellers independently winning customers through a clearly understood motion.

Stage matters.

ARR matters.

Funding matters.

Customer count matters.

But none of them individually answers the question.

Is this commercial system ready to be replicated?

That requires evidence.

Evidence that you know where to play.

Evidence that you understand the problems that create action.

Evidence that strangers will engage.

Evidence that strangers will buy.

Evidence that non-founders can execute.

Evidence that the founder can leave routine deals alone.

Evidence that the economics can work.

And enough understanding of the funnel to form a credible hypothesis about what additional capacity will produce.

That is Minimum Viable Repeatability.

The objective is not certainty. It is earned confidence.

There will always be a leap of faith when an early-stage company scales.

You cannot spreadsheet your way out of entrepreneurship.

But there is a huge difference between taking a calculated risk with evidence underneath it and scaling because the revenue plan says you need another five people.

The first is a commercial decision.

The second is hope wearing a forecast.

Before adding headcount, I want the organisation to have earned the confidence to scale.

Not because the founder feels ready.

Not because the board wants growth.

Not because funding arrived.

Not because the company crossed an arbitrary ARR milestone.

Because enough of the commercial system has been discovered, codified, transferred and proved that the organisation understands what it is multiplying.

Discover. Codify. Transfer. Prove. Scale.

The order matters.

Are you actually ready to scale?

I have now built these principles into the 6M Sales OS Assessment, designed specifically for SaaS businesses moving from founder-led revenue towards a repeatable commercial organisation.

The assessment examines six areas:

Market. Message. Motion. Method. Measurement. Management.

But more importantly, it tests the evidence underneath them.

Where does the business genuinely know how its GTM works?

Where is it still operating on a hypothesis?

Where does founder dependency remain?

Which elements have successfully transferred to the team?

And which Scale Readiness Gates need to be closed before significant additional sales investment makes sense?

The output is not simply a score.

It is a diagnostic of the current Sales OS, a Founder Dependency Index, an evidence-gap analysis and a prioritised plan for increasing repeatability.

If you are a SaaS founder, CEO or investor working with a business from pre-revenue through roughly £5m ARR and you are asking whether now is genuinely the right time to scale sales, message me “MVR”.

I would much rather help you answer that question before the hiring plan is approved than six months afterwards when everyone is trying to work out why the numbers have not moved.

Because before you scale the sales team, there is one question worth answering properly:

Are you adding capacity to a system, or headcount to an experiment?