"We Need a New Website" Is the Wrong Question

Every Month I Hear the Same Sentence

"We need a new website." That's how 9 out of 10 conversations start when a potential client first calls or writes. And almost every time — it's not what they actually need.

A couple months ago the director of a consulting firm came in. "Our website looks old, we need a new one." Fine. I looked. Yes, the design wasn't the most modern. But then I started asking questions:

• "How's it going with client inquiries?" — "Could be better, we get 5-6 per month, need at least 15."
• "Do you know how many people visit the site?" — "No idea."
• "Have you tried changing anything to increase inquiries?" — "No, we just need a new website."

See the problem? She believes the answer is "new website". But her real problem is "not enough client inquiries". And those are two completely different things.

A Website Is Not a Goal. It's a Tool.

Imagine you have a toothache. You go to the dentist. Do you say "I need a new filling"? No. You say "my tooth hurts" — and let the dentist diagnose and suggest a solution. Maybe it's a filling. Maybe a root canal. Maybe just a hygiene issue.

Websites work exactly the same way. "I need a new website" is like telling the dentist "I need a filling" — you're prescribing the solution before understanding the problem.

Usually, when we dig deeper, the real problem is something from this list:

• "We don't get enough client inquiries from the internet"
• "Our competitors look more professional than us"
• "People can't find us on Google"
• "Our sales process is chaotic — inquiries get lost in email"
• "We don't want to look like a small company, because we're not"

Each of these problems might have a different solution. Sometimes it IS a new website. But sometimes — targeted UX improvements, SEO optimization, CRM integration, or simply better content. And often that costs much less than a full rebuild.

The Right Process: From Problem to Solution

When we work with a client, we ALWAYS start with the business problem, not the technology. The process looks like this:

Step 1: Understanding — what are we actually trying to achieve?

The first meeting isn't about design or technology. It's about your business. I want to understand:

• What do you sell and to whom?
• How does your client find you?
• What's your sales cycle?
• What role does the website play in this process?
• What do you expect from the website — specifically, with numbers?

Without clear answers to these, any website will be "shooting in the dark" — might hit, might not.

Step 2: Audit — what currently works and what doesn't?

Before changing anything — we look at what already exists. Maybe your current website isn't that bad — maybe it just needs specific improvements. Or maybe the foundation is unstable and you really do need to start from scratch. But you can only know this after an audit, not from gut feelings.

Step 3: Strategy — what will have the biggest impact?

Not everything needs to happen at once. We prioritize: what will deliver the biggest business impact fastest? Maybe start with CTA improvements and mobile version, but postpone the design overhaul to phase two?

Step 4: Only now — technology and development

Only after knowing the problem, analyzing the situation, and creating a strategy — do we start discussing technologies, design, and development. Then choosing between WordPress, headless CMS, or a custom solution is logical and justified, not random.

A Real Example That Shows the Difference

Real situation from last year. Client — a mid-sized engineering services company. Came with a clear wish: "we need a new website, the old one looks terrible."

We started the process. In the first meeting we identified the real problems:

• The website contact form generated ~5 inquiries per month, but the sales team needed at least 20
• Inquiries that did come in often got lost in email between colleagues
• Potential clients didn't know about half their services because they were "buried" in the website

The solution we proposed was NOT a completely new website. It was:

• UX restructuring — each service got its own landing page with a clear CTA
• Contact form optimization — fewer fields, social proof added next to the form
• CRM integration — all inquiries automatically go into a system with reminders
• Basic SEO — meta tags, sitemap, speed optimization

Result after 3 months: 22 inquiries per month (was 5). And the design barely changed — same fonts, colors, images. What changed was structure, content, and systems.

Cost: approximately 40% of what a completely new website would have been. Result — 4x more inquiries.

What to Do If You "Need a New Website"

Before calling an agency or freelancer, honestly answer three questions:

1. What business problem am I trying to solve? Not "the website looks old" — but "we're not getting enough clients" or "we can't be found on Google."
2. How will I measure success? Specific numbers — inquiry count, conversion %, traffic. If you can't measure it — you won't know if the new website helped.
3. Who is my ideal client? What are they searching for? What are their doubts? How do they make decisions? A website not built for this person — won't work.

If you have clear answers — any good agency can propose a concrete solution. If not — start with a free consultation where we'll help formulate them.

FAQ

How to know — new website or just improvements?

If the technical foundation is stable (not slow, secure, works on mobile) — usually targeted improvements are enough. If the foundation is unstable (old WordPress, slow hosting, falling apart) — a rebuild may be more effective long-term.

How long does the right process take?

Audit and strategy: 1-2 weeks. Targeted improvements: 2-4 weeks. Full rebuild: 2-4 months depending on scope. But results start appearing in the first phase already.

But I really don't like how the website looks...

I get it! And design IS important. But start with strategy — understand what the website needs to do, then design accordingly. New design without strategy = beautiful website that still doesn't work. I've seen it too many times.