What Clients Actually Mean When They Say They Want a Website

I get this a lot. Someone reaches out, tells me they need a website, and we start talking. Ten minutes into the conversation it becomes clear that what they actually need has very little to do with a website.

Sometimes they need a booking system. Sometimes they need a way to qualify leads before they waste time on calls. Sometimes they need their sales process to stop living in someone's inbox. Sometimes they just need their business to look credible enough that people stop hesitating before they buy.

A website can solve all of those things. But "I need a website" rarely tells you which one.

The word website carries a lot of baggage

For most people, website is the default word for anything digital. It's the closest thing they have to describing a presence online, a tool that works, a problem solved. It's a placeholder word for a solution they haven't fully defined yet.

That's not a criticism. It's actually useful information. When someone says they need a website, the real conversation is just starting.

What I actually hear

When a small business owner says they need a website, they usually mean: people don't take me seriously enough yet. The solution might be a clean one-page site with a strong about section and a contact form. Or it might be getting their Google Business profile sorted first. Or both.

When a consultant says they need a website, they usually mean: I'm losing work to people who look more established than me. The solution is positioning and credibility, not just design.

When a founder says they need a website, they sometimes mean: I need something to show investors or early users. That's a landing page with a clear value proposition and a waitlist, not a full site.

When an operator says they need a website, they often mean: our current process is broken and we're losing time or customers because of it. That's a workflow problem. Sometimes a website helps. Sometimes it's the wrong tool entirely.

The question I always ask

Before I talk about pages, design, or technology, I ask one thing: what do you want someone to do after they visit your site?

Not what you want them to see. What you want them to do.

That question cuts through a lot of noise fast. If someone says "I want them to book a call," that's a completely different build than "I want them to browse my portfolio" or "I want them to sign up for early access."

The action defines the tool. The tool does not define the action.

Why this matters for the budget conversation

One of the most common mistakes I see is people spending money on the wrong thing. A beautiful five-page website with professional photography and custom animations, when what they actually needed was a focused landing page with a clear call to action and a working contact form.

The expensive version looked more impressive. The simpler version would have gotten more results.

I'd rather build you the thing that works than the thing that looks good in a portfolio screenshot.

What to do before you talk to anyone

Before you reach out to a developer or an agency, spend ten minutes answering these three things. What do you want someone to do when they land on your site? What's stopping them from doing that right now? What would change in your business if that problem was solved?

You don't need a full brief. You don't need wireframes or a mood board. Just honest answers to those three questions.

If you have them, the conversation that follows will be faster, cheaper, and more likely to produce something that actually works.

If you don't have them yet, that's fine too. It just means the first conversation is about finding those answers, not about building anything.

That's still a good use of an hour.