Chapter 3: Cost Structure Forecasting

Costs Are Step Functions

A pervasive failure pattern in startups: treating costs as linear percentages of revenue. In reality, costs jump in discrete steps.

Hiring a second sales manager, upgrading database instances, or crossing a compliance threshold (like SOC2 audit) results in sudden, non-linear jumps in expense. The Cost Structure Forecaster models these "step functions" so you're never blindsided.

Understanding why costs behave this way is critical. Most business expenses have thresholds -- they remain constant until you hit a capacity limit, at which point they jump to a new level. A single PostgreSQL instance handles your first 10,000 users, but at 15,000 users, you need a read replica, load balancer, and caching layer. Your costs don't gradually increase by $5 per user -- they jump by $800/month all at once. A solo customer success manager handles 50 accounts, but at 60 accounts, quality drops precipitously, and you need to hire a second person at $70,000/year. These "step function" jumps are the landmines buried in your cost model.

The founders who navigate this well are the ones who map these thresholds in advance. They know that at 100 customers, they'll need a second support hire. At 500 customers, they'll need SOC2 certification. At 1,000 customers, they'll need a dedicated DevOps engineer. Each of these creates a predictable cost jump that should be modeled, not discovered in a crisis.

The Hidden Costs Founders Forget

Beyond the obvious categories, several cost lines regularly catch founders off guard:

Burn Rate Scenarios

The Burn Rate Calculator models your "Runway" -- the time until you exhaust cash reserves. Investors now demand 18-24 months of runway to weather market volatility. This isn't an arbitrary number -- it reflects the typical time needed to find product-market fit, iterate on your business model, and raise the next round of funding.

Burn rate is deceptively simple to calculate but critically important to get right. Many founders calculate their burn rate once and never update it, leading to nasty surprises. Your burn rate should be recalculated monthly, with particular attention to how it changes as you hire, scale infrastructure, and invest in marketing.

The "Default Alive" Test

Y Combinator's Paul Graham popularized the question: "Are you default alive or default dead?" The answer depends on three variables: your current monthly revenue, your monthly growth rate, and your monthly expenses. If you extrapolate your revenue growth and it crosses your expense line before your cash runs out, you're default alive. If it doesn't, you're default dead.

This is the single most important question to answer at the feasibility stage, because it determines your strategic options. Default alive companies can be selective about investors, patient about product decisions, and aggressive about pricing experiments. Default dead companies are at the mercy of external capital and can't afford to experiment -- they need things to work on the first try.

AI-Specific Cost Drivers

Forecasting for AI startups requires granular modeling of "Compute Unit Economics." This is a new discipline that most traditional financial models don't cover, but it's essential for any startup building on foundation models.

Modeling AI Costs in Practice

To model AI costs accurately, you need to understand your product's "interaction profile" -- the mix of simple, standard, and complex queries a typical user generates. Here's a practical approach:

1. Log everything during prototyping. Track token counts, latency, and cost for every AI interaction in your prototype or MVP. This gives you real data instead of estimates.
2. Calculate cost per user per month. Multiply average interactions per user by average cost per interaction. This becomes your AI COGS per user.
3. Model the range. Your lightest users might cost $0.50/month in inference, while power users might cost $15/month. Understand this distribution because it affects your pricing tiers.
4. Plan for cost decline. AI inference costs have been declining 50-70% annually. Your year-two model can assume lower costs, but your year-one model should use today's prices.

What You Walk Away With

• Cost Classification: Fixed vs. variable costs clearly separated in your model, with step-function thresholds identified and planned for.
• Burn Rate Scenarios: Understanding of "Default Alive" vs. "Venture Scale" paths, with clear criteria for choosing between them.
• AI Cost Model: Granular understanding of token/inference economics, model routing strategy, and optimization levers.
• Runway Calculation: A clear view of your "Cash Zero" date under conservative, base, and optimistic scenarios.
• Hidden Cost Awareness: Identification of the support burden, hiring costs, technical debt, and compliance expenses that frequently blindside early-stage startups.