Designing the Business Model

A venture thesis needs an economic engine, not just a product sketch

Customer discovery can confirm pain without proving a company can capture value. Dispatch managers at mid-market HVAC firms may hate whiteboard scheduling and still resist software that costs more than the overtime it saves. A business model (how a venture creates, delivers, and captures value) translates RelayOps's emergency dispatch insight into revenue logic, cost structure, and repeatable unit economics before the team burns runway on the wrong wedge.

Maya Chen and Jordan Okonkwo left Summit Climate with operator credibility but not a finished P&L (profit and loss statement, summary of revenue and expenses). ENT 401 interviews suggested WTP (willingness to pay, stated price acceptance in discovery) of $89 to $149 per technician per month. That range is a hypothesis until contracts renew. Designing the business model forces founders to name who pays, for what job, on what cadence, with what gross margin, and which costs scale with technicians versus logos.

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 402 (Product-Market Fit and Startup Experimentation) 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. This lesson connects opportunity validation to the build-and-test phase. ENT 402 (Product-Market Fit and Startup Experimentation) goes deeper on assumption maps and MVP variants; ENT 301 keeps the integrated arc so you can advise founders who must ship learning and revenue in the same quarter.

RelayOps's early model is B2B SaaS (business-to-business software as a service, subscription software sold to companies) priced per active field technician, sold through founder-led pilots, and delivered as a narrow emergency dispatch console before broader scheduling modules. Your job is to stress-test whether that model survives contact with payroll, procurement, and summer peak season churn.

Business Model Canvas for operator-led B2B SaaS

The Business Model Canvas (a one-page map of nine building blocks that describe how a venture works) is not a pitch-deck decoration. It is a checklist for falsifiable economics. RelayOps fills nine blocks with field-service specifics: customer segments (80-to-200 technician residential-heavy HVAC and plumbing firms in Sun Belt metros), value propositions (cut median emergency dispatch time and overtime on peak weeks), channels (founder-led outbound and trade association intros), customer relationships (high-touch onboarding with dispatcher champions), revenue streams (monthly per-technician subscription), key resources (dispatch workflow IP and integration adapters), key activities (pilot delivery and usage reviews), key partners (SMS gateways and optional CRM connectors), and cost structure (engineering payroll, cloud hosting, and customer success hours per logo).

Founders fail when they treat all nine blocks as equally certain. After ENT 401, RelayOps should mark revenue streams and channels as high-uncertainty until three paid pilots renew. Value propositions carry medium certainty because pain was observed repeatedly. Cost structure is partially known from burn ($45,000 per month) and runway ($400,000 pre-seed). The canvas exposes which block must move next, not whether the logo looks balanced.

For B2B operations software, the canvas should include an implicit tenth block: implementation burden. If RelayOps requires two weeks of dispatcher retraining per site, CAC (customer acquisition cost, sales and marketing spend to win one paying customer) understates true cost unless onboarding hours appear in key activities and cost structure.

RelayOps canvas excerpt with evidence labels:

Label strength honestly. Descriptive evidence supports the next experiment; it does not justify a national rollout. ENT 402 teaches how to convert exploratory revenue blocks into validated blocks using paid pilots and kill criteria.

Value capture: per-seat pricing and annual contract value

RelayOps prices per active technician rather than per dispatcher seat because field capacity is what owners budget. A 100-technician firm at $28 per technician per month yields $2,800 MRR (monthly recurring revenue, predictable subscription revenue per month) and $33,600 ACV (annual contract value, yearly revenue per customer logo). Discovery WTP ranged $89 to $149; pilot pricing often lands near $99 to anchor inside that band without training customers to expect $49 forever.

Per-seat models align revenue with customer growth: when a plumbing firm hires 15 technicians for summer, RelayOps's revenue rises if technicians are active in the system. The model fails if customers game inactive seats or if dispatchers refuse to tag technicians in the console. Usage-based top-ups are an alternative, but they complicate forecasting for early-stage boards that need simple ARR (annual recurring revenue, MRR times twelve) narratives.

Maya should model three ACV scenarios in every board update: conservative ($89 per tech), base ($99), and stretch ($129). At 100 technicians, those map to $106,800, $118,800, and $154,800 ACV per logo. Multiplying by beachhead logo count shows whether seed capital ($1.8 million target) matches realistic penetration, not TAM (total addressable market, entire theoretical demand) fantasy.

Unit economics and payback before scale

A business model is viable only if unit economics (profit or contribution per customer relative to acquisition and delivery cost) work at the beachhead, not after mythical scale. RelayOps assumes CAC of roughly $18,000 per logo through founder-led sales (Maya's time, travel, pilot support, and Jordan's onboarding engineering). At $2,800 MRR and 80% gross margin, monthly gross profit is about $2,240. Payback months equal CAC divided by monthly gross profit: 18,000 / 2,240 ≈ 8.0 months.

Founders should print payback alongside LTV (lifetime value, expected gross profit over a customer relationship). If gross churn is 15% annually at steady state, average customer life is roughly 1 / 0.15 ≈ 6.7 years in a simple model, but early-stage logos churn faster when pilots fail. Using a conservative 3-year life at $2,240 monthly margin yields LTV ≈ $80,640 before discounting. LTV-to-CAC above 3:1 is a common investor heuristic; RelayOps must verify it with renewal data, not interview enthusiasm.

Overtime reduction is the customer-side unit economic story. If RelayOps saves 10% overtime on a 100-technician firm spending $1.2 million annually on field labor overtime, $120,000 is the value pool. Software at $118,800 ACV captures roughly 99% of stated savings if fully attributed, which owners will challenge. Positioning should claim a credible slice (for example 20-30% of overtime reduction) to preserve trust.

Wedge, scope boundary, and services trap

Business model design picks a wedge (the narrow job that earns the first budget and usage habit) and defers adjacent jobs. RelayOps's wedge is emergency dispatch for residential-heavy HVAC firms, not full replacement of ServiceTitan. Invoicing, inventory, marketing automation, and AI route optimization sit outside the initial scope boundary.

Custom services revenue is a common trap. If pilots pay $20,000 setup fees for bespoke integrations, gross margin looks healthy while the company becomes a consultancy. RelayOps should cap services at 10% of revenue and treat them as learning scaffolding, not the model. ENT 402's concierge MVP uses manual routing temporarily; the business model must still point to software margin.

Jordan's engineering roadmap should map every feature to a canvas block. A QuickBooks export belongs in key partners and feasibility assumptions, not in month-one value propositions unless a pilot owner makes renewal contingent on it.

Linking the model to ENT 402 experimentation

Every canvas block should spawn at least one ranked assumption on the assumption map (beliefs plotted by impact if wrong and uncertainty, used to prioritize tests). RelayOps ranks desirability of dispatcher adoption before viability of enterprise pricing. ENT 402 provides textbook depth on RAT (riskiest assumption test, the cheapest experiment that could falsify the highest-impact uncertain belief) design; ENT 301 requires you to see the canvas and the map as one system.

When Maya updates investors, she should show which canvas block moved last month. Example: "Revenue streams shifted from exploratory to descriptive because Desert Cool paid $27,324 for a 90-day pilot at $99 per technician." That sentence is more convincing than a feature screenshot.

Board members should challenge block coupling. If channels stay founder-led while cost structure adds three account executives, payback math breaks. Designing the business model is choosing what not to fund yet.

Maya prepares a seed narrative. Jordan wants to add a mobile app and ServiceTitan integration. An angel asks whether RelayOps is a software company or a dispatch consultancy. Maya runs a canvas-based stress test with explicit arithmetic.

Part A: Canvas gaps flagged

Revenue streams remain exploratory: zero renewals after paid pilot. Channels depend on Maya's network in Phoenix; no repeatable playbook. Key partners for CRM sync are undefined. Value proposition claims 40% dispatch time reduction; only 12 live emergency jobs logged at first pilot site.

Cost structure adds $12,000 per month if Jordan hires a mobile contractor. Payback stretches if CAC rises without conversion improvement.

Part B: Unit economics table

Check: 92 × $99 = $9,108 MRR ✓. 9,108 × 0.75 = $6,831 ✓.

Part C: Recommendation

Persevere on per-technician SaaS wedge; defer mobile and ServiceTitan API until emergency queue RAT passes. Cap services revenue. Publish payback and LTV-to-CAC using pilot CAC ($14,000) separately from scaled CAC ($18,000) so investors see learning efficiency.

Managerial read: the angel's consultancy fear is valid until software margin exceeds 70% of revenue for two consecutive quarters.

Part D: Managerial read

If the owner asks why RelayOps costs less than ServiceTitan, Maya answers with wedge scope: emergency dispatch reliability, not full ERP (enterprise resource planning, integrated back-office system). Price per technician maps to measurable overtime reduction, not seat count for office staff.

HeatRoute Dispatch (fictional) mapped a beautiful Business Model Canvas but priced flat per company regardless of technician count. Mid-market HVAC owners with 120 technicians felt punished versus competitors with 60. HeatRoute's ACV looked stable while unit economics hid margin collapse on large logos. RelayOps's per-technician model aligns price with capacity and makes expansion revenue visible when firms hire seasonal techs.

Managerial read: revenue model choice is segmentation choice. Flat pricing signals SMB (small and medium-sized business) mindset; per-seat signals operational scale.

RelayOps debates two models for year one: (A) pure per-technician SaaS at $99 with no setup fee, or (B) $15,000 setup plus $79 per technician per month. Expected pilot: 92 technicians for 90 days. CAC is $16,000 under both models. Gross margin is 78% on recurring revenue; setup fees carry 40% margin due to engineering time.

Tasks: (1) Compute 90-day revenue under A and B. (2) Compute payback months using 90-day gross profit as a simple proxy for monthly GP (divide 90-day GP by 3). (3) Recommend A or B for learning and investor narrative in one paragraph.

Solution

Model A: 92 × $99 × 3 = $27,324 total; recurring GP = 27,324 × 0.78 = $21,313; monthly GP proxy = 21,313 / 3 = $7,104; payback = 16,000 / 7,104 ≈ 2.25 months.

Model B: Recurring = 92 × $79 × 3 = $21,804; setup = $15,000; total = $36,804; recurring GP = 21,804 × 0.78 = $17,007; setup GP = 15,000 × 0.40 = $6,000; total GP = $23,007; monthly GP proxy = 23,007 / 3 = $7,669; payback = 16,000 / 7,669 ≈ 2.09 months.

Recommend Model A for learning: it preserves WTP signal inside the $89-$149 band without teaching owners to expect heavy services discounts. Model B improves short-term cash but blurs software versus consultancy margin. Check: Model A 90-day revenue $27,324 ✓; Model B total $36,804 ✓.

Key takeaways

• Business model design connects pain validation to revenue, cost, and margin logic.
• Per-technician pricing aligns RelayOps with how HVAC owners budget field capacity.
• Unit economics and payback must work at beachhead scale before hiring a sales team.
• Wedge scope and services caps prevent consultancy drift during pilots.
• Canvas blocks should link to ranked assumptions tested in ENT 402-style experiments.

1. Fill a Business Model Canvas for RelayOps and mark each block exploratory, descriptive, or validated.
2. Compute payback for a 120-technician logo at $109 per month with $20,000 CAC and 80% gross margin.
3. Continue to Minimum Viable Products: how RelayOps scopes the emergency dispatch MVP.

Applying Designing the Business Model at RelayOps

When RelayOps applies designing the business model, 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 business models, MVPs, and experimentation 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 designing the business model 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 designing the business model. 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 business models, MVPs, and experimentation 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. Designing the Business Model 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 402 (Product-Market Fit and Startup Experimentation). 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 designing the business model, 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 designing the business model 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 designing the business model 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. Designing the Business Model is how teams convert stories into capital-efficient learning.

Applying Designing the Business Model at RelayOps

When RelayOps applies designing the business model, 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 business models, MVPs, and experimentation 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 designing the business model 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 designing the business model. 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 business models, MVPs, and experimentation 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. Designing the Business Model 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 402 (Product-Market Fit and Startup Experimentation). ENT 301 integrates the full arc; electives provide textbook-depth units you can take after this core course.