Activation, Engagement and Retention: From Analysis to Action

Analysis without action is another dashboard

RelayOps can plot cohorts, audit assumptions, and compute health scores. Customers still churn if insights do not become playbooks: onboarding changes, success calls, segment filters, and product tweaks within seven days of a red score.

This closing Unit 2 lesson builds action plans from SunLine's red health score and Desert Cool's yellow-to-green path. You will write customer success playbooks, engineering micro-sprints, and executive decisions tied to retention metrics.

RelayOps is the anchor venture for ENT 402. It sells B2B (business-to-business, software sold to companies rather than consumers) field-service dispatch and scheduling software to mid-market commercial HVAC (heating, ventilation, and air conditioning) companies with 50 to 150 field technicians. Founders Maya Chen (CEO, former dispatch manager) and Jordan Okonkwo (CTO) completed 28 discovery interviews in ENT 401. Those interviews confirmed that dispatch managers lose roughly 14% of revenue to missed appointments, double-bookings, and slow emergency routing. The beachhead segment is commercial HVAC operators in Phoenix and Dallas. Stated willingness to pay in interviews ranged from $89 to $149 per technician per month for software that reliably solves dispatch chaos.

Unit 3 will connect retention patterns to product-market fit signals. Here you fix habits before measuring PMF.

Operational vocabulary at RelayOps is measured against Phoenix pilot scorecards, not dictionary completeness. Maya ties each term from this lesson to a field on the weekly dashboard Desert Cool, SunLine, and Valley Air review together. When a dispatch manager says "production ready," the glossary entry lists uptime, silent job drops, and override visibility, not feature parity with ServiceTitan. Jordan links engineering milestones to those same words so pull requests either advance the published RAT or appear on a deferral list with assumption ranks.

Founders should rehearse definitions aloud before customer calls the way finance teams rehearse earnings scripts. If Maya cannot define "live entry" in one sentence with a numeric threshold, dispatchers will not comply consistently. ENT 401 established that mid-market HVAC firms lose roughly 14% of revenue to dispatch chaos; ENT 402 vocabulary explains how MVP tests prove whether RelayOps recovers a measurable slice of that loss without claiming full product-market fit prematurely.

Playbooks by metric failure mode

Map metric failures to playbooks. Low activation: sandbox training, buddy shift, owner mandate memo. Low engagement depth: remove parallel spreadsheet, add live-entry validation. Poor retention: segment disqualification, pricing change, or feature pivot to audit wedge.

Each playbook lists owner, duration, cost, success threshold. SunLine low activation playbook: 2-week buddy program, $2,500, target first-loop ≥80%.

Playbooks are not one-size: low-volume emergency sites get audit-trail wedge playbook instead of speed playbook.

Avoid playbook sprawl: maximum three active playbooks company-wide during pilot phase.

Board members and pilot customers interpret the same English words through different incentives. Owners hear ROI (return on investment, profit or cost savings compared with spend). Dispatchers hear Tuesday-morning friction. Engineers hear technical debt. RelayOps publishes a single learning agenda so "success" always references emergency dispatch time, usage percentage, and renewal intent together rather than whichever metric flatters one stakeholder today.

Document vocabulary changes in the assumption map version history the same way you version pricing. When RelayOps redefines activation from "first login" to "first completed emergency loop," every cohort chart gets a footnote. Without version discipline, teams compare incompatible retention curves and draw wrong scale decisions heading into Dallas expansion or Unit 3 product-market fit measurement.

RelayOps retention playbooks:

Micro-sprints tied to retention

Engineering prioritizes micro-sprints (≤1 week) when diagnostics pinpoint UX blockers. Jordan's queue: call popup (4 days), sandbox mode (3 days), duplicate job warning (2 days). Each links to funnel stage metric target.

Feature moratorium during red health accounts: no new modules until coverage ≥65% for 2 consecutive weeks.

Micro-sprints include rollback plan if guardrail metrics worsen.

Success measured by before-after funnel conversion, not ship date.

Board members and pilot customers interpret the same English words through different incentives. Owners hear ROI (return on investment, profit or cost savings compared with spend). Dispatchers hear Tuesday-morning friction. Engineers hear technical debt. RelayOps publishes a single learning agenda so "success" always references emergency dispatch time, usage percentage, and renewal intent together rather than whichever metric flatters one stakeholder today.

Document vocabulary changes in the assumption map version history the same way you version pricing. When RelayOps redefines activation from "first login" to "first completed emergency loop," every cohort chart gets a footnote. Without version discipline, teams compare incompatible retention curves and draw wrong scale decisions heading into Dallas expansion or Unit 3 product-market fit measurement.

Customer success cadence

Customer success cadence for early B2B: green accounts monthly check-in, yellow biweekly, red weekly. Agenda: metric review, playbook status, blocker escalation.

Maya's 30-minute red call script: confirm data accuracy, agree one customer action (owner email), one RelayOps action (training date), document in CRM (customer relationship management, system of record for accounts).

Success team size: founders cover first 10 accounts; hire CS (customer success) manager only when ≥8 green accounts with playbooks standardized.

Escalation to owner within 48 hours if coverage drops 15 points week-over-week.

Board members and pilot customers interpret the same English words through different incentives. Owners hear ROI (return on investment, profit or cost savings compared with spend). Dispatchers hear Tuesday-morning friction. Engineers hear technical debt. RelayOps publishes a single learning agenda so "success" always references emergency dispatch time, usage percentage, and renewal intent together rather than whichever metric flatters one stakeholder today.

Document vocabulary changes in the assumption map version history the same way you version pricing. When RelayOps redefines activation from "first login" to "first completed emergency loop," every cohort chart gets a footnote. Without version discipline, teams compare incompatible retention curves and draw wrong scale decisions heading into Dallas expansion or Unit 3 product-market fit measurement.

From retention action to PMF readiness

Unit 2 actions prepare Unit 3 PMF measurement. PMF readiness checklist: (1) two cohorts week-8 usage ≥65%, (2) quality renewals ≥2/3 pilots, (3) health score green on ≥50% of ARR, (4) segment ICP documented, (5) playbooks reproducible without founder on every call.

RelayOps status after actions: Desert Cool green path, Valley Air yellow improving, SunLine red on audit-trail pivot. ARR quality $190,080 from two renewals vs $330,264 full potential.

Do not declare PMF; declare readiness to apply PMF surveys and scale tests in Unit 3.

Document retained learnings in assumption map: low emergency volume segment needs different wedge.

Board members and pilot customers interpret the same English words through different incentives. Owners hear ROI (return on investment, profit or cost savings compared with spend). Dispatchers hear Tuesday-morning friction. Engineers hear technical debt. RelayOps publishes a single learning agenda so "success" always references emergency dispatch time, usage percentage, and renewal intent together rather than whichever metric flatters one stakeholder today.

Document vocabulary changes in the assumption map version history the same way you version pricing. When RelayOps redefines activation from "first login" to "first completed emergency loop," every cohort chart gets a footnote. Without version discipline, teams compare incompatible retention curves and draw wrong scale decisions heading into Dallas expansion or Unit 3 product-market fit measurement.

SunLine health 45.7 red. 118 techs, $99/tech, $14,040 MRR (monthly recurring revenue, subscription revenue per month) at risk. Goal: health ≥60 in 30 days or exit segment.

Rehearse reconciliation checks at the bottom of every worked example the way accountants foot a ledger. RelayOps examples use technician counts, price per seat, weekly emergency volume, and runway months that must multiply consistently. If 92 technicians at $99 per month times three months does not equal the pilot revenue line in the table, the lesson fails its MBA standard even when the narrative sounds plausible.

Customer discovery from ENT 401 is the anchor evidence layer beneath every term in this lesson. Problem validation justifies why RelayOps exists; MVP vocabulary explains how founders test behavior change without pretending interviews predict Monday-morning whiteboard habits. Keep both layers visible when writing gate memos so investors see a chain from 28 interviews to three paid pilots to renewal arithmetic, not a jump from slides to product-market fit slogans.

Part A: Action plan

Operational vocabulary at RelayOps is measured against Phoenix pilot scorecards, not dictionary completeness. Maya ties each term from this lesson to a field on the weekly dashboard Desert Cool, SunLine, and Valley Air review together. When a dispatch manager says "production ready," the glossary entry lists uptime, silent job drops, and override visibility, not feature parity with ServiceTitan. Jordan links engineering milestones to those same words so pull requests either advance the published RAT or appear on a deferral list with assumption ranks.

Founders should rehearse definitions aloud before customer calls the way finance teams rehearse earnings scripts. If Maya cannot define "live entry" in one sentence with a numeric threshold, dispatchers will not comply consistently. ENT 401 established that mid-market HVAC firms lose roughly 14% of revenue to dispatch chaos; ENT 402 vocabulary explains how MVP tests prove whether RelayOps recovers a measurable slice of that loss without claiming full product-market fit prematurely.

Part B: Outcome math

If recovery succeeds: 118 × $99 × 12 = $140,184 ARR retained. If fail and churn: lose $140,184, save ~$40k future CS/engineering chasing bad fit.

Total intervention cost ~$11,500 + founder time vs $140k ARR upside.

Operational vocabulary at RelayOps is measured against Phoenix pilot scorecards, not dictionary completeness. Maya ties each term from this lesson to a field on the weekly dashboard Desert Cool, SunLine, and Valley Air review together. When a dispatch manager says "production ready," the glossary entry lists uptime, silent job drops, and override visibility, not feature parity with ServiceTitan. Jordan links engineering milestones to those same words so pull requests either advance the published RAT or appear on a deferral list with assumption ranks.

Founders should rehearse definitions aloud before customer calls the way finance teams rehearse earnings scripts. If Maya cannot define "live entry" in one sentence with a numeric threshold, dispatchers will not comply consistently. ENT 401 established that mid-market HVAC firms lose roughly 14% of revenue to dispatch chaos; ENT 402 vocabulary explains how MVP tests prove whether RelayOps recovers a measurable slice of that loss without claiming full product-market fit prematurely.

Part C: Reconciliation

118 × 99 = 11,682 MRR; ×12 = 140,184 ARR ✓. Intervention $2,500 + $9,000 ≈ $11,500 ✓. ROI positive if success probability >8% ($11.5k/$140k) ✓.

Operational vocabulary at RelayOps is measured against Phoenix pilot scorecards, not dictionary completeness. Maya ties each term from this lesson to a field on the weekly dashboard Desert Cool, SunLine, and Valley Air review together. When a dispatch manager says "production ready," the glossary entry lists uptime, silent job drops, and override visibility, not feature parity with ServiceTitan. Jordan links engineering milestones to those same words so pull requests either advance the published RAT or appear on a deferral list with assumption ranks.

Founders should rehearse definitions aloud before customer calls the way finance teams rehearse earnings scripts. If Maya cannot define "live entry" in one sentence with a numeric threshold, dispatchers will not comply consistently. ENT 401 established that mid-market HVAC firms lose roughly 14% of revenue to dispatch chaos; ENT 402 vocabulary explains how MVP tests prove whether RelayOps recovers a measurable slice of that loss without claiming full product-market fit prematurely.

Part D: Managerial read

Board: "Walk away from SunLine now." Response: "30-day playbook costs $11.5k with defined exit; immediate walk loses $140k ARR option and beachhead reference if recoverable."

Board members and pilot customers interpret the same English words through different incentives. Owners hear ROI (return on investment, profit or cost savings compared with spend). Dispatchers hear Tuesday-morning friction. Engineers hear technical debt. RelayOps publishes a single learning agenda so "success" always references emergency dispatch time, usage percentage, and renewal intent together rather than whichever metric flatters one stakeholder today.

Document vocabulary changes in the assumption map version history the same way you version pricing. When RelayOps redefines activation from "first login" to "first completed emergency loop," every cohort chart gets a footnote. Without version discipline, teams compare incompatible retention curves and draw wrong scale decisions heading into Dallas expansion or Unit 3 product-market fit measurement.

RetainCo (fictional) hired analyst to build Looker dashboards while churn rose. No playbooks existed. RelayOps ties every dashboard metric to playbook owner and deadline.

Rehearse reconciliation checks at the bottom of every worked example the way accountants foot a ledger. RelayOps examples use technician counts, price per seat, weekly emergency volume, and runway months that must multiply consistently. If 92 technicians at $99 per month times three months does not equal the pilot revenue line in the table, the lesson fails its MBA standard even when the narrative sounds plausible.

Customer discovery from ENT 401 is the anchor evidence layer beneath every term in this lesson. Problem validation justifies why RelayOps exists; MVP vocabulary explains how founders test behavior change without pretending interviews predict Monday-morning whiteboard habits. Keep both layers visible when writing gate memos so investors see a chain from 28 interviews to three paid pilots to renewal arithmetic, not a jump from slides to product-market fit slogans.

Valley Air health 72 yellow. Coverage 71%, activation 75%, time beat 59%. Choose one playbook from this lesson for 14 days. Estimate ARR ($80,784) protected if health reaches 76 and renewal expands from 68 to 80 techs at $99.

Rehearse reconciliation checks at the bottom of every worked example the way accountants foot a ledger. RelayOps examples use technician counts, price per seat, weekly emergency volume, and runway months that must multiply consistently. If 92 technicians at $99 per month times three months does not equal the pilot revenue line in the table, the lesson fails its MBA standard even when the narrative sounds plausible.

Customer discovery from ENT 401 is the anchor evidence layer beneath every term in this lesson. Problem validation justifies why RelayOps exists; MVP vocabulary explains how founders test behavior change without pretending interviews predict Monday-morning whiteboard habits. Keep both layers visible when writing gate memos so investors see a chain from 28 interviews to three paid pilots to renewal arithmetic, not a jump from slides to product-market fit slogans.

Solution

Weakest factor activation 75% vs coverage 71%: deploy TTA + floater sandbox playbook (owner Maya, 14 days).

Current ARR 68 × 99 × 12 = $80,784. Expanded 80 × 99 × 12 = $95,040. Upside $14,256 if expansion tied to activation fix.

Success: activation ≥85%, health ≥76. Check: 80×99×12=95,040; delta 14,256 ✓

Operational vocabulary at RelayOps is measured against Phoenix pilot scorecards, not dictionary completeness. Maya ties each term from this lesson to a field on the weekly dashboard Desert Cool, SunLine, and Valley Air review together. When a dispatch manager says "production ready," the glossary entry lists uptime, silent job drops, and override visibility, not feature parity with ServiceTitan. Jordan links engineering milestones to those same words so pull requests either advance the published RAT or appear on a deferral list with assumption ranks.

Founders should rehearse definitions aloud before customer calls the way finance teams rehearse earnings scripts. If Maya cannot define "live entry" in one sentence with a numeric threshold, dispatchers will not comply consistently. ENT 401 established that mid-market HVAC firms lose roughly 14% of revenue to dispatch chaos; ENT 402 vocabulary explains how MVP tests prove whether RelayOps recovers a measurable slice of that loss without claiming full product-market fit prematurely.

Board members and pilot customers interpret the same English words through different incentives. Owners hear ROI (return on investment, profit or cost savings compared with spend). Dispatchers hear Tuesday-morning friction. Engineers hear technical debt. RelayOps publishes a single learning agenda so "success" always references emergency dispatch time, usage percentage, and renewal intent together rather than whichever metric flatters one stakeholder today.

Document vocabulary changes in the assumption map version history the same way you version pricing. When RelayOps redefines activation from "first login" to "first completed emergency loop," every cohort chart gets a footnote. Without version discipline, teams compare incompatible retention curves and draw wrong scale decisions heading into Dallas expansion or Unit 3 product-market fit measurement.

Key takeaways

• Map metric failures to named playbooks with owners and thresholds.
• Engineering micro-sprints target funnel stages, not random features.
• Customer success cadence scales green/yellow/red contact frequency.
• PMF readiness checklist precedes PMF surveys and scale hiring.
• Compare playbook cost to ARR at risk before walking away from accounts.

1. Write a 14-day playbook for one yellow RelayOps account.
2. Which Unit 2 metric would you put on the founder weekly dashboard?
3. Continue to Unit 3: Product-Market Fit Signals and Measurement.