What a $30k website should actually include

A prospective client asking "why does a website cost $30,000" is usually comparing against a $500 template purchase, and the honest answer isn't about pixels; it's about what a template can't do: a content and information architecture built around how their specific customers actually search and decide, not a generic layout.

At that budget, the deliverable should include a real design system, not just a homepage mockup, performance engineering treated as a requirement rather than a hope, structured content that a non-technical team can actually update without breaking the design, and enough SEO foundation (proper metadata, semantic structure, sitemaps) that the site is discoverable on day one.

What it usually shouldn't include: a bespoke CMS built from scratch when an existing headless CMS solves the problem for a fraction of the maintenance cost, or custom animation work that exists to impress the client in the handoff meeting rather than to serve the visitor.

The honest pitch isn't "more expensive means better." It's "this budget buys a system built around your actual customers and maintainable by your actual team," which is a different, more defensible claim than pointing at the price of a template and explaining why it's not enough.