You’re Losing Money. Your Instinct Says Cut. Your Instinct Is Frequently, Precisely Wrong.

●1 ●6 ●34
calendar_today ago • schedule1 min read

Part 4 of 4 on IBR's Mini Strategy Handbook for AI Founders. The last review is a five-minute finance lens that would have saved a lot of businesses I've watched shrink themselves to death.

Here’s the situation the handbook closes on, and if you’ve run anything, you’ve lived it. Revenue has plateaued. Every month closes red. You do the responsible thing: cut marketing, freeze hiring, trim every discretionary line. And the loss… doesn’t move. Or deepens. So you cut again, more responsibly, and it deepens again, and at some point somebody says the word “shut” in a meeting.

Vivek Bisht’s The Contribution Factor argues that a lot of these businesses aren’t broken. They’re sub-scale, and every “responsible” cut makes them smaller and therefore worse. The tool that tells the two apart is one subtraction.

The formula, and where your next order actually goes
Contribution Factor = Price − Variable Cost per Order. It’s what’s left from each sale after paying the costs of making that sale, and it “contributes” toward the fixed costs, rent, salaries, software, until those are covered, after which every further order is profit.

That’s genuinely the whole thing. But the diagnostic power comes from what the sign and scale of the number tell you to do, and it’s here that most founders’ instincts fail.

Negative: every sale loses money, scaling makes it worse, fix unit economics before anything else. Positive but low volume: the model works, you’re just too small to cover the cost base, so spend more, not less, and grow into it. Positive and covering fixed costs: you’ve crossed break-even; defend margins, reinvest selectively. The middle row is where a startling number of “failing” businesses actually live, and it’s exactly the row where cutting kills you.

The death spiral, and its reversal
The handbook’s case is Treya Gifts, an Indian DTC brand selling STEM toys for kids. Loyal customers, strong reviews, eighteen months of plateau and monthly losses, and the founders were doing the textbook thing: slashing marketing, freezing spend, trimming everything variable. Each round of cuts was followed by a proportionate drop in orders, and the losses persisted, because the same fixed costs were now spread across fewer orders. Every cut was defensible. The loop was fatal.

IBR rebuilt the P&L per order and the contribution factor came back clearly positive, about 33% of revenue. Treya wasn’t selling at a loss. It was sub-scale. So the recommendation was the opposite of every instinct in the room: increase marketing until volume comfortably cleared the fixed-cost barrier, with guardrails, cap cost-per-order below the contribution margin so every incremental order stayed profitable, shift toward channels with clean per-order attribution so you can watch the number live, and freeze fixed costs, no hires, no warehouse, until volume stabilized. Twelve weeks later: orders up 180%, contribution factor steady at 33%, fixed costs up 8%, and the business moved from monthly loss to monthly profit. Not by cutting. By spending more on the one line that was working.

Where I’d argue with a word: “responsible”
My quibble this time isn’t with the framework, it’s with the vocabulary founders use around it. Cutting costs when you see red ink is described, universally, as “responsible,” and spending more as “reckless.” The contribution lens shows the labels are backwards for a specific, common case. When each order is profitable and you don’t have enough of them, cutting the thing that produces orders is the reckless move dressed as prudence. It feels responsible because it’s painful and it’s what your board expects. Pain is not a signal of correctness. Ask Part 3.

The handbook flags the misclassification that causes most of this, and it’s the single most useful sentence in the review: performance marketing is a variable cost, not fixed overhead. File it under overhead and you will cut it at exactly the moment you should be doubling it.

The AI-startup edition, which the handbook leaves for us
The Treya case is e-commerce; the handbook is for AI founders. So let me draw the translation, because AI businesses have a variable-cost line that didn’t exist five years ago and that founders routinely misfile.

Inference tokens per job are variable. So are third-party API calls, human-review minutes, and payment fees. Salaries, cloud baseline, SaaS seats and the model you fine-tuned once are fixed. Which means an AI product can have a negative contribution factor while looking healthy on gross margin slides, if each job burns more tokens than the price covers, and it can be positive-but-sub-scale while looking doomed, if you’ve been treating the ads that bring jobs as overhead. Run the per-job P&L. Put the token bill in the variable column where it belongs. Then read the number and decide, from the table above, not from your stomach.

One more AI-specific wrinkle: token prices fall. A negative contribution factor today may be positive in two quarters with no change on your side, which is the only case I know where “wait” is a legitimate unit-economics strategy. Note it, date it, and don’t confuse it with the sub-scale case, which waiting only worsens.

Closing the series
Four reviews, one arc. Launch wide and win by what you cut. Distribute through a specific person with a specific scar, because polish is free now. Read every signal by what it cost the customer to send. And when the numbers still come back red, decide (this one) with one subtraction whether you’re broken or merely small, because the fixes are opposites and the instinct usually picks the wrong one.

What I like about the handbook, beyond the frameworks, is the through-line I keep meeting everywhere this year: the cheap things, building, polish, attention got cheaper (for more on this, read this small book) and the expensive things, judgment about what to cut, a checkable point of view, a customer’s costly commitment, the discipline to read a number instead of a feeling, got scarcer. IBR’s own tagline says it better than I can: judgment is scarce, execution is abundant.

Which is a strategy handbook’s way of saying what my last four articles said about AI. Nice to know the founders and the models are learning the same lesson.

-Hardik

I’ve spent about two decades building data and AI systems, and enough time around P&Ls to have watched good businesses cut themselves into the ground while calling it discipline. This closes my four-part walk through IBR’s handbook. If it was useful, the original is free at ikanabusinessreview.com and worth your subscription; and if you missed Parts 1–3, they’re the launch, the distribution, and the signal you’ll need before this one applies. Subscribe here too, obviously; my contribution factor per reader is positive and I’m merely sub-scale.

Series map: Part 1 · The Inverted Launch → Part 2 · The Founder Is the Channel → Part 3 · The Signal Cost Principle → Part 4 · The Contribution Factor (this).

Source: Ikana Business Review, Mini Strategy Handbook for AI Founders (August 2026), Review 04, “The Contribution Factor” by Vivek Bisht, including the formula, the decision table, and the Treya Gifts case (+180% orders, 33% contribution factor held, +8% fixed costs, loss to profit in twelve weeks); full case at ikanabusinessreview.com. The “responsible” argument, the AI-startup variable-cost translation, and the falling-token-price wrinkle are mine.

🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.

More Posts

A Textile Mill's Dyehouse Ramp Curve: Get One Step Wrong and the Sheet Belongs to the Master

aiomniu - Oct 18

Ecommerce SEO Audit Checklist

floxolab - Sep 1

Your Tech Stack Isn’t Your Ceiling. Your Story Is

Karol Modelski - Apr 9

Your AI Doesn't Just Write Tests. It Runs Them Too.

Kevin Martinez - May 12

Everyone says DeepSeek is cheaper, but I got tired of guessing the exact math. So I built a calculat

abarth23 - Apr 27
chevron_left
544 Points • 41 Badges
16Posts
7Comments
11Connections
Waltzing with compilers for 2 decades, now teaching LLMs the same dance.
I ship AI systems that wor... Show more

Related Jobs

View all jobs →

Commenters (This Week)

6 comments
1 comment
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!