If you have ever asked three developers what a custom web app costs, you probably got three very different answers. That is not because someone is overcharging. It is because "a web app" can mean a simple booking form or a multi-role platform with payments, and the price follows the scope, not the label.
I build web apps for small businesses and startups, so here is how I think about cost, and how you can get a quote you can trust.
What actually decides the price
1. Scope and number of features. Every feature is time. A public page with a contact form is a very different job from a system where customers log in, place orders and track them, and your staff manage everything from an admin panel.
2. Who uses it and how. One type of user is simple. Customers, staff and an owner, each seeing different things, means more design, more testing and more security work.
3. Integrations. Taking payments is the big one. Connecting Stripe, PayPal, PayMongo, Dragonpay or Maya is not just adding a button. It means handling failed payments, duplicate notifications and refunds correctly, so you never end up with an order that was not paid for or a payment with no order.
4. Design. Starting from a clean, simple layout costs less than a fully custom brand design with animation. Both are valid, but decide which you need.
5. Existing systems. Moving data out of spreadsheets, an old website or another app takes careful work, and it is often where surprises hide.
6. Hosting and upkeep. The app has to live somewhere, and someone has to keep it updated, backed up and secure. This is an ongoing cost that is easy to forget in the first quote.
Three common ways to work together
- Fixed-scope build. You and the developer agree on exactly what will be built, for how long and for how much. Best when you know what you need.
- Monthly retainer. A set amount of time each month for improvements and support. Best once your app is live and growing.
- Rescue or migration. Fixing a slow or broken site, or moving it to better hosting. Usually scoped after an audit.
How to get a quote you can compare
Before you contact anyone, write a one-page brief:
- What problem the app solves, in two or three sentences.
- Who will use it (customers, staff, both).
- A list of must-have features, separate from nice-to-haves.
- Any systems it has to connect to, such as payments, email or an existing site.
- Your target launch date.
Then ask each developer the same questions: What exactly is included? Who pays for hosting and domain? How many rounds of changes are covered? What happens after launch? Who owns the code?
Red flags
- A price with no written scope.
- No mention of hosting, security or backups.
- Nobody asks you what your business actually needs.
- You will not own the code or the accounts it runs on.
The honest answer
A small, fixed-scope first version and a full platform with payments and several user types sit in very different price brackets. The cheapest way to find out where yours falls is a short conversation about your idea.
If you would like a straight estimate, send me your one-page brief. I will tell you what I would build first, what can wait, and what it is likely to cost, before you commit to anything.