You have an idea for an app, maybe for customers to book and pay, maybe for your staff to stop juggling texts and spreadsheets. You asked around, and the quotes came back anywhere from a few thousand dollars to a quarter of a million. Meanwhile, AI tools promise a finished app by the end of the afternoon. So, how much does it cost to build an app for a business? A small-business app can cost under $10,000 or well over $100,000, because a booking tool, an internal staff tool, a responsive web app and a public iPhone and Android app are different projects with different price tags. The build price is also only part of the bill, and it can hide the costs that decide whether the app keeps running after launch. You can sort out which project you actually have, and what it should cost, before you spend anything.
Key Takeaways
In Clutch's 2025 survey of 158 U.S. small-business owners with an app, 33% spent under $10,000 and 32% spent more than $50,000.
Payments, bookings, logins, integrations and compliance work each add design, backend, testing and support time on top of a simple web app or internal tool.
Apple charges $99 per membership year and Google Play charges a one-time $25 registration; hosting, services and updates cost far more over time.
If a responsive web app or an existing tool already does the three jobs you need, do not commission a custom build yet.
It should say who holds the code, the design files, the cloud and store accounts, the data and the passwords after handover.
What does it cost to build an app for a business?
The broadest published figures come from Clutch's survey of small-business app owners, updated July 2, 2025. It asked 158 U.S. small-business owners and managers who have a mobile app what they spent. A third (33%) spent under $10,000. Almost another third (32%) spent more than $50,000. The full range ran from under $10,000 to more than $100,000.
Read that as proof of spread, not as a price list. The survey does not split its results into web apps, booking apps, payment apps or staff tools, so no single number from it can tell you what your app will cost. What it does tell you is that two quotes ten times apart can both be real, because they are often pricing two different things.
If you are pricing freelance help instead, Upwork's published marketplace rates for mobile-app developers show a median of $18 to $39 per hour. That is a marketplace median, not an agency benchmark, and an hourly rate says nothing about how many hours your scope needs. Agency directories also publish ranges, but those come from their own reviewed projects, so treat them as a sample rather than the market.
| Figure | What it is | Source and limit |
|---|---|---|
| 33% spent under $10,000 | Small-business app build spend | Clutch survey of 158 U.S. owners and managers, updated July 2, 2025; not split by app type |
| 32% spent over $50,000 | Small-business app build spend | Same Clutch survey |
| $18 to $39 per hour | Median rate for mobile-app developers | Upwork marketplace data; not an agency rate |
| $99 per year | Apple Developer Program membership | Apple's enrollment page |
| $25 one time | Google Play full-distribution registration | Google Play Console help |
| 15% on first $1 million | Google Play service fee tier for enrolled developers | Google's service-fee page; terms vary by market and transaction |
Why do app quotes range from a few thousand dollars to six figures?
The price climbs with each job the app has to do and each system it has to talk to. A quote for "an app" can mean a customer portal, a responsive website, an installable web app, an internal staff tool, a booking product or a full iPhone and Android build. Before you compare two numbers, find out which of those each supplier thinks it is pricing. The sections below cover what sits at each end.
What keeps the cost down
A simple responsive web app or internal tool can skip two separate native codebases and all of the app store work. It runs in a browser, gets built once and gets improved once for every device. If the job is narrow, the users are your own staff and there is no payment or sensitive data involved, the project can stay small.
What pushes the cost up
Every one of these adds design, backend work, testing and ongoing support to the bill:
- Payments: Checkout, refunds, receipts and the rules around card data.
- Bookings: Calendars, availability, cancellations and staff schedules.
- Logins and user roles: Accounts, passwords, permissions and what each person can see.
- Integrations: Connections to your CRM, accounting, inventory or booking tools, plus moving existing data across.
- Admin tools: The screens your team uses to manage everything behind the app.
- Compliance and security: Privacy, accessibility and security review, which grow with the kind of data you hold.
- Two native apps: A separate iPhone and Android build, plus store submission for each.
None of these is a reason to avoid building. Each one is a line that should appear, by name, in any quote you get. When one quote lists them and another does not, the cheaper number may simply be leaving them out.
How much does it cost to build an app with AI or a no-code tool?
The subscription price of an AI app builder or no-code platform is easy to find, and it is not comparable to the price of a finished custom app. What you get for that subscription varies by product: how it deploys, how it stores your data, what testing exists, who owns the result and what it costs to run once real customers use it.
These tools can speed up a prototype or handle a narrow internal workflow. No platform or standards source cited here shows that they reliably produce production-ready apps in an afternoon. A working demo still needs clear requirements, access control, testing, a privacy and security review, a real deployment and proof that you own what was built before customers or staff rely on it.
So, treat an AI-built or no-code version as a test. Run your three required jobs through it with real users. If it holds up, you may have your answer for the price of a subscription. If it breaks on logins, data or integrations, that tells you exactly what a paid build needs to cover.
What will the app cost to run after it launches?
The build price is the number on the quote. The running cost is the number that decides whether the app keeps working a year from now. These costs fall into separate buckets, and a low build quote does not tell you any of them are included. Ask about each one by name.
Hosting, services and upkeep
Expect ongoing charges for:
- Hosting: Servers, managed databases and APIs.
- Third-party services: Payments, maps, text messages and email.
- Monitoring and backups: Knowing when it breaks and being able to restore it.
- Updates: Operating system and SDK changes that force app updates, plus bug fixes.
- Security work: Patches and review as new problems are found.
- Support: Someone who answers when staff or customers get stuck.
No published source gives a universal dollar figure for these, because they depend on how many users the app has and which services it calls. Get each one written into the quote with a monthly or yearly estimate.
The two fixed store fees
These are the only fixed figures in the whole budget, and they are small. Apple's Developer Program costs $99 per membership year. Google Play registration for full distribution is a one-time $25. Google also offers a free limited distribution option, restricted to 20 devices. Either way, Google requires an identity-verified developer account, and personal accounts face testing requirements before an app can go out, as its Play Console account guidance explains. Those steps add time to a launch, so they belong in the schedule.
Store commissions, and when they do not apply
Apple says its commission on digital goods and services is normally 30%, and 15% for developers in its Small Business Program and for qualifying subscriptions. Google says its standard 15% tier applies to the first $1 million of annual earnings for enrolled developers, with terms that vary by market and transaction.
Those commissions do not apply just because your app takes a booking or sells a product. Guideline 3.1.3(e) of Apple's App Review Guidelines says physical goods and services consumed outside the app must use a payment method other than Apple's in-app purchase. A haircut, a class or a repair visit booked through the app is a physical service, so it runs through a normal card processor instead.
Do you need a native app, or will a web app or existing tool do the job?
A native iPhone and Android app earns its cost when the business has a repeated mobile task that clearly benefits from the device itself. That means reliable push notifications, work that runs in the background, deep access to hardware such as the camera or sensors, full offline use, or customers who expect to find you in an app store. Customers using phones is not, by itself, a reason to go native.
A responsive web app reaches people by a link the moment it goes live. It can be shared, found in search and improved once for every device. Google describes progressive web apps as combining features of mobile sites and native apps, and notes that they still need to be indexable and linkable like any web page. For many booking, ordering and staff tasks, a well-built responsive website or web app does the job on a phone without an app store at all.
An existing software product can be the best answer of all. If its workflows, permissions, integrations, pricing, data export, support and data handling cover what you need, use it, and build only the piece it cannot do. Check the exit before you commit, because a product you rent can change its plan or close, which is the risk covered in our post on what to do when a website builder shuts down or changes its plan.
This is the answer that costs a custom developer the job. If a responsive web app or an existing tool can already do the three jobs your business actually needs, do not commission a custom build yet. The same goes if you have not defined the workflow, who uses it, what data it holds and who maintains it. Set up and test the existing route first, or pay for a short, separately priced definition phase. You keep the option to build later, and you will know exactly what you are building when you do.
What can you check in fifteen minutes before you ask for a quote?
This check will not price a complex build. What it does is turn "we need an app" into a one-page comparison that makes every quote you collect answer the same question. Do it before you contact anyone.
The fifteen-minute app check
- 1
Minutes 0 to 5
Write the three jobs the app must do in terms you can observe, such as "a customer picks a service and gets a confirmed appointment," not "a modern app." For each, name the user, what starts it, what goes in, what comes out and what fails if it is down.
- 2
Minutes 5 to 10
Test existing booking, CRM, store, form, workflow and portal products against those three jobs. Check data export, permissions, integrations and how each one works on a phone.
- 3
Minutes 10 to 15
Decide who uses it, how often and on which device. Note whether it must work offline or use device features, and whether a link in a browser would be enough.
At the end you should have a short list of non-negotiables and a note on which tools passed or failed each job. If something passed all three, you may not need a build. If nothing did, you now know the gap a quote has to close.
What should a real app quote spell out?
A feature list is not a specification, and a quote built on one leaves the expensive questions open. A quote you can compare against another should state the scope, the terms and, above all, who owns what when the work is done. Ownership is your exit door: the app, the code and the accounts leave with you if you ever change suppliers.
The scope and terms
Look for each of these in writing:
- Users and outcomes: Who the app is for and the jobs it must complete.
- Features in and out: What is included, and what is explicitly excluded.
- Platforms and roles: Web, iPhone, Android, and the permission levels for each user type.
- Integrations: Which systems it connects to, and who pays for those services.
- Milestones and acceptance tests: How you will confirm each stage works before paying for it.
- Design and accessibility: What is designed, and which accessibility standard applies. W3C's WCAG 2.2, republished December 12, 2024, covers web content on mobile devices.
- Hosting and data location: Where the app runs and where your data lives.
- Testing, store submission and launch: Who does each, and when.
- Change requests: The rate for anything added after you sign.
- Support after launch: What is covered, for how long and at what cost.
Security belongs in the quote too. NIST's Secure Software Development guidance, SP 800-218, published February 2022, says buyers can use its shared vocabulary to talk to suppliers and calls for agreements that spell out who is responsible for what. For a mobile app, the OWASP MASVS lists the areas to ask about, including storage, cryptography, logins, network, platform, code and privacy. Apple also holds the developer responsible for the behavior of every ad network, analytics tool and third-party SDK inside the app.
Ownership and handover
The quote should name who controls the code and where it is stored, the design files, the domain, the cloud accounts, the Apple and Google store accounts, every login, the data and the documentation, plus how handover works. If the supplier builds everything inside its own accounts, you may not be able to move, fix or even see your own app without them. That same trap shows up with ad accounts, as in the case of an agency that won't give you your Google Ads account.
Where app projects go wrong
No published dataset ranks small-business app failures by how often they happen. The list below is a practical order for checking your own plan, not a frequency ranking:
- An undefined workflow, which turns into scope that keeps changing.
- Choosing custom software before testing an existing tool or a web app.
- Unpriced integrations, data migration, permissions and support.
- Unclear acceptance tests, so nobody can say when the work is done.
- Accounts and code held by the supplier.
- Skipped updates, security, backups and monitoring after launch.
- Launch expectations that run ahead of the plan for getting people to use it.
Fixing any of these after the fact costs more than settling it in the quote. A missing handover can mean a large recovery job. An undefined workflow usually needs a bounded planning phase before any more building. There is no reliable universal dollar figure for these repairs, which is one more reason to close them before you sign.
Are you ready to price your business app?
Pick an answer to begin.
1. A customer books a haircut through your app. Does Apple take its in-app purchase commission on that payment?
2. What does Clutch's 2025 survey of small-business app owners show about build cost?
3. A responsive web app or an existing tool already does the three jobs you need. What should you do next?
Frequently Asked Questions About how much does it cost to build an app for a business
How much does it cost to make an app for your business?
Clutch's 2025 survey of 158 U.S. small-business owners with an app found 33% spent under $10,000 and 32% spent more than $50,000, with a range past $100,000. The type of app, its features and its integrations decide where yours lands.
How much does it cost to build an app from scratch?
A custom build from scratch sits toward the higher end of that range once it includes payments, bookings, logins, integrations or two native apps. Ask for a written scope first, because two quotes for "an app from scratch" may describe very different projects.
How much does it cost to build an app with AI?
The builder subscription is cheap, but it is not comparable to a finished app. Deployment, data handling, testing, security review and ownership still need checking before customers or staff rely on it.
What does it cost to hire an app developer?
Upwork reports a median of $18 to $39 per hour for mobile-app developers on its marketplace. Agency pricing is different, and the number of hours your scope needs matters more than the rate.
What does it cost to put an app on Apple and Google?
Apple's Developer Program is $99 per membership year. Google Play full distribution is a one-time $25 registration, and Google's free limited option is restricted to 20 devices.
Who owns the code when I build an app for my business?
Whoever the contract says. Make sure it names you as the owner of the code, the design files, the domain, the cloud and store accounts, the data and the logins, and spells out how handover works.
Final Thoughts
A business app can cost under $10,000 or more than $100,000, and the gap comes from what the app has to do: payments, bookings, logins, integrations and two native builds each add to the bill. The store fees are small and fixed, while hosting, services, updates and support keep arriving after launch. A quote you can trust names the scope, the exclusions, the running costs and who owns everything at the end. Before any of that, fifteen minutes with a notebook can tell you whether a web app or a tool you already pay for does the job.
Settling those questions first means the money goes to the app you need, one your staff can support and your customers can finish a task in. It also means that if you ever change suppliers, the code, the data and the accounts leave with you.
If your check turns up a real gap, Web Leveling can help turn your three jobs, your users and your tool test into a scope you can price. Our application development work covers web apps, internal tools and custom builds, with the code and accounts handed over in your name. If a web app or an existing product already solves the problem, we will point you to it. We work with small and medium businesses across the country and overseas. Send us the three jobs your app needs to do, and we will tell you which route fits.
Terms
App cost words in this post
Tap a term to see what it means.
Native app. An app built separately for iPhone or Android and installed from an app store.
Responsive web app. An app that runs in a web browser and adjusts to any screen, reached by a link.
Progressive web app (PWA). A web app that can be installed on a device and behave more like a native app.
SaaS. Software as a service, an existing product you rent by subscription instead of building.
Integration. A connection that lets the app share data with another system, such as a CRM or accounting tool.
Acceptance test. An agreed check that proves a piece of work does what the scope says before you sign off on it.
Handover. The transfer of code, files, accounts and logins from the builder to the business.
