How Much Should a Website or App Actually Cost? A Straight Answer

"How much does a website cost" gets answered with "it depends" so often that the question starts to feel unanswerable. It isn't. It depends on specific, nameable things, and we'd rather walk through what those things are than dodge the question the way a lot of agencies do until they've locked you into a call.

The variables that actually move the number

• Number of distinct page types and how much custom design each one needs, versus reusing the same layout with different content.
• Whether there's custom backend logic — a booking system, a payment flow, a user account system — versus a marketing site with a contact form.
• How much content needs to be written, translated, or migrated from an existing site, since content work is real work even when it's not code.
• Integration complexity — connecting to a CRM, a payment gateway, an existing internal system — which is often the part that quietly doubles a timeline.
• Ongoing needs after launch — who updates it, how often, and whether that's built into the plan or discovered as a surprise later, the same conversation we cover in what happens after launch.

Rough ranges, honestly stated

A focused marketing website with a handful of pages and no custom backend logic is a different order of magnitude from a custom web application with user accounts, a database, and business logic behind it — and that second category is a different order of magnitude again from a multi-platform product with a mobile app alongside it. Anyone quoting you the same number for all three either hasn't understood your scope yet or is padding one of them.

A quote isn't a guess dressed up as a number. It's a reflection of how clearly the scope has been defined — which is exactly why a clear brief changes the number more than almost anything else.

Why the cheapest quote is often the most expensive one

The lowest quote in a batch is frequently the one that scoped the least, not the one that's most efficient. It's worth asking directly what's excluded, not just what's included — testing, revisions, post-launch support, content — because those exclusions tend to reappear later as change orders, at a worse rate than if they'd been in the original scope.

If you want an honest number for your specific project, the fastest way to get one is a clear brief — see how to brief a dev agency — followed by a direct conversation, not a form that spits out a generic range.