It's the first question everyone asks, and "it depends" is a frustrating answer. So let's make it useful: here's what actually moves the number, and how to spend well rather than just spend less.
What drives the cost
Cost tracks complexity, not page count. The big drivers are:
- Scope. A brochure website, an internal tool and a multi-tenant SaaS platform are three different animals. More features and more user types mean more to design, build and test.
- Integrations. Every external system you connect to - payments, email, accounting, third-party APIs - adds work and edge cases.
- Data and logic. A form that saves a record is cheap. A double-entry ledger, real-time ordering or AI document reading is not.
- Users and roles. Accounts, permissions, multi-tenancy and data isolation add real engineering under the surface.
- Design polish and accessibility. "Good enough" and "genuinely lovely on every device" are different budgets.
- Non-functionals. Security, performance, hosting, backups and monitoring - invisible in a demo, essential in real life.
Why "cheap" can be the expensive option
The lowest quote often wins the order and loses the year. Corners get cut on the parts you can't see - security, maintainability, testing - and you pay for it later in outages, rework or a rebuild. Software you can't safely change is a liability, not a bargain.
How to keep it under control
You have more control than it feels like:
- Start small. Agree a first milestone that delivers something real and usable, then build from there. It de-risks the spend and gets you value early.
- Prioritise ruthlessly. Separate "must launch with" from "would be nice". Half the wishlist usually turns out to be phase two.
- Buy the commodity parts. Don't pay to rebuild things that off-the-shelf tools already do well - build the part that's genuinely yours.
- Build to maintain. Boring, well-structured code is cheaper over the life of the product than clever code nobody can touch.
The mindset that saves money
Think total cost of ownership, not sticker price. A system that's a little more to build but easy to run and change beats a cheap one that fights you every month.
How we quote
We start by understanding the outcome you need, then propose a sensible first milestone and are honest about what things take - no padded scope, no surprise invoices. If a cheaper off-the-shelf route would serve you better, we'll say so.
Want a realistic figure for your idea? Tell us what you're trying to build and we'll give you a straight view.