Nobody likes hearing “it depends” when they ask what a website costs. It sounds evasive, like a way to avoid committing to a number. But for most web projects, it’s the only honest answer, and understanding why actually helps you get a more accurate quote, not a vaguer one.
“It depends” isn’t a dodge. It’s what happens when a fair price requires knowing what you actually need before naming a number.
Primo Collab
A website isn’t one product, it’s a range of scope
“Build me a website” could mean a single-page brochure site with no ongoing content, or a full e-commerce build with custom checkout logic, inventory sync, and a content strategy behind it. Those two projects don’t share a price range, and any number given before scope is defined is either a lowball meant to get you on the phone, or padded high enough to cover whatever the real project turns out to be.
The variables that actually move the number
- Custom functionality vs. standard features. A contact form is standard. A custom quote calculator, membership gating, or third-party API integration is not, and each adds real development time.
- Content volume and who’s providing it. A 5-page site and a 40-page site with existing copy and photography are very different scopes, even on the same platform with the same design complexity.
- Design from scratch vs. building on an existing system. A fully custom design takes meaningfully longer than adapting a proven template or existing design system.
- Integration complexity. Connecting to a CRM, a payment processor, an inventory system, or existing internal tools adds real time that a simple site never touches.
- Timeline. A rushed turnaround costs more than a normal one, for the same reason overnight shipping costs more than standard.
What a fair quoting process actually looks like
A quote that means anything requires a real conversation first: what pages, what functionality, what content exists already, what integrations matter, what the timeline is. A number given without that conversation is a guess, not a quote, whether it comes in low to win the project or high to cover the unknown.
How to get a more accurate number faster
Come to the first conversation with a rough list: pages you need, anything beyond a standard contact form, whether content and photography already exist, and any tools the site needs to connect to (booking software, CRM, payment processor). The more of that you can answer upfront, the faster “it depends” turns into an actual number.
The mistake to avoid
Chasing the lowest quoted number without comparing what’s actually included leads to the most common bad outcome in web projects: a low number that balloons once “extras” get added back in, or a finished site that’s missing functionality that was assumed to be standard. A quote is only comparable to another quote once both cover the same defined scope.