How much does an app cost? Why the price depends on you
Why an app’s price runs from R$15k to half a million, and how a non-technical founder estimates the right number before asking for the first quote.
The first call almost always has the same question in it. The founder describes the product for ten minutes, with striking clarity about the customer and the problem, and then asks the question they came to ask: “how much does an app like this cost?” The honest answer disappoints, because the honest answer is another question.
A custom app in Brazil costs, in practice, from R$15,000 to more than R$500,000. That range is so wide it’s useless. And it’s wide not because the market is confused, but because an app’s price isn’t a number on a table: it’s the output of decisions the founder hasn’t made yet. Anyone who answers “it costs R$80,000” without asking a single question back is guessing, or selling a package that may not be yours.
This piece won’t hand you a number. It hands you what’s missing so you can reach one yourself: the variables that move the price, the three real build paths and what each truly costs, and the cost that vanishes from every quote. At the end, four questions that set the price before you talk to any vendor.
Why “how much does an app cost” is the wrong question
Ask “how much does a house cost” and nobody answers with a number. They answer with questions: how many bedrooms, which neighborhood, renovating or building from scratch. Software is the same, with one twist: most of the cost lives in things you can’t see from the street.
Look at what happens in Brazilian developer forums like r/brdev every time someone asks the price of an app. The answers fight each other, from R$5,000 to R$300,000, and they’re all right, because each one priced a different app. A chat with login and a marketplace with payments, payouts to sellers and fraud screening are “an app” in the founder’s head and two projects with nothing in common underneath.
The price, then, is an output, not an input. It falls out of three decisions: the size of the scope, the build path you choose, and how long the product will live after launch. Move any one of them and the number moves. That’s why defining the scope before you hire a developer is worth more to your wallet than any price research.
The three paths, and what each really costs
There are three ways to get an app off the ground in Brazil. They don’t compete for the same project: each one fits a different moment in the company’s life.
No-code (Bubble, FlutterFlow, Glide). You assemble the app on a visual platform, without programming. It costs from R$0 to R$15,000 if you build it yourself, or R$15,000 to R$40,000 if you hire someone to build it for you, plus the platform’s monthly fee. It’s the right path to validate an idea before spending for real. The ceiling shows up when the product grows: a business rule the platform didn’t anticipate, a subscription cost that scales with users, performance that stalls on the hundredth screen. Most founders stay on no-code about six months too long.
Freelancer or cheap software shop. A marketplace dev or a small shop ships custom code at the lowest quote. It costs from R$25,000 to R$80,000 for a first app. The range is tempting, and it’s where most of the bad stories live: scope that grows mid-build, code nobody can maintain afterward, the dev who vanishes the week before delivery. It isn’t a rule, but it’s frequent enough that the founder hears from everyone that they “already got burned by a freelancer.”
Engineering partner. A team that runs discovery, defines the scope with you, builds, and stays on after launch. It costs from R$80,000 to R$500,000 or more, depending on size. It’s expensive on the invoice and cheaper on the total when the product is the center of the business and has to last, because you pay once for a system that survives year two and year three. The difference isn’t the programming language. It’s having a tech partner that isn’t a black box, that shows the decisions instead of hiding them.
The expensive mistake isn’t choosing the cheap path. It’s choosing the cheap path for a problem that called for the expensive one, and finding out the next year that you’ll pay for all of it again.
The cost that vanishes from every quote: maintenance
Every app quote talks about launch day. Almost none talk about the two years after it, which is where the real money gets spent.
Software isn’t a building that gets finished. It’s closer to a car: it runs well, and it still goes to the shop. The phone’s operating system changes and breaks the login screen. A library the app depends on stops getting updates and opens a security hole. The customer asks for a tweak, a competitor ships a feature, the regulation changes. Keeping an app running costs, per year, somewhere between 15% and 25% of what it cost to build, and that bill starts the month after launch, not years later.
That’s why “how much does an app cost” needs a sibling nobody asks: how much does it cost to keep it alive? A R$60,000 app that nobody budgeted to maintain becomes an orphan asset the moment the only dev who understood the code walks out the door. Launching the app is the start of the cost, not the end.
The four questions that set the price
Before asking for any quote, answer these four questions. They do the work the vendor would do, and they pull you out of the position where all you can do is accept or reject a number.
1. Does the app need to exist, or does the idea need validating? If you don’t have paying customers yet, the right product is the smallest one that proves the thesis, not the app of your dreams. Here no-code usually wins. Building the full system before validation is the most expensive way to learn nobody wanted the product. It’s worth knowing the difference between a real minimum scope and a wish list dressed up as an MVP.
2. How many critical flows does the app have? Count the actions that, if they break, take the business down with them: signup, payment, payout, delivery. An app with one critical flow is one project. With five, it’s five projects. The number of flows predicts the price better than the number of screens.
3. Is the app the product, or a support tool? If the software is what the customer pays to use, it’s the center and deserves engineering that lasts. If it’s an internal tool that organizes operations, the math changes, but not below what you imagine: well-built internal tools tend to return more than another customer-facing feature.
4. What’s your appetite, in money and in time? Here it’s worth borrowing an idea from Shape Up, by Basecamp: a budget starts with a number and ends with a design, not the other way around. Instead of asking “how much to do all of this,” say “I have R$50,000 and three months, what fits?” Fixing the time and the money and letting the scope vary is what separates a project that ships from one that blows up. The serious vendor prefers that conversation; the one who doesn’t is selling you the invoice, not the result.
With the four answers in hand, you no longer ask “how much does an app cost.” You say what you need, with what appetite, and you judge who understood. The number stops being a guess and becomes a decision.
The cheapest quote is usually the most expensive
The math almost nobody does is the rework math. A R$30,000 app that has to be rebuilt from scratch the next year cost R$30,000 plus the real app, plus a year lost, plus the customer you didn’t serve while you fixed it. The cheap option didn’t turn out expensive by bad luck. It turned out expensive because the low price came from cutting exactly the parts that don’t show up in the demo: error handling, security, code the next person can read.
We’ve watched the same film play out in different product teams. The founder picks the lowest quote, gets something that works in the presentation, and finds out six months later that every simple change takes weeks, because the system was built to pass the demo, not to grow. Then the real cost arrives all at once. Good software looks simple from the outside, even when it’s built with precision underneath; bad software does the opposite, looks finished and bills you later.
There’s no right price for an app. There’s the range that makes sense for the problem you have, at the stage the company is in. Answer the four questions, choose the path with an eye on year two, and treat any quote that arrives with no questions back for what it is: a well-dressed guess.
Frequently asked questions
What does it cost to build an app?
In Brazil, from R$15,000 to more than R$500,000. No-code you build yourself sits near the bottom; a custom app with a freelancer or shop runs R$25,000 to R$80,000; an engineering partner for a product that’s the center of the business starts at R$80,000. The figure follows the scope, the build path, and how long the product needs to last.
How much does an app cost on average?
The “average” misleads, because it mixes projects with nothing in common. For a first custom app with few critical flows, the most common range in Brazil is R$40,000 to R$120,000. Marketplaces, fintechs, and anything with payments and fraud screening sit well above that. And add 15% to 25% per year for maintenance.
How much does it cost to publish an app to the stores?
Publishing is the cheap part. An Apple developer account costs US$99 per year and a Google Play one costs US$25 once. What weighs isn’t the registration, it’s everything before it and everything after, in maintenance. Be wary of quotes that highlight the publishing fee to look complete.
Is it worth starting on no-code?
To validate an idea before you have paying customers, almost always. No-code is the cheapest way to find out whether the product has demand. The mistake is treating the platform as the final architecture: most founders stay on no-code six to twelve months past the point where the product already called for custom engineering.