From 0 to 1, 10, 100: When the Growth Stage Changes, the Operational Focus Must Change Too

01 GSP analysis

First determine whether validation, replication, or synergy is needed

The stages from 0 to 1, 1 to 10, and 10 to 100 are tools for discussing growth stages; they do not correspond to revenue, headcount, or store count, nor are they strictly linear. Different businesses can have multiple stages coexisting, and mature companies launching new ventures may return to validation. The core of stage determination is identifying which aspect currently most needs validation, replication, or synergy, thereby deciding where to allocate resources.

A specific operational issue is that many companies mistakenly equate stage with scale metrics, leading to premature channel expansion when value validation is needed, or relying on individual talent when replication is required. For example, suppose a chain restaurant company has a new delivery brand with steady orders, but if it hasn't identified the success factors, rapid store expansion may fail due to inconsistent service. At this point, the judgment should be: is the bottleneck that value is unvalidated, or that replication mechanisms are not yet formed?

The causal mechanism is that stage determines the key constraint: from 0 to 1, the constraint is whether the value hypothesis holds; from 1 to 10, whether actions are repeatable; from 10 to 100, whether synergy is smooth. The condition for success is that the team can distinguish between accidental success and systematic capability, and is willing to adjust resource priorities. In a hypothetical scenario, if a promotion brings many new customers but repeat purchase rates are low, it indicates that value validation is incomplete, not that growth is replicable.

A practical operation is to answer quarterly for each business unit: do we most need to validate, replicate, or synergize? And list evidence. Rebuttable signals include: if resource investment does not change key metrics, or if the team keeps discussing the same issue, the stage judgment may be wrong. In such cases, re-examine rather than mechanically proceed.

02 GSP analysis

The OECD comparison: growth stages do not follow company age

OECD examines scaling through different investment and transformation paths rather than studying only newly founded businesses. In this article, “0 to 1, 1 to 10, and 10 to 100” is GSP's metaphor for operating tasks. It is not an OECD statistical definition or a fixed revenue threshold. One company may face several stages at once: its core business needs organizational coordination, a new product is still testing willingness to buy, and a new region is examining whether established practices travel.

GSP therefore proposes diagnosing the product–customer–channel business unit. Each unit records its value hypothesis, transactions that have actually occurred, delivery capability and next constraint, rather than assigning the whole company a permanent stage label. This changes resource decisions. Experience from a mature business may support a new one, but it cannot replace evidence of demand in a different market. A new venture needs a learning budget, but cannot borrow established delivery staff indefinitely. Its owner should define the scope, duration and return conditions for shared resources. Stage review becomes a discussion of coordination as well as growth. The question is not which team is more advanced, but which task deserves attention now and which proposed expansion still lacks a necessary condition. A manager can consequently maintain standardized operations in one unit while permitting bounded exploration in another, without treating either approach as the universal answer.

03 GSP analysis

A Toyota process comparison: identify what should not be replicated

Toyota emphasizes detecting abnormalities and preventing their onward passage. In a discussion of growth stages, this offers a process comparison for the quality of replication, not a guarantee of business expansion. Early success may depend on the founder's explanation, a familiar customer's tolerance or an employee's extra recovery work. Copying only the sales script, without recording those hidden compensations, can make delivery deviations harder to see as customers and locations multiply.

GSP proposes tracing a real order from promise to acceptance before attempting replication. Identify which steps an ordinary role can already perform reliably, which still depend on a particular person, and which exceptions should pause order taking or change the promise. A pilot can deliberately include orders without the conveniences present in the original success, testing whether documentation, training and tools can support delivery on their own. Where gaps appear, revise the template, responsibilities or assortment before expanding, rather than asking key staff to compensate permanently. Process discipline does not remove uncertainty from exploratory work. An experiment with a new value proposition may fail, but a delivery already promised to a customer needs an executable remedy. Separating those task types preserves learning speed without treating an early, contingent success as a capability ready for scale. It also makes the evidence for the next expansion decision more concrete than a general claim that the team has become mature.

04 GSP analysis

From 0 to 1, validate user choice, not just collect approval

The core of the 0 to 1 stage is not collecting positive feedback, but validating whether real users are willing to support the value proposition with actions. Agreement in interviews, willingness to experience, actual usage, and sustained purchase represent signals of increasing strength, with correspondingly higher credibility. Teams should clarify the value hypothesis that most needs validation and design rebuttable tests around it.

In practice, first define a clear core audience, describe their typical scenarios and existing alternatives, then propose a hypothesis: users will choose us because of a specific unique value. A daily business example (hypothetical): a food ingredient delivery service for small restaurants hypothesizes that owners will switch to the service because it reduces procurement time. The team can invite target owners to try it and observe whether they place orders in real operations, rather than just listening to verbal approval.

Validation must distinguish different levels: interview agreement may be influenced by politeness or context, willingness to experience reflects initial interest, actual usage exposes real obstacles, and purchase is the strongest commitment. If users frequently try but do not buy, the value hypothesis may be invalid; if post-purchase repeat rates are low, delivery capability is questionable. Rebuttable signals include: no active search by the core audience, no conversion after trials, or extreme price sensitivity.

For implementation, it is recommended to conduct in-depth interviews with 20 target users over two weeks, invite 10 of them to participate in prototype testing, and record their success rates in completing key tasks. Also track feedback after the first transaction to see if users actively recommend. If most users say 'it's good' but take no further action, treat the hypothesis as failed and adjust the value proposition or audience, rather than increasing marketing spend.

05 GSP analysis

Constraints exposed by the first delivery determine next investments

In the value validation phase, product experience, service delivery, and real user feedback must be tested simultaneously. Suppose a small consulting firm provides initial process diagnostics to five manufacturing companies, promising to deliver an actionable improvement checklist within one week. If clients receive the checklist on time and adjust their production scheduling accordingly, it indicates that the value hypothesis is initially valid; if clients feedback that the content is generic and not actionable, the problem may lie in delivery capability rather than demand judgment.

When delivery exposes constraints, the team needs to distinguish between two types of signals: first, users do not approve of the solution itself, manifested by refusal to pay or explicit statements like 'this is not what we need,' which points to the value hypothesis being invalid; second, users approve of the direction but complain about slow response or rough reports, which points to insufficient service capability or resource allocation. The former should return to redefining users and scenarios, while the latter requires optimizing processes, supplementing skills, or adjusting tools.

Suppose in the second service, the team finds that clients value immediate feedback after on-site interviews more than written reports. If the team still invests in report polishing according to the original plan, it deviates from the true value. A practical approach is: after each delivery, record users' specific actions, unmet requests, and churn points, and review weekly, categorizing feedback into 'misunderstanding of needs' or 'execution shortcomings.'

If users verbally approve but are reluctant to actually use, choose again, or recommend, first review the reasons for choice and delivery experience, and do not judge the value hypothesis as valid based on a single signal. Faster delivery but recurring problems may also indicate that the verification step is being compressed, rather than users not needing the service. It is recommended to map different situations to original records, then decide whether to adjust the proposition, strengthen capabilities, or change the order of work; before the cause is distinguished, continuing to expand marketing may cause the same problem to recur.

06 GSP analysis

From 1 to 10, first separate accidental factors in a single success

Entering the 1 to 10 stage, the core issue is no longer whether value is valid, but whether growth can be repeated. A successful sales campaign, an outstanding store performance, or even the personal abilities of a few core employees can make the team mistakenly believe the model is proven. To identify accidental factors, break down success into specific actions and conditions: does this result depend on the founder personally negotiating, extra support from a special client, large discounts, or scarce resources? If these conditions are removed, would the same actions still yield similar results?

Suppose a regional restaurant brand sees significant monthly revenue growth because the founder invited food bloggers to visit, bringing a short-term influx of customers. If the team directly replicates this blogger visit action in other cities, they may find diminishing returns because the original success depended on the founder's personal relationships and the specific city's media environment. A safer approach is to first fix the necessary replicable conditions, such as product quality standards, service flow, and repurchase mechanisms, then test in small scale with different implementers or scenarios.

Repeatability is not about copying forms. Teams often mistake surface actions for mechanisms, such as seeing others succeed with live-stream selling and thinking live-stream is a panacea, while ignoring the underlying product selection logic, supply chain responsiveness, and after-sales capabilities. To distinguish which factors are necessary conditions for business success and which are accidental boosts, design controlled experiments: under similar conditions, have different personnel execute the same process and observe whether results are stable; or test in different regions and customer groups to see which aspects remain effective.

In daily operations, rebuttable signals include: when the founder is absent, new customer acquisition speed drops significantly; or when discounts stop, repurchase rates quickly fall. These signals indicate growth still relies on individuals or short-term stimuli, not systematic capability. A practical operation is to create a 'success breakdown checklist' for each review, marking: which actions in this growth can be standardized, which depend on specific resources, and which need further validation. Through continuous breakdown and validation, gradually turn accidental success into repeatable operational mechanisms, laying the foundation for the next stage of scale expansion.

07 GSP analysis

Relationships and channels must jointly support repeatable operations

In the 1 to 10 stage, a common operational problem is: a marketing campaign brings sales, but repurchases plummet the next month; a store performs outstandingly, but it is difficult to replicate in other stores. The causal mechanism is that success often mixes accidental factors, such as the founder personally selling, special customer resources, or limited-time discounts, and the team has not yet identified the core variables that truly drive user choice and retention. The condition for success is that the company can break down the complete user journey from content exposure to experience, transaction, service, and repurchase into observable steps, and define consistent event standards (such as 'valid lead' and 'activated user').

Suppose a SaaS company's first batch of customers comes from the founder's industry network, with high renewal rates. When the growth target shifts to 1 to 10, the team hypothesizes that 'customer success visits' are key to repurchase, but does not verify whether customers from other channels need the same. In daily business, they can compare behavioral data of customers from different sources. If they find that the activation rate of advertising-sourced customers is significantly lower than that of referral customers, it indicates a gap in value proposition communication or the onboarding process. At this point, relationship management (such as regular visits) can improve retention, but without standardized processes, effectiveness will depend on individual employee experience.

Practical operations include: mapping channel roles along the user journey, clarifying the tasks of content, experience, transaction, and service; establishing unified behavioral event definitions for users from different sources, observing conversion differences from first contact to repurchase; distilling effective experiences into operational manuals and service SOPs, and setting up feedback loops for frontline teams to regularly submit evidence of 'what works and what doesn't.' Meanwhile, relationship management and process building are interdependent: relationship maintenance provides qualitative insights, and processes ensure insights translate into consistent actions.

Rebuttable signals include: if after changing implementers, repurchase rates drop significantly, the process is not truly solidified; if behavioral differences among users from different channels cannot be explained by existing data, event definitions may be too coarse; if the team relies on special resources (such as exclusive discounts) to maintain growth, replication conditions are not met. When these signals appear, the company should return to the starting point of 1 to 10 and re-break down success factors, rather than blindly expanding investment.

08 GSP analysis

From 10 to 100, synergy must be written into organizational interfaces

As scale grows from 10 to 100, business often spans more regions, channels, products, and teams simultaneously. At this point, synergy is no longer a naturally formed tacit understanding but a mechanism that needs to be explicitly written into organizational interfaces. Organizational interfaces refer to the handover points and rules in collaboration between different teams and functions. If these interfaces are vague, common problems include: brand information expressed inconsistently across channels, service standards deviating in different regions, experience remaining only within individual teams, and inconsistent data definitions leading to decision conflicts.

To avoid two extremes: one is that all matters require headquarters approval, leading to slow decisions and loss of local flexibility; the other is complete laissez-faire, where teams operate independently, and brand promises and user experience gradually diverge. A feasible approach is to first clarify which brand commitments must be consistent nationwide, such as core value propositions and key service bottom lines; and which aspects allow local variation, such as promotional methods and channel combinations. On this basis, set up experience-sharing mechanisms so effective practices from different markets can be seen and referenced; establish escalation paths for anomalies, providing clear feedback channels when local issues exceed authorized scope; unify data maintenance responsibilities to ensure consistent definitions of key metrics; and establish rules for resolving resource conflicts to avoid cross-regional competition for limited resources.

Suppose a chain service brand, after expanding to a new city, finds rising customer complaint rates. If organizational interfaces are missing, each store may adjust service processes on its own, leading to inconsistent experiences. By clarifying the authority boundaries between headquarters and regions, with headquarters retaining core service standards and regions adjusting local details, while establishing weekly experience-sharing meetings and anomaly reporting systems, consistency can be maintained while preserving flexibility. This is a hypothetical example to illustrate how interface mechanisms operate, not an actual case.

Practical operations include: drawing cross-departmental collaboration flowcharts, marking key handover points; assigning responsible persons and decision authority for each interface; establishing regular cross-regional review meetings to share successes and failures; using shared data dashboards to ensure real-time visibility of key metrics. Rebuttable signals are: if after expansion, customer satisfaction declines, internal communication costs rise, or new markets rely long-term on headquarters decisions, the synergy mechanism is not effectively established. In such cases, check whether interface rules are clear, rather than simply adding approval layers.

09 GSP analysis

The proportion of mindshare, relationships, and capabilities should shift with bottlenecks

Investment in mindshare, relationships, and capabilities is not evenly distributed but dynamically moves with stage bottlenecks. All three always occur simultaneously, but there is no fixed weight for resource allocation, and industry ratios cannot be directly applied. The key to determining the allocation is to use the core questions of each stage and stage outputs to discuss the opportunity cost of resources: if the current bottleneck is that value is not validated, more brand exposure cannot bring sustained choice; if the bottleneck is that experience cannot be replicated, single-point success cannot be scaled.

Suppose a company is moving from 1 to 10, but finds that new customer growth depends on the founder's personal negotiations. Then the bottleneck lies in a repeatable customer acquisition mechanism, not insufficient brand awareness. At this point, resources should shift from expanding exposure to mapping the user journey, fixing sales actions, and using consistent definitions to observe the performance of users from different sources. If the team still invests in mindshare building according to the inertia of 0 to 1, it will miss the window for process consolidation.

Conversely, if the company has entered the 10 to 100 stage but still allocates most resources to single-point validation, synergy capabilities will lag. At this time, use the T5 original definition to check strategic planning and execution: whether brand upgrading clarifies long-term direction, whether business transformation and data unification support cross-departmental planning, and whether channel coordination and user management ensure continuous experience. If digital tools lack clear users and feedback methods, investment may become a formality.

A practical approach is to list quarterly for each business unit: current stage, main bottleneck, resource allocation, and actual proportions of the three capabilities, and check against stage outputs for mismatch. Rebuttable signals include: key metrics not improving but brand activities continuously increasing, or process documents complete but no one executes them. When these signals appear, adjust budget priorities to let resources flow to the real bottleneck.

10 Suggested actions

Establish a stage review that can change budget priorities

The core of stage review is to make resource allocation change with operational focus, rather than mechanically following a fixed cycle. Companies can record four types of information for each business unit: evidence for the current stage judgment, main hypotheses being tested, specific questions to validate next, and the resources, responsible persons, and feedback mechanisms needed for validation. The value of this record is that it forces the team to turn 'which stage we are in' from a verbal judgment into a verifiable written basis, avoiding budget decisions based solely on intuition or inertia.

In specific operations, a common problem is that resources are still allocated according to the logic of the previous stage. For example, a company has validated its core value from 0 to 1 and entered the replication stage from 1 to 10, but the budget still heavily invests in brand advertising rather than channel sorting and operational process consolidation. At this point, the stage review should reveal: is the current bottleneck that value is not understood, or that growth actions are not repeatable? If the hypothesis is the latter, budget should shift toward user journey breakdown, content method consolidation, and feedback mechanism building.

Suppose a daily business example: a chain restaurant brand, after succeeding with one store, plans to expand to ten. The team hypothesizes that 'dish taste is the key to replication,' but the review finds that the single store's success depends on the founder's on-site management. Thus, the next validation can be set as: can a new store maintain food quality and customer ratings without the founder? Required resources include standardized operation manuals, store manager training systems, and customer feedback collection tools. If validation fails, the replication premise is not established, and the company needs to revisit the value hypothesis or adjust expansion pace.

Practical operations are: at the end of each quarter or operating cycle, the business leader convenes a review meeting to check hypotheses and evidence item by item, and clarify which tasks to retain or cancel. Rebuttable signals include: budget allocation clearly misaligned with stage focus, key hypotheses long untested, or feedback mechanisms unused. If these signals appear, adjust resource priorities immediately, rather than waiting for fixed nodes.

11 Suggested actions

Allow returning to validation to preserve room for correction during expansion

When a company enters the expansion phase, changes in demand, weak repurchase, or handover anomalies are often early signals. At this point, it is recommended to pause expansion and re-examine whether the value hypothesis and replication premises still hold. For example, suppose in a certain region, new customer growth slows and repeat purchase rates decline. This may mean the original value proposition fails in new scenarios, or the replication process depended on specific conditions. Pausing expansion is not regression but preserving space for correction, avoiding amplifying investment in the wrong direction.

The causal mechanism of re-examination is that expansion is usually based on validated success from 0 to 1, but changes in market environment, user preferences, or competitive landscape may invalidate these premises. If signals are ignored and replication continues as planned, it may lead to resource waste and organizational inertia. The condition for success is that the company can distinguish temporary fluctuations from structural changes and has a decision mechanism for rapid adjustment.

In specific operations, establish anomaly monitoring indicators, such as repurchase rate, customer churn rate, and delivery cycle. When indicators deviate from thresholds, trigger a re-examination process. Re-examination requires cross-departmental collaboration to re-evaluate user needs, value propositions, and replication processes, and clarify which information still needs verification. For example, if the hypothesis is that users in new markets have the same pain points as old markets, but actual feedback shows higher price sensitivity, adjust the value proposition or replication strategy.

Rebuttable signals include: after re-examination, the hypothesis still holds, but execution deviations cause problems, so no pause is needed; or the problem stems from external short-term shocks rather than structural changes. In such cases, continue expansion but optimize execution. When managing mature core businesses and new ventures with parallel goals, set clear priorities to ensure resource allocation aligns with stage objectives. Ultimately, allowing return to validation is to ensure expansion is built on continuous validation, not blind replication.