Buyer resource
What a Custom Website or Business Application Actually Costs
A custom website or business application has no single market price; the cost is set by four things: whether the design is template-based or original, how many outside systems it must connect to, whether it handles accounts, payments or regulated data, and how much of the content and decision-making you supply yourself. Honest vendors price those drivers, not the label.
Published · Last reviewed by Geek Engineering senior engineering review.
Why quotes for the same project differ so much
Ask five vendors to quote 'a website for my business' and the numbers can differ by a factor of ten, because each vendor imagined a different project. One priced a configured template, another priced original design with custom features, and a third quietly excluded content, testing and launch. The spread is not dishonesty; it is an under-specified question.
The fix is to understand which band your project is actually in before you collect quotes, and then force every quote to cover the same scope lines.
The four questions that set the band
- Design: will a quality template with your branding do, or does the business need original design and interaction work?
- Integrations: how many outside systems must it talk to — payments, inventory, a CRM, production equipment, legacy databases? Each integration is its own small project.
- Trust surface: does it handle user accounts, payments, personal data or regulated records? Those bring security, testing and compliance work that a brochure site never needs.
- Your side of the work: who writes the content, supplies photos, makes decisions and tests? Vendor-supplied content and slow decisions both cost real money.
The project classes
| Project class | What it typically includes | What moves it up a band |
|---|---|---|
| Template marketing site | A proven theme, your branding and content, standard pages, basic SEO setup | Original design, custom features, copywriting you ask the vendor to do |
| Custom marketing site | Original design, custom components, content structure, analytics, performance work | Many page types, multilingual content, a CMS your team will edit |
| Web application | Accounts, roles, forms, dashboards, a database, an admin area, automated tests | Payments, file handling, notifications, offline use, audit trails |
| Integrated platform | An application plus connections to ERP, CRM, equipment or legacy systems | Undocumented legacy systems, data migration, uptime guarantees |
Where the money actually goes
Programming is rarely the majority of a serious project. Discovery and specification, design, content, integration work, testing, deployment and the first month of fixes all take real hours. A quote that is all 'development' has usually left the rest out, and the gap reappears later as change orders.
- Discovery and specification: agreeing what is being built before it is built
- Design and content: the part users actually see and read
- Build and integration: the programming itself
- Testing and launch: browsers, devices, data migration, go-live
- The first ninety days: fixes, small changes and tuning after real use
The recurring costs nobody mentions
Ask every vendor for the expected yearly running cost alongside the build quote. A build priced attractively against an expensive run model is not the bargain it appears.
- Hosting and infrastructure, which scale with traffic and data
- Third-party licenses: plugins, email services, maps, search, monitoring
- Security updates and dependency maintenance, even when nothing changes
- Content upkeep, because a stale site quietly stops converting
- Support: who answers when something breaks at month seven, and at what rate
How to get a number you can trust
A real number comes from a short, paid discovery exercise: a vendor reviews what you have, what you need and what it must connect to, then produces a scoped estimate with the assumptions written down. It costs little, and it converts the quote from a guess into a commitment.
A precise fixed price offered immediately from a one-page description is the opposite signal: either the price is padded for safety, or the gaps will come back as change orders. Treat it as a red flag, not a convenience.
Key takeaways
- There is no market price; there are drivers that set a band.
- Design originality, integrations, trust surface and your own workload set the band.
- Compare quotes line by line on scope, and ask for the yearly running cost.
- A paid discovery produces a number you can hold a vendor to.
Related questions
Why did I get quotes that differ by ten times for the same website?
Because the vendors priced different projects. One assumed a configured template, another original design and custom features, and they excluded different things: content, testing, migration, support. Force every quote onto the same scope lines — design, content, integrations, testing, launch, support — and most of the spread collapses into visible exclusions.
Is a cheap template site good enough for a real business?
Often yes, and it is the honest starting point when the site's job is to present the business clearly and be found. A template becomes the wrong answer when the business needs custom functionality, deep integrations, or a distinctive experience that templates cannot express — at which point you are in a different project class, not a more expensive template.
What does a web application cost to run after launch?
Plan for hosting, third-party licenses, security and dependency updates, periodic content work and a support arrangement. A reasonable rule is to expect meaningful yearly spend for as long as the system matters to the business, and to get the expected figure from the vendor in writing before the build starts.
How can I reduce the cost without wrecking the project?
Cut scope, not quality: launch with fewer features done properly rather than everything done thinly. Supply your own content and decisions quickly, reuse proven components instead of inventing, and phase the integrations so the riskiest one is not blocking launch. The expensive failure mode is paying twice — once for the cheap version, then again for the rebuild.
Should a software project be fixed price or time and materials?
Fixed price suits a scope that is genuinely defined, usually after a paid discovery. Time and materials suits discovery-led work and anything touching undocumented legacy systems. A fixed price against an unknown scope is the same risk with contingency added and less visibility into how it is spent.
Continue your project research
Build vs buy software
When custom software is the wrong answer.
Software development services
Custom applications, integrations and dashboards.
What to know before building a business
The full pillar guide this page was split from.
Automation project cost drivers
The same honesty applied to automation projects.
Prefer to talk this through?
Send a short brief — objective, equipment, timeline — and a senior engineer will respond with questions and an honest fit assessment.
Get a Quote