System Active / Node 01
Unit Cost Architecture

Your tech costs are on the P&L.
What they cost per unit isn't.

Margineer deconstructs your consolidated COGS lines bottoms-up—isolating cloud infrastructure, LLM token consumption, third-party APIs, and technical delivery payroll. We transform raw operations data into clear, defensible gross margins so you can optimize pricing ahead of rising costs.

Fig. 1 — Where You Stand

Gross Margin Benchmarks by Business Model

Business ModelHealthyWatchAt Risk
Pure SaaS / Software≥75%60–75%<60%
AI / LLM-Embedded Product≥60%45–60%<45%
Infrastructure or Compute-Heavy Product≥65%50–65%<50%
Services-Heavy / High-Touch Delivery≥55%40–55%<40%
General starting points, not a verdict — find your row, then run your own numbers.

Built by operators who've run cloud cost and FinOps functions inside real technology organizations — not analysts who've only studied the reports.

The Problem

One line on the P&L. Six things blended into it.

Your COGS is already consolidated — that's what accounting is for. It's just too blended to answer the question that actually matters: does the price still cover what it costs to deliver?

01

Cloud & Hosting

AWS, GCP, Azure, and owned infrastructure that scales with usage — one part of a bigger, blended COGS number.

02

AI & LLM Consumption

Claude, OpenAI, and other model costs billed by the token — often the fastest-growing line nobody's isolated yet.

03

Embedded Software & APIs

Auth0, SendGrid, Twilio, and other vendor APIs baked into what it actually costs to deliver the product.

04

Merchant Processing Fees

Stripe, Adyen, and gateway fees that scale as a % of gross revenue — a different lever than usage-based software.

05

Production & Delivery Headcount

The fully loaded cost of DevOps, SREs, and technical support keeping the product live for customers.

06

Capitalized Product Amortization

Non-cash amortization of capitalized development costs — easy to omit until an audit finds it.

How It Works

From one blended COGS line to a price per unit.

1
Enter revenue, units, and your six COGS lines.
Cloud, AI usage, embedded software, merchant fees, delivery headcount, and capitalized amortization — broken out, not blended.
2
See your real gross margin and cost per unit.
The number a single COGS line on the P&L never shows you directly.
3
Get the price needed to hit your target margin — as costs rise.
Including what happens to the required price at 10% and 25% higher costs.
78% Gross Margin

This is the number a blended COGS line never shows you directly — and the one your pricing should be built around.

Not ready to run the full Diagnostic?

Get the one-page benchmark cheat sheet — the margin ranges by business model, sent straight to your inbox. No calculator required.

One email. Sent once. No spam.

"If you don't know your unit cost, you don't actually know your price — you're just guessing and hoping the gap doesn't close on you."

The Diagnostic

Gross Margin & Unit Cost

Enter annual figures to see your gross margin and cost per unit instantly. Unlock the full sensitivity report and pricing guidance with your work email.

Executive Snapshot

Five inputs. A 60-second read on what your cloud bill is really doing to your valuation.
Quick Read
$
$
#
The Four Signals
Cloud Waste Estimate
—
Idle and over-provisioned resources, estimated from tagging maturity.
Cloud Cost % of Revenue
—
Healthy SaaS range is typically 15–30% of revenue.
Unallocated / Untraceable Spend
—
Industry target is under 10% — above that, nobody owns the number.
Cloud Cost Per Customer
—
What it costs, in raw infrastructure alone, to serve one account.
These are illustrative estimates built from industry-standard FinOps heuristics, not a measured audit of your actual tagging or usage data — a real teardown replaces these with your real numbers.
Want the granular, bottoms-up version?
Continue to the Full Diagnostic ↓

Gross Margin & Unit Cost Calculator

Break your COGS down bottoms-up to see what it costs to serve one unit.
FY2026 · No. 002

Illustrative profiles — not real client data. Your architecture doesn't look like our templates?

$
#
%
Cost of Goods Sold (COGS) — bottoms-up
Total COGS
$0
—
Enter your COGS lines above to see the breakdown.
These six lines are what's already blended into your COGS on the P&L. Breaking them out bottoms-up — AI usage, merchant fees, and capitalized amortization included — is what makes the margin and unit cost below meaningful.
—Margin
Cost Per Unit
—

Fill in revenue, units, and all six COGS lines to see your gross margin and cost per unit.

The Playbook

A working reference for
pricing ahead of rising costs

Not a framework to memorize — a set of tools to reach for when you're building a budget, setting a price, or trying to figure out why margin slipped.

The COGS Breakdown Margin Benchmarks The Pricing Math Where Margin Quietly Erodes Glossary Review Cadence FAQ
01 — Framework

The COGS breakdown

This is the detail sitting inside the single COGS line on your income statement. Naming each part separately is what makes gross margin actionable instead of just reportable.

Cloud & Hosting

What scales with usage

AWS, GCP, Azure, and owned or colocated infrastructure billed by consumption. The most usage-sensitive line — it moves with every customer you add, whether or not your price does.

AI & LLM Consumption

What scales with every request

Claude, OpenAI, and other model or inference costs — priced by token or request, moving with usage in a way flat subscriptions rarely account for. Increasingly one of the fastest-growing lines in the stack, and one of the least isolated.

Embedded Software & APIs

What's built into the product

Auth0, SendGrid, Twilio, and other vendor APIs embedded in product delivery — distinct from internal tools, which are overhead, not COGS.

Merchant Processing Fees

What scales with revenue, not usage

Stripe, Adyen, PayPal, and other gateway fees — typically a fixed percentage of gross revenue plus a per-transaction charge. Blended into "software," it hides a lever that moves in lockstep with growth rather than efficiency.

Production & Delivery Headcount

What people cost to keep it live

The fully loaded cost of DevOps, SREs, and Tier-1/2 technical support directly required to keep the product running — not account managers or R&D headcount building what's next.

Capitalized Product Amortization

What GAAP requires you to see

Under standards like ASC 350-40, development costs capitalized during the application development stage get amortized into COGS once the product goes live — a non-cash line non-finance founders routinely miss.

02 — Reference

Gross margin benchmarks

General reference ranges by business model — not a verdict, and not a substitute for your own peer data. How you classify a cost between COGS and operating expense changes this picture as much as the cost itself does.

Business ModelHealthyWatchAt Risk
Pure SaaS / Software≥75%60–75%<60%
AI / LLM-Embedded Product≥60%45–60%<45%
Infrastructure or Compute-Heavy Product≥65%50–65%<50%
Services-Heavy / High-Touch Delivery≥55%40–55%<40%

A product that embeds heavy AI, LLM, or third-party data costs will run lower than pure software by design — that's a model difference, not automatically a problem. Run your own numbers in the calculator.

03 — Method

The pricing math, plainly

Three numbers, one formula. This is the entire logic behind the calculator.

Step 1

Find cost per unit

Total COGS ÷ units sold or active customers. This is what it actually costs to deliver one unit of your product, fully loaded.

Step 2

Set a target margin

The gross margin you need to fund R&D, sales, and overhead below the line — informed by the benchmarks above, not copied from them.

Step 3

Solve for price

Price = Cost Per Unit ÷ (1 − Target Margin). As cost per unit rises, the price required to hold the same margin rises with it — automatically, not by guesswork.

04 — Patterns

Where margin quietly erodes

None of these look like a bad decision in the moment. They look like reasonable calls that nobody re-priced against.

1

Pricing set once, never revisited

The price was right when COGS was lower. Nobody rechecked it as third-party or cloud costs rose underneath it.

2

Usage-based costs sold under a flat price

COGS that scales with usage — API calls, storage, compute — sold under a flat subscription. Margin erodes with every heavy user, invisibly.

3

Discounting without checking unit cost

A deal gets discounted below what it costs to serve, because nobody had the unit cost number in the room when the discount was approved.

4

A healthy blended margin hiding a losing segment

The overall number looks fine. One product line or customer segment underneath it is being subsidized by the rest.

5

Support cost that scales with complexity, not price

Enterprise accounts with heavy onboarding and support cost priced the same as self-serve customers who need almost none.

6

Infrastructure misclassified as overhead

Costs that directly support delivery get booked as general operating expense instead of COGS — margin looks better than it is, and nobody catches it until pricing breaks.

7

AI costs treated as a fixed line

Claude, OpenAI, or other model usage is billed by the token, but sold to customers as a flat feature or flat subscription tier. Heavier users quietly cost more to serve, with nothing in the price reflecting it.

8

Merchant fees blended into "software"

Payment processing scales as a percentage of gross revenue, not usage — a fundamentally different lever than a software subscription. Blending it in hides how much growth itself is costing in transaction fees.

9

Unamortized capitalized software

Development costs capitalized under standards like ASC 350-40 and never amortized into COGS make gross margin look better than it is — until an audit or acquirer's diligence team finds it.

05 — Glossary

Terms worth knowing

Vocabulary that shows up in margin and pricing conversations, defined plainly.

Gross Margin
Revenue minus COGS, divided by revenue. The percentage of every dollar that's left after covering the direct cost of delivering the product — before R&D, sales, and overhead.
Inference Cost
The per-request cost of running a prompt through an AI model like Claude or GPT, typically billed by input and output tokens. Behaves more like a cloud cost than a flat software subscription — it scales directly with usage.
Merchant Discount Rate (MDR)
The percentage plus fixed fee a payment processor like Stripe or Adyen charges per transaction — typically around 2.9% + $0.30. Scales with gross revenue, not usage, which makes it a different lever than the rest of COGS.
Capitalized Software (ASC 350-40)
An accounting standard requiring certain internal-use software development costs to be capitalized rather than expensed immediately, then amortized into COGS once the product goes live. Easy for non-finance founders to miss until an audit or acquirer's diligence process surfaces it.
COGS (Cost of Goods Sold)
The direct costs of delivering your product — hosting, third-party software embedded in the product, infrastructure, and delivery headcount. Distinct from R&D or general overhead, which sit below the gross margin line.
Unit Economics
What it costs to deliver one unit of your product or service, set against what that unit brings in — the building block for understanding whether growth makes the business more or less efficient.
Cost-Plus Pricing
Setting price by starting from unit cost and adding a target margin on top — the logic behind the calculator's "price needed" figure.
Contribution Margin
Revenue minus variable costs for a specific product, deal, or customer — useful for spotting the segment hiding underneath a healthy blended gross margin.
Fully Loaded Cost (Headcount)
An employee's total cost to the business — salary plus benefits, payroll taxes, equity, and a share of overhead — not just the number on their offer letter.
FinOps
The discipline of bringing finance, engineering, and business teams together to make informed, collaborative decisions about cloud spend — treating cost as something engineering actively manages, not something finance discovers after the fact.
Shelfware
Software that's paid for but sitting unused — licenses bought for a plan that changed, seats provisioned for people who've since left.
06 — Practice

A simple review cadence

Margin doesn't erode because nobody cares. It erodes because nobody's checking the price against the cost on a rhythm.

Monthly

Review cloud and usage-based COGS against forecast. Flag any category that moved without a known cause.

Quarterly

Recalculate cost per unit and check it against current pricing — not just against last quarter's number.

Annually

Run the full gross margin breakdown, reset target margin, and reprice ahead of the cost increases you can already see coming.

07 — FAQ

Common questions

The things people usually ask before they run the numbers.

What's a good gross margin for a SaaS company?

Most pure software businesses target 75% or higher. Anything embedding heavy AI, LLM, or infrastructure cost typically runs lower by design — see the benchmark table above for ranges by business model. These are general starting points, not a verdict on your specific business.

How do I price a feature built on Claude, GPT, or another AI model?

Start by isolating the per-request token cost for that feature specifically, then decide whether to price it as a flat add-on (simpler, but risks losing money on heavy users) or usage-based (protects margin, adds billing complexity). The Diagnostic's sensitivity table shows what happens to required price as that cost rises.

Should Customer Success headcount be in COGS or operating expense?

Generally, headcount that keeps the product running for existing customers — support, DevOps, SRE — belongs in COGS. Headcount focused on expansion, upsell, or new sales sits in operating expense. This is exactly the kind of classification question a full teardown resolves line by line.

What is capitalized software amortization, and why does it matter?

Under standards like ASC 350-40, certain development costs get capitalized rather than expensed immediately, then amortized into COGS once the product is live. It's a non-cash line that's easy to miss — and a common surprise during an audit or an acquirer's due diligence.

Is the Diagnostic's benchmark data based on real client data?

No — the ranges shown are general practitioner starting points, stated plainly rather than dressed up as proprietary research. A full teardown replaces these general ranges with numbers specific to your actual contracts, usage, and headcount.

What happens after I submit my email in the Diagnostic?

You'll get your full sensitivity report and the benchmark guide. If your numbers suggest a real margin gap, we'll follow up about whether a full teardown makes sense — there's no obligation either way.

The Approach

Built by people who've
priced a product against
rising cost, not just studied it

Margineer is a free tool from Marginwell — a fractional VP of Finance, Technology & FinOps practice. The calculator is the first look; the teardown is where the real work happens.

Why this exists

Most cost tools stop at spend

Cloud cost tools optimize cloud. Procurement tools optimize contracts. AI usage — Claude, OpenAI, and the rest — usually gets buried inside whichever of those it was easiest to bill to. Almost nothing connects the resulting COGS back to gross margin and price.

What the calculator is

A first read, not a full audit

Six COGS lines and a unit count won't catch everything — a mispriced enterprise contract, an unamortized software asset, or usage-based cost hiding inside a flat category. What it will do is tell you, honestly, whether your price still covers your cost. That's the point.

What the benchmarks are

Starting points, stated plainly

The margin ranges behind every stamp are general practitioner guidance, not a proprietary dataset claiming false precision. They're visible in the Playbook because a benchmark you can't see isn't one you can trust — or challenge.

What happens after

A teardown, line by line

A "Watch" or "At Risk" margin means cost is outrunning price somewhere specific — not where, or by how much. That's the work a full engagement does: COGS line by line, against your actual contracts and pricing.

Marginwell

Fractional VP of Finance, Technology & FinOps

A small, capped practice working directly with growth-stage SaaS and technology companies on the margin and cost questions that don't fit a generalist fractional CFO — because pricing against a rising COGS usually needs someone who's done it before.

Get The Insights

The margin research,
before anyone else sees it.

New benchmark data, pricing frameworks, and margin research as they're published — straight to your inbox. No sales calls, no screening, just the insights.

Stay in the Loop

We're building out the full Margineer research library. Drop your email to get new benchmarks, frameworks, and playbook updates as they go live.
One email. No spam. Unsubscribe anytime.

You're on the list.

We'll send new margin research and benchmark data as it's published — no sales calls attached.