# An AI SaaS gross margin calculator, and the inputs it needs > An AI SaaS gross margin calculator needs four inputs, and most teams guess three. Margin computed blended, per tier and per customer, with math. URL: https://getculpa.com/ai-saas-gross-margin-calculator Last reviewed: 2026-08-01 ## Answer An AI SaaS gross margin calculator needs four inputs: revenue for the period, model spend, the share of that spend serving customers, and infrastructure that scales with usage. Most teams have the first and guess the rest. Culpa, a local-first LLM cost, margin, and forecast ledger, reconciles metered spend against revenue you import, so the middle two stop being estimates. ## Why this happens The same month yields three different margins depending on how you cut it, and all three are correct. Blended margin tells you whether the business works. Margin per plan tier tells you which plan works. Margin per customer tells you which accounts work. Teams report the first, make decisions that only the second and third can answer, and end up defending a healthy blended figure while their fastest-growing tier loses money on every new logo. ## What this usually looks like - Board reporting carries one gross margin number and no breakdown behind it. - The tier sales pushes hardest has never had its margin computed separately. - Model spend and revenue live in systems nobody has joined, so margin gets assembled by hand each quarter. - Blended margin looks stable across a period when the mix underneath it moved a long way. ## Common mistakes - Reporting only blended gross margin. Why it hurts: A blend hides a loss-making tier behind a profitable one, and growth then makes the problem bigger. Do instead: Compute margin per tier and per account as well, and treat the blend as a summary rather than a finding. - Leaving usage-scaling infrastructure out of the cost line. Why it hurts: Vector storage, embedding refreshes and egress all grow with usage, so margin reads high by whatever they cost. Do instead: Include every cost that moves with usage, and keep fixed platform costs out so the line stays comparable. - Computing margin once a quarter. Why it hurts: Model mix and provider rates both move monthly, so a quarterly figure describes a period already gone. Do instead: Recompute monthly against a dated price book, and watch the trend rather than the level. ## Self-check - Write down revenue and model spend for last month, then compute the blend. That's your starting point, not your answer. - Split both sides by plan tier and compute margin for each. The spread will be wider than expected. - Check what share of model spend is customer-serving rather than evaluation or internal work. - Add every infrastructure cost that grows with usage, then recompute. Note how far the number moved. - Find the tier with the lowest margin and check whether it's the one your sales team is compensated to sell. ## One month, three tiers, three very different answers (illustrative) A product on GPT-5.4 at real rates of $2.50 per million input and $15.00 output. Customer counts, plan prices and per-customer token volumes below are modelled. Starter: 400 customers x $29 = $11,600 revenue. Each uses (1.2 x $2.50) + (0.2 x $15.00) = $6.00, so $2,400 cost, margin 79.3% Growth: 90 customers x $149 = $13,410. Each uses (9 x $2.50) + (1.6 x $15.00) = $46.50, so $4,185 cost, margin 68.8% Scale: 12 customers x $499 = $5,988. Each uses (60 x $2.50) + (14 x $15.00) = $360.00, so $4,320 cost, margin 27.9% Blended: $30,998 revenue against $10,905 cost = 64.8% Scale is 19% of revenue and 40% of model spend, on 12 accounts The blended 64.8% sits between three tiers that behave nothing alike, and the worst of them at 27.9% is the one with the biggest logos and the loudest growth story. ## Cost figures Every figure carries its confidence and its source. No figure on this site is provider-reported. - 27.9% to 79.3% — modelled gross margin spread across three plan tiers in the same month [estimated] Source: Each tier computed at real GPT-5.4 rates per million from the price book, effective 2026-07-02. A range because customer counts and token volumes are modelled. - $10,905 — modelled total monthly model spend across all three tiers [calculated] Source: $2,400 + $4,185 + $4,320 from the teardown arithmetic at real GPT-5.4 rates. ## FAQ Q: What belongs in the cost line of an AI gross margin calculation? A: Model spend for customer-serving traffic, retries included, plus any infrastructure that scales with usage such as vector storage and embedding refreshes. Fixed platform costs and evaluation runs belong elsewhere, or the line stops being comparable month to month. Q: Why does margin per tier differ so much from blended margin? A: Because usage per customer varies far more than price per customer. A tier priced at seventeen times another can carry sixty times the model spend, so the blend describes an average customer who exists nowhere in your base. Q: How often should gross margin be recomputed? A: Monthly. Model mix drifts, prompts grow and provider rates change on dates you don't control, so a quarterly figure is usually describing conditions that stopped applying weeks before anyone read it. ## Sources - OpenAI API pricing: https://developers.openai.com/api/docs/pricing Run the free Cost Leak Scan: https://app.getculpa.com/scan?source=pseo&slug=ai-saas-gross-margin-calculator&cluster=margin Machine-readable index of every guide: https://getculpa.com/api/pages Human-readable index of every guide: https://getculpa.com/guides Site overview: https://app.getculpa.com/llms.txt Privacy: Culpa runs on your infrastructure. Your prompts and responses never leave it. Culpa counts calls to run your plan, and it fails open, so if it ever breaks your app keeps running.