Building Initial Distribution

Distribution is designed, not discovered after product ships

Distribution (how target customers learn, evaluate, and buy a product) is the other half of PMF. RelayOps can prove emergency dispatch value in Phoenix and still fail if qualified pipeline stays at 22 opportunities while the ICP list holds 85 firms. Maya Chen's calendar is not a channel; it is a bottleneck.

Initial distribution for founder-led B2B SaaS favors density channels: association meetings, operator referrals, dispatch consultant intros, and targeted outbound to scored ICP accounts. Paid ads and reseller partnerships come after repeatability, not before.

RelayOps is a B2B (business-to-business, selling to companies) SaaS (software as a service, subscription software delivered over the internet) venture improving dispatch and scheduling for mid-market field-service companies and the anchor venture for ENT 301. Founders Maya Chen (CEO, former dispatch manager at regional HVAC operator Summit Climate) and Jordan Okonkwo (CTO, former platform engineer) left Summit Climate in 2025 after living dispatch-center chaos firsthand. Their initial beachhead is 80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians. Discovery work confirmed 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows tied to same-day capacity loss when dispatchers rebalance schedules across phone calls, whiteboards, and legacy CRM tabs without a live view of technician skill, location, and parts. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo).

Throughout this course, RelayOps evolves from opportunity hypothesis to scaled venture. Elective depth lives in ENT 403 (Startup Go-to-Market and Founder-Led Sales) when you want a full unit on that phase. ENT 301 teaches the integrated journey so you can advise founders, invest, or launch with disciplined evidence. ENT 403 covers channel tests and partner motions. ENT 301 integrates distribution with beachhead math, positioning, and pricing so RelayOps does not buy top-of-funnel volume that ICP filters reject.

This lesson covers channel sequencing, referral loops, content that converts operators, and measuring channel CAC (customer acquisition cost, spend to win one paying customer).

Channel sequencing for pre-seed RelayOps

Channel order: (1) founder network and Summit Climate alumni intros, (2) PHCC (Plumbing-Heating-Cooling Contractors, trade association) local chapter events, (3) customer referral asks post-renewal, (4) tight outbound to ICP score ≥12, (5) dispatch consultant partnerships, (6) deferred paid search and reseller.

Each channel gets a 90-day experiment card: hypothesis, spend cap, qualified opp target, kill rule.

Jumping to channel six early wastes learning because messaging is not stable.

Referral loop design

Referrals require a referral moment: after measurable win, owner meeting, or association award. RelayOps asks Desert Cool owner for two intros after renewal with draft email and specific ICP fit explanation.

Incentive: $500 account credit per signed pilot, capped to avoid channel conflict.

Track referral-sourced pipeline percent. Target 25% before geographic expansion.

Operator content that earns meetings

Generic blogs fail. Operator content wins: "Phoenix heat-wave dispatch postmortem template," "Emergency job live-entry checklist," "Overtime postmortem spreadsheet." Maya publishes one practical artifact monthly tied to wedge.

Content qualifies: download form asks technician count and dispatch tool; low scores auto-nurture, high scores trigger founder email.

Jordan writes reliability postmortems, not AI thought leadership.

Partnership discipline

Dispatch consultants and small MSPs (managed service providers, IT firms serving local businesses) can intro accounts. RelayOps offers 10% first-year revenue share with ICP scorecard enforced; partner cannot bring enterprise security accounts.

Partnerships fail when anyone can sell anyone. Co-marketing only after three successful joint intros.

ServiceTitan marketplace listing is year-two option, not beachhead wedge.

Channel CAC and payback by source

Founder network CAC is low cash, high time. Events cost $2,000 plus travel for 6 qualified opps. Referral CAC is credit $500 plus founder dinner time. Outbound costs tools plus 20 hours per week.

RelayOps logs channel on every opportunity. Quarterly review kills channels with qualified opp cost above $4,000 or close rate below 15%.

Distribution success is measured at Qualified stage, not clicks.

Illustrative channel scorecard:

Goal: add 14 qualified opportunities to close 9-logo gap. Budget $8,000 cash plus founder time.

Part A: Channel allocation

Kill paid search until outbound converts.

Part B: Referral script

Post-renewal ask: "You cut emergency dispatch to under 5 minutes. Two peer owners in Phoenix still on whiteboards would benefit. Can I send a short forwardable note naming the pilot terms and kill criteria?" Forwardable note includes ICP fit and $99 pilot price per technician.

Specific ask beats "know anyone."

Part C: Check

Total qualified target 18 ≥ 14 gap ✓. Cash $6,000 ≤ $8,000 budget ✓. Referral target 6 = 2 intros per renewing logo × 3 logos ✓.

Part D: Managerial read

Distribution plan is a table with owners and kill rules, not a marketing wish list.

TechDispatch Ads (fictional) spent $40,000 on Google ads to "HVAC software" keywords, producing 40 MQLs (marketing qualified leads, marketing-sourced contacts) and 2 qualified opps outside segment. RelayOps runs outbound to scored lists before broad keywords.

Managerial read: distribution without ICP is expensive noise.

RelayOps tests PHCC sponsorship ($3,000) expecting 8 conversations, 5 qualified opps, 2 pilots, founder time 40 hours valued at $150/hour.

Tasks: (1) Compute total channel cost including time. (2) If one pilot renews at 90 techs × $99, compute CAC per pilot won. (3) Kill or continue channel at 90 days if only 3 qualified opps materialize?

Solution

Total cost: $3,000 + 40×$150 = $3,000 + $6,000 = $9,000.

If 2 pilots won from channel (hypothesis): CAC $9,000/2 = $4,500 per pilot before renewals. One renewing logo at 90×$99×12=$106,920 ACV shows attractive ratio if retention holds, but sample is tiny.

If only 3 qualified opps at 90 days vs 5 target: continue one more quarter with messaging fix if close rate healthy; kill if qualified cost >$4,000 and zero pilots. At 3 opps, cost per qualified = $9,000/3 = $3,000 (high but not auto-kill); set kill if next quarter stays below 15% close. Check: 3000+6000=9000 ✓; 9000/2=4500 ✓.

Key takeaways

• Initial distribution sequences cheap learning channels before paid scale.
• Referral loops need specific forwardable asks tied to pilot terms.
• Operator content qualifies leads through ICP fields, not vanity traffic.
• Log channel on every opp and kill weak sources with explicit rules.
• ENT 403 expands partner motions and first marketing hire timing.

1. Draft a 90-day RelayOps distribution table with budgets, targets, and kill rules.
2. Write a post-renewal referral email Maya can forward in under 120 words.
3. Preview Unit 5 Startup Finance: how distribution CAC flows into runway planning.

Applying Building Initial Distribution at RelayOps

When RelayOps applies building initial distribution, Maya Chen and Jordan Okonkwo anchor decisions in field evidence, not slide optimism. Their beachhead (80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians) experiences 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows. Discovery interviews suggested $89 to $149 per technician per month in discovery interviews. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo). Every framework in this lesson should translate into a falsifiable claim about that segment, not generic startup advice.

Consider how go-to-market, positioning, and founder-led sales changes capital allocation. RelayOps started with roughly $400k runway and ~$45k monthly burn before seed. A one-month delay on the wrong opportunity costs more than a month of disciplined interviews. That is why building initial distribution is a CEO-level skill, not a brainstorming exercise.

Document owners alongside metrics. Maya owns discovery synthesis; Jordan owns build scope tied to assumption ranks; both sign kill criteria before pilots. When definitions live in a shared glossary (pilot versus beta, activation versus login), the team avoids comparing incompatible cohort charts after Dallas expansion.

Extended RelayOps scenario: cross-functional read

Imagine RelayOps's quarterly review for building initial distribution. An angel investor asks whether dispatch pain justifies another build sprint. A pilot COO asks whether overtime reduction pays for software. A dispatcher lead asks whether the console survives Monday heat-wave call volume. A weak go-to-market, positioning, and founder-led sales answer pleases one stakeholder. A strong answer links evidence: interview prevalence, timed shadow data, pilot median dispatch time, and renewal intent.

Work a conservative arithmetic example. Suppose RelayOps targets 100-technician firms at $28 per technician per month ($2,800 MRR per logo). Closing 18 beachhead logos yields $50,400 MRR ($605k ARR). If CAC (customer acquisition cost, sales and marketing to win one paying customer) is $18,000 per logo, payback in months equals CAC divided by monthly gross profit. At 80% gross margin on MRR, monthly profit ~$2,240; payback ~8 months. Check: 18,000 / 2,240 ≈ 8.0 ✓. Founders who skip this math raise before they know whether GTM is repeatable.

Stakeholder conflict is normal. Jordan may push feature breadth; Maya must protect RAT (riskiest assumption test, cheapest experiment that falsifies the highest-impact uncertain belief) scope. Building Initial Distribution gives language to negotiate with pre-registered metrics rather than charisma. If evidence is descriptive only, label it and fund the next test instead of scaling spend.

For deeper study on this unit's specialty, see ENT 403 (Startup Go-to-Market and Founder-Led Sales). ENT 301 integrates the full arc; electives provide textbook-depth units you can take after this core course.

Technical mechanics and checks (RelayOps patterns)

For building initial distribution, show work the way finance shows reconciliations. Opportunity scorecards print weighted criteria and explicit kill rules. Interview synthesis tables show code frequency with qualified denominators only. MVP scorecards list assumption rank, build weeks, runway share, and kill criteria. Cap tables after SAFE conversion show pre-money, post-money, and founder ownership with check lines.

Use plain-language hypotheses before instruments. Example: "If fewer than six of ten operations leaders rank same-day rebalance in top-three pains, RelayOps deprioritizes hypothesis H1." That hypothesis is falsifiable without code. Weak hypotheses hide inside feature roadmaps.

Spreadsheet grain matters. Customer-level tables suit funnel conversion; logo-month tables suit retention; assumption-level tables suit experiment backlogs. RelayOps forbids ambiguous metrics like "engagement" without operational definitions tied to dispatch jobs routed per active day.

Common executive questions (and disciplined answers)

Executives ask short questions that require long disciplined answers. "How sure are we?" maps to evidence labels (exploratory, descriptive, causal), not bravado. "What is the dollar impact?" maps to overtime saved, slots recovered, or MRR with stated assumptions. "Can we ship faster?" maps to risk of untested adoption during live emergencies. "Why not copy ServiceTitan?" maps to wedge focus and beachhead economics, not feature envy.

RelayOps's credible answer format for building initial distribution is three bullets: recommendation, evidence strength, and next test if limitations matter. A fourth bullet states what would falsify the recommendation within 60 days. That discipline prevents founders from becoming either bottlenecks or rubber stamps for investor narratives.

Judgment under uncertainty (RelayOps decision log)

Founders who master building initial distribution keep a decision log: date, decision, evidence at time, dissent captured, review date. When RelayOps chose emergency-queue MVP over full suite parity, the log recorded HeatRoute's LOI-to-active failure mode as contrast case. When Phoenix beat Dallas on retention, the log triggered segment screener review rather than blaming sales tone.

Your workbook should mirror that log format for one venture you follow. If you cannot write dissent and kill criteria, you have a story, not a decision. Building Initial Distribution is how teams convert stories into capital-efficient learning.

Applying Building Initial Distribution at RelayOps

When RelayOps applies building initial distribution, Maya Chen and Jordan Okonkwo anchor decisions in field evidence, not slide optimism. Their beachhead (80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians) experiences 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows. Discovery interviews suggested $89 to $149 per technician per month in discovery interviews. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo). Every framework in this lesson should translate into a falsifiable claim about that segment, not generic startup advice.

Consider how go-to-market, positioning, and founder-led sales changes capital allocation. RelayOps started with roughly $400k runway and ~$45k monthly burn before seed. A one-month delay on the wrong opportunity costs more than a month of disciplined interviews. That is why building initial distribution is a CEO-level skill, not a brainstorming exercise.

Document owners alongside metrics. Maya owns discovery synthesis; Jordan owns build scope tied to assumption ranks; both sign kill criteria before pilots. When definitions live in a shared glossary (pilot versus beta, activation versus login), the team avoids comparing incompatible cohort charts after Dallas expansion.

Extended RelayOps scenario: cross-functional read

Imagine RelayOps's quarterly review for building initial distribution. An angel investor asks whether dispatch pain justifies another build sprint. A pilot COO asks whether overtime reduction pays for software. A dispatcher lead asks whether the console survives Monday heat-wave call volume. A weak go-to-market, positioning, and founder-led sales answer pleases one stakeholder. A strong answer links evidence: interview prevalence, timed shadow data, pilot median dispatch time, and renewal intent.

Work a conservative arithmetic example. Suppose RelayOps targets 100-technician firms at $28 per technician per month ($2,800 MRR per logo). Closing 18 beachhead logos yields $50,400 MRR ($605k ARR). If CAC (customer acquisition cost, sales and marketing to win one paying customer) is $18,000 per logo, payback in months equals CAC divided by monthly gross profit. At 80% gross margin on MRR, monthly profit ~$2,240; payback ~8 months. Check: 18,000 / 2,240 ≈ 8.0 ✓. Founders who skip this math raise before they know whether GTM is repeatable.

Stakeholder conflict is normal. Jordan may push feature breadth; Maya must protect RAT (riskiest assumption test, cheapest experiment that falsifies the highest-impact uncertain belief) scope. Building Initial Distribution gives language to negotiate with pre-registered metrics rather than charisma. If evidence is descriptive only, label it and fund the next test instead of scaling spend.

For deeper study on this unit's specialty, see ENT 403 (Startup Go-to-Market and Founder-Led Sales). ENT 301 integrates the full arc; electives provide textbook-depth units you can take after this core course.