Startup Cost Structures

Cost structure is the physics of your venture

Every startup story eventually collides with a spreadsheet. Founders who understand cost structure (how fixed and variable costs combine to produce unit economics and monthly burn) can explain why a $33,600 annual contract still loses money in year one, or why two engineers on payroll consume eight months of runway before a single beachhead logo renews.

RelayOps enters this unit with validated dispatch pain, early pilot revenue, and roughly $400k cash on hand. Maya Chen (CEO) and Jordan Okonkwo (CTO) must separate fixed costs (salaries, rent, core tools that persist if revenue is zero) from variable costs (cloud usage tied to active technicians, success hours per onboarding, payment processing). Confusing the two produces fantasy unit economics and surprise board meetings.

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 404 (Entrepreneurial Finance, SAFEs and Cap Tables) 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 maps RelayOps cost categories, contribution margin per technician seat, and how cost structure choices constrain fundraising timing. Deeper instrument modeling lives in ENT 404 (Entrepreneurial Finance, SAFEs and Cap Tables); ENT 301 integrates finance with the operating journey.

Fixed versus variable costs in early B2B SaaS

Fixed costs at RelayOps include founder salaries ($14,000 per month combined at below-market cash), office coworking ($1,200), core SaaS stack ($2,800), and insurance ($600). These costs recur if customer count is zero. Variable costs scale with usage and delivery: AWS and telephony ($1.40 per active technician per month), customer success onboarding ($3,200 per new logo in month one), and payment fees (2.9% of collections).

B2B workflow software often looks high-margin at scale but assisted at pilot stage. RelayOps gross margin on software revenue targets 80% at steady state; pilot delivery pulls effective margin to ~62% when success hours are fully loaded.

Managers should print a monthly cost bridge: starting cash, revenue collected, fixed burn, variable burn, ending cash. Ambiguous "ops" line items hide hiring mistakes.

RelayOps monthly cost map (pre-seed operating plan):

Semi-fixed costs are the dangerous middle: they feel variable in spirit but contractually fixed for a quarter. RelayOps caps GTM experiments at $6,000 per month until CAC (customer acquisition cost, sales and marketing to win one paying customer) payback is measured.

Contribution margin and unit economics

Contribution margin per technician seat equals price minus variable cost per seat. RelayOps prices at $28 per technician per month in early contracts. Variable cloud and support allocation: ~$4.20 per seat. Contribution margin: $23.80 per seat per month, or 85% on seat-level variable costs only.

Logo-level economics require technician count. A 100-technician logo generates $2,800 MRR and ~$2,380 monthly contribution before fixed GTM and engineering. ACV (annual contract value, yearly revenue per customer contract) at that price: $33,600. Check: 100 × $28 × 12 = $33,600 ✓

Unit economics connect to cost structure: if onboarding stays founder-heavy, the "variable" success line is artificially low and margin is overstated.

People costs dominate pre-PMF startups

At pre-seed, 70 to 85% of burn is people. RelayOps fully loaded monthly burn approximates $45k with two founders, one contractor, and modest GTM. Adding a full-time AE (account executive, quota-carrying seller) at $9,500 loaded per month plus $4,000 travel and tools raises burn ~30% before that hire closes a single logo.

Hiring before cost structure clarity is how teams buy a shorter runway without buying learning speed. ENT 301 treats headcount as the largest fixed-cost lever; ENT 406 covers scaling org design in depth.

Contractor versus employee tradeoff: contractors add flexibility but weaken IP assignment clarity; RelayOps converts critical contractors to employees before seed close.

Capital intensity and operating leverage

Operating leverage means fixed costs spread across more revenue units. RelayOps at 5 logos and 420 technicians has very different leverage than at 50 logos. Engineering fixed across 420 seats yields ~$20 per seat; across 42 seats yields ~$200 per seat.

Capital-intensive models (inventory, hardware installs) differ from RelayOps SaaS pattern. Students should label which costs are recoverable on churn (cloud) versus sunk (six weeks of custom integration).

Cost structure links to fundraising narrative

Investors do not fund burn; they fund milestones per dollar. RelayOps seed narrative: $1.8M SAFE (simple agreement for future equity, investment converting to shares at a future priced round) buys 24 months to $3.2M ARR (annual recurring revenue, subscription revenue times twelve) with CAC payback under 12 months.

Cost structure tables in the data room must reconcile to bank statements. Maya keeps a rolling three-month actuals versus plan with variance explanations.

RelayOps integrative read: cost structure as strategy

Cost structure is not only finance; it is strategy made visible. When RelayOps chooses a coworking office instead of a dedicated lease, it buys optionality at the cost of privacy for sales calls. When it caps contractor spend instead of hiring a second engineer, it buys runway months at the cost of integration speed. Every line item should have a named owner and a kill criterion.

Students auditing any venture should ask: which costs rise automatically with revenue, which costs rise with headcount decisions, and which costs are truly sunk? RelayOps cloud costs rise with technician seats; founder salaries rise only when the board approves market adjustments; custom integration work for a single logo is sunk if that logo churns.

Cross-link to ENT 404: investors will rebuild your cost bridge from bank PDFs. If marketing spend sits in the CEO's personal card, diligence slows and trust drops. Maya centralizes spend on company cards with monthly classification rules.

Maya prepares a board-ready cost bridge. Assumptions: 18 logos, 1,620 active technicians (90 average per logo), $28 per technician per month, 80% logo gross margin target at steady state, current burn ~$45,000 per month.

Part A: Revenue and variable costs

MRR: 1,620 × $28 = $45,360. Check: 1,620 × 28 = 45,360 ✓

Variable cloud/comms: 1,620 × $1.40 = $2,268.

Payment processing (2.9%): $45,360 × 0.029 = $1,315.

Success hours (steady state, $1,100 per logo per month): 18 × $1,100 = $19,800.

Total variable: $2,268 + $1,315 + $19,800 = $23,383.

Part B: Fixed costs and net burn

Fixed operating (people, rent, tools, GTM base): ~$45,000 pre-scale; at 18 logos add one CS hire $7,500 loaded.

Fixed subtotal: ~$52,500.

Contribution after variable: $45,360 − $23,383 = $21,977.

Net burn: $52,500 − $21,977 = $30,523 per month.

Check: positive contribution but still net burn until scale or efficiency gains ✓

Part C: Sensitivity

If average technicians per logo falls to 75: MRR = 18 × 75 × $28 = $37,800. Variable ~$19,400. Contribution ~$18,400. Net burn rises to ~$34,100.

Managerial trigger: if logo-weighted technician count drops below 80 for two quarters, revisit ICP (ideal customer profile, best-fit customer definition) screener before adding AE headcount.

Part D: Managerial read

Board question: "Why raise seed if contribution margin is positive?" Answer: positive unit contribution does not cover fixed GTM and product investment required to reach $3.2M ARR. External capital buys milestone velocity, not survival alone. See ENT 404 for round modeling.

FieldInstall sold IoT (internet of things, connected device) dispatch tablets with $40,000 upfront install revenue and $6,000 annual software. Founders treated install crews as "one-time" and excluded them from CAC. True cost structure: $18,000 hardware COGS (cost of goods sold, direct product cost) plus $9,000 install labor per logo. First-year gross profit was negative on 60% of deals. RelayOps avoids hardware COGS; its risk is services masquerading as SaaS through heavy onboarding.

Managerial read: map every cost to fixed, variable, or sunk before quoting ACV-based payback.

RelayOps closes 3 new logos at 110 technicians each, $28 per month, with $3,800 onboarding cost per logo in month one. Fixed burn stays $45,000. Compute: (1) incremental MRR, (2) month-one variable onboarding total, (3) net burn in month one if no other changes. Show check lines.

Solution

(1) Incremental MRR: 3 × 110 × $28 = $9,240. Check: 330 × 28 = 9,240 ✓

(2) Onboarding variable: 3 × $3,800 = $11,400. Check: 11,400 ✓

(3) Assume baseline net burn $45,000 with contribution from existing base unchanged; incremental contribution month one ≈ $9,240 − (330 × $1.40) − 2.9% fees ≈ $9,240 − $462 − $268 = $8,510. Net burn ≈ $45,000 − $8,510 + $11,400 = $47,890. Check: burn rises in month one due to onboarding spike ✓

Managerial read: logo cohort economics improve from month two if onboarding is one-time.

Why does RelayOps classify GTM experiments as semi-fixed rather than variable?

Solution

Spend is committed for a quarter (events, SDR tools) but not strictly proportional to technician seats. Labeling it variable would understate fixed runway risk when pausing experiments is politically hard.

Key takeaways

• Separate fixed, variable, and semi-fixed costs before fundraising narratives.
• Contribution margin per seat differs from logo-level profitability after onboarding.
• People dominate pre-PMF burn; headcount is the primary fixed lever.
• Operating leverage improves as technician seats spread engineering fixed costs.
• Cost bridges must reconcile to bank actuals for investor diligence.

1. Build a one-page cost bridge for RelayOps with your own headcount assumptions.
2. Identify one RelayOps cost that is miscategorized as variable today.
3. Continue to Lesson 2: Runway and Burn.

Applying Startup Cost Structures at RelayOps

When RelayOps applies startup cost structures, 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 startup finance, runway, and fundraising instruments 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 startup cost structures 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 startup cost structures. 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 startup finance, runway, and fundraising instruments 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. Startup Cost Structures 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 404 (Entrepreneurial Finance, SAFEs and Cap Tables). 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 startup cost structures, 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 startup cost structures 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 startup cost structures 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. Startup Cost Structures is how teams convert stories into capital-efficient learning.

Applying Startup Cost Structures at RelayOps

When RelayOps applies startup cost structures, 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 startup finance, runway, and fundraising instruments 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 startup cost structures 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 startup cost structures. 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 startup finance, runway, and fundraising instruments 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. Startup Cost Structures 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 404 (Entrepreneurial Finance, SAFEs and Cap Tables). 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 startup cost structures, 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 startup cost structures 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 startup cost structures 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. Startup Cost Structures is how teams convert stories into capital-efficient learning.