What a custom web platform really costs
What drives the price of custom software, what I have built, and how fixed-scope pricing works, from the engineer who builds it.
Hemen Hiwa Kamal5 min read
Most quotes for custom software differ for one reason: they describe different amounts of work. Hourly rates matter much less than people expect. A buyer who compares two quotes without comparing scope is comparing two different products.
This article explains what moves the price, what I have seen on projects I built, and how I price my own work, so you can judge any quote you receive, mine included.
The five things that set the price#
| Driver | Why it matters |
|---|---|
| Number of systems | A web app, a mobile app, and a backend are three builds, not one. Each has its own design, logic, testing, and release process. |
| Integrations | Payments, CRMs, email, identity, and AI services each take time to connect, and each can change under you. |
| Business rules | Pricing logic, roles and permissions, approvals, and edge cases are where most hidden work lives. |
| What exists today | Replacing or migrating an existing system costs more than building on an empty page. |
| Certainty of scope | The less settled the requirements, the more a fixed price has to include a margin for the unknown. |
If you remember only one thing, remember the first: count the systems. It predicts the bill better than anything else.
What I have built#
Anviil, a platform for personal trainers. It took about six months to build and consists of three separate systems: a web application, a mobile app, and a backend. I mention it because it shows how effort scales. Nothing in it is exotic. The size comes from having three systems that must behave as one.
Östermalms Blommor is a florist in Stockholm that had only a physical storefront and needed to become visible online. The project was an online shop for customers plus a full management dashboard for the owner: analytics, orders and order tracking, product and category management, discounts, checkout, and employee accounts with separate permissions. Nothing in that list is unusual on its own. What sets the price is that it is all of it at once, and that the admin side is as much work as the shop the customer sees.
Rough ranges#
These are starting points for fixed-scope projects. The exact number depends on the five drivers above, and I confirm it after a scoping conversation.
| Project type | Typical starting point | Typical duration |
|---|---|---|
| A shop or portal with an admin dashboard | from $45,000 | 2 to 3 months |
| A web platform with a backend, integrations, and roles | from $120,000 | 4 to 6 months |
| A mobile app added to a platform | priced separately, on top of the platform | depends on scope |
The mobile app is optional, and many projects are better off without it at first. When it is included, it is a separate build with its own cost, as the first table explains.
If your budget sits well below these numbers, a smaller first phase usually makes more sense than a cheaper version of the whole thing.
How I price my own work#
I work on a fixed price based on a written scope, and I keep it simple:
- Discovery first. A short, paid phase that ends with a scope document you own. You can take it to any developer. Most quote disagreements get resolved here, before anyone commits to the big number.
- A fixed price for the agreed scope, paid in full when we sign the contract, before work begins. I do not bill in milestones, because invoicing cycles create delays that slow the project down for both of us. In return, the contract protects you: a defined delivery schedule, and a refund for any work not yet delivered if either of us ends the engagement early.
- Written change requests. If something outside the scope comes up, I estimate it and you approve it before any work starts. Nothing is added silently, in either direction.
- An optional retainer after handoff for maintenance, improvements, and support. It is a separate agreement. You are never locked in, and the handoff includes everything another engineer would need to take over.
Questions to ask any developer before you sign#
- What exactly is in scope, and what is not? Can I see it in writing?
- What happens when requirements change halfway through?
- Who owns the code and the accounts on the day we finish?
- How will I see working software before the final delivery?
- What happens to my payment if the project ends early?
- What is the plan if you are unavailable for a week?
Good answers to these protect you more than a lower price does.
Want a number for your project?#
The fastest way to get one is a short conversation about what you are trying to build. I will tell you honestly whether it fits, roughly what it involves, and what a sensible first phase looks like.
Hemen Hiwa Kamal is a full-stack engineer in Sweden who builds complete web platforms for companies, from first scope to handover.