You've shipped the app. The onboarding works, the crashes are mostly gone, and a few early users are saying nice things. Then the awkward question lands on the table.
How does this thing make money?
That's where a lot of NZ and AU founders stall. Building is concrete. Monetization feels murkier. You can tweak screens, fix bugs, ship features. Revenue strategy is messier because it sits at the intersection of product, pricing, user psychology, privacy, and plain old market size. A tactic that looks brilliant in a US growth thread can fall flat here because the audience is smaller and the room for waste is tiny.
I've seen founders spend months polishing an app, then treat pricing like an afterthought. They'll say, “We'll add subscriptions later,” or “Maybe ads can cover it.” Sometimes they can. Often they can't. The model needs to fit the product and the market from the start.
A familiar story goes like this. A founder in Auckland or Brisbane builds a tidy little app that solves a real problem. Maybe it helps tradies quote jobs faster. Maybe it helps parents manage school logistics. Maybe it's a niche fitness tool with a sharp user experience. The first milestone feels huge because it is huge. The app is live.
Then revenue becomes the problem.
The first instinct is usually to copy whatever the category leader is doing. Subscription? Sure. Ads? Maybe. One-off payment? Sounds simple. But copy-paste thinking is dangerous when your home market is smaller and your users are often more price-conscious than the product blogs like to admit. You need a model that matches how often people use the app, what pain it removes, and how much friction they'll tolerate before bailing.
If you're still early, it helps to revisit the product decisions that got you here. A lot of monetization problems start as product-shaping problems. The teams that think about this while planning features usually end up in a better spot than the teams that leave it until launch. If you need a reset on the product side, this practical guide on building a mobile app from scratch is worth a skim.
Practical rule: If users can't explain your app's value in one sentence, they probably won't pay for it in any model.
The good news is that app monetization strategies aren't magic. They're choices. Hard choices sometimes, yes, but still choices. And once you strip away the hype, most apps earn money through a small handful of models.
Think of your app like a neighbourhood coffee shop.
A subscription is the monthly coffee club. People pay on a recurring basis because they want steady access and they know what they're getting. An in-app purchase is the extra pastry, fancy beans, or branded mug. It's optional, specific, and tied to a moment of intent. Advertising is the noticeboard near the till. Someone else pays for access to your audience.
Those are the big three. Nearly everything else is a variation on them.
Subscriptions work when the app keeps solving the same problem over time. Finance tools, productivity apps, coaching apps, media products, B2B software. If the user comes back regularly and the value compounds, recurring pricing can make sense.
The upside is obvious. Predictable revenue is easier to plan around than one-off spikes. The downside is just as obvious. If the value feels thin after the first week, churn will tell you very quickly.
This model also forces discipline. You can't hide behind a flashy launch. You have to keep earning the renewal.
In-app purchases suit products where users want upgrades, extras, or convenience without committing to a monthly bill. Games use this naturally, but so do editing tools, creator apps, education products, and specialist utilities.
The trick is not to make the app feel stingy. If the purchase feels like a toll booth blocking basic use, people get grumpy fast. If it feels like a fair trade for extra value, they'll accept it.
A one-off upgrade can also work well in this part of the world because some users hate another recurring charge, even when they like the app.
Advertising still matters because free entry matters. As of March 2024, in-app advertising was used by 31% of apps globally, while 3% used upfront payment and 5% relied on in-app billing, according to this overview of app monetization strategy patterns. For NZ founders, that's a useful reality check. Free-to-download, then monetise later, is the common baseline because it reduces friction in a smaller market.
That doesn't mean ads are easy money. They work best when the app has enough engagement and the ad experience doesn't wreck the product.
If you want another practical perspective on ways to boost your app's revenue, that resource is worth reading alongside your product plans.
| Model | Best For | Pros | Cons |
|---|---|---|---|
| Subscription | Apps with recurring value, content, SaaS, productivity | Predictable revenue, strong fit for loyal users | Harder sell if value isn't continuous, churn can bite |
| In-app purchases | Games, creator tools, utility add-ons, feature unlocks | Flexible, lower commitment, works for specific needs | Revenue can be uneven, poor gating annoys users |
| Advertising | Broad audience apps, free tools, casual products | Low install friction, monetises non-paying users | Needs care with UX, privacy limits can reduce reliability |
A quick note on upfront paid downloads. They still exist, but they're rarely my first choice for NZ or AU consumer apps. Asking for money before users see value is a tough ask when alternatives are one tap away.
Most apps don't have one type of user. They have several.
One group will happily pay for convenience. Another will never subscribe but might buy a one-off feature. A third group won't spend at all, yet they still create value if you can monetise their attention without making the app miserable. That's why hybrid models have gone from clever to normal.
According to this breakdown of hybrid app monetization trends, 82% of non-gaming apps use subscriptions alongside other approaches, and 72% of mobile game developers use hybrid strategies. The same source notes that global app usage reached 5.1 trillion hours in 2024, a 6% year-on-year increase. That tells you there's enough engagement in the market to support layered models, if the product is designed properly.
A few common combinations show up again and again:
What doesn't work is bolting every revenue idea onto the same app and hoping something sticks. That usually creates a weird, grabby product. Too many prompts. Too many choices. Too much noise.
Hybrid monetization is really segmentation disguised as pricing. You're matching the revenue model to different kinds of intent.
Some users pay with money. Some pay with attention. Some pay only when the problem gets urgent enough.
That's not cynical. It's product reality.
The strongest hybrid setups feel simple to the user even when they're economically layered behind the scenes. A free user sees a clean, useful experience. A power user sees a clear upgrade path. A reluctant payer still has a tolerable route through the product. Everyone understands the rules.
If you're unsure where to start, pick one primary model and one supporting model. Any more than that, early on, and you'll spend more time explaining your pricing than improving your app.
Here, generic advice often loses its stability.
A lot of app monetization strategies assume you can throw a wide net into a massive home market and improve the numbers later. That logic breaks quickly in New Zealand. With New Zealand's population estimated at around 5.3 million in a recent projection, founders can't assume US-style scale, and revenue efficiency often matters more than pure user growth, as discussed in this piece on monetization in smaller app markets.
That one fact changes the whole equation.
An ad-supported app can work here, but it needs healthy engagement and a product that people return to often. If usage is occasional, broad-reach ad logic gets shaky. You may get installs and still struggle to build meaningful revenue because the domestic pool is limited.
For small-market apps, ads are usually best treated as a support stream, not the whole business.
A narrow app with a clear commercial use case often outperforms a broad app with vague value. That feels backwards at first. More people should mean more opportunity, right? In the US, maybe. In NZ and even in parts of Australia, a niche audience that really cares is often worth more than a casual mass audience that doesn't.
That's why local B2B apps, specialist field tools, education products, and vertical SaaS can punch above their weight. They solve expensive problems. Expensive problems tolerate stronger pricing.
If you're building for smaller operators, there's a wider commercial lesson in how small businesses in New Zealand adopt software. They tend to value practicality over novelty, and that changes what they'll pay for.
Ask these questions before choosing a model:
How often will users come back
Regular use supports subscriptions better than occasional use.
Is the problem expensive or just annoying
Expensive problems can support higher-value pricing. Mild annoyances often can't.
Can Australia widen the market quickly
Some apps should treat NZ as the proving ground and Australia as the primary revenue engine.
Will local trust matter
Finance, health, and business workflows often need stronger trust signals than entertainment apps.
Founder shorthand: In a small market, the wrong monetization model doesn't just slow growth. It can kill the economics before you learn anything useful.
The best local strategy is often staged. Start with a model that is efficient in NZ, then localise pricing and expand once the retention and revenue basics are proven.
Pricing makes founders twitchy because it feels permanent. It isn't. It's a live system. You set a price, watch behaviour, adjust, and learn. Then you do it again.
That said, random guessing is not strategy. If you change numbers every other week without a framework, you'll create noise instead of insight.
Competitor pricing is useful context. It is not a map. Your product might save more time, solve a narrower problem, or serve a different customer segment entirely. Copying the biggest player often leads founders to undercharge or overpromise.
A better starting point is this: what outcome is the user buying, and how often do they need that outcome?
If the answer is ongoing and business-critical, recurring pricing is easier to justify. If it's occasional or task-based, a one-off purchase may fit better.
A pricing problem is often a messaging problem in a fake moustache.
The number matters, yes, but the paywall also does heavy lifting. Which plan appears first? What is included? Is the annual plan framed as the default? Are you showing the upgrade before the user has experienced the core value? Small changes in sequence and framing can alter conversion behaviour a lot, even without changing the underlying offer.
Useful tests include:
Tier structure
Try fewer plans before adding more. Too much choice can freeze people.
Positioning
Frame the premium plan around outcomes, not feature laundry lists.
Timing
Ask for money after a meaningful “aha” moment, not before.
Plan mix
Monthly and annual can serve different user mindsets. Let behaviour guide what gets prominence.
For subscription models, the scoreboard is straightforward. Founders need to track MRR, CAC, LTV, and churn rate to know whether recurring revenue can outpace acquisition cost and user drop-off, as outlined in this guide to subscription app monetization metrics.
If I had to be blunt, these metrics matter more than your app store compliments.
If CAC rises and churn stays ugly, a “good” conversion rate can still hide a bad business.
NZ and AU users can be pragmatic buyers. They'll pay when the value is obvious. They'll also cancel without ceremony if the app becomes a nice-to-have instead of a need-to-have.
That creates a funny tension. You may need to charge more than feels comfortable because the market is smaller, but you also need to present the value with painful clarity. No fluff. No vague premium tier names. Say what changes for the user when they pay.
And lifetime deals? Sometimes useful for early cash flow, sometimes a trap. They can feel brilliant in the moment and, despite their initial appeal, kneecap future recurring revenue. Tread carefully.
The local market gives you some clean examples if you look past the buzzwords.
Xero is the classic subscription story. It works because accounting is not a one-off event. The value repeats. Businesses reconcile, invoice, report, and collaborate over time. That kind of workflow naturally fits recurring pricing.
The lesson isn't “copy Xero's model.” It's simpler than that. If your product becomes part of a customer's operating rhythm, subscription pricing feels normal.
Sharesies is interesting because it sits closer to a hybrid logic. The product can monetise committed users through recurring access while also matching parts of revenue to activity. That matters in finance. Users don't all behave the same way, and a model that mirrors usage often feels fairer than one blunt price for everyone.
You see this in plenty of modern products, not just fintech. Some users want ongoing access. Others want occasional transactions. Good monetization respects both.
On the consumer side, especially for games and broad lifestyle products, the cleanest setups often combine optional purchases with a free path that doesn't feel punitive. Rewarded upgrades, cosmetic extras, convenience boosts. The details vary, but the pattern is familiar.
The trick is restraint. Local users are quick to sniff out a greedy app.
If you're working through your own structure, this guide to effective product pricing strategies is useful because it pushes you back toward customer value instead of gut feel.
A good monetization model should feel like part of the product, not a tax bolted on at the last minute.
That's what the better local apps get right. Their pricing logic fits the shape of the product. It doesn't fight it.
This is the part founders love to postpone right up until it bites them.
Monetization isn't just product and pricing. It's also tax, consent, payment flow, refunds, and data handling. Get sloppy here and you can create real operational pain, even if the app itself is solid.
For NZ founders, this matters a lot. New Zealand's Privacy Act 2020 and the Office of the Privacy Commissioner's guidance on consent-based tracking place clear limits on personal information use, which makes typical ad-led monetization less reliable and pushes teams toward first-party data and contextual advertising, as noted in this article on privacy-aware monetization and user acquisition.
That means lazy assumptions from overseas playbooks can get you into trouble. If your revenue plan depends on broad user tracking, you need to sanity-check it early.
Most founders end up looking at Stripe, app store billing, or a web checkout stack, depending on the product. The exact setup varies, but the principle doesn't. Make billing understandable. Make cancellation clear. Make refunds and support easy to find.
Your terms matter too. Not because anyone enjoys reading them, but because trust compounds when money is involved. If you need a starting point for drafting commercial terms or service language, a tool like the LegesGPT contract generator can help you get the first draft moving before legal review.
If your app touches fintech, lending, payments, or data-sharing workflows, the bar rises quickly. Open banking is a good example of a category where monetization, trust, and compliance all tangle together. This overview of open banking in New Zealand shows why local payment and data rules can't be treated as a side issue.
A few practical checks help:
Consent flow
Make it obvious what data you collect and why.
Billing language
Say when users are charged, what renews, and how they cancel.
Tax handling
Confirm how GST and cross-border sales apply to your setup with proper advice.
Support path
Give users a real route for billing questions. Hidden support links are a false economy.
This stuff isn't glamorous. But it's part of the product. Users don't separate trust from monetization. Neither should you.
There isn't a single magic number because app category, pricing, and customer type all change the picture. What matters is trend and diagnosis. If churn is stubbornly high, don't just blame price. Check onboarding, feature adoption, support friction, and whether users hit value fast enough.
You can. I wouldn't. Their costs, target segment, and product depth may be totally different from yours. Use competitor pricing as context, then make your own call based on actual user behaviour and your unit economics.
Yes. If your monetization depends on store-based subscriptions or in-app purchases, platform fees affect your margin and pricing flexibility. Build that into the model early so you don't end up with a product that looks healthy at the top line and thin underneath.
If you're building or scaling an app business across New Zealand or Australia, NZ Apps is worth keeping on your radar. It covers the local app and tech scene with a founder lens, and it's a handy place to get regional context, discover companies, and stay close to what's happening in the NZ and AU market.
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