Search-to-Scale Readiness Scorecard

Scale One Motion, Not the Whole Product

The client-reporting product in the preceding confidence review has earned a careful next step. Small agencies return to send weekly reports, several have paid, and one has referred a peer. That evidence supports another comparable cohort.

It does not support every action usually hidden inside the word scale. Recruiting four more small agencies, buying a broad stream of leads, building roles for larger agencies, hiring support, and hardening the entire system are five different commitments. Each needs different evidence and exposes the founder to a different cost.

Use this scorecard when a defined segment and value path show credible pull and the founder is considering a durable investment. The scorecard tests one proposed motion at a time. It asks whether retained value, acquisition, delivery, dependency, economics, and founder capacity converge strongly enough to justify that motion—and what must remain in search.

Do not add the signals into a total. Strong retention cannot cancel a delivery process that consumes the founder. A repeatable channel cannot repair weak return behavior. A production incident can justify a repair without proving that acquisition should increase.

Name the Commitment Before Judging Readiness

“Move to scale” is too broad to approve or reject. State the customer, value path, proposed increase, durable work, and limit.

READINESS BOUNDARY
Decision due:
Segment, buyer, and operator:
Value path that customers repeat:
Natural cycle of that value path:
Proposed scale motion:
What will increase—accounts, usage, spend, commitments, or delegation:
Durable investment being considered:
Founder time and cash placed at risk:
Customer dependency placed at risk:
Time or cohort boundary for this decision:
Adjacent segments, features, and channels excluded:

A useful boundary for the reporting product is:

Recruit four more small agencies with weekly client meetings, test the standard import repair, and make only the setup path durable enough to learn whether those accounts can reach a first report without data cleanup. Do not increase paid acquisition, move upmarket, hire, or harden unrelated systems.

This is a transition experiment, not a declaration that the company has entered a new stage. Search and scale can coexist. The founder may standardize one repeated step while keeping pricing, acquisition, and adjacent segments deliberately reversible.

Read Six Conditions in Order

For each condition, use account-level evidence from the same segment and offer. Mark it blocked, emerging, or ready for this commitment, then write the observation behind the read. The words summarize judgment; they do not replace it.

Blocked means the condition contradicts the proposed motion or remains too unknown to place more customers or fixed cost behind it. Emerging means a coherent pattern exists but still depends on a small sample, few natural cycles, founder selection, manual rescue, or an untested change. Ready for this commitment means the pattern has repeated under conditions close enough to the proposed increase and no known failure makes that increase reckless.

1. Retained value

Start with the behavior worth making more durable. Which customers complete the value-producing workflow, return when the job recurs, and notice when the product fails? Keep activation, return, payment, renewal, and expansion tied to inspectable accounts. If retained users and paying users belong to different segments, the motion is blocked until the claim is narrowed.

RETAINED VALUE
Eligible accounts and exact denominator:
Repeated value event and natural-cycle window:
Payment, renewal, or expansion after value:
Founder prompts, discounts, and exceptions:
Strongest counterexample:
Read—blocked / emerging / ready for this commitment:
Why:

2. Reach

The proposed channel must bring back the kind of customer who retained, not merely traffic or demonstrations. Record the message, qualification boundary, conversion to the repeated value event, cash cost, and founder time. A channel can be manual and still be legible; it is not repeatable when every prospect requires a new story.

REACH
Channel and qualifying message:
Qualified accounts reached from this channel:
Accounts that activated, returned, and paid:
Cash and founder time per serious opportunity:
Capacity before response or follow-up degrades:
Read—blocked / emerging / ready for this commitment:
Why:

3. Repeatable delivery

Follow one account from promise to first value and return. Name every manual step, custom exception, support intervention, and recovery. Repeated founder work can be valuable evidence: it shows what may be standardized, productized, priced, documented, or delegated. It becomes a blocker when the scale motion would multiply work that is still different for every account.

DELIVERY
Promise-to-value path:
Steps that repeat across successful accounts:
Founder work per activation and natural cycle:
Custom work and exceptions:
Most common activation or support failure:
Step proposed for standardization or removal:
Read—blocked / emerging / ready for this commitment:
Why:

4. Customer dependency and system risk

Harden where real customers now depend on the product. Name the failure that could damage value, money, data, trust, or recovery, and the current evidence that it can occur. A hypothetical million-user bottleneck does not qualify. Neither does an impressive infrastructure project detached from the retained workflow.

Baseline security, privacy, backups, and recovery do not wait for scale. This condition asks what additional durability the proposed increase creates a reason to fund.

DEPENDENCY AND RISK
Workflow customers now depend on:
Observed incident, limit, or credible near-term failure:
Accounts, data, revenue, or trust exposed:
Detection and recovery today:
Minimum durable repair:
Speculative hardening explicitly deferred:
Read—blocked / emerging / ready for this commitment:
Why:

5. Economics

Revenue can conceal custom service, discounts, variable infrastructure cost, refunds, or support time. Use a range when the sample is small. The question is not whether a polished lifetime-value model exists. It is whether the proposed motion predictably improves the business or merely purchases more obligation.

ECONOMICS
Price and payment terms represented:
Revenue after discounts, refunds, and pass-through cost:
Founder delivery and support time per account:
Variable product and service cost:
Cost or commitment introduced by this motion:
Economic assumption most likely to fail:
Read—blocked / emerging / ready for this commitment:
Why:

6. Founder capacity

Finish with the constraint that often disappears from a company-shaped plan. Name the bottleneck as a repeated action in a known motion, not as “too busy.” Estimate what the proposed increase would do to sales follow-up, support, recovery, product judgment, and personal operating limits. Hiring is justified only when the work is stable enough to hand over and the founder can support the commitment.

FOUNDER CAPACITY
Repeated bottleneck:
Current hours or interruptions per natural cycle:
Load added by the proposed increase:
Work that can be removed, automated, priced, documented, or delegated:
Work that still requires founder judgment:
Failure signal that would stop the motion:
Read—blocked / emerging / ready for this commitment:
Why:

Let the Commitment Meet Its Blocking Condition

Now read across the six conditions without averaging them. The proposed motion can proceed only as far as its relevant blocking condition allows.

If retained value is blocked, return to customer and product search. If reach is blocked, do not buy more traffic; test a narrower channel or message. If delivery is blocked, expose fewer accounts while removing or standardizing the repeated burden. If dependency is blocked, repair the customer-facing failure before increasing exposure. If economics is blocked, change price, promise, scope, or delivery. If founder capacity is blocked, reduce the motion before considering automation or help.

An emerging condition usually permits another bounded cohort or a reversible repair, not a permanent team, broad campaign, annual contract, or major platform investment. A condition that is ready for one commitment may be blocked for a larger one. Founder-led outreach may be ready for eight more accounts while broad paid acquisition remains untested.

Complete the decision in ordinary language:

SEARCH-TO-SCALE DECISION
Proposed motion:
Condition that limits it:
Decision—stay in search / run a transition experiment / scale one motion:
Evidence that authorizes this decision:
First durable investment:
Accounts, spend, usage, or time exposed:
Success behavior by the next natural cycle:
Stop or reversal condition:
Work explicitly not authorized:
Review date or cohort boundary:

Read the Reporting Product Honestly

For the small-agency reporting product, retained value is emerging: four of five activated accounts returned at the next weekly cycle, three paid, and the same recurring job appears across the accounts. Reach is emerging too, but it comes mainly through the founder and has not demonstrated capacity beyond a small cohort.

Delivery blocks broad acquisition. Three of the five successful activations needed data-mapping help, and founder load averages 35 minutes per active account. The proposed import repair has not yet carried an account to first value. Customer dependency and economics are still bounded: no observed system failure calls for broad hardening, and the small paid sample does not yet show what support load looks like beyond the first cycles.

The honest decision is to run a transition experiment with four comparable agencies. The first durable investment is the narrow import path because it addresses repeated work on the retained value path. Success means that the new accounts produce a first client-ready report without founder data cleanup and return at the following weekly cycle. If two accounts require bespoke cleanup, or support load causes existing customer work to slip, stop the cohort and return to delivery search.

This decision does not authorize paid acquisition, custom roles for larger agencies, a support hire, or a general reliability program. Those commitments have not earned the same confidence.

Preserve the Evidence After the Decision

Attach the cohort, revenue, channel, support, incident, and founder-time records behind the review. Preserve contrary accounts and definition changes. At the next boundary, compare what happened with the expected behavior; do not rewrite the old decision so it appears inevitable.

The scorecard is complete when a skeptical future reader can see why one motion received durable effort, why its exposure is bounded, and what remained in search. Scale begins with a specific obligation to make proven value more repeatable. Everything else still has to earn its turn.