Methods and Models for Activation, Engagement and Retention

Models turn retention anxiety into measurable curves

Founders say "retention feels okay" when they have not plotted cohorts. Methods and models make habit visible: activation funnels, retention curves, habit loops, and health scores. RelayOps uses lightweight models appropriate to six dispatchers per site, not billion-user consumer math.

This lesson covers cohort retention tables, funnel analysis, the Hook Model adapted for B2B, and customer health scoring for early accounts.

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 2 Lesson 1 defined strategic logic. Here you build spreadsheets investors and operators both trust.

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.

Cohort retention tables

A cohort groups customers by start week or month. Cohort retention table shows percent of cohort still active at week N after start. RelayOps rows are pilot start weeks; columns week 0 through week 12; cell value is percent dispatchers with ≥1 emergency loop that week.

Read shape, not single cells: improving cohorts (later rows greener) mean onboarding fixes work. Flattening curves near 60-70% may be acceptable for part-time floaters; flattening near 30% is segment failure.

Combine dispatcher cohort with account cohort: account retains while dispatcher churn within account signals training debt.

Export tables weekly from analytics; manual spreadsheets invite copy errors during fundraising.

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 dispatcher cohort retention (% active dispatchers):

Desert Cool and Valley flatten above 65%; SunLine decays toward 50%, confirming segment or onboarding issue from Unit 1 case.

Activation funnels

Funnel stages for RelayOps: invite sent → login → first job created → first full loop → second loop within 72 hours. Conversion rates between stages localize drop-offs. If login is 95% but first loop 40%, training or UI blocker sits at job creation.

Funnel analysis is per site during pilots because onboarding differs. Aggregate funnels hide SunLine's login success with loop failure.

Time between stages matters: median 18 hours from login to first loop is healthy; 6 days suggests procrastination or avoidance.

Experiment interventions attach to stages: SMS reminder at 24 hours if no first loop improves stage 3-4 conversion in A/B at next pilot.

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.

Hook Model for B2B workflow habits

The Hook Model (trigger, action, variable reward, investment) explains habit formation. Trigger: emergency phone ring or dashboard alert. Action: assign tech in console. Variable reward: faster customer relief, visible ETA improvement. Investment: dispatcher maintains technician skill tags and service zones in RelayOps, increasing switching cost.

B2B hooks must survive manager turnover. Owner mandate creates external trigger when internal trigger weak. RelayOps documents owner memo as trigger infrastructure.

Variable reward is subtle in ops software: not likes, but avoided chaos. Metrics should capture "jobs saved from double-book" as qualitative reward logs.

Investment phase: data entry that makes next dispatch faster (tech skills, customer notes). RelayOps prioritizes investment features only after loop adoption proven.

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 health scores (early stage)

Customer health score combines usage, outcome, support, and payment signals into red/yellow/green status. Early RelayOps formula (0-100): 40% emergency job coverage, 30% activated dispatcher rate, 20% median time vs baseline, 10% support ticket severity.

Desert Cool example: coverage 74% → 29.6 points; activation 83% → 24.9; time beat baseline 62% → 18.6; no P1 tickets → 10. Total ≈ 83 green.

SunLine: coverage 52% → 20.8; activation 40% → 12; time improvement 43% → 8.6; tickets 2 P2 → 7. Total ≈ 48 yellow/red.

Health scores prioritize Maya's weekly calls. Scores are diagnostic, not contractual SLAs (service level agreements, promised service standards).

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 funnel week 2: invite 5 → login 5 (100%) → first loop 2 (40%) → second loop 72h 1 (20%). Target: first loop ≥80%.

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: Drop-off diagnosis

Drop between login and first loop (100% to 40%) implicates job creation UX or fear during live calls, not access issues. Qual: dispatchers fear "breaking" live emergencies.

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: Intervention and expected lift

Intervention: sandbox mode with recorded calls plus buddy shift with Maya. Cost $2,500 travel. Expected first-loop conversion 40% → 70% (3.5 of 5 dispatchers). If second-loop holds 80% of activated, week-8 usage could rise from 52% toward 65%+, crossing kill threshold.

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

5 × 70% = 3.5 ≈ 3-4 dispatchers first loop ✓. Usage lift estimate depends on job share per dispatcher; if 3 of 5 active cover 65% jobs vs 2 of 5 at 52%, plausible ✓.

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

CFO at SunLine: "Training costs more than software." Response: "Without 80% first-loop conversion, $99/tech subscription churns; $2,500 training protects $14,040 monthly contract (118 × $99)."

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.

CloudMaint (fictional) health scores used login counts only. Accounts showed green while missed jobs rose. RelayOps weights outcome (dispatch time vs baseline) at 30% to prevent hollow engagement.

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.

Compute Desert Cool health score using formula: 40% coverage (74%), 30% activation (83%), 30% time improvement (62% reduction from 12 min baseline). Compare to SunLine: 52%, 40%, 43%. Which gets red/yellow/green if green ≥75, yellow 50-74, red <50?

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

Desert Cool: 0.4×74 + 0.3×83 + 0.3×62 = 29.6 + 24.9 + 18.6 = 73.1 yellow (just below green if strict). Using 30% time weight on 62% improvement: 73.1.

SunLine: 0.4×52 + 0.3×40 + 0.3×43 = 20.8 + 12 + 12.9 = 45.7 red.

Prioritize SunLine intervention; Desert Cool needs minor UX polish to cross 75. Check arithmetic ✓

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

• Cohort retention tables reveal curve shape, not single renewal moments.
• Activation funnels localize drop-offs for targeted experiments.
• Hook Model adapts to B2B via triggers, rewards, and investment data.
• Early health scores blend usage, activation, outcome, and support.
• Per-site analysis beats aggregated dashboards during pilot phase.

1. Sketch a 4-stage activation funnel for RelayOps with target conversion rates.
2. Which Hook Model stage is weakest for HVAC dispatchers in your view?
3. Continue to Lesson 3: Evidence, Metrics and Assumptions in Activation, Engagement and Retention.