Discover. Codify. Transfer. Prove. Scale.

A practical 90-day operating model to earn the right to scale.

The board approves three sales hires.

The spreadsheet looks sensible. Each salesperson carries a quota. Ramp time is accounted for. Revenue rises as the team expands.

Then the hires arrive.

They need the founder to explain the product’s value. They need introductions to get conversations started. They need help diagnosing the buyer’s problem, building the business case and navigating the difficult commercial conversations.

The founder becomes busier. The forecast becomes harder to defend. The new hires become frustrated.

Eventually, someone asks whether they recruited the wrong people.

Perhaps they did. But there is an earlier question that deserves an answer:

What, exactly, were those people supposed to repeat?

The founder’s network? Their authority to change the roadmap? Their instinct for which opportunities were worth pursuing? Their ability to assemble an offer around what one particular customer needed?

Those things may have helped create a valuable business. They do not automatically constitute a sales system another person can operate.

If every additional salesperson increases the demand on the founder, founder capacity becomes the ceiling on growth.

That is the problem this series has been working towards solving.

The decision underneath the entire series

We began with a distinction that should sit behind every early commercial investment: winning revenue and building a repeatable way to win revenue are different achievements.

The first tells you that someone will buy. The second requires evidence about how demand is created, why opportunities progress, what customers receive and whether someone else can execute the work.

Each article has examined part of that system.

Your executable market determines where you can credibly compete now. Winning scenarios make the circumstances behind a purchase specific enough to recognise and repeat. The Founder Dependency Index exposes where the founder remains structurally necessary.

Stage-fit hiring asks whether someone can succeed with the resources and uncertainty that actually exist. Pipeline diagnosis tests whether the forecast reflects buyer evidence. Product accountability prevents commercial teams being held responsible for constraints they cannot remove.

The leadership discussion extends the same principle: as the organisation grows, someone must own the quality of the system producing the number.

Together, these ideas lead to one question:

What evidence justifies the next investment in growth?

“Revenue is increasing” provides part of the answer. “We raised money” describes available resources. “The market is enormous” describes potential.

None, by itself, establishes that another salesperson will inherit something that works.

Why premature scaling becomes so expensive

The obvious cost is payroll. The less visible cost is that adding people introduces more variation into a system you do not yet understand.

One seller targets larger customers. Another changes the messaging. A third discounts to create urgency. The founder joins the difficult deals and makes exceptions to keep them moving.

When the results differ, which variable explains the difference?

You now have more activity and more opinions, but potentially less clarity about what produces a good outcome.

That makes management harder. Coaching becomes inconsistent because nobody has established what good execution looks like. Forecasting becomes a negotiation over confidence. Product receives conflicting requests from opportunities that may never have belonged in the target market.

Meanwhile, the founder sees experienced hires struggling with work that once felt instinctive and concludes that they need to stay involved.

The dependency reinforces itself.

This is why codifying the Sales Operating System matters. It creates a basis for deciding what to preserve, what to transfer and what to change.

It also protects the team. Before judging whether someone has failed to execute, you should be able to explain the approach they were expected to execute, why it was plausible and what support it required.

You cannot eliminate uncertainty in an early business. You can make it visible enough to manage.

What the next 90 days should achieve

The operating model is simple to remember:

Discover. Codify. Transfer. Prove. Scale.

Its purpose is to work towards Minimum Viable Repeatability: enough evidence that additional headcount primarily adds capacity rather than uncertainty.

That requires a bounded claim. You might establish repeatability for one customer group, buying situation and demand source while other parts of the business remain experimental.

Be specific about what you have proved.

The 90 days provide a period of concentrated work and a decision point. They do not guarantee a fully validated sales motion. A business with a nine-month buying process will need different evidence and a longer observation period than one closing business within weeks.

Discovery should inform codification. Attempts to transfer the approach will expose gaps. Live opportunities will test assumptions throughout.

The calendar creates discipline. The evidence determines progression.

1. Discover the mechanism behind the revenue

Days 1–30. Led by the revenue leader, with direct access to the founder, buyers and customer evidence.

Start by explaining the revenue you already have.

Choose a meaningful set of wins, losses, stalled opportunities and customers whose experience after purchase was disappointing. If the business has very few deals, inspect them all and acknowledge the limits of the sample.

Reconstruct what happened. Review conversations, emails, proposals, commercial concessions and implementation requirements. Speak to buyers about their decision, including those who stayed with the status quo.

The useful questions go deeper than why they liked the product.

What happened inside their business that made the problem urgent? Who experienced the consequences? Who committed resources? What alternative would they have chosen? What nearly stopped the purchase?

Then examine your contribution. How did you reach them? Which intervention changed the outcome? What did the founder know, promise or authorise that another seller could not?

Identify the circumstances you can win again

Look for a recurring combination of customer characteristics, buying triggers, problems, stakeholders and product fit.

“Mid-market companies” gives a seller a large population to search. A winning scenario gives them a reason to start a particular conversation.

For example: an operations leader whose company has opened several new sites and can no longer manage approvals through separate spreadsheets has a recognisable situation. You can investigate its consequences, identify relevant accounts and test whether the same problem exists elsewhere.

That is how an executable market starts becoming operational.

Three or four scenarios can provide useful focus. But do not manufacture four because the framework mentions four. One defensible scenario is more useful than several attractive guesses.

Separate the product advantage from the founder advantage

Consider a fictional workflow SaaS company preparing to hire three account executives. This example is illustrative.

The founder has won customers across several sectors and believes the product has broad appeal.

Deal review reveals a narrower pattern. The strongest customers bought after expanding to additional sites. Their operations leaders needed visibility and consistent approvals across locations.

Larger prospects appeared interested, but several required an integration the product could not support. Other wins depended on personal introductions and the founder constructing the entire business case.

The business now has three distinct questions: whether the additional-sites scenario is repeatable, whether demand can be created beyond existing relationships, and whether the product gap makes a separate segment unsuitable.

That is a much better starting point for investment.

Establish a baseline of dependency

Record where the founder is involved and what that involvement accomplishes. Presence alone tells you little.

An occasional executive conversation differs from personally running discovery, rewriting every proposal or repeatedly rescuing negotiations.

Measure the pattern by stage and reason. Include founder time, unplanned interventions and decisions only they can make. Use the Founder Dependency Index to direct investigation, supported by actual deal evidence.

By day 30, you should have a bounded market, candidate winning scenarios, a dependency baseline and a list of constraints with owners.

The test is whether you can explain why the approach might work again, show what supports that explanation and name the evidence that would cause you to reconsider.

2. Codify the decisions that make the motion work

Days 31–60. Owned by the revenue leader, with sellers testing whether the system is usable.

Codification begins with judgement.

What should the seller notice? What must they understand before moving forward? When should they involve someone else? Which opportunities should they stop pursuing?

A description of what happened in a successful deal can help. But copying its sequence does not necessarily reproduce the conditions that made it successful.

The value lies in extracting decisions someone can apply to a different buyer facing a comparable situation.

Use the 6M Sales OS to connect those decisions:

• Market: Which customers and buying situations can we credibly win?
• Message: What problem matters, why act now and why choose us?
• Motion: How do we reach buyers and help them progress towards a decision?
• Model: What commercial economics, roles and capacity assumptions make the approach viable?
• Measurement: What evidence tells us whether it is working?
• Management: How do we coach execution, maintain standards and improve the system?

These elements affect each other. A higher-touch motion changes the economics. A different customer segment may require different proof, stakeholders and implementation support.

The system should make those relationships visible.

Build something a seller can use during real work

For each winning scenario, create a concise guide covering the trigger, buyer context, discovery questions, qualification requirements, relevant evidence and common obstacles.

Include examples of strong and weak execution. Explain what an acceptable next step looks like and which conditions make an opportunity a poor fit.

Then use the guide on actual opportunities.

If a seller still cannot decide what to investigate next, another page of product information is unlikely to solve the problem. The missing element may be a decision rule, a worked example or a skill that requires practice.

Our fictional company creates a guide for the additional-sites scenario. It helps sellers investigate duplicated work, delays and the operational consequences of inconsistent approvals.

It also gives them a way to build the business case with the buyer. Prospects requiring the unsupported integration are identified early, with clear rules about qualification and product escalation.

Make stages reflect buyer progress

A completed demonstration proves that a demonstration occurred.

It does not establish that the buyer accepts the problem, sees sufficient value or intends to commit resources.

Stage criteria should therefore capture observable progress: an agreed problem, a credible stakeholder map, access to the decision process, evaluation criteria or a mutually owned plan.

Qualification frameworks such as MEDDPICC can help organise that investigation. Their usefulness depends on the quality of the evidence recorded and how managers challenge it.

A completed field containing seller opinion remains seller opinion.

The same discipline applies to pipeline coverage. A multiple becomes useful when you understand conversion, timing and the composition of the opportunities behind it.

Codify the exceptions too

Some deals will need executive involvement, commercial flexibility or technical support. Define when those exceptions are justified, who authorises them and how they affect the interpretation of the result.

Otherwise, every exception quietly becomes part of the assumed standard motion.

By day 60, you should have usable scenario guides, qualification and stage criteria, explicit commercial assumptions and a management rhythm.

The test is whether another seller can use the system to make a sound decision on a live opportunity and explain their reasoning.

3. Transfer capability and ownership

Days 61–90, with practice beginning earlier. Owned by the manager responsible for seller development.

This is where the difference between documentation and a working system becomes visible.

The seller has read the guide. They understand the product. They can repeat the positioning.

Then the buyer gives an ambiguous answer, introduces an unfamiliar objection or asks for a commitment the seller cannot make.

What happens next?

If the founder immediately takes over, the commercial outcome may be protected. But the team has learned little about whether the capability has transferred.

Transfer requires deliberate practice, observed execution and a gradual change in ownership.

Make the founder’s reasoning visible

Start with demonstration. The founder or revenue leader runs the work and explains the decisions afterwards.

Why challenge that answer? Why delay the demo? Why involve finance now? Why decline a request that appeared to help the deal?

Experienced people can perform these judgements so quickly that they struggle to describe them. A manager needs to slow the work down enough for someone else to learn it.

Then move through rehearsal, supported live execution and independent ownership. Use real scenarios and inspect specific behaviours.

A seller being comfortable with the material is useful. A seller applying it appropriately under pressure is stronger evidence.

Diagnose failed transfer accurately

When someone follows the guidance and struggles, several explanations are possible.

The scenario may be poorly defined. The guidance may omit a critical judgement. The seller may need coaching. They may lack authority or technical support. The product may not deliver what the conversation requires.

There may also be a genuine mismatch between the person and the stage of the business.

Distinguish those explanations before deciding what to change.

This connects directly to stage-fit hiring. Someone accustomed to established demand, specialist support and a recognised brand may be excellent in that environment. The current role may require them to create access, test assumptions and help improve the motion while carrying a number.

Assess the work you need them to do.

Make founder withdrawal deliberate

Our fictional company’s seller runs effective discovery but struggles to construct the business case. The founder intervenes and helps keep the opportunity alive.

The manager records the intervention, reviews what was missing and practises the relevant conversation with the seller. On the next comparable opportunity, the seller leads that work independently.

That is progress. It needs further observation.

Every founder rescue may help this quarter’s revenue. It also reveals a capability, authority or system gap that still needs attention.

The destination is the founder almost entirely out of routine selling, with exceptional executive sponsorship serving a defined purpose.

That requires a change from the founder too. The team needs room to execute well in its own voice. If every stylistic difference triggers intervention, independence remains out of reach.

By day 90, you should have observed examples of independent execution, a record of remaining dependencies and targeted coaching actions.

The test is whether the team can perform the critical work without routine founder rescue.

4. Prove what works beyond the founder

Days 61–90 and beyond where required. Owned by the revenue leader, with consistent measurement and scrutiny from the CEO.

A win is encouraging. Proof requires knowing what the win demonstrates.

A seller might close an opportunity that the founder sourced, qualified and negotiated. That can be good execution of the final stage. It provides limited evidence about independently generating and converting demand.

Equally, a deal won through an extraordinary discount or a bespoke product commitment may say little about the economics of the standard motion.

Define the claim you are testing before evaluating the result.

For example: can a seller create qualified opportunities among companies opening additional sites, build a credible business case and progress them through the normal buying process using the current product and commercial model?

That claim is specific enough to investigate.

Follow comparable opportunities over time

Track opportunities by relevant characteristics: scenario, source, seller, size, entry date and material exceptions.

Separate founder-network demand from independently created demand. Keep incomplete opportunities visible. Avoid drawing a firm conclusion from a conversion percentage without showing the number of cases and how long they have been observed.

Two wins from four opportunities may justify continuing a test. They offer a fragile basis for a large hiring commitment.

Look across five areas:

• Demand: Can the team reach and engage suitable buyers beyond the founder’s relationships?
• Progression: Do buyers make meaningful commitments as opportunities develop?
• Independence: Which critical activities still require founder involvement?
• Economics: Do price, acquisition effort and delivery requirements support a viable motion?
• Customer value: Can customers achieve the outcome that justified buying?

These questions prevent one attractive number from carrying the entire decision.

Explain what caused the result

Suppose progression improves. Was discovery better? Did qualification remove unsuitable opportunities earlier? Did the founder quietly join every late-stage call? Did the business offer more favourable terms?

Those explanations imply different decisions about capacity.

In our fictional company, independently generated opportunities begin progressing within the additional-sites scenario. The seller can establish the problem and build the case for change.

Prospects requiring the missing integration continue to stall.

The revenue leader should make that pattern visible and quantify its commercial implications. The product leader must assess feasibility and priority. The CEO must resolve the trade-off between pursuing that segment and concentrating resources elsewhere.

More sales activity cannot make a missing product capability exist.

This is where accountability needs precision. Sales owns execution within its remit. Cross-functional constraints require decisions from people with the authority to remove them.

Respect the time needed for evidence

For a longer enterprise sales cycle, 90 days may produce stronger discovery, better stakeholder access and more credible evaluation plans.

Those are useful leading signals. They do not establish repeatable closing, delivery or retention.

Use mature historical deals where they are sufficiently comparable, state the limitations and continue observing the new opportunities. Set the next review around when meaningful evidence should become available.

By day 90, you should be able to distinguish what has been demonstrated, what remains plausible and what has been contradicted.

The test is whether the evidence supports the next increment of investment, with uncertainty made explicit.

5. Scale the part that has earned investment

Day 90 is a decision point. The CEO owns the investment decision, informed by the revenue leader and relevant functional owners.

The calendar does not certify repeatability.

At the review, make one of three decisions.

Scale selectively

The evidence supports adding capacity to a defined motion.

Specify the market, scenario, role and support required. Explain the bottleneck the investment removes and the assumptions behind the expected return.

Capacity might mean another seller. It could also mean implementation support, technical expertise or management time if those are the factors constraining a working motion.

The hiring plan should follow that diagnosis.

Continue proving

The signals are promising, but the sample, elapsed time or observed independence is insufficient.

Name the unresolved question. Define the evidence required and when it can reasonably be reviewed. Decide what level of spending is proportionate while uncertainty remains.

“Keep going” is too vague to manage.

Fix the constraint

The test has exposed a problem that blocks further investment: an unsuitable market, weak execution, an unresolved product gap, founder dependency or poor economics.

Give the issue an owner with the authority to act. Establish what must change before reconsidering scale.

Our fictional company chooses continued proof for the additional-sites scenario and a separate decision on the integration gap. Its original three-person hiring plan is deferred.

The business has gained a clearer investment case and avoided treating every source of revenue as evidence for the same expansion plan.

When capacity is added, keep testing whether the conditions hold. Changing geography, segment, channel and seller profile together creates a substantially different proposition.

Evidence for one motion gives you a basis for expanding that motion. Broader expansion needs its own justification.

The management system behind the model

None of this survives through a document alone.

The business needs a weekly rhythm that connects buyer evidence to coaching, operational changes and leadership decisions.

Review a manageable set of opportunities in enough depth to understand why they moved or stalled. Inspect calls alongside CRM records. Examine founder interventions. Challenge assumptions that are beginning to appear as facts.

Each review should end with specific actions, owners and a reason to expect those actions will help.

The founder contributes knowledge and progressively releases routine execution. The revenue leader owns the commercial system, including diagnosis and improvement. The CEO resolves constraints and priorities that cross functional boundaries.

As the business grows, first-line managers coach sellers and deals. Leaders of managers examine whether coaching, qualification and execution standards are consistent across teams.

A senior leader needs to know when to inspect an individual opportunity and when a recurring pattern requires a change to the system.

In a small company, one person may carry several of these responsibilities. Name the work anyway. Otherwise essential decisions disappear between job titles.

This is also why the revenue number must remain connected to how it was produced. An apparently healthy quarter can contain increasing founder intervention, weakening economics or customer commitments the business will struggle to fulfil.

Management needs visibility into those conditions before they become next quarter’s surprise.

The Scale Hack view

The central argument of this series is that growth decisions should be grounded in how the business actually wins.

A large market does not identify the customers you can win today. A prestigious sales CV does not establish stage fit. Pipeline volume does not establish buying intent. Founder-led revenue does not establish independent execution.

Each requires investigation.

Discover gives you an explanation worth testing. Codify makes the decisions usable. Transfer exposes whether capability can move beyond the founder. Prove establishes the boundaries of the evidence. Scale commits resources where that evidence supports them.

You may reach day 90 ready to hire. You may have narrowed the market, changed the motion or uncovered a product decision that needs to come first.

The value is a clearer basis for action.

Before approving the next sales hire, ask what they will inherit: a defined market, credible messaging, usable qualification standards, effective coaching and evidence that the motion works.

Then ask the question underneath the spreadsheet:

What exactly are we asking this person to repeat?

Where is the evidence that they can?

Make the next 90 days count

If this series has exposed gaps in your sales operation, the next step is to address them.

The Scale Hack programme helps founders turn the way they win today into a sales system their team can run, improve and scale.

Starting with the 6M Sales OS Diagnostic, we assess where you are, identify what is holding growth back and build a prioritised 90-day plan around your business.

The work focuses on outcomes that matter:

• Less dependence on you: identify and transfer the decisions that keep pulling the founder back into routine selling.
• Sharper commercial focus: concentrate effort on the customers and buying situations you can credibly win.
• More consistent execution: give sellers clear qualification standards, practical guidance and coaching they can apply.
• Better visibility: understand why deals move, where they stall and how much confidence to place in the forecast.
• More confident investment decisions: establish what needs fixing, what needs further proof and where additional capacity is justified.

The aim is a business where growth becomes more manageable, your team takes greater ownership and your next hire inherits a system they can use.