How much does it cost to build an app in 2026?

It is the first question almost everyone asks, and the honest first answer is “it depends.” That sounds like a dodge, but it is the most useful thing we can tell you, because the biggest decisions about cost are yours to make, not ours.

The price of an app is set by two things: what you decide you cannot launch without, and what you are happy to leave for later. Get those right and a good app is far more affordable than the eye-watering figures the internet likes to quote. This post walks through the choices that actually move the number.

So what does an app cost in New Zealand?

There is no single price, but here is some rough market context for custom-built apps in New Zealand, in NZD. Treat these as broad bands to set expectations, not a rate card.

• A lean, focused first version: often somewhere around NZ$15,000 to $40,000. One clear job done well, built as a web app, with the must-have features and nothing you do not yet need.

• A more involved app: roughly NZ$40,000 to $100,000. Several connected features, user accounts with different permissions, payments, and an admin side for your team.

• A large, multi-feature platform, or full native apps built per device: NZ$100,000 and up, driven by how many features and kinds of user it has to serve from day one.

Two things pull most projects toward the bottom of that picture rather than the top: building the smallest version that proves the idea first, and the fact that building with AI is genuinely faster than it used to be. More on both below.

It depends on your must-haves

Almost every app idea is really a wish list, and almost none of it is needed to launch. The single most powerful thing you can do for your budget is to sort that list into what you must have on day one and what you can live without for now. Every item you can defer is money you do not spend yet, and often never need to.

The questions worth asking yourself, in plain terms:

• Do you need to take payments? A secure way to charge customers, handle subscriptions or process orders is genuinely valuable and genuinely more work to build safely. Worth it when money flows through the app on day one, easy to add later when it does not.

• Do you need AI features? Things like smart search, automatic summaries, a chat assistant or content generation are very doable and increasingly expected. They are also a real feature to design and build, so they belong on the must-have list only if they are part of why people would use the app.

• How custom does the design need to be? A clean, well-built app using a sensible design system is quick and looks professional. Bespoke, hand-crafted screens for everything cost more, and are worth paying for only where customers actually feel them.

• Do you need marketing built in? Getting found matters as much as the app itself. Search visibility, a landing page, email capture and analytics can be part of the plan or a later phase, but budget for them somewhere, because an app nobody can find is the most expensive kind.

• How many kinds of user? One where everyone sees the same thing is simpler than one with customers, staff and admins who each see and do different things. Every role is its own set of screens and rules.

None of these are reasons to spend more. They are the dials. A good partner helps you turn up the few your customers will feel and turn down the ones they never will.

Web app or native app? The choice that moves the price most

This one decision changes the cost more than almost anything else, so it is worth understanding even though it sounds technical.

A web app is a single build that runs on phones, tablets and desktops through the browser. Because there is only one thing to make and one thing to maintain, it is cheaper to build, cheaper to run, and faster to change. The trade is that it can feel very slightly less smooth than an app built specifically for your phone.

A native app is built separately for iPhone and for Android. It gets you the slickest, most polished feel, and it sits in the app stores. But you are closer to building and maintaining two apps rather than one, which roughly doubles both the build and the ongoing upkeep.

For most first versions, a web app is the sensible choice: you reach everyone, you spend far less, and you keep it easy to change while you are still learning what people want. Native becomes worth it once you know the app is a hit and you need that last bit of polish, or a specific phone feature only native can reach. It is a choice about what you will sacrifice for a lower price, and for most people at the start, a little smoothness is a very fair trade.

How AI changed the maths

Building an app is genuinely faster than it was even a couple of years ago. We lean on modern AI-assisted development to move quickly through the routine, repetitive parts of a build, which means the same app takes less time, and less time means less cost.

What that does not do is replace the judgement that actually makes an app good: how it should work, what to leave out, whether it is any nice to use. Faster is only worth anything if the result is solid, so we put the time AI saves back into the decisions that need a human. The result is more app for your budget, not a cheaper-feeling one.

What about the cost after you launch?

The build is a one-off. Running the app is ongoing, usually much smaller, and worth planning for. Running costs cover hosting, any third-party services, and the steady trickle of fixes and small improvements every live product needs.

How the app is built quietly changes this too. We design services to scale to zero, which means the hosting behind your app costs almost nothing while nobody is using it and only grows as real usage does. Instead of a flat monthly bill sized for a busy day you might not have yet, your running cost tracks what is actually happening. Early on, when traffic is low and hard to predict, that matters a lot. Choosing a web app helps here as well, because there is one thing to keep running rather than two.

So what should you budget?

If you are starting out, the best plan is not to fixate on a single number but to get ruthless about your must-haves first. Pick the one job people will come for, build that as a web app, add only the features that job truly needs, and put it in front of real users. That focused first version is usually the low end of the picture above, not the middle, and it teaches you more than any amount of planning could. From there you invest in what is working, with evidence behind every dollar.

Most of the cost of an app is decided in the scoping, not the coding, and an hour spent working out what to leave out is the cheapest hour in the whole project. If you have an idea and want a real number for it, get in touch and we will talk it through honestly, including which of your must-haves really are, and the version we would build first.