How Much Does It Cost to Build an App? The Full List to Price Yourself

How much does it cost to build an app? It depends on what's on the list, and the answer comes in 2 parts: a launch number (what you spend to get it live) and a running number (what it costs each month, and each customer, to keep it going). Below are the buckets that make up both, and where to price each one yourself today.

This guide is a shopping list, with no habits or tool picks in it. Ways to spend fewer credits once you're building live in our guide on habits that save credits, and keeping the first version small, the biggest cost cut of all, is covered in Build Small or Go Home.

Why won't a single number help you?

Because the number hides the part that matters. 2 founders can use the same builder and end up with very different totals, since one app sends email, takes payments, and stores photos, and the other is a single page with a form. That's why any app development cost estimate swings so widely.

So I won't quote you a figure, because anything I printed here would be wrong for somebody by next month. What doesn't go stale is the list. Once you know every bucket and where its price lives, an honest estimate takes an afternoon, and I'd jot the date beside every price you look up, since the next plan change will quietly undo it.

What are you paying the AI builder for?

Usually a subscription plus usage. Some AI app builders, Lovable among them, measure usage in credits, which are units the tool deducts as it does work for you.

One balance can cover more than you'd guess. Lovable's credits page says the same credits pay for building, chatting with the tool, hosting your app with its built-in backend, and AI features your published app uses. Build mode is priced on usage, so small, focused edits usually cost less than big generations. If the balance hits zero, building stops and AI features in the live app stop working. The published site stays up and keeps serving pages, but apps that lean on the built-in backend can pause, database included.

In other words, for some builders, building and keeping the app running come out of the same pot. When you price this bucket, I'd ask your tool 3 questions:

1. What does the plan include, and what counts as extra usage?
2. Does hosting or the database draw from the same balance as building?
3. What happens to my live app if the balance runs out?

Still choosing a tool? Our Lovable vs Bolt.new vs Replit guide can help.

What does it cost to keep the app running?

This is where your running number comes from, and it's easy to underestimate, because the builder's preview makes everything feel free. Each item below usually has its own provider and its own pricing page. Setting them up safely is covered in our guide on adding payments, email, and analytics, so here it's only about cost.

• Domain. Your web address, like yourname.com, usually paid yearly to a registrar. Some builders sell domains directly. Lovable's docs say custom domains are available on its paid plans and can be bought inside the tool. Check the renewal price too, since it can differ from the first year.
• Hosting. The service that keeps your app online for visitors (deploying is the step that puts it there). It may be bundled with your builder or billed by a separate host.
• Database and file storage. The database holds your app's records, such as users and orders, and file storage holds uploads like photos. Both tend to grow with users and data.
• Email sending. Receipts, password resets, and reminders go through an email service, usually priced by volume.
• Payment processing fees. Payment companies take a cut of each sale. Look up the current fee on your provider's own pricing page (Stripe's, for example) on the day you budget, and note whether international cards cost extra.
• Analytics. If your builder's visitor numbers answer your questions, this line can be zero. A separate tool only earns its place once you have a question it answers.

I'd price the fees per customer rather than per month. "What does one paying customer cost me?" is easier to reason about than a monthly guess, and it leads straight to the most useful number in this whole exercise: how many customers it takes to cover the app.

What about design assets and legal pages?

Design assets are the fonts, photos, icons, and illustrations that make your app look like yours instead of a template. Some are free with conditions, and some are licensed, so read the license as well as the price tag.

Legal pages are things like a privacy policy and terms of service. I'm not giving legal advice, and this guide can't tell you what yours should say. It's still a real line on the budget. Founders cover it in different ways, from a template service to a lawyer, and a fair first question is how much personal information your app collects, and from whom. Price whichever route you pick. (Customers notice too. Our Trust and Legitimacy area looks for actual legal pages, because that's one of the things people check before trusting you with money.)

How much is your own time worth here?

In my view, this is the bucket most budgets leave blank. Building with AI moves a lot of the work from a developer's hours to yours: writing prompts, clicking through every screen, testing on your phone, and writing the copy.

To price it, pick an hourly number that means something to you, then estimate hours for planning, building, testing, and launch. You don't have to pay yourself that money. Writing it down just keeps you honest about the trade you're making.

Why budget for fix-and-polish rounds?

The first version that works is rarely the one you ship. There's the round where a change breaks something else, and the round where a friend can't find the sign-up button (which is always funnier when it's someone else's app).

Each round costs credits and hours, so I'd give fixing its own line from day one instead of treating it as a surprise. When something does break, our guide on fixing errors without starting over can save you from paying for the same screen twice.

What does it cost to get outside eyes on it?

You built it, so you know where everything is. A customer doesn't, which makes a fresh read worth a line of its own.

The cheapest version is watching 2 or 3 people use your app, which costs time and maybe a coffee. Our audit is the other version, and it fits neatly on a budget sheet: $27, one time, with a full refund on request within 24 hours of delivery if the report isn't useful. You get a score and ranked fixes, so you know where to spend your next round of credits before you spend them.

Should you hire a developer or build with AI?

It's a real choice, and the costs land in different places. With a developer or agency, you mostly pay for their time and judgment, by the hour or by quote, and the fair way to compare is written quotes for the same written scope. With an AI builder, you pay a subscription and usage, and the planning, testing, and deciding shift mostly to you.

A developer brings experience you'd otherwise build up yourself, which matters most for apps that handle sensitive data. The cost to build an app with AI can be lower in cash while asking more of your hours. Some founders mix both, building the first version with AI and then paying someone for a specific job. Either way, the running buckets above still apply.

How do you fill in your own budget?

Say there's a founder (we invented her) building a houseplant-care subscription app. Subscribers add their plants and get watering reminders by email (the plants, famously, do not care about her launch date). Here's her worksheet, with the amounts left for you.

Add the one-time lines and you have her launch number. Add the monthly and per-customer lines and you have her running number. Divide that running number by what one subscriber pays, after fees, and she knows how many plant lovers it takes before the app pays for itself. That's the number I'd want on the fridge.

Sources, all read 13 October 2026: Lovable's "Credits and usage" documentation (undated) and Lovable's "Set up a custom domain" documentation (undated).