Revenue Is Not Repeatability

Codifying the Sales Operating System in Founder-Led SaaS

There is a sentence I hear surprisingly often in early-stage SaaS:

“We know how to sell this. We just need more salespeople.”

It sounds logical. The founder has closed customers, revenue is growing, prospects like the product, investors want acceleration, and there is more opportunity than one person can handle. So the next move seems obvious: hire salespeople and scale what is already working.

Except there is one important question that often has not been answered:

What, exactly, is working?

Does the company genuinely have a repeatable commercial motion, or does the founder have an extraordinary ability to sell something they understand better than anyone else in the world?

Those are not remotely the same thing. Confusing one for the other is one of the most expensive mistakes an early-stage SaaS company can make.

The objective of the transition from founder-led sales is therefore not simply to build a sales team around the founder. It is eventually to remove the founder from the sales process almost entirely.

That does not mean the founder should never meet another prospect. An executive sponsor can add enormous weight to a strategically important opportunity at any stage of company growth. But that should be the exception rather than the operating model.

The target state is a company where 99% of the founder's time can go into driving the business forward: product, strategy, fundraising, leadership, hiring, partnerships and the next phase of growth. Revenue should continue whether the founder joins a sales call or not.

Getting there requires much more than recruitment. It requires taking the commercial intelligence that currently exists inside the founder's head and turning it into an operating system that somebody else can execute.

That is what I mean by codifying the Sales Operating System, or Sales OS.

And I believe it is a distinct stage of company building that too many SaaS businesses attempt to skip.

Revenue proves that customers will buy. It does not prove that GTM will scale.

ARR is one of the most important metrics in SaaS. It is also a poor measure of GTM maturity.

Imagine two SaaS businesses sitting at £1.5 million ARR.

Company A has 15 customers. Ten came through the founder's previous industry relationships, three were investor introductions and two arrived through referrals.

Company B has 60 customers. Most had no previous relationship with the company, and multiple salespeople have sourced and closed those customers across several cohorts using broadly similar positioning, qualification and commercial processes.

On a revenue chart, both businesses are at £1.5 million ARR.

Commercially, they are in completely different places.

This is why I distinguish between Revenue Validation and GTM Validation.

Revenue Validation tells us that somebody is prepared to buy the product.

GTM Validation tells us that the business can repeatedly identify the right strangers, create relevance, diagnose a problem, establish sufficient value and convert those people into customers through an economically viable process.

The first is essential. The second is what allows you to scale.

Founder networks, investor introductions and referrals are not bad revenue. Far from it. They are often exactly how an early-stage company should acquire its first customers. They create access, accelerate learning, generate proof and validate whether customers are willing to exchange money for the product.

What they do not necessarily validate is distribution.

That distinction matters because the first sales hire does not inherit the founder's network, reputation, history or authority.

The founder can call somebody they have known for ten years and say, “I've built something I think solves that problem we used to talk about. Can I show you?”

The new AE cannot.

They have to create the conversation from nothing. That requires a completely different level of precision around whom to contact, why that person should care, what problem to lead with, what creates urgency and why an unknown SaaS company deserves their attention.

This is why cold wins are so valuable during early GTM development. They are not simply another source of ARR. They are evidence of transferability.

There is increasingly strong early-stage SaaS guidance supporting the need to deliberately test cold acquisition rather than relying solely on founder relationships, and to begin with a deliberately narrow ICP before attempting to broaden the market.

If you have £2 million ARR but almost all of it depends upon relationships that disappear when the founder leaves the room, you may have excellent early commercial traction.

But you do not necessarily have a scalable Sales OS.

The founder carries the operating system in their head

This is the core of the problem.

Good founders rarely sell their product in the way a newly hired salesperson does. They have context. They know why the company exists. They recognise the problem before the prospect has finished describing it. They understand the history behind the product and know which feature matters to which type of customer, as well as which features should barely be mentioned.

They know why three previous prospects walked away. They know which objection is genuine and which is a smokescreen. They understand which apparently attractive prospects will consume six months of resources and never buy. They recognise that one seemingly insignificant comment in discovery actually points towards a much larger organisational problem.

Often, they are not consciously processing any of this.

They just know.

That is both the superpower and the limitation of founder-led sales. The commercial system already exists, but much of it has not been externalised.

Research into this transition describes the core challenge as converting implicit founder intuition into explicit, transferable commercial mechanics. I think that captures the issue extremely well.

You cannot onboard a salesperson with intuition. You cannot build a forecast around instinct. You cannot coach against “you'll know it when you see it”. And you certainly cannot scale something nobody can explain.

Codification is therefore an exercise in commercial knowledge extraction.

The question is not simply, “What does the founder do on a sales call?”

The better question is:

“What does the founder know that enables them to make good commercial decisions?”

That knowledge needs to be extracted, challenged, tested, structured and ultimately transferred.

Your investor market and your sales market are not the same thing

Most startups understand TAM, SAM and SOM. The problem is how those numbers are often used.

The investor version of TAM is deliberately exciting. "The global market is worth £30 billion". "There are 400,000 companies that could theoretically use the product". "Every enterprise above 1,000 employees could potentially become a customer".

That is perfectly reasonable when explaining long-term opportunity.

It is almost useless as an instruction to a salesperson.

A salesperson does not need to know that 400,000 businesses could buy the product. They need to know which 500 are most likely to buy it now, why, and how to recognise them.

This is where early-stage businesses frequently dilute their GTM.

Because the product potentially solves problems across ten industries, they speak to all ten. Because four personas could use it, they message all four. Because it has 20 capabilities, they mention all 20.

The resulting positioning becomes technically inclusive and commercially weak.

The product becomes relevant to everybody and urgent to nobody.

For that reason, I add another concept beneath TAM, SAM and SOM:

The Executable Market

The Executable Market is the part of your opportunity you are capable of attacking convincingly today.

Not eventually. Not once Product ships another 20 features. Not once you have a US sales team.

Today.

I think about the Executable Market as the intersection of six things:

Customer fit. Problem intensity. Buying trigger. Accessibility. Product readiness. Evidence that you can win.

It will almost certainly be dramatically smaller than your investor TAM.

Good.

At this stage, the objective is not maximum market coverage. It is maximum learning density.

Pick two or three entry points where the problem is unusually acute and your existing product is unusually credible. Become exceptional there. Learn the industry language. Understand the triggers. Win reference customers. Build proof. Recognise the buying committee. Understand objections before they are voiced and understand why deals die.

Become a rockstar in a deliberately small number of markets.

Then expand.

That is not limiting ambition. It is sequencing ambition.

A £10 billion TAM may tell an investor where the company could eventually go.

Your Executable Market tells the GTM team where to start winning on Monday morning.

Focus creates specificity

Once you narrow the market, something important happens: you can stop talking generically.

Imagine a company positioning itself as:

“An AI-powered platform helping organisations improve operational efficiency and collaboration.”

It might be accurate.

It is also almost impossible to prospect against.

Now compare that with:

“We work with multi-site professional-services companies immediately after an acquisition, when fragmented systems make onboarding hundreds of new employees painfully slow.”

Suddenly we have something tangible.

There is a customer, a situation, a trigger, a problem, an operational impact and probably a group of people who care.

Most importantly, there is a reason to have the conversation now.

This is where the second major element of codification begins.

Codify the scenarios where you actually win

I do not believe early-stage SaaS companies need 25 sales plays.

They need a small number of Winning Scenarios they understand extraordinarily well. Typically, I would begin with three or four.

A Winning Scenario is the intersection of a particular type of customer, an identifiable situation and a problem painful enough to drive change.

Each scenario should answer a consistent set of questions.

Who experiences the problem most intensely? What usually happens immediately before the problem becomes urgent? How does the customer describe it in their own language? What does it cost them? How are they solving it today and why is that inadequate? Who normally cares? Who owns the budget? Who can block the deal? What alternatives will be considered? What proof makes our story credible? Why do we win? Why do we lose?

When you analyse the founder's early deals this way, patterns begin to emerge.

Perhaps your most successful customers all experienced the same regulatory change. Perhaps they were all replacing the same legacy system. Perhaps a particular organisational event creates urgency. Perhaps companies above a certain size convert at three times the rate of smaller accounts. Perhaps one persona loves the product but never owns budget. Perhaps the deals that move fastest all begin with the same business problem.

Those observations are gold.

Because the founder's intuition can now start becoming a commercial hypothesis.

And that hypothesis can be taught.

Where founder-led sales often breaks during the handover

The founder may know surprisingly little about the formal terminology of sales. They may never have used MEDDPICC. They may not structure discovery according to a recognised framework. Their CRM hygiene might be dreadful.

And yet they can be extraordinarily effective.

Why?

Because they understand the problem.

Then the first sales team arrives.

They do not have ten years of industry experience. They do not have the founder's scar tissue. They were not there when the product was conceived and they have not spoken to the first 50 prospects.

So how do they create credibility?

They learn the thing immediately available to them:

the product.

Features. Integrations. Dashboards. Architecture. Workflows. Roadmap.

The salesperson becomes increasingly confident talking about what the software does, while the customer is usually thinking about something completely different:

“Why should I change anything?”

This is how a problem-led founder motion quietly becomes a feature-led sales motion. It is one of the key reasons founder results fail to transfer.

The answer is not more product training.

The answer is capturing enough customer and industry context that the salesperson can understand and diagnose the world in which the product matters.

Before teaching them every feature, teach them what typically breaks, why it breaks, what happens if nobody fixes it, who notices first, what it costs, which event makes the pain intolerable, what the prospect would normally do instead, how someone in that industry describes the issue and what “good” actually looks like.

Only then does the product become relevant.

The product should be the proof of the solution, not the starting point of the conversation.

The 6M Sales Operating System

I use six interconnected layers to think about this transition.

Together, they form what I call the 6M Sales Operating System:

1. Market: Where should we play?

This includes the ICP, negative ICP, Executable Market, beachhead segments, account prioritisation and buying triggers.

2. Message: What problem do we have the right to own?

This includes Winning Scenarios, problem language, business impact, personas, relevance, differentiation, proof and the reason to act.

3. Motion: How do we systematically create and convert demand?

This covers outbound, inbound, partnerships, founder channels, ACV alignment, sales coverage, the buying journey and the path from target account to customer.

4. Method: How should a competent salesperson execute?

This includes discovery, qualification, stakeholder mapping, product demonstration, business-case development, evaluation, objections, commercial process and close.

5. Measurement: How do we know what is actually working?

Pipeline source, stage conversion, win rate, cycle length, deal value, velocity, acquisition economics, retention signals and the performance of individual Winning Scenarios all belong here.

6. Management: How do we make the system transferable and improve it?

Hiring, onboarding, certification, coaching, deal inspection, forecasting, operating cadence, accountability and continuous playbook development.

There is an important dependency between them.

Market informs Message. Message informs Motion. Motion determines Method. Method creates Measurement. Measurement informs Management. Management feeds learning back into every previous layer.

If the first two are weak, sophistication in the remaining four will not save you.

A beautifully managed sales team pointed at the wrong market with weak messaging simply becomes extremely efficient at losing.

The sales process should describe the buyer, not the salesperson

Once the Market, Message and Motion have enough evidence behind them, the formal sales process can be built.

But there is a trap here too.

Look at many early-stage CRMs and you will find opportunity stages such as:

Demo Completed. Proposal Sent. Contract Sent. Legal.

These describe things we did.

They do not necessarily tell us whether the customer progressed.

A demo being completed is an activity. Agreement on the customer's technical or business evaluation criteria represents buyer progress.

Sending a proposal is an activity. Validating the business case with someone able to authorise the purchase represents buyer progress.

This distinction matters enormously.

A mature Sales OS moves opportunities based on evidence.

Instead of “Discovery Completed”, require a documented business problem and measurable impact that the customer has validated.

Instead of “Demo Completed”, require agreement that the proposed capability addresses the defined problem and clarity around the remaining evaluation criteria.

Instead of “Proposal Sent”, require access to the commercial decision maker and an agreed buying process.

Instead of “Contract Sent”, require confirmation of procurement, security and legal steps, alongside clear ownership of each.

The principle is simple:

A deal should not progress because the salesperson moved. It should progress because the buyer moved.

That change alone dramatically improves forecast quality and coaching.

Instead of asking, “How are you feeling about Acme?”, a manager can ask, “What evidence do we have that the business impact has been validated by the economic buyer?”

One generates opinion.

The other generates diagnosis.

You cannot solve an uncodified GTM motion with headcount

This is the moment where commercial mistakes become expensive.

The founder is exhausted. The board expects growth. Pipeline targets increase. Perhaps there is fresh capital following a raise.

So the answer appears obvious:

More sellers.

But additional headcount does not fix an unclear market, generic positioning or an unproven sales motion.

It multiplies them.

Recent private B2B SaaS benchmarking shows how significant commercial expenditure becomes. In 2026, median companies in one large private SaaS dataset spent approximately 15% of ARR on selling and 8% on marketing.

At the same time, recent B2B sales benchmarking across more than 150 organisations showed average AE ramp-to-full-productivity reaching 6.2 months, while fewer than half of AEs achieved annual quota. That dataset is broader than sub-£5m SaaS businesses, so it should not be treated as a direct startup benchmark, but the implication is still important.

Hiring a salesperson and creating productive sales capacity are not the same event.

The economics make experimentation with headcount extremely expensive.

Which leads to one of the most important principles in the entire Sales OS:

Headcount scales a system. Headcount is not a substitute for one.

Your first sales hires need to build the machine while operating it

This has significant implications for hiring.

One mistake I see regularly is an early-stage SaaS company deciding it needs to “professionalise sales”, then hiring somebody from Salesforce, Microsoft, ServiceNow or another global software business.

They have an incredible CV. They have closed huge deals. They have recognisable logos throughout their history and have consistently hit target.

There is nothing inherently wrong with that candidate.

The mistake is assuming that past success automatically proves stage fit.

Consider the environment in which an AE at a global category leader may operate. Customers know the company. There is category awareness. Marketing creates demand. There may be SDRs, enablement, reference customers, battlecards, established pricing, solution consultants, RevOps, a defined sales process and experienced managers who have seen hundreds of similar opportunities.

There is customer trust before the AE enters the room.

Now remove almost all of it.

That is startup selling.

The early-stage rep may need to find the account, work out why it should care, create the message, write the outbound, run discovery, diagnose an unfamiliar industry problem, demonstrate the product, create the business case, navigate security, work out pricing, close the deal and then tell the company what they learned.

Those are different jobs.

At this stage, you are not hiring somebody merely to operate the machine.

You are hiring somebody capable of helping construct the machine while simultaneously operating it.

I care far more about whether somebody has sold successfully when nobody knew their company's name.

Have they created their own pipeline? Can they operate without enormous enablement infrastructure? Can they turn conversations into playbooks? Can they distinguish between an ICP problem and an individual salesperson problem? Can they diagnose the customer rather than pitch the product? Can they challenge the playbook constructively when reality disproves it? Can they operate with imperfect information? Have they helped build before?

Logo prestige is not irrelevant.

But at this stage, stage relevance is far more important than logo prestige.

Codifying GTM and scaling GTM are different disciplines

This distinction is not discussed enough.

A company moving from £20 million to £50 million ARR is typically asking questions such as: How do we increase territory productivity? How do we specialise? How do we improve pipeline coverage? How do we increase enterprise penetration? How do we improve forecast accuracy? How do we improve manager leverage? How do we expand internationally?

Those are primarily scaling questions.

A pre-revenue or £2 million ARR founder may be asking something fundamentally different.

Who actually buys this? Which of the ten use cases should we lead with? Why do customers really purchase? Can outbound work? What is a good opportunity? Who should we avoid? Can anyone other than me close this? What does a normal sales cycle even look like?

Those are discovery and codification questions.

The mistake is applying scaling answers to codification problems.

More SDRs. More territories. More tooling. More managers. More process. More dashboards. More pipeline. More sellers.

None of those necessarily answer the fundamental question:

Do we know enough about how this market buys to make success reproducible?

You cannot optimise a machine while you are still discovering its architecture.

The sequence should be:

Discover. Codify. Transfer. Prove. Scale.

Not:

Sell. Hire. Hope.

The founder's final sales job is to make themselves unnecessary

This is where I disagree with the idea that the mature form of founder-led sales is simply a founder who sells less.

That does not go far enough.

The end state should be a commercial organisation capable of functioning without the founder.

That does not mean banning the founder from customer conversations. A CEO joining a seven-figure strategic opportunity as executive sponsor can be extremely powerful. A founder speaking to an important prospect about long-term product vision may materially increase trust.

But those interventions should represent deliberate executive leverage.

They should not compensate for deficiencies in the sales process.

The founder should not be required to rescue discovery. They should not need to run the demo. They should not need to explain the value because the AE cannot. They should not be the only person capable of progressing a senior stakeholder. They should not be required to close every meaningful opportunity, and they certainly should not be carrying half of the forecast.

The goal is founder independence, not reduced founder dependence.

Because every hour a founder spends performing work the commercial organisation should eventually be able to perform is an hour not spent on work that only the founder can do.

The company needs them building the next version of the business.

The Sales OS needs to sell the current one.

So how do you know whether the Sales OS has actually been codified?

This is where I think much of the advice around early-stage GTM becomes frustratingly vague.

Companies are told to document the process, create the ICP, write a playbook, implement a methodology, define their stages and train their reps.

All reasonable advice.

But how do you determine whether any of it is actually transferable?

I use what I call the 6M Sales OS Diagnostic.

It deliberately measures maturity not according to whether something exists, but according to whether it has successfully moved from founder intuition to independent repeatability.

Every capability is assessed against five levels:

0. Unknown: We have not established the answer yet.

1. Founder-dependent: The knowledge exists primarily through founder judgement, relationships or individual intuition.

2. Codified hypothesis: We have documented an explicit hypothesis or process and can teach it.

3. Evidenced: Repeated customer and pipeline evidence supports the hypothesis.

4. Repeatable: Non-founders can execute it consistently and the business can measure and improve it.

That distinction matters.

A 40-page ICP document is not automatically more mature than a founder's instinct.

Documentation without evidence is simply a well-written hypothesis.

The objective is repeatability.

What the 6M diagnostic actually assesses

Within Market, I look for precision around the ICP, a clear negative ICP, an Executable Market, evidence behind selected beachheads and identifiable buying triggers.

Within Message, I look at problem definition, Winning Scenarios, the ability to quantify business impact, persona and stakeholder relevance, and proof and differentiation.

Within Motion, I assess acquisition routes, evidence of cold GTM, whether the economics match the sales approach, how closely the motion reflects the customer's buying journey and, critically, whether opportunities can progress without founder dependency.

Within Method, I look at discovery and diagnosis, qualification, buyer-based stage gates, the ability to connect the product to the diagnosed problem, and commercial execution through stakeholders, objections, competition, procurement and close.

Within Measurement, I look at pipeline source, conversion, velocity, win/loss intelligence and enough economic visibility to understand whether the commercial model can become viable.

And within Management, I assess onboarding, certification, coaching, deal inspection, forecasting, operating cadence and whether the company is continuously feeding new commercial learning back into the Sales OS.

Each of those dimensions can be scored, but the number itself is not the most important output.

The shape of the system matters more than the headline score.

A company can have sophisticated measurement, excellent managers and a rigorous methodology, but if its Market score is weak, all of that sophistication may simply be pointed at the wrong customer.

The Founder Dependency Test

The overall 6M score is therefore only part of the assessment.

I separately look at how dependent the revenue process remains on the founder.

Can target markets be selected without them? Can accounts be prioritised? Can outbound messaging be created? Can strategic conversations be opened? Can discovery happen? Can value be articulated? Can the product be demonstrated? Can executives be engaged? Can objections be managed? Can commercials be negotiated? Can deals close? Can the forecast be called accurately?

The objective is not necessarily to reach absolute zero founder involvement.

The objective is to understand the difference between the founder being useful and the founder being required.

If the founder joins a strategic conversation because their presence raises the probability of winning, that is leverage.

If the founder joins because the deal is unlikely to progress without them, that is dependency.

That difference is fundamental.

Scale readiness should be gated by evidence, not ARR

This is why I would not tell a founder that reaching £1 million, £2 million or £5 million ARR automatically means the organisation is ready to scale sales.

Instead, I would look for evidence that a series of important questions can be answered positively.

Can we clearly identify the customers we intend to attack now?

Have our core Winning Scenarios been repeatedly observed in real conversations and deals?

Can the company create meaningful demand outside the founder's network?

Has independently created demand converted into paying customers?

Can non-founders run the majority of the commercial process?

Can routine opportunities close without founder intervention?

Does the sales motion have directionally credible economics?

Do we understand enough of the funnel to form a rational hypothesis about what additional sales capacity will produce?

If several of those answers are no, the solution may not be “hire more”.

It may be codify more.

Minimum Viable Repeatability

I do not believe a founder needs a perfect commercial system before hiring salespeople.

That is unrealistic.

The first sales hires are themselves an important part of the experiment because they test whether the founder's knowledge can actually transfer.

But there is a point at which enough evidence should exist to justify meaningful scaling.

I call this Minimum Viable Repeatability.

It does not mean every number is predictable. It does not mean every rep hits quota. It does not mean the ICP will never evolve.

It means enough of the operating system has been validated that adding another salesperson primarily adds capacity, rather than another variable to the experiment.

A business approaching MVR should know where it wins, understand which problems create action, have evidence that strangers will buy, demonstrate that non-founders can execute the core motion, no longer structurally require the founder, measure the key funnel assumptions, possess directionally credible economics and be able to diagnose why opportunities win and lose.

That is the inflection point I care about.

Not £1 million ARR.

Not £2 million ARR.

Not Series A.

Not 50 customers.

Those milestones may provide context, but the more important question is:

Can another capable human reproduce the outcome?

If the answer is no, the commercial engine is not yet ready to be scaled aggressively.

And if the answer is “we don't know”, hiring five more people is a remarkably expensive way of finding out.

The diagnostic should produce a build plan, not just a score

This is important.

A useful Sales OS assessment should never finish with:

“You scored 73 out of 120.”

Who cares?

The value is understanding why.

The 6M diagnostic therefore produces five practical outputs.

First, a 6M Heatmap, showing where the commercial system is strong, weak or disproportionately dependent on certain individuals.

Second, a Founder Dependency Map, identifying exactly where the revenue process still relies on founder knowledge, authority, relationships or intervention.

Third, an Evidence Gap Analysis, distinguishing between what the organisation genuinely knows, what it currently believes, and what remains unknown.

Fourth, a Codification Backlog, converting those gaps into specific pieces of commercial work.

And finally, a 90-Day Transfer Plan, prioritising the actions required to reduce founder dependency and increase GTM repeatability.

That turns the framework from an interesting score into something operational.

The diagnostic tells you where the Sales OS is weak.

The 90-day plan tells you what to build.

And the next diagnostic tells you whether it worked.

The Sales OS should behave like a scientific system

This is perhaps the most important element of the methodology.

Every playbook begins as a hypothesis.

The ICP is a hypothesis. A Winning Scenario is a hypothesis. Your positioning is a hypothesis. A cold email is a hypothesis. Pricing is a hypothesis. Your qualification criteria are hypotheses.

The organisation then exposes those hypotheses to the market.

Some survive.

Some do not.

The learning loop therefore looks like this:

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

Then repeat.

This matters because codification should never mean bureaucracy.

A Sales OS should not be a giant PDF that becomes less accurate every month after it is written.

It should be a living commercial learning system.

Version 0.1 may largely reflect founder assumptions. Version 0.5 incorporates early customer conversations. Version 1.0 includes the first repeatable win patterns. Version 2.0 reflects what the first independent sellers have learned.

If an early-stage sales playbook has not changed in a year, I would question whether it still represents reality.

The objective is not to create documentation.

It is to increase the rate at which the organisation learns what makes customers buy and make that knowledge transferable.

A Sales OS is not a playbook

There will be documents.

There should be.

ICP definitions. Negative ICP criteria. Market maps. Winning Scenario cards. Persona maps. Problem statements. Discovery guides. Qualification criteria. Objection libraries. Competitive positioning. Demo architecture. Stage definitions. Exit evidence. Outbound plays. Business-case templates. Forecast definitions. Onboarding. Certification. Management cadence.

But none of those things, independently, are the Sales OS.

They are representations of it.

The operating system is the commercial logic connecting them.

We pursue these companies because these conditions make the problem unusually painful.

We lead with this problem because this buyer consistently cares about this consequence.

We qualify this way because these attributes correlate with winning.

We demonstrate these capabilities because they address the outcome established during discovery.

We move the opportunity because the customer has demonstrated this evidence.

We coach against these standards because they reflect how our best deals actually progress.

We measure these variables because they tell us which parts of our commercial hypothesis are true.

That is an operating system.

Everything else is documentation.

Revenue is not repeatability

Founder-led sales is not something to be embarrassed by.

It is an extraordinary early-stage advantage.

But it is supposed to produce something:

knowledge.

The founder is effectively the first commercial laboratory.

Every conversation should improve understanding of the market. Every objection should improve the message. Every win should refine the ICP. Every loss should challenge an assumption. Every customer should provide evidence about where the product creates genuine value.

Eventually, that knowledge must leave the founder's head.

Because the ultimate objective is not to build a sales organisation that works around the founder.

It is to build one that works without them.

The founder may still enter the biggest boardroom. They may still sponsor the strategic relationship. They may still tell the story no salesperson can tell quite as powerfully.

But those should be moments of executive leverage, not structural dependency.

A scalable SaaS business should not require its founder to keep selling today's product.

It needs them building tomorrow's company.

That transition does not happen when you hire a VP Sales.

It does not happen when ARR crosses £1 million.

And it does not happen when you implement a CRM.

It happens when the commercial knowledge that made founder-led sales successful has been identified, tested, codified, transferred and proven in the hands of somebody else.

Discover. Codify. Transfer. Prove. Scale.

That is the journey.

And before putting another five names onto the sales org chart, I would ask one final question:

What, exactly, are you asking them to replicate?

If this is the problem you are facing, let's talk.

If you are a founder, CEO or investor working with a business from pre-revenue through to roughly £5 million ARR, there is a good chance you will encounter this transition.

Perhaps the founder is still closing most of the revenue.

Perhaps the first sales hires are struggling to reproduce founder results.

Perhaps you have traction but cannot confidently explain why you win.

Perhaps the board wants to accelerate hiring, but nobody is entirely sure whether the GTM motion is genuinely ready.

Or perhaps you want to build the commercial operating system before committing heavily to sales headcount.

This is exactly the problem I work on.

I have built a full 6M Sales OS Assessment around the framework above to diagnose founder dependency, GTM evidence gaps, commercial maturity and scale readiness, and to translate those findings into a practical codification and transfer plan.

If you want to understand whether your sales engine is genuinely ready to scale, send me a message with “6M”.

We can put the framework against your current GTM motion and identify where the dependencies, evidence gaps and scaling risks sit.

Sometimes the conclusion will be that the business is ready to accelerate.

Sometimes it will be that 90 days spent codifying the engine could prevent 12 months spent scaling the wrong one.

Either way, it is worth knowing before you press the accelerator.

Research and evidence

This thesis draws on a combination of practical SaaS GTM experience and research covering founder-led sales, early-stage SaaS growth, sales productivity, commercial economics and sales-process design.

Among the external research considered were Bessemer Venture Partners' work on the journey from founder-led sales towards scalable GTM; SaaS Capital's private B2B SaaS spending benchmarks; The Bridge Group's AE productivity and ramp research; research and methodology from Winning by Design; a16z's work on early sales leadership and scaling; and broader research into the risks of premature organisational scaling.

The purpose of those sources is not to prescribe a universal SaaS formula. Early-stage companies vary enormously by market, ACV, product complexity and buying journey. Rather, they provide external evidence against which the central thesis can be tested:

Commercial traction and commercial repeatability are not the same thing.