Building a Repeatable Go-to-Market Engine: Final Applied Review

The managerial question this capstone answers

RelayOps enters this lesson with real traction and real fragmentation. Maya Chen and Jordan Park have built incident response and on-call operations software that customers retain. They have chosen a beachhead: U.S. Series B SaaS (software-as-a-service, software delivered online by subscription*) companies with 80 to 300 engineers, cloud-native monitoring, and Slack-centric workflows. They have $920,000 ARR (annual recurring revenue, subscription revenue normalized to a year*) across 21 accounts. Average ACV (average contract value, mean first-year contract size*) is roughly $44,000. Sales cycles for ICP (ideal customer profile, written description of the segment where the offer wins most predictably*) accounts cluster near 51 days, but off-ICP revenue still represents 14% of ARR. The board wants a credible path to $3M ARR within 18 months without betting the company on a single heroic hire or a channel fad.

This capstone is the integrative review for ENT 403. It connects Unit 1 beachhead and ICP discipline, Unit 2 positioning and category design, Unit 3 founder-led pipeline creation, Unit 4 channels and partnerships, Unit 5 pricing and packaging, and Units 6.1 through 6.3 integration, advanced judgment, and measurement. You will leave with a full GTM engine (go-to-market engine, connected policies, playbooks, and metrics that produce predictable revenue*) design: not slides, but operating numbers, hiring sequence, channel economics, pricing evolution, quarterly milestones, and kill criteria.

The capstone format mirrors what a Series A (first institutional venture round after seed traction) data room should contain: an ARR waterfall you can reconcile, a capacity model that explains hiring, cohort proof of repeatability, and explicit falsification tests if the engine stalls.

RelayOps baseline: integrated snapshot at $920K ARR

Before forward planning, anchor facts from prior units.

Company: RelayOps, B2B SaaS incident response and on-call platform. Founders: Maya Chen (CEO), Jordan Park (CTO). Team size: 18 full-time equivalents. Gross margin (revenue minus direct delivery cost): approximately 78%.

Beachhead (Unit 1): U.S. Series B SaaS, 150 to 500 employees, $15M to $80M ARR, Datadog or Grafana, Slack, AWS (Amazon Web Services, Amazon's cloud platform*), weekly production incidents. Negative filters: enterprise banks in year one, on-prem-only, teams without 24/7 on-call.

Positioning wedge (Unit 2): Reduce MTTA (mean time to acknowledge, speed to first human response on an incident*) by 40% within 30 days via Slack-native escalation. Competitive frame: alternative to PagerDuty for mid-market SaaS velocity, not generic "incident management suite."

Founder pipeline (Unit 3): Stages: Target → Discovery → Pilot → Security Review → Close → Live. Pilot success metric: first live incident acknowledged in RelayOps within 14 days. SQL (sales qualified lead, opportunity vetted for pain, budget, timeline, and authority*) requires technographic confirmation.

Channels (Unit 4): Referrals (38% of SQLs, 31% win rate), ABM (account-based marketing, coordinated outreach to named accounts*) list of 260 accounts, selective events, paused broad paid search, Datadog marketplace pilot.

Pricing (Unit 5): Platform fee plus per on-call seat; typical ICP deal $46K ACV annual prepay; discount guardrail 10% without CEO approval.

Integration health (Unit 6.1): ICP win rate 27%; median cycle 51 days; implementation median 18 days; off-ICP ARR 14% (miss vs 12% target); discount rate 11% on recent bookings.

This baseline is the starting balance sheet of the GTM engine. Scaling to $3M is a change program, not a hope program.

The $3M ARR target: decomposition and feasibility

$3M ARR = $920K existing base + net new ARR from logos, expansion, minus churn and contraction.

Over 18 months, RelayOps models:

Base case targets $3.0M month 18. Bear case $2.65M if win rate dips. Bull case $3.2M if referral channel accelerates.

Feasibility test: new logo ARR $1.68M over 18 months requires average $93K new ARR per month booked. At $47K ACV, that is roughly two logos per month sustained, rising to three in later quarters. With ICP win rate 25% and SQL→close funnel from Lesson 6.3, required SQLs ≈ 8 to 10 per month at maturity. Referral plus ABM must supply that volume without drowning founders in off-ICP noise.

NRR (net revenue retention, revenue from existing customers including expansion minus churn*) target: 110% to 115% on ICP cohorts. GRR (gross revenue retention, revenue kept excluding expansion*) target: ≥90%. Expansion funds roughly 30% of growth; logos fund 70%. Neglecting either breaks the path.

Check base case ARR walk: 920 + 1,680 + 620 − 140 − 280 = 2,800. Additional expansion in months 13 to 18 on new logos adds ~$200K, closing toward $3.0M ✓

Phase 1 (Months 1-6): Fix integration leaks before acceleration

Advanced GTM scaling fails when teams accelerate into leaks. RelayOps Phase 1 prioritizes integration debt paydown from Lesson 6.1 audit.

Month 1-2: Instrument and enforce

CRM mandatory fields: ICP score, channel source, loss code, discount reason, committee map complete by Pilot stage. Weekly Tier 1 dashboard live (Lesson 6.3). Decline policy for off-ICP SQLs enforced at Discovery. Referral bonus restructured: $2,500 only for ICP-fit intros that reach Pilot.

Expected outcome: off-ICP ARR share falls from 14% toward 11% without forced churn of legacy accounts.

Month 3-4: Channel rebalancing

Pause non-ICP paid search entirely. Shift $4,000/month to beachhead landing page, retargeting, and SaaS Reliability Breakfast events (reference density play from Unit 1). Launch Datadog marketplace listing with ICP-minimum copy.

Target channel mix end of Phase 1:

Phase 1 new ARR booking target: $380K in six months (~8 logos), ending ARR ~$1.3M including expansion and churn.

Month 5-6: Playbook hardening and AE prep

Document mutual action plan template, security FAQ v2, pricing calculator. Founder selling hours logged: target 180/month Maya, reduce to 140 by month 6 as growth lead absorbs qualification.

AE hire conditional gate (Lesson 6.2): pipeline weighted ICP ≥$1.2M. RelayOps runs referral accelerator to hit gate by month 6.

Kill criterion Phase 1: if ICP win rate <20% for two consecutive months while SQL volume rises, halt channel spend and run positioning/postmortem wedge review (Unit 2) before Phase 2.

Phase 2 (Months 7-12): Transfer motion and scale capacity

Phase 2 introduces first AE (month 7 start), expands ABM list to 380 accounts, and pilots packaging v2 for high-incident customers.

AE #1 profile and ramp

• Quota: $400K new ARR year one (pro-rated $300K from July)
• Base/variable: $110K / $110K
• Territory: ICP Series B SaaS only
• Ramp: Q3 70% quota, Q4 100%

Maya transfers closing calls on opps after Pilot success metric met. Founder remains on strategic accounts and all pricing exceptions.

Capacity model month 7-12

Hours per ICP opp: 9 by month 12 (play maturity). Quarterly opps worked: ~85. At 26% win rate, ~22 closes/year from seller capacity, split Maya + AE.

Packaging v2 cohort (Unit 5)

Add incident volume tier above 600 monthly incidents: +$8K annual platform surcharge with dedicated CS health check. Grandfather existing 21 customers. Test on next eight ICP prospects.

Success metric: expansion ARR from tier upsell ≥$120K in Phase 2 without cycle lengthening >10%.

Channel evolution

Referral program adds customer advisory board (CAB, small group of reference customers*) of six ICP VP Engineering sponsors. ABM adds fintech SaaS adjacency slice (10% of list) after compliance export ships (Unit 1 adjacency rule).

Phase 2 ARR target: exit month 12 at $2.05M ARR.

Check Q3-Q4 walk from $1.3M Phase 1 end: 1.3 + 0.31 + 0.055 − 0.045 ≈ 1.62; continue layering ✓

Phase 3 (Months 13-18): Repeatability proof and Series A narrative

Phase 3 hires AE #2 (month 14), customer success manager dedicated to expansion, and part-time RevOps (revenue operations, systems connecting marketing, sales, and success data*) contractor. Goal: demonstrate narrow cohort variance suitable for Series A.

Hiring sequence rationale

AE #2 only after AE #1 reaches ≥75% quota in Q4 and implementation median stays ≤21 days. Premature second hire reintroduces Lesson 6.2 failure mode.

Series A narrative metrics (month 18 target)

Rule of 40 (heuristic: revenue growth rate plus profit margin should exceed 40%) for RelayOps month 18: ARR grew from $920K to $3M in 18 months (~147% annualized on average), gross margin 78%. Proxy sum exceeds 40 if opex (operating expense) discipline holds.

Phase 3 logo target: 13 to 15 logos per half-year at $47K to $50K ACV as packaging v2 lifts ASP (average selling price, mean deal size*) slightly.

Ending ARR month 18 base case:

920 + 1,680 new + 620 expansion − 420 churn/contraction ≈ $2.8M; late-quarter expansion on new logos adds ~$200K → ~$3.0M ✓

Integrated playbook: how each unit shows up in one deal

Walk through Northwind Analytics, fictional Series B SaaS, 220 engineers, Datadog + Slack, to see integration in one motion.

Unit 1: Northwind scores 84/100 on FIT score (firmographic 38/40, integration 28/30, pain 18/30). Passes beachhead.

Unit 2: Outbound uses wedge message: "Cut MTTA 40% in 30 days without replacing PagerDuty on day one." Category frame: escalation orchestration layer.

Unit 3: Discovery maps VP Engineering champion and IT security reviewer. Pilot mutual action plan signed week 1. Pilot success: Sev-2 incident acknowledged in 4 minutes vs 11-minute baseline.

Unit 4: Source: customer referral from prior ICP logo. Referral bonus triggers on pilot start.

Unit 5: Pricing calculator: 45 seats × $780 + $12K platform = $47,100; 5% annual prepay discount approved within policy.

Unit 6: CRM fields complete; Tier 2 metrics update; implementation scheduled within 4 days; cohort tagged Q4-Referral.

Close in 44 days. Implementation 17 days. Month 6 expansion conversation scheduled at seat growth trigger.

This single-thread story is what "repeatable" means: each unit's output is an input to the next stage with no orphan exceptions.

Organization design: who owns the engine at each ARR stage

GTM engines fail when ownership is implicit. RelayOps maps roles across the $920K to $3M journey.

$920K to $1.3M ARR (Phase 1): Founders plus one growth generalist. Maya owns beachhead, pricing exceptions, and Tier 1 metrics. Jordan owns product gates and implementation template. Growth lead owns ABM list, events, and channel tags. No AE. Finance contractor reconciles ARR monthly.

$1.3M to $2.0M ARR (Phase 2): Add AE #1, part-time CS specialist, SDR contract (10 hours/week prospecting only into named ABM accounts, not broad cold calling). Maya shifts to 40% selling, 30% partnerships, 30% fundraising prep. RevOps contractor 10 hours/month builds dashboard v2.

$2.0M to $3.0M ARR (Phase 3): AE #2, full-time CS manager, dedicated implementation engineer, RevOps 0.5 FTE (full-time equivalent). First sales manager not hired until AE #2 reaches quota two consecutive quarters (likely post $3M).

Competitive response playbook

PagerDuty and legacy vendors do not stand still. RelayOps documents competitive battle cards (one-page summaries of positioning against a specific competitor) tied to Unit 2 messaging.

Scenario: PagerDuty bundles chat integration free.

Response sequence:

1. Do not change beachhead or panic-discount (Layer 5 policy).
2. Interview five won and five lost deals within 14 days (learning loop).
3. If losses cite "good enough incumbent," sharpen wedge to time-to-value and Slack workflow depth, not feature parity.
4. Publish customer proof: MTTA delta distribution from ICP cohort, not single logo story.
5. If win rate drops below 20% for 60 days after response, run packaging cohort test (free implementation hours capped at 10, not ACV discount).

Scenario: New startup undercuts price 50%.

RelayOps compares TCO (total cost of ownership, full cost including implementation, support, and switching*):

Battle card trains AE to reframe price objections into risk and implementation math, not feature lists.

Founder sales playbook deliverable (ENT 403 portfolio)

This capstone doubles as the founder sales playbook deliverable referenced in the unit overview. Minimum sections RelayOps publishes internally:

1. ICP one-pager (Unit 1): firmographics, technographics, pain fit, negative filters, FIT scoring
2. Positioning brief (Unit 2): wedge, category frame, three approved headlines, forbidden phrases ("generic incident management")
3. Pipeline manual (Unit 3): stage definitions, exit criteria, discovery script outline, pilot mutual action plan template, security FAQ index
4. Channel playbook (Unit 4): referral rules, ABM list criteria, event ROI (return on investment) threshold, partner margin floors
5. Pricing sheet (Unit 5): seat table, platform fee, volume tier, discount matrix, prepay policy
6. Integration checklist (Unit 6): six checkpoints, change request form, kill criteria library
7. Metrics glossary (Unit 6.3): Tier 1/2/3 definitions, ARR waterfall formula, DRI map

Playbook version control matters. RelayOps labels v2.4 after packaging tier addition; AE onboarding requires sign-off on version hash in CRM.

Cash and burn coupling (bridge to ENT 404)

GTM engine plans must connect to cash. RelayOps at $920K ARR with ~$185K monthly burn and ~$640K cash by mid-year (per ENT 404 anchor) cannot fund unlimited S&M (sales and marketing) acceleration.

S&M budget bands:

Efficiency improves as referrals rise. Kill criterion: if CAC payback exceeds 12 months for two quarters, cut Phase 3 event spend before cutting CS.

New ARR booked must convert to cash via annual prepay policy (Unit 5). RelayOps targets ≥70% annual prepay on new logos. At $460K new ARR booked with 70% prepay, cash collection ~$322K vs monthly contracts ~$38K first-year cash impact. Prepay policy is a GTM implementation choice with balance sheet consequences.

Quarterly operating calendar (18 months)

Engine health scorecard aggregates six integration checkpoints across layers with trailing 90-day evidence. Score ≥4.0/5.0 required to claim "repeatable" in fundraise narrative.

Customer success as GTM output, not afterthought

Repeatable GTM includes post-sale motion. RelayOps CS playbook for ICP:

Days 1-7: Kickoff, integration checklist, executive sponsor intro.

Days 8-21: First MTTA improvement workshop; baseline vs week three comparison documented for case study permission.

Days 22-60: Blameless postmortem template imported; VP Eng QBR scheduled.

Days 61-180: Seat expansion trigger when engineering headcount grows 15% or on-call rotation adds third team.

Churn early warning: MTTA not improved by day 30, or <50% weekly active responders by day 45.

CS metrics feed Tier 1 GRR. A sales team that closes logos CS cannot implement destroys NRR and referral supply. Phase 1 deliberately fixes implementation median before AE hire.

ENT 403 unit synthesis: what each unit contributed to the engine

Before diving into financial models, step back and articulate how each course unit changed RelayOps operating system. Investors and new hires ask this question. A credible answer is specific.

Unit 1 (Beachhead and ICP) supplied the filter that makes every downstream metric meaningful. Without Series B SaaS concentration, win rate and cycle time would blend incompatible deals. RelayOps policies from Unit 1 still govern at $3M: three-account product rule, decline template, annual planning from SOM (serviceable obtainable market, realistic near-term winnable revenue*) not TAM (total addressable market, revenue if everyone bought*). The engine cannot scale off-ICP ARR share above 12% without renegotiating the beachhead contract with the board.

Unit 2 (Positioning and Category Design) supplied the language that makes ABM and referrals efficient. When a VP Engineering forwards RelayOps email internally, the wedge "40% MTTA in 30 days" travels better than "incident management platform." Category design choice (escalation orchestration vs full suite replacement) reduces competitive evaluations to winnable criteria. Positioning also constrains product: postmortem features exist on roadmap but do not lead marketing until wedge saturation signals in win/loss data.

Unit 3 (Founder-Led Sales and Pipeline Creation) supplied the motion that produces labeled learning. Stage definitions, pilot success metrics, and committee maps are the raw material for repeatability statistics. Founder selling was never the destination; it was the instrument that produced 38 closed ICP opportunities with coded outcomes. Transfer to AE #1 copies that motion, not Maya's personality.

Unit 4 (Channels and Partnerships) supplied the levers that amplify filtered demand. Referrals outperform paid search because ICP density is higher, not because referrals are morally superior. RelayOps rejected MSP and premature PLG because channel economics failed integration checkpoints. At $3M, channel mix targets 45% referral, 35% ABM, 12% events, 8% marketplace: a measured portfolio, not a single hack.

Unit 5 (Pricing, Packaging, and Revenue Models) supplied the capture mechanism for value delivered. Seat plus platform pricing aligns with buyer budget psychology in Series B SaaS. Annual prepay improves cash conversion for burn management. Packaging v2 ties revenue to incident volume where delivery cost scales. Discount matrix prevents silent margin erosion that would break CAC payback claims in Series A diligence.

Unit 6 (This unit) supplied the governance and measurement glue. Integration checkpoints prevent units from fighting in silence. Tier 1 metrics prove whether Units 1 through 5 still cohere at scale. The capstone plan is the first time all units appear in one forward model with shared assumptions.

A manager auditing any startup GTM engine should ask: can leadership name the filter, language, motion, levers, capture mechanism, and governance for their company in one page? If not, they have tactics, not an engine.

Phase 1 week-by-week execution (months 1-3 detail)

Week 1: CRM audit; list missing ICP fields on 100% of open opps; assign sales ops fix.

Week 2: Publish decline template; train growth lead on polite disqualification script.

Week 3: Tier 1 dashboard v1; Monday revenue meeting starts red/yellow/green Tier 1 review.

Week 4: Referral policy update communicated to customers; ICP-only bonus effective.

Week 5: Paid search paused; budget reallocated to landing page test.

Week 6: Landing page B publishes wedge headline; conversion benchmark 4%.

Week 7: First SaaS Reliability Breakfast event; 22 attendees; 4 ICP SQLs.

Week 8: Loss code retrospective on ten closed-lost deals; top code "wedge mismatch" at 30%.

Week 9: Security FAQ v2 published; average Security Review stage drops from 18 to 12 days.

Week 10: Datadog marketplace listing submitted.

Week 11: Implementation backlog review; median days 20; hire CS contractor 20 hours/week.

Week 12: Phase 1 scorecard vs plan: new ARR booked $182K vs $190K target (miss); ICP win rate 25% (pass); off-ICP ARR 11.5% (pass).

Phase 1 miss on new ARR is acceptable if leading indicators improved: referral SQLs +22%, implementation median −2 days, discount rate −3 points. Boards fund trajectory when integration metrics green even if logo count slightly lags.

Part A: Quarterly ARR waterfall (base case)

Late Q4 expansion pull-forward from packaging v2 and AE #2 ramp adds $360K expansion not fully shown in quarterly smoothing → **$3.0M** reported month 18.

Check: cumulative new ≈ $1,560K in table + $120K pull-forward ≈ $1,680K target ✓

Part B: Logo and funnel math (Y2 Q4)

Target 15 logos at $50K ASP = $750K new ARR quarter.

Required ICP SQLs at 26% SQL→close and 44% SQL→pilot, 38% pilot→close:

15 / (0.44 × 0.38) ≈ 90 SQLs if using pilot path; simplified SQL→close 26% → 15/0.26 ≈ 58 SQLs (opps worked to close).

Channel plan 58 SQLs: referrals 24, ABM 20, events 8, marketplace 6.

S&M budget Y2 Q4: $185K. CAC per logo 185/15 ≈ $12.3K. Payback (50K × 0.78) = 39K gross profit year one; 12.3/39 × 12 ≈ 3.8 months ✓

Part C: Capacity reconciliation

AE #1 and #2 combined 320 selling hours/month × 3 months = 960 hours.

90 SQLs × 6 hours average (mature play) = 540 hours. Pilot support 30 × 8 hours = 240. Total 780 < 960 ✓

Part D: Board questions and answers

Q: Why not two AEs in Y1 Q3? A: Pipeline coverage failed gate; integration leaks would have amplified.

Q: What if PagerDuty drops price 30%? A: Wedge shifts to implementation speed and Slack workflow depth; packaging v2 adds value metric beyond seat count; kill if win rate drops <18% for two quarters.

Q: Is $3M ARR enough for Series A? A: With 113% NRR and ≤8 month payback, yes for devtools SaaS; otherwise raise efficiency before round.

Suppose Y1 Q3 delivers:

• ICP win rate 17%
• Median cycle 74 days
• Implementation median 29 days
• New ARR $90K vs $155K plan

RelayOps triggers engine review protocol (Unit 6 integration):

Week 1: 15 lost-deal interviews; loss codes aggregated.

Week 2: Hypothesis tests:

Week 3: Actions:

• Pause marketplace spend
• Freeze fintech adjacency
• Ship postmortem export MVP only if three-account rule satisfied (2 of 3 references already requested)
• Delay AE #2; Maya back on closing calls

Week 4: Falsification metric for Q4: win rate ≥22% on 25+ opps or revise beachhead formally.

Bear case ARR month 18 revises to $2.4M. Board prefers honest reset over inflated plan.

Packaging v2 adds incident volume tier. Cohort of eight prospects:

Weighted ACV (8 deals): (5×46 + 3×54)/8 = $49K. Cycle within 10% of baseline → packaging pass.

Expansion on legacy 21 customers: 6 adopt tier upsell at +$6K average = +$36K ARR expansion without new logos.

Check: tier upsell gross margin 80% vs 78% base (less support per incremental dollar) ✓

RelayOps prepares the following exhibit for institutional diligence.

Part A: Cohort retention curve (ICP logos only)

Blended month-12 NRR on mature cohorts: 113%. No ICP logo churn in first six months of last four cohorts.

Part B: Sales efficiency

Magic number above 0.75 suggests efficient scaling room. Below 0.5 would trigger efficiency review.

Part C: Variance proof (repeatability)

Narrow interquartile range supports "repeatable" claim. Early off-ICP deals excluded from distribution.

Part D: Managerial read

Investor objection: "Growth decelerates after $3M." RelayOps response: referral channel still under-monetized; Datadog marketplace early; packaging v2 raises ASP; AE layer only two reps. Adjacency (Series C SaaS) sequenced after engine scorecard passes 4.0.

Part A: Timeline

Part B: Economics

CAC for this deal: referral bonus $2,500 + 6 hours founder time (~$900 internal) ≈ $3,400.

First-year gross profit: $47,100 × 0.78 = $36,738. Payback <2 months.

Part C: Integration failures avoided

Junior SRE tried to join discovery alone (committee risk). Policy required VP Eng by Pilot week 1. Off-ICP subsidiary of same parent flagged but subsidiary scored ICP independently.

Part D: Replication plan

Add Northwind technographics and loss-win notes to ABM lookalike list. Tag five accounts for outbound wave 12. Expected 2 SQLs at 30% referral-like win rate.

Check: 2 × 0.30 × $47K ≈ $28K expected ARR from replication wave ✓

Score RelayOps month 18 outcomes:

Tasks:

1. Compute weighted engine score if ICP and capacity checkpoints are weighted 25% each and others 12.5% each.
2. Does RelayOps pass 4.0 fundraise threshold?
3. What single operational fix raises capacity fit fastest without hurting ICP fit?

Solution

1. Weighted score

ICP: 5 × 0.25 = 1.25

Capacity: 3 × 0.25 = 0.75

Message: 4 × 0.125 = 0.50

Motion: 4 × 0.125 = 0.50

Price: 4 × 0.125 = 0.50

Proof: 5 × 0.125 = 0.625

Total = 4.125

2. Threshold

4.125 ≥ 4.0 → pass narrowly; capacity is drag.

3. Fix

Hire implementation engineer and enforce kickoff within 5 days of close (CS playbook metric). Defer AE #2 expansion until median implementation ≤21 days for two months. Do not loosen ICP gates to feed implementation queue faster; that lowers GRR.

RelayOps month 12 actual: $2.02M ARR, ICP share 86%, NRR 111%, AE #1 at 68% quota, implementation median 23 days, referral SQLs flat quarter-over-quarter.

Tasks:

1. Compute how much new + expansion ARR RelayOps needs in months 13-18 to reach $3M from $2.02M base if churn+contraction run $110K over that period.
2. At $49K ACV and 25% win rate, how many ICP SQLs are required to produce the new logo portion if expansion contributes $320K net over six months?
3. Write a one-page decision memo (300-400 words) choosing among: (A) hire AE #2 month 13, (B) delay AE #2 and fund customer marketing for referrals, (C) launch PLG free tier. Pick one with integration checkpoints and kill criterion.
4. List three metrics from Tier 1 (Lesson 6.3) you would show Series A investors and one metric you would deprioritize with rationale.

Solution

1. ARR gap

Target $3M − $2.02M base = $980K gross growth needed.

Net of churn+contr $110K: need $980K + $110K = $1,090K from new logos + expansion combined.

If expansion contributes $320K net (given in task 2 setup): new logos need $1,090K − $320K = $770K new logo ARR.

Check: 2.02 + 0.77 + 0.32 − 0.11 = 3.00 ✓

2. SQL math

Logos needed: 770,000 / 49,000 ≈ 15.7 → 16 logos.

At 25% SQL→close (simplified): SQLs = 16 / 0.25 = 64 SQLs over six months (~11/month).

If using pilot path 40% × 55% = 22% effective, SQLs = 16 / 0.22 ≈ 73.

3. Sample decision memo

Recommendation: (B) Delay AE #2 90 days; fund referral and CAB program.

AE #1 at 68% quota with rising implementation median signals motion transfer incomplete, not headcount shortage. Integration checkpoint Motion fit fails: 23-day implementation exceeds 21-day band. Adding AE #2 imports pipeline demand before delivery stabilizes, risking GRR.

Allocate $45K over 90 days to customer marketing: CAB launch, three case studies, referral tooling. Target +8 referral ICP SQLs/quarter at 30% win rate ≈ 2.4 logos/quarter ≈ $117K new ARR/quarter from referrals alone, plus CS capacity preserved.

Kill criterion: if referral SQLs do not rise ≥15% by month 15 and AE #1 quota attainment <75%, execute AE #2 hire with reduced $350K quota and mandatory playbook certification.

Reject PLG free tier: production incident risk and ICP gating failure in sandbox experiment (Lesson 6.2).

4. Investor metrics

Show: ICP ARR share (86%), NRR (111%), CAC payback (trend), median ICP cycle band, GRR.

Deprioritize: Total SQL count (volume without ICP fit misleads); replace with ICP SQL win rate and cohort implementation days.

Explain why in prose: at month 12, RelayOps already proved it can generate SQLs. The bottleneck is conversion and delivery, not top-of-funnel volume. Investors pattern-match to engines that convert homogeneously; raw SQL count without ICP tag is a vanity metric that could hide paid search mistakes from Phase 1.

Closing integration test

Before you leave ENT 403, run this five-minute test on RelayOps or your own venture:

1. State beachhead in one sentence with negative filters.
2. State positioning wedge without feature list.
3. Name three pipeline stages with written exit criteria.
4. Name top two channels with ICP win rate and payback.
5. State ACV, discount policy, and one packaging rule.
6. Name three Tier 1 metrics with target bands.

If any answer requires more than ten seconds of hesitation, the engine has a gap in that layer. Fix the gap before scaling spend, hires, or fundraising narrative. RelayOps at $920K passed items 1 through 3 weakly and items 4 through 6 inconsistently. The 18-month plan exists to make all six answers automatic for any leader on the team. That is the difference between a startup that tells a GTM story and one that operates a GTM engine.

Key takeaways

• Scaling from $920K to $3M ARR requires integrated phases: fix leaks, transfer motion, then prove cohort narrowness for fundraising.
• ARR waterfalls must reconcile new, expansion, churn, and contraction; logos alone do not carry the target.
• Hiring sequence follows pipeline coverage and playbook transfer, not calendar ambition.
• Each ENT 403 unit manifests as concrete artifacts in a single customer motion, not abstract strategy.
• Bear-case protocols with pre-written kill criteria preserve board trust when quarters miss.

1. Draft an 18-month ARR waterfall for your venture (or RelayOps) with quarterly new, expansion, and churn. Include one explicit check line.
2. Run the six integration checkpoints on your biggest upcoming GTM bet (hire, channel, pricing change). Pass or block?
3. Return to the unit page for assessments: applied project, drill, and reflection on Building a Repeatable Go-to-Market Engine.