The month my gross margin scared me at $38K MRR: a founder diary (2026)

Quick answer (2026): At $38,000 MRR, growing and, on paper, healthy, I finally sat down and worked out my gross margin instead of just my revenue. It was about 62%, well under the roughly 75% or higher that is treated as a good SaaS gross margin, with 80%+ considered exceptional and anything below 70% a warning sign (Stripe, 2024; G-Squared, February 2026). The main culprit was the cost of the AI features I had been proud of. Over one month I cut the cost of delivering the product from about $14,400 to roughly $9,000 without touching the parts customers actually valued, and gross margin climbed from about 62% to 76%. MRR had hidden a margin that was quietly rotting.

This is a composite founder diary. The founder is anonymized and the dollar figures are self-reported and rounded. The gross-margin benchmarks and the AI-margin figures are sourced and year-tagged in the Sources section.

The number I had never actually looked at

For most of a year my dashboard had one number on it that mattered to me: MRR. It went up. That was the whole story I told myself, and it was a good story. $38K MRR, solo, growing month over month. By every measure I was tracking, I was winning.

Then a Stripe payout landed that felt small. Not catastrophically small, just smaller than a growing business should feel. I had noticed the same thing the month before and told myself it was quarterly annual-plan timing. This time I did not have a story ready, so I did the thing I had been avoiding. I opened a blank spreadsheet and wrote down what it actually cost me to run the product for a month.

I was not looking at gross margin because I did not really think it applied to me. Gross margin felt like a word for finance teams and board decks, not for one person with a laptop. That was the mistake. Gross margin is not an investor metric. It is the share of every dollar that survives after you have paid the direct cost of delivering your software, and for a solo founder it is the difference between a business that funds your life and one that just looks like it does.

What gross margin actually is, in a solo founder's terms

The formula is boring. Gross margin is total revenue minus your cost of revenue, divided by total revenue. The part that trips people up is what counts as cost of revenue, or COGS.

For a SaaS product, COGS is the direct cost of keeping the thing running and delivered: hosting and infrastructure, the database, direct cloud and API spend, plus the tools and people directly involved in support and delivering the service (Stripe, 2024). It is not your marketing, not your own salary as the founder-builder, and not the time you spend building brand-new features. It is what it costs to serve the customers you already have.

Here is what mine looked like, rounded, at $38K MRR:

That is about 62% gross margin. On the widely used benchmark, a good SaaS gross margin is 75% or higher, with 80%+ marking exceptional efficiency and a 50%-plus range considered acceptable only for very early-stage companies (Stripe, 2024). I was two years in and sitting at early-stage margins without realizing it.

One honest footnote, because the number is worse than it looks: I do not pay myself a delivery salary, and a chunk of the support hours are still mine. If I costed my own time properly, the true margin would be lower again. The cash version flattered me.

The line item that scared me

The row I could not stop staring at was the AI one. $5,600 a month, and climbing faster than revenue, because every new active user ran more inference. I had shipped a set of "smart" features the year before and they were genuinely popular. They were also the reason my margin looked nothing like a normal software business.

That turns out to be one of the defining margin stories of 2026. Where classic SaaS clusters around 75%, AI-native products are running dramatically leaner: the 2026 benchmark work cites data putting AI-heavy companies at roughly 25% gross margin, because model inference is a real, usage-scaling cost of goods rather than a near-zero marginal one (G-Squared, February 2026). Founders have been saying the same thing to each other all year. On r/founder in May 2026 someone doing around $50K a month wrote that "AI API credits are eating a huge chunk of our margins," and the replies were a long line of people nodding. On r/SaaS the recurring warning was blunter: most early-stage founders think their margin is 70% to 80% and it is actually closer to 50% to 60%, and they do not find out until something forces them to look.

I had let a growing top line hide the fact that my most-loved feature was also my least profitable one.

The month I did margin surgery

I gave myself one month and one rule: cut the cost of delivery without degrading anything a paying customer would feel. No gutting support, no ripping out features people relied on. Just waste.

Five levers did almost all of it.

I stopped paying full price for cheap work. A large share of my AI calls were routine, low-stakes tasks that did not need my most expensive model. I routed those to a smaller, cheaper model and kept the flagship model only for the calls where quality visibly mattered. That one change cut the AI bill by nearly half on its own.

I cached the obvious things. A surprising number of AI calls were re-computing near-identical results for near-identical inputs. Caching common responses and batching background jobs took another bite out of inference spend, and nobody noticed except my invoice.

I moved the heaviest feature behind a higher tier. The single most expensive AI feature was being used most heavily by my cheapest customers. I did not remove it. I moved its heavy-usage form into a higher-priced plan, so the people generating the cost were the people paying for it. Usage-based cost, meet usage-based price.

I right-sized the infrastructure. The database was the next lever. I had already learned once before that moving a workload off an expensive managed service can cut a bill in half, so I moved one heavy background workload off the pricey path and committed to annual, reserved pricing on what was left. Hosting dropped without a single user seeing a change.

I raised prices, a little. The last lever was the one I had been avoiding. I had raised prices on existing customers once before and survived it, so I nudged new-plan pricing up modestly to reflect what the product now did. Not a shock, just an honest catch-up.

By the end of the month the cost to deliver had fallen from about $14,400 to roughly $9,000, and gross margin had gone from about 62% to 76%. Same product, same customers, same MRR. The business just kept far more of every dollar.

The honest part: margin has a floor

Here is the trap on the other side, and I nearly fell into it. Once you can move margin, cutting cost feels like a cheat code, and you start eyeing the support tooling and the "expensive" feature that only 8% of customers use.

That is where margin surgery turns into self-harm. Gross margin is a measure of how efficiently you deliver, not a target to maximize at any price. The costs that quietly keep customers, responsive support, the reliability that a real database buys you, the feature a small but loyal segment stays for, are not waste. Cut them and the margin looks better for exactly one quarter, until retention gives the number back with interest.

So I set a floor. I would chase obvious waste, mismatched pricing, and lazy architecture as hard as I could. I would not touch anything that a paying customer would feel. The goal was never the highest possible margin. It was a healthy margin I could defend without making the product worse.

What I track now

The lasting change was not the spreadsheet. It was adding one number next to MRR and never letting them travel alone again.

Now, once a month, I spend fifteen minutes putting revenue and gross margin side by side. If MRR is up and margin is flat or rising, that is real growth. If MRR is up and margin is sliding, that is not growth, it is a business getting more expensive to run faster than it is getting bigger, and I want to know that on the day it starts, not the quarter it hurts.

MRR tells you the top line is working. Gross margin tells you whether the business underneath it is.

If you take one thing from this: track gross margin next to MRR from the first paying customer. A rising top line can hide a margin that is quietly falling, and by the time the bank balance tells you, you have priced and built a whole year on the wrong number.

Keep reading

• The month I migrated off Firebase at $26K MRR
• Raising prices on existing customers: my $18K MRR diary