Gross Margin

For a long time a single revenue number was the whole pitch. "We did $750,000 last year and we'll do $1.5 million this year" landed as a company doing twice as well. But if producing that $750,000 burned $450,000 on servers and support staff, only $300,000 was actually left. Worse, the $1.5 million year carries $900,000 of the same costs. Growing revenue doesn't make that company any more comfortable, and looking at revenue alone never shows it.

The problem showed up constantly in investor meetings. A company would introduce itself as software, and a closer look would find one engineer assigned to each customer, building something slightly different for every account. Double the customers, double the headcount, and the hiring plan grows on exactly the same curve as the revenue plan. That company and one where a thousand accounts share a single build are completely different businesses even at identical revenue — but the top line of the income statement makes them look the same.

Gross margin exists to separate those two with one number. It asks how much of the money earned is left rather than how much came in, and the answer is exactly what the company gains from signing one more customer.

Subtract cost of goods sold (COGS) from revenue and divide the remainder by revenue. On $38,000 of monthly revenue with $9,500 of COGS, the $28,500 left over divided by $38,000 gives 75 percent.

COGS is what it directly costs to produce that revenue. In a software business the line usually holds four things.

1. Servers and infrastructure. The cloud bill for running the product, which rises as customers arrive.
2. Customer support salaries. The people answering tickets and handling outages. More accounts means more of them.
3. Payment processing fees. The cut taken by card networks and processors, typically 2 to 3 percent of each charge.
4. Third-party services embedded in the product. Text messaging, maps, and anything else billed by usage.

What stays out matters just as much. Engineering salaries, marketing spend, office rent, and executive pay are not COGS, because none of them move when one more customer signs. Engineers build the same product whether there are 100 accounts or 300, and rent comes out exactly as written in the lease.

Some items sit on the line. Onboarding specialists who set up new accounts are the classic case: the work scales with new customers, so many companies book them as COGS, while others treat it as an extension of selling and leave it out. Either choice is defensible as long as it stays fixed. If the rule shifts every quarter, monthly recurring revenue (MRR) can hold perfectly steady while the margin drifts, and nobody can tell whether the movement is real or an accounting change.

Subscription software usually lands between 70 and 80 percent. One build serves a thousand accounts, so each additional customer costs little beyond some server capacity and a slice of support time. A few companies clear 85 percent, and they tend to be the ones where the product runs with almost no human touching it.

A number in the forties says more about the shape of the business than about cost discipline. It usually means people, not product, are doing the work — custom features per account, or a product complex enough that every customer needs a dedicated person. In that structure, doubling revenue leaves the same share behind, so scale isn't the fix.

The trend carries more information than the level. If 78 percent slid to 71 over four quarters, something changed in between: discounted enterprise deals that eat unusual server capacity, or a product that got complicated enough to generate more tickets. If revenue tripled while the percentage held flat, costs are not rising in proportion to customers, which is the structural claim confirmed.

This ratio also feeds other math. CAC payback, the number of months it takes to earn back what acquiring a customer cost, divides that cost by the margin the customer leaves each month rather than by what they pay. Let gross margin fall from 75 percent to 50 and payback stretches by half again, with no change in acquisition spending at all.

"Gross margin is 78 percent, so assume this account leaves us about $296 a month."

Plan against what's left after cost, not against the $380 the customer pays.

"We went from 71 to 64 percent this quarter and I want to know why before anything else."

The drop matters less than finding what changed underneath it.

"By gross margin this isn't software, it's a services business."

A person is attached to every account, so it won't be valued like a product company.

At Pagedeck, Grace checks this number first every time she puts investor materials together. Last quarter came in at 74 percent, down from 79 two quarters earlier. When she asked why, Theo explained that three large accounts had arrived and quadrupled stored data, taking the cloud bill up with it. Mia pointed out that all three were on flat pricing regardless of storage — contracts that cost the company more the more they were used.

What came out of that meeting wasn't a cost-cutting plan but a pricing change. Once storage above a threshold raises the price, the ratio holds as accounts grow.

The most common misreading is that a high gross margin means the company is making money. The word margin invites it. But this is the ratio at one specific stage, with engineering salaries, marketing, and rent all still below it. A company at 80 percent gross margin losing $150,000 a month at the operating line is an ordinary situation. Read the number as a profit signal and start hiring against it, and cash runs out long before the ratio does anything alarming.

"Cut costs and the number goes up" is half right. Tuning server configuration to lower the cloud bill genuinely raises it. But the same effect comes far more often from moving a line item: shift the support team out of COGS and into general expenses and the margin jumps five points that day. From outside the company that difference is nearly invisible, which is why comparing margins across companies means asking what each one put in COGS.