How much does it cost to build an app for a small business?

Bizer · 2026-10-01

The median annual wage for a US software developer was $135,980 in May 2025, according to the Bureau of Labor Statistics. Spread over a 2,080 hour work year, that is about $65 an hour, in salary alone, before benefits, a designer, testing or an agency's margin.

That is the honest starting point for the question, because an app's price is almost entirely hours. Ask anyone quoting you how many hours they expect, and multiply. A quote that will not give you hours is a quote you cannot check.

What a small app actually takes

A customer app usually means three pieces of work, not one:

• An iPhone version and an Android version, or one shared codebase that produces both.
• A back end: the server and database that hold your customers, orders or bookings, and the screens you use to manage them.
• Design and testing, which first-time buyers forget and which take longer than the code.

Three months of one developer at the median wage is roughly $34,000 in pay. Most first apps take more than one person and more than three months. We are not going to give you a price range, because ranges published without the scope behind them are guesses. Use the hours.

The costs after launch

This is the part that turns a project into a commitment.

• Store fees. As of October 2026, the Apple Developer Program costs $99 a year and a Google Play developer account is a one-time $25 fee, per Apple's and Google's own developer pages.
• Store commissions. If your app sells digital goods or subscriptions, Apple's App Store Small Business Program takes 15 percent for qualifying developers under $1 million a year, and Google Play takes 15 percent on the first $1 million of yearly earnings. Physical goods and services are handled differently, so read the rules for what you sell.
• Updates. Apple and Google release new versions of their phone software every year. Apps that are not updated break, slowly and then all at once.
• Hosting and support. The back end runs every month, and somebody answers when it goes down.

Budget for maintenance as a yearly cost, not a surprise. If you cannot name the person who will update the app next autumn, you are not ready to build it.

Do you need an app at all?

Usually not. Ask what the app would do that a fast, mobile-friendly website cannot. The honest answers are short:

• Push notifications to people who agreed to them.
• Working offline, such as a field crew logging jobs with no signal.
• Hardware: the camera, a scanner, a card reader, location in the background.
• Daily use. People will keep an app for something they open every day or every week. They will not download one to book an oil change twice a year.

If your idea is "customers can see our menu, hours and prices", that is a website. If it is "customers can book", that is a booking tool you subscribe to. If it is "a loyalty card", your point of sale system very likely has one already. Each of those costs a small monthly fee instead of a project.

Who should build: a business whose customers would open the app every week, with something the existing tools cannot do, and a budget to keep it alive for years. A coffee shop with an ordering app it runs itself can make sense. A plumber's app almost never does.

A cheaper middle path

Between "subscribe to a tool" and "build a custom app" there is a lot of room. A progressive web app is a website that can be saved to a phone's home screen and behave much like an app, with no store and no commission. Internal tools, such as a job log or a stock count for your own staff, are often built quickly with no-code builders on top of a spreadsheet, because nobody outside the business has to download them.

Start there. If people use the small version, you have evidence for the big one, and a much better brief to hand a developer.

How do you get a quote you can trust?

Write a one-page brief: who uses it, the five things they must be able to do, what it connects to, and what it does not need to do yet. Ask two or three developers for an hourly estimate against that page, plus their yearly maintenance estimate. Pay for a small first phase before you commit to the whole thing.

The cost you are protecting against is not the build. It is the app that is finished, launched and opened by nobody.

What is uncertain

AI coding tools have reduced the hours some simple apps take, and as of October 2026 nobody can say reliably by how much for a given project. Treat any quote that leans on that saving with interest and some caution. Maintenance, store rules and the need for someone to own the thing have not changed.