How much does it cost to build a web app?
A web app is not priced by its screens. It is priced by what it has to keep right: who can see what, money, data, and the other systems it talks to. That is why a client portal can cost more than a large website, and why a first version that does one thing well costs a fraction of a full product. Here is what drives the cost, what comes back every month, and how to start small.
What drives the cost
- User roles. One kind of user is simple. Customers, staff and an admin who each see different things multiply the work and the testing.
- Accounts and sign-in: passwords, sign-in with Google, password reset, invitations.
- Payments: one-off or subscriptions, refunds, invoices, and confirming each payment with the provider rather than trusting the browser.
- Integrations: a CRM, a calendar, accounting software, a delivery service, a marketplace.
- An admin panel, so your team can manage users, orders and content without a developer.
- Data you bring in: moving years of records from spreadsheets or an old system.
- How many flows the product has. Each path a user can take, from booking to cancelling to complaining, is designed, built and tested.
Start with the smallest product that is useful
The most reliable way to keep the cost down is a first version with one core flow: a customer books a slot, a client sees their order status, a seller lists an item. Launch it, watch real people use it, and add the next feature when someone asks for it. Most features planned before launch turn out to matter less than the ones users ask for afterwards.
- Use proven services for sign-in, payments and email instead of building them.
- Build for the web: one codebase works on phones, tablets and computers, with no app store.
- Prototype it yourself with an AI app builder first. A clickable prototype is the clearest brief you can give anyone, including yourself.
What you keep paying after launch
| How it is billed | What to know | |
|---|---|---|
| Hosting and database | Monthly, grows with use | Free or low-cost tiers often cover a first version. |
| Email and messages | Per message or monthly | Confirmations, reminders, password resets. |
| Payment fees | A share of each payment | Charged by the payment provider, not the developer. |
| AI features | Per use | AI search or writing features pay the AI provider per request. |
| Updates and fixes | Ongoing | Libraries need updates and security fixes. Budget for them, or learn to do them. |
| New features | Every time | Usually the largest cost over the years, unless your team builds them. |
Ways to build it, and how each is priced
| Yourself, with AI | No-code platform | Freelancer | Agency or studio | |
|---|---|---|---|---|
| How you pay | Subscriptions, credits and your time | A monthly plan per app or per user | Hourly or per milestone | A project quote, then change requests |
| Good for | Prototypes and internal tools | Simple internal apps | A defined, modest scope | Large products with many people |
| Who owns it | You | The platform runs it | Depends on whose accounts | Depends on the contract |
| Main risk | Security and data mistakes | Limits and per-user pricing as you grow | Nobody else knows the code | Cost and timeline grow with each change |
Questions to ask before you agree a price
What exactly is in the first version?
A written list of flows and roles. Anything not on it is a change, and changes are where budgets break.
Fixed price or hourly?
For a first version with a clear scope, a fixed price protects you. For open-ended work, agree a cap.
Whose accounts?
Code repository, hosting, database, domain and payment provider, all in your name from day one.
What will it cost to run?
Ask for the monthly services the app needs, so the running cost is no surprise.
Who adds the next feature?
If the answer is always "us, for a new invoice", that is part of the price.
When it is worth getting help
- Real customers will pay or leave personal data in the app.
- Your prototype works, but every new feature breaks an old one.
- You want to keep building features yourself, on a foundation that will hold.
Our price does not depend on the size of the app: $450 on the Solo plan, fixed. We build the foundation (structure, data, accounts, the core features and a safe way to publish changes) and teach you to build every next feature yourself with AI. If several people will build on it, the Team plan trains up to 15 of them for $1,900.
Frequently asked questions
Why do web app quotes vary so much?
Because "a booking app" can mean one calendar or a system with staff schedules, payments, reminders and reports. Send the same written list of flows and roles to everyone you ask.
Is a web app cheaper than a mobile app?
Usually, yes: one codebase runs in the browser on every device, with no app store reviews and no separate iOS and Android versions to keep in step.
What does an MVP need?
The one flow that proves people want the product, the sign-in it needs, and a simple admin view for you. Everything else can wait until users ask for it.
Can I build the first version myself?
A prototype, yes, and it is a good idea. Before real users bring money or personal data, put it on a foundation designed for that, or have it checked.
What will the app cost per month?
It depends on the services it uses and how many people use it. Small apps often start on free or low-cost tiers; ask for the list of services before you build.