Integrating the Elements of Scaling Evidence into Repeatable Growth

From directional PMF to repeatable growth

Directional product-market fit means a wedge works in a defined beachhead with assistance. Repeatable growth means a new logo can onboard, activate, retain, and pay with a documented playbook, predictable unit economics, and channel mechanics that do not depend on the CEO's Rolodex.

Scaling is not spending more on ads. It is proving that the last dollar of acquisition produces a customer that looks like the best current customers, without founder heroics.

RelayOps is the anchor venture for ENT 402. Founders Maya Chen (CEO, former dispatch manager) and Jordan Okonkwo (CTO) completed customer discovery in ENT 401: 28 discovery interviews in ENT 401 confirmed dispatch managers lose roughly 14% of revenue to missed appointments, double-bookings, and slow emergency routing. Their beachhead is mid-market commercial HVAC operators in Phoenix and Dallas with 50 to 150 field technicians. Interview evidence suggested $89 to $149 per technician per month for software that reliably solves dispatch chaos.

After Units 1 through 3 (MVP strategy, experiment design, activation and retention), RelayOps ran five pilot customers (three in Phoenix, two in Dallas), covering 87 technicians at $119 per technician per month. Monthly recurring revenue (MRR, the subscription revenue recognized each month) reached $10,353 ($124,236 ARR, annual recurring revenue). Emergency dispatch median improved from 12 minutes median emergency dispatch time before RelayOps to 4.2 minutes. four of five pilots renewed after 90 days (80% logo retention). The Sean Ellis survey scored 42% of active dispatchers chose very disappointed if RelayOps disappeared, above the commonly cited 40% threshold for early PMF (product-market fit, evidence that a product satisfies strong demand in a target segment).

Month 7: RelayOps holds seven logos, $12,019 MRR, onboarding v2 playbook, founder hours 3.1 per logo. Maya wants to hire an SDR (sales development representative, outbound prospecting role). Jordan wants self-serve signup. This unit integrates ENT 402 evidence into a growth system.

Repeatable growth is the capstone evidence standard for ENT 402. RelayOps must show that logo eight and nine behave like logos three and four without Maya sleeping in the dispatch room. Integration means every prior unit output appears in one Q3 operating plan with owners.

Repeatable growth is the capstone evidence standard for ENT 402. RelayOps must show that logo eight and nine behave like logos three and four without Maya sleeping in the dispatch room. Integration means every prior unit output appears in one Q3 operating plan with owners.

Integrating scaling evidence means every prior unit artifact appears in one operating plan with owners and budgets. RelayOps Q3 plan names Maya owner of channel tests, Jordan owner of analytics instrumentation, customer success owner of activation gates. Repeatability checklist failures block spend even when MRR grows. Association channel partial pass prevents SDR hire but justifies a second sponsorship with revised activation rescue timing. Referral loop experiments cost little cash but require CRM hygiene to attribute pipeline correctly. The pre-scale plan is versioned and linked from board decks so investors see falsifiers, not only TAM slides.

The repeatability checklist

Before scaling spend, RelayOps checks: (1) Playbook: onboarding steps documented with time estimates, (2) Metrics: new logos hit weekly active gates without founder on-site, (3) Economics: CAC payback within 18 months on gross margin, (4) Support: success hours ≤2 per logo, (5) Sales cycle: median days from qualified lead to go-live stable across 3+ logos.

Missing any item means growth experiments stay bounded. RelayOps fails item 3 today because CAC not yet measured with paid channel.

Repeatability is segment-specific. Phoenix repeatability does not prove Dallas without another cohort read.

Repeatability checklist item "sales cycle stable" requires median and interquartile range, not one fast deal.

Repeatability checklist item "sales cycle stable" requires median and interquartile range, not one fast deal.

RelayOps repeatability scorecard (month 7):

Growth loops vs one-off sales

Growth loops are mechanisms where existing usage generates new demand: referrals, technician job switches that carry RelayOps to new employers, HVAC trade association demos. One-off sales are founder dinners. Loops scale; dinners do not.

RelayOps loop candidate: dispatch managers at Sunbelt Service refer peers after comparing emergency metrics at association meetup. Track referral-sourced pipeline separately.

Scaling spend should attach to loops with measurable conversion, not hope.

Growth loops deserve experiment IDs like product tests. GRO-001 association sponsorship tracked in registry.

Growth loops deserve experiment IDs like product tests. GRO-001 association sponsorship tracked in registry.

Channel fit as a second PMF problem

Product-market fit without channel fit (a acquisition path that reaches ICP at viable CAC) stalls companies. RelayOps ICP: 50-150 tech commercial HVAC, Phoenix/Dallas. Channels to test: founder network (proven), HVAC association sponsorships, LinkedIn outbound to ops titles, partner referrals from equipment distributors.

Each channel gets a mini PMF scoreboard: meetings booked, qualified rate, pilot conversion, weekly active at day 45, CAC.

Do not scale a channel until two consecutive cohorts match founder-led activation.

Channel fit mini scoreboards mirror PMF scoreboards: same threshold discipline, different funnel stages.

Channel fit mini scoreboards mirror PMF scoreboards: same threshold discipline, different funnel stages.

Integrating experimentation units into a growth plan

ENT 402 arc: MVP assumptions → experiment design → activation/retention → PMF signals → pivot discipline → scaling evidence. The pre-scale experimentation plan deliverable is the written integration: which assumptions are retired, which metrics govern scale gates, which channel tests run in quarter three.

RelayOps plan header: "Scale emergency dispatch wedge in Sun Belt commercial HVAC via playbook-led outbound and referrals; do not expand SKU until schedule beta passes guardrails on second metro."

Integration prevents scaling the wrong proof point.

Pre-scale plan section headers map 1:1 to course units for grader and board readability.

Pre-scale plan section headers map 1:1 to course units for grader and board readability.

Organizational readiness without over-hiring

Repeatable growth requires roles, not necessarily large teams. RelayOps month 7 org: Maya sales/founder, Jordan product/engineering, part-time CS (customer success, post-sale adoption support), contract bookkeeper. SDR hire deferred until channel test shows CAC ≤$18,000 per logo at 20-tech average ($2,380 MRR), payback 7.6 months on 80% gross margin ($1,904/month gross profit per logo). Check: 18,000 / 1,904 ≈ 9.5 months; refine to 18-month payback requires CAC ≤$34,272 or higher ARPA.

Hire when gates pass, not when investors suggest headcount as progress signal.

Organizational readiness: part-time CS at 9 logos is bridge staffing, not scale staffing.

Organizational readiness: part-time CS at 9 logos is bridge staffing, not scale staffing.

RelayOps integrative read: Integrating the Elements of Scaling Evid

RelayOps founders Maya Chen (CEO, former dispatch manager) and Jordan Okonkwo (CTO) use this lesson's frameworks against live pilot data: 87 technicians, $10,353 MRR, 4.2 minutes median dispatch, 78% weekly active dispatchers, four of five pilots renewed after 90 days (80% logo retention). Numbers reconcile across examples in this lesson when assumptions are stated explicitly.

Managers reading this lesson without a dashboard should still extract decision rules: define the segment and job, predeclare thresholds, separate leading from lagging signals, document churn logos alongside renewals, and tie scale bets to falsifiers. RelayOps applies those rules before every board send and every roadmap sprint plan.

The ENT 401 discovery baseline (28 discovery interviews in ENT 401 confirmed dispatch managers lose roughly 14% of revenue to missed appointments, double-bookings, and slow emergency routing) remains the anchor for ROI (return on investment, value gained versus cost) storytelling. If dispatch improvements did not connect to revenue leakage reduction, PMF metrics would be technically interesting but commercially irrelevant. RelayOps estimates 14% revenue at risk on a $12M ARR (annual recurring revenue, yearly revenue run rate) HVAC firm equals $1.68M exposure. Cutting emergency dispatch from 12 to 4.2 minutes contributes to recapturing part of that leakage; PMF measurement tracks whether customers believe the connection enough to renew.

Cross-functional alignment means Maya (GTM), Jordan (product/engineering), and customer success read the same scoreboard definitions. When definitions diverge, PMF debates become political. Written charters and event taxonomies prevent drift. This integrative habit closes the loop between Scaling Evidence into Repeatable Growth theory and RelayOps operating reality.

RelayOps integrative read: Integrating the Elements of Scaling Evid

RelayOps founders Maya Chen (CEO, former dispatch manager) and Jordan Okonkwo (CTO) use this lesson's frameworks against live pilot data: 87 technicians, $10,353 MRR, 4.2 minutes median dispatch, 78% weekly active dispatchers, four of five pilots renewed after 90 days (80% logo retention). Numbers reconcile across examples in this lesson when assumptions are stated explicitly.

Managers reading this lesson without a dashboard should still extract decision rules: define the segment and job, predeclare thresholds, separate leading from lagging signals, document churn logos alongside renewals, and tie scale bets to falsifiers. RelayOps applies those rules before every board send and every roadmap sprint plan.

The ENT 401 discovery baseline (28 discovery interviews in ENT 401 confirmed dispatch managers lose roughly 14% of revenue to missed appointments, double-bookings, and slow emergency routing) remains the anchor for ROI (return on investment, value gained versus cost) storytelling. If dispatch improvements did not connect to revenue leakage reduction, PMF metrics would be technically interesting but commercially irrelevant. RelayOps estimates 14% revenue at risk on a $12M ARR HVAC firm equals $1.68M exposure. Cutting emergency dispatch from 12 to 4.2 minutes contributes to recapturing part of that leakage; PMF measurement tracks whether customers believe the connection enough to renew.

Cross-functional alignment means Maya (GTM), Jordan (product/engineering), and customer success read the same scoreboard definitions. When definitions diverge, PMF debates become political. Written charters and event taxonomies prevent drift. This integrative habit closes the loop between Scaling Evidence into Repeatable Growth theory and RelayOps operating reality.

Managerial synthesis and next review gate

Every ENT 402 lesson ends with a managerial question a board member could ask. For Integrating the Elements of Scaling Evidence into Repeatable Growth, the answer must cite RelayOps numbers, not general startup wisdom. Practice stating the recommendation in two sentences: what we believe, what would falsify it within 60 days.

RelayOps documents the next review date on the decision log before closing the meeting. Review gates include metric thresholds, owner names, and budget caps. This prevents "we will look at it again" without a calendar anchor.

Students applying this lesson to another venture should replace RelayOps constants with their own reconciled figures while keeping the same structural rigor: two worked examples, explicit check lines, mistakes table, practice solution, five takeaways, three after prompts. Depth comes from specificity, not adjectives.

Unit 6 lesson 1 connects backward to prior ENT 402 units and forward to the pre-scale experimentation plan deliverable. RelayOps is intentionally narrow (commercial HVAC, emergency dispatch, Sun Belt metros) so you can trace every metric to a named customer logo and dispatcher cohort.

RelayOps month-by-month operating notes reinforce this lesson: Maya publishes a one-page metric appendix after every board meeting; Jordan links each shipped feature to a scoreboard row or falsifier; customer success logs weekly active exports with logo and metro tags. When Desert Cool expanded technician seats, MRR increased by $714 (6 × $119) while weekly active held at 89%, showing expansion without adoption decay. When North Ridge churned, the team lost $1,428 MRR (12 × $119) but gained clarity on owner-training requirements now embedded in onboarding v2. These operating habits turn frameworks into evidence investors can diligence. Students should mirror the habit: every recommendation in your pre-scale plan links to a number, a date, and a named owner.

Team maps ENT 402 outputs into Q3 growth plan. Budget for channel tests: $25,000 over 12 weeks.

Q3 budget $25k is 8.3% of remaining runway $301k. Check: 25/301 ≈ 8.3% ✓

Q3 budget $25k is 8.3% of remaining runway $301k. Check: 25/301 ≈ 8.3% ✓

Part A: Evidence integration map

MVP unit: emergency wedge validated. Experiment unit: replication falsifier drove onboarding v2. Activation unit: weekly active gate 70%. PMF unit: directional claim, $12,019 MRR. Pivot unit: schedule paused, price test running. Scale unit: test association channel + referral loop.

Part B: Q3 bounded channel test

HVAC association Phoenix chapter: $8,000 sponsorship + 2 demos. Target: 6 qualified ops leaders, 2 pilots, CAC cap $12,000 per won logo (25% of $8k + $4k founder time allocated across 2 wins). Success: both pilots ≥70% weekly active day 45.

Referral incentive: one month free per referred logo that renews (cost ~$119 × 20 techs = $2,380 foregone revenue, cap 3 per quarter).

Part C: Scale gate

If association channel produces 2/2 pilots passing gates with fully loaded CAC ≤$15,000, approve SDR hire Q4. Else continue founder-led with playbook refinements. Runway: $301k − $25k test = $276k. Check: 276 ✓

Q3 budget $25k is 8.3% of remaining runway $301k. Check: 25/301 ≈ 8.3% ✓

Q3 budget $25k is 8.3% of remaining runway $301k. Check: 25/301 ≈ 8.3% ✓

Part D: Managerial read

Investor: "Double down on winning product." Managerial read: product won in beachhead; channel not proven; $25k test buys repeatability evidence cheaper than $120k AE year-one fully loaded.

Additional board probe: ask what sample size would upgrade RelayOps from directional to statistical confidence. Answer: typically 10+ logos in beachhead with similar weekly active variance bands, or 30+ Sean Ellis responses on a fixed cohort definition.

GrowFleet (fictional) scaled paid search before playbook existed. 14 logos acquired, weekly active 41% average, CAC $28k, churn 35% year one. Product worked for founder-sold logos. RelayOps integration checklist blocks that path until unassisted activation passes.

GrowFleet scaled paid search with 41% weekly active on acquired logos versus 79% founder-led.

GrowFleet scaled paid search with 41% weekly active on acquired logos versus 79% founder-led.

RelayOps contrast case reinforces the same unit theme: measure what matters for the core job, document failure modes honestly, and tie recommendations to runway months and falsifiers rather than narrative momentum.

Association test results: 5 qualified leads, 2 pilots, 1 churned day 30 (weekly active 44%), 1 active at 73% weekly active. Spend $9,200. Average logo 18 techs at $129.

Tasks: (1) Compute CAC per won logo (2 pilots started, 1 retained). (2) Pass or fail scale gate? (3) One integration fix for pre-scale plan.

(4) One retained logo fails 2/2 pilot pass rule; continue channel test with activation rescue.

(4) One retained logo fails 2/2 pilot pass rule; continue channel test with activation rescue.

Show all arithmetic with a check line. State segment scope (RelayOps commercial HVAC beachhead unless otherwise noted).

Solution

(1) CAC = $9,200 / 1 retained = $9,200 per retained logo. Check: 9,200 ✓ (below $15,000 cap).

(2) Partial pass: CAC pass, but n=1 retained logo fails "2/2 pilots pass gates" rule. Continue founder-led + second association event; defer SDR.

(3) Add activation rescue playbook trigger at day 14 if weekly active <60%, before day 30 churn.

(4) Defer SDR; run association v2 with day-14 rescue playbook from practice integration fix.

(4) Defer SDR; run association v2 with day-14 rescue playbook from practice integration fix.

Managerial read: document this solution in the decision log with date, owner Maya Chen, and review trigger in 30 days.

Repeatability also means finance can model CAC payback without founder adjustments. RelayOps builds a simple spreadsheet: CAC numerator includes sponsorship, travel, and allocated founder sales hours; denominator uses activated logos only, not pilots still in onboarding.

Key takeaways

• Repeatable growth requires playbook, economics, and unassisted activation.
• Channel fit is a second PMF problem with its own scoreboard.
• Integrate all ENT 402 units into the pre-scale experimentation plan.
• Favor growth loops and referrals before paid scale.
• Hire into proven channels, not into hope.

1. Score RelayOps repeatability checklist honestly for your own venture or case.
2. Which channel would you test first after founder-led sales?
3. Continue to Lesson 2: Advanced Questions in Scaling Evidence into Repeatable Growth.