No app has a list price, but you can reason about the number. In New Zealand, a focused first release commonly starts in the low tens of thousands, and a platform with several integrations runs higher and ships in stages. At Putti we've priced mobile app development in New Zealand since 2010, and four things move the number every time.
What does a first release cost?
A focused first release commonly starts in the low tens of thousands. That buys design, the build, App Store and Google Play submission, and a few weeks of fixes after launch. It doesn't buy every feature on the whiteboard, and it shouldn't. Gull's fuel pricing app is the shape of it: head office needed competitor prices collected in real time so they could update their own every day, so that's what got built.
A full platform is a different job. Several user types, an admin back end, payments and two or three integrations put you well above the first bracket, and we deliver it in stages so you see working software early rather than waiting on one big launch. Wendy's ordering apps had in-app payment and POS integration from the start. That's exactly the kind of scope that moves a build from the first bracket to the second.
What drives the cost of an app?
Four things, in roughly this order.
- Scope. How much the app does. Every screen, every role and every edge case is work, and the edge cases are where estimates go wrong.
- Integrations. Payments, a POS, a CRM, an accounting system, a legacy database. Each one adds build time, testing time and a third party whose timetable you don't control.
- Platform choice. Cross-platform with React Native or Flutter gives you one codebase for iOS and Android and roughly halves the build effort. Native on both platforms costs more and is worth it when the app leans hard on the hardware.
- Polish and the non-functionals. Offline support, security, scale and accessibility. They're invisible when done well and expensive to retrofit.
Day rates barely matter next to these. Two agencies with the same rate can land a long way apart on the same brief, because one scoped it and the other guessed.
Does the timeline change the price?
Mostly through scope. A focused first release typically takes 8 to 16 weeks from design through store submission, and larger platforms run 4 to 12 months in stages. Time stretches when a third party is slow or a store review bounces a build, and each extra week is a cost. Fletcher Building's employee app went live in under a week because the scope was deliberately small: push notifications, health check-ins and FAQs for 7,000 staff. Small scope, fast launch, and a bill to match. The same logic is how we keep apps for small businesses and startups affordable.
What does it cost to keep an app running?
Budget for life after launch. Apple and Google ship operating system updates every year, and an app nobody maintains starts misbehaving on new phones within a couple of them. Maintenance covers OS and SDK updates, crash fixes, store compliance, security patches and the small improvements real usage asks for. What drives that cost is how many integrations you have and how often the business wants changes, not the size of the original build. We hold long-term support arrangements for apps we built and for apps we didn't, and the NZ Herald app has been supported through later releases and a premium subscription launch on that basis.
How do you get an accurate number?
Scope first, then price. A short discovery writes down what the first release does and doesn't do, which integrations are in and which wait for release two, and what the launch covers. We fix the price against that document, so the number you sign is the number you pay. If you want the wider picture, custom software cost in New Zealand covers web platforms and systems alongside apps. If you're building in Auckland, our app developers in Auckland can scope it in a room with you, or get in touch and we'll give you an honest range.
Frequently asked questions
-
How much does it cost to build an app in New Zealand?
A focused first release commonly starts in the low tens of thousands of dollars. A full platform with several user types, payments and two or three integrations runs higher and is delivered in stages. The number moves with scope, integrations, platform choice and polish far more than with any agency's day rate, so get the scope written down before you compare quotes.
-
Why do app quotes vary so much between agencies?
Because most quotes price a guess. Two teams reading the same one-page brief will imagine two different apps, and the cheaper quote is often the one that imagined less. Ask each agency what their number includes and excludes. If one has written down the screens, the integrations and the launch work and the other hasn't, you're not comparing like with like.
-
Is a cross-platform app cheaper than native?
Usually. React Native or Flutter gives you one codebase for iOS and Android and roughly halves the build effort compared with two native apps. Go native when you need deep hardware access, heavy background processing or interfaces that have to feel exactly right on each platform. Putti builds both and recommends per project, so the saving is real and not a compromise you discover later.
-
What ongoing costs should I budget for after launch?
Maintenance covers operating system and SDK updates, crash fixes, store compliance, security patches and the small improvements real usage asks for. The two things that drive it are how many integrations the app has and how often the business wants changes. Hosting and third-party services are separate and scale with users. Treat all of it as a line item from day one rather than a surprise in year two.
-
Can I get a fixed price for an app?
Yes, once the first release is scoped. Putti runs a short discovery, writes down what the release does and doesn't do, and fixes the price against that document. A fixed price on a vague brief protects nobody, because every ambiguity becomes an argument later. Scope first, then a number you can hold us to.