How many platforms
iOS and Android and web is three products sharing a backend, not one product. Cross-platform frameworks narrow the gap but do not close it.
Most cost guides give you a range so wide it is useless. This one gives you indicative ranges drawn from real PixelForce engagements, what sits inside each, and the specific decisions that move a project from one end of a range to the other. They are guidance for planning, not a quote.
An app is not one purchase. It is a sequence of them, and the reason published ranges are so wide is that they blend all of these into a single number. Here is how a PixelForce engagement is actually priced. Treat every range below as guidance for planning rather than a quote.
| Stage | What it is, and when it applies | Price |
|---|---|---|
| Discovery call | A structured conversation about the idea, the constraints and the commercial goal. Always the first step. | No charge |
| Product Design Blueprint | Scoping and design. Research, user flows, full UI design, technical architecture and a costed build plan. You own the output whether or not we build it. Mandatory before any build. A small proof of concept can sit near $20,000; a larger or more complex engagement can reach $65,000 or above. | $20,000 - $65,000+ |
| Proof of concept build | A working test of the single riskiest assumption. Not a product - an answer. Right when the question is "will this work at all" and speed matters more than polish. Still needs its own reduced scoping first. | $50,000 - $100,000 |
| MVP build | Development, QA and release of a real product people pay for - iOS, Android, web, backend and infrastructure. The full go-to-market build, and the band most funded startups and established businesses land in. | $100,000 - $350,000+ $150,000 - $300,000 typical |
| Ongoing support | A dedicated squad on a four-week cycle - features, fixes, infrastructure and iteration. After launch. Five tiers from Steady through to Momentum, sized to how fast you want to move. | $10,000 - $50,000+ per 4 weeks |
| Tech audit | An independent read on an existing codebase - what is salvageable, what is not, what it will cost. For when you have inherited a build or a previous agency has left problems behind. | $5,000 - $15,000 from $5,000 per platform |
| Project takeover | Stabilising and taking ownership of an existing platform. Rescue work, following a tech audit. | $20,000 - $50,000 |
These ranges are guidance, not a quote. They are drawn from real PixelForce engagements and are wide on purpose, because a two-screen internal tool and a marketplace with payments and compliance obligations are both "an app". Where your project lands depends on scope, platforms, integrations and the standard it has to meet - none of which can be known from a page. Figures are indicative, exclude third-party costs such as app store fees, cloud hosting and licences, and are current as at August 2026. The only number that means anything is the one that comes out of a scoping engagement, and that is the point of the Blueprint.
The rule underneath all of this is simple, and we do not make exceptions to it: no Blueprint, no Build. Quoting a build price before the scoping work is done means guessing, and a guessed number is the single most common reason app projects overrun.
Two apps that sound identical in a first conversation can differ by $150,000. These are the decisions responsible.
iOS and Android and web is three products sharing a backend, not one product. Cross-platform frameworks narrow the gap but do not close it.
Screen count is a reasonable proxy for scope. An onboarding flow, a settings area and a profile page are three separate design and build jobs.
A content app reading from an API is not a marketplace with payments, matching and dispute handling. The visible app can look the same.
Payments, identity, mapping, wearables, CRM and legacy systems each carry their own design, build and testing cost - and their own failure modes.
Health, finance and anything handling personal information carries obligations under the Privacy Act 1988 that shape architecture from day one.
Building for the next twelve months and building for 100,000 users are different architectures. Choosing correctly early is the cheapest decision available.
The lowest number in a competitive process is often the one that has not thought hardest about the problem. It is priced against what you described, not against what you will need once real users arrive.
We rebuild other people's apps regularly enough to see the pattern. We have rescued more than fifteen platforms in the past three years. In that work app ratings recovered from 3.8 to 4.6 stars, crash rates were typically cut by 50 to 70 percent within two weeks, and feature development ran 60 to 80 percent faster after modernisation. On Move With Us, a platform with more than 200,000 users, we reduced crash rates by 50 percent and improved performance by 40 percent with zero business interruption.
Every one of those projects was cheaper to build the first time than it was to build twice.
The Blueprint is not a document exercise. It produces the full design, the technical architecture and a costed build plan, and you own it whether or not we do the build. Founders regularly use it to raise. It is also the cheapest point at which to discover that the idea needs reshaping.
A proof of concept exists to test the riskiest assumption before committing to a full build. It is the right choice when speed and budget matter more than polish, and the wrong choice when you need something users can actually live in.
This is the band a real go-to-market build lands in. It is what we built SWEAT from - the app generated $17 million in its first year, went on to reach 30 million users across 155 countries, and was acquired for $400 million. EzLicence, which we built and still operate, now processes more than $100 million in annual bookings.
Launch is the start of the work, not the end of it. A retainer buys a dedicated squad on a four-week cycle. The tier you pick sets how much you ship per cycle, not the quality of what ships.
A number given before scoping is a guess dressed up as a quote. If an agency gives you a fixed build price in your first conversation, they are either padding heavily to cover the unknowns or they will come back for more later.
What we will do on a first call is tell you which band your idea is likely to sit in, what would push it into the next one, and whether the thing you are describing is worth building at all. That conversation is free and it takes about 45 minutes.
Want a real number for your idea rather than a range?
Book a discovery callThe same canonical PixelForce engagement model behind 100+ shipped products and $1.5B+ in combined client revenue, applied to your app. The 1-3-1 method runs through every conversation - one problem, three options with honest trade-offs across budget, timeline and scope, one recommendation. No Blueprint, no Build.
A free, no-obligation conversation to find the right path for your app before you commit a dollar.
Everything you need to build with total confidence - a fully costed, designed plan with no scope surprises.
From approved designs to your live app, built and tested at a steady sprint cadence.
We do not disappear at launch - monitoring, warranty, and an optional retainer keep your app growing.
The questions buyers and search engines ask most about this stage.
No obligation, and no scope you cannot afford. You leave the first call with one recommendation and the reasoning behind it - even when that recommendation is not us.