You can stare at a healthy revenue graph and still feel uneasy. The invoices are going out, Stripe is humming, customers are signing up, and yet the bank balance tells a messier story. That's usually the moment founders ask the crucial question, not “Are people buying?” but “When does this business stop bleeding cash?”
Break even analysis is the clean answer to that question. It's the point where total revenue matches total cost, so you're no longer losing money on each period. For a first-time SaaS founder, that matters more than a shiny top-line number because subscriptions, churn, payroll, and cloud bills all tug in different directions.
A lot of founders don't need more motivation. They need a clearer map. One month the dashboard looks fine, the next month payroll lands, and suddenly the whole thing feels like a balancing act on a windy wharf.
That's where break even analysis earns its keep. It tells you the point where the business can stand on its own feet for that period, without hand-waving or hope. If you're borrowing, it gets even more real, because debt service is part of the picture too.
In New Zealand, the standard Small Business Cashflow (SBC) loan makes this practical to think about. The published structure allows a maximum loan of NZ$10,000 plus NZ$1,800 per full-time equivalent employee for an eligible business, with 3% per year interest and a five-year term. Inland Revenue also shows the scheme is designed for businesses with up to 50 employees, so the repayment load can vary a lot depending on headcount and lending capacity, which is exactly why founders should model break-even before taking the money. The local repayment setup makes the idea feel less abstract and more like a live planning tool, not classroom theory. Business Loan Warrior explains break-even is a useful plain-English companion if you want another founder-friendly take, and NZ founders can also keep a local context in mind through NZ Apps' small business overview.
Practical rule: if you can't show how the loan changes your monthly break-even point, you probably haven't modelled the loan properly.
The big win here is simple. Break even analysis strips the fog off growth and asks one blunt question, “How much revenue do we need to cover the machine we've built?” Once you know that, pricing talks get sharper, hiring gets more honest, and runway planning gets a lot less wishful.
At heart, break even analysis only cares about three things. The first is fixed costs, which stay put whether you sell one subscription or a hundred. The second is variable costs, which rise as activity rises. The third is selling price, which is what each customer pays, whether that's monthly, annually, or by usage tier.
Think of fixed costs as the rent on the building and variable costs as the power bill that swells when the lights stay on longer. For a SaaS business, fixed costs can include founder salaries, rent, software subscriptions, and baseline admin. Variable costs are more likely to show up as payment fees, hosting tied to usage, or customer support that expands as the base grows.
The Ministry of Business, Innovation and Employment treats business costs as a mix of fixed and variable components, which is exactly the lens break-even uses. The common formula is Break-even quantity = Fixed costs / (Selling price per unit – Variable cost per unit), and that's the one founders keep coming back to when they're testing pricing or setting sales targets. A business breaks even only when revenue equals total cost, not when the graph “looks pretty” or the pipeline feels full.
Strip the maths back and it's almost too simple. Every sale has to carry part of the fixed-cost load, and the amount left after variable costs is the contribution margin. That leftover piece is what pays the bills you can't dodge.
If your contribution margin is thin, growth can feel busy without actually getting you closer to profit.
That's why the formula matters in practice. It helps you see whether the business model is built on enough margin, or whether you're just collecting customers while the cost base sneaks up behind you. For NZ founders, using local cost structures matters, because rent, payroll, and distribution can move the break-even point fast in a small market.
Most break-even explainers still talk like every business sells boxes off a shelf. That's fine for a warehouse, but it gets clumsy fast for app and software founders. You're not counting widgets. You're watching sign-ups, active subscribers, churn, and monthly recurring revenue.
The old “units sold” language can mislead a SaaS team because one customer isn't always one clean unit. A customer on a monthly plan is different from one on an annual plan. A light user creates a different cost pattern from a heavy user. And churn means the customer count at month-end is only part of the story.
This matters in New Zealand because a lot of local tech businesses live in recurring revenue, not one-off sales. Stats NZ reported that in 2024, ICT industry GDP was NZ$9.9 billion, and software publishing sat among the largest ICT industries, which tells you something useful about the shape of the market. Many NZ founders are building subscription businesses, platform businesses, or service-plus-software hybrids, not old-school product lines. Guides that stay stuck on unit sales don't help much when the core question is how much monthly recurring revenue covers the cost base.
For that reason, recurring revenue thinking is the better fit. A founder can ask, “How many active subscribers do I need?” or “What MRR level covers payroll, support, and cloud spend?” That's a far more useful lens than pretending a SaaS product behaves like a carton of milk.
If you want a broader glossary-style view of recurring revenue as a business model, Fundl's recurring revenue guide is a handy read, especially if you're comparing plans, churn, and retention language with your own dashboard. The point is simple. For SaaS, break even analysis still works, but the unit of measure needs to fit the model.
Once you stop asking only “How many sales?” and start asking “How much recurring revenue?” the model becomes far more useful. You can map the cost of churn, the drag of support, and the benefit of pricing changes without forcing everything into a fake unit count. That's the cleanest way to make the maths feel like business, not bookkeeping theatre.
Let's make this concrete with a fictional app business called KiwiCal, an Auckland-based appointment scheduling SaaS. It sells subscriptions, not one-off licences, so the main question is how many paying customers it needs each month to cover the cost base.
Here's the setup.
| Item | Cost/Value | Notes |
|---|---|---|
| Monthly fixed costs | NZ$12,000 | Founders' pay, office, and core software stack |
| Price per subscriber | NZ$30 | Monthly subscription fee |
| Variable cost per subscriber | NZ$3 | Payment fees and usage-linked costs |
| Contribution margin per subscriber | NZ$27 | Price minus variable cost |
The formula from the earlier section does the heavy lifting. Break-even quantity = Fixed costs / (Selling price per unit - Variable cost per unit), so KiwiCal needs NZ$12,000 / NZ$27 subscribers, or the nearest whole number above that, to cover its monthly cost base. That's the practical answer founders care about, because it turns a fuzzy growth target into a clear subscription target.
For mixed pricing or service-heavy businesses, dollar sales can be easier to work with than unit counts. The break-even point can be expressed in sales dollars by dividing fixed costs by the contribution margin ratio, which is useful when different tiers or add-ons make “one unit” a slippery idea. That approach suits a lot of AU and NZ businesses with layered offers or blended service lines. American Express Business breaks down revenue-based break-even in a way that matches how many founders sell.
For KiwiCal, that means you can look at both angles. Subscriber count tells you the operating target. Revenue tells you the monthly cash target. Those are not the same thing, and that's where founders often get tripped up.
A good habit is to run both views in the same spreadsheet, then keep them next to your sales forecast. NZ Apps' startup validation guide is a useful companion if you're still deciding whether the customer problem is strong enough to support the model.
The numbers aren't the point. The discipline is. Once you can see the break-even line clearly, you can test pricing, staffing, and product scope without guessing. That saves a lot of expensive optimism.
The best founders don't treat break even analysis like a one-off spreadsheet exercise. They use it as a decision filter. That's where the model starts paying rent.
A small change in costs or pricing can move the target quite a bit. Raise a founder salary, and fixed costs jump. Cut your price, and the contribution margin shrinks. Add a cheaper plan, and the mix may improve or worsen depending on how customers behave.
That's why a simple spreadsheet is enough to begin with. Google Sheets works fine. Causal is useful if you want a cleaner planning model and scenario handling. You don't need fancy software to ask good questions, just a model that updates quickly when inputs change. NZ Apps' productivity guide is a sensible next stop if you're trying to connect financial modelling with day-to-day output.
A break-even model gets sharper when you run “what if” cases. What if support headcount goes up? What if a higher-priced plan improves margin? What if you move to a smaller office and trim fixed costs? Those are practical choices, not academic exercises.
Useful habit: recalculate break-even whenever pricing, staffing, or product mix changes, because stale numbers breed false confidence.
The value here is strategic clarity. You can see which lever moves the business. Sometimes it's price. Sometimes it's cost control. Sometimes it's feature scope, because every extra feature can drag in support and delivery effort that changes the whole picture.
A founder who checks break-even regularly makes better calls on hiring and sales targets. That doesn't guarantee success. It just means the next decision is built on something sturdier than a hunch.
The maths is simple. The mistakes are not. Founders usually trip over the same few issues, and each one makes the result less useful.
First, they forget costs. Founder salaries vanish from the model because, well, founders are used to skipping their own pay. Annual software renewals get left out or added in full rather than spread across the year. Taxes get ignored until the numbers feel magically too good.
Second, they misclassify costs. A salesperson's commission is not a fixed cost. It moves with sales. The same goes for transaction fees and some support costs in a software business. If those are parked in the wrong bucket, the break-even number gets distorted and the model starts lying politely.
Third, they treat the analysis like a one-and-done task. That's a trap. Pricing changes. Headcount changes. Cloud bills change. Your break-even point should move with the business, not sit frozen in a file called something like “final_final_v3”.
The simplest fix is to keep the model light, clear, and alive. Review it when the business changes, not six months later when the old assumptions have already gone stale. A decent spreadsheet, a clean profit-and-loss export from Xero, and a willingness to face awkward numbers are usually enough.
Break even analysis works best when it's honest. Not optimistic. Not theatrical. Just honest.
If you're building a SaaS or app business in New Zealand or Australia, NZ Apps can help you stay close to the local market while you make smarter financial calls. Visit NZ Apps for regional coverage, founder-focused guides, and practical context that helps you test pricing, margins, and growth plans with a sharper eye.
Add your NZ or Australian app or tech company to the NZ Apps directory and get discovered by founders and operators across the region.
Get ListedReach tech decision-makers across New Zealand and Australia. Sponsored and dofollow editorial links, permanent featured listings, and sponsored articles on a DA30+ .co.nz domain.
See Options