A template isn’t a strategy.

The builder isn’t the problem.

You’ve probably heard the advice: use a website builder, pick a template, and save yourself the cost of a professional. You can make something that looks just as good.

Sometimes, you can. A template can be a sensible starting point. If you need a straightforward site, have a clear offer, and can give the work the time it needs, doing it yourself may be the right decision.

The leap comes when “looks good” becomes “does the same job.” A screenshot can show the layout. It cannot show whether the right customer understands the offer, trusts it, completes an inquiry, or receives a useful response.

And the professional response shouldn’t be to call people idiots for trying. Explain the work. If you can’t explain what your fee buys beyond access to a page editor, the question is fair.

The decisions come before the layout.

Who are you trying to reach? What problem brings them to you? Which service do you actually want more inquiries about? Why should someone choose you, and what can you show to support that choice?

Those answers should shape the pages, their order, the copy, and the next step. Without them, it is easy to spend an afternoon choosing a button color for an offer nobody understands. At least the button had a productive afternoon.

Design matters. It gives information hierarchy, makes the experience easier to navigate, and helps your business present itself consistently. But it needs something specific to communicate. “We provide innovative solutions” doesn’t become useful because it arrives in a beautiful font.

Follow the customer past the nice homepage.

Imagine someone looking for a kitchen renovation. They land on a polished site with excellent photography. Can they tell whether the business serves their area? Whether it takes projects like theirs? What the first conversation involves?

Now follow the inquiry. Does the form work on a phone? Does it ask for enough information without turning into homework? Does the message reach someone who will respond? Can the business tell which inquiries are relevant?

For a store, follow a purchase through product selection, shipping information, checkout, confirmation, and support. A customer buys through that whole experience. The homepage is one stop.

These are practical checks, not an argument for making every website complicated. Often the useful change is a clearer service page, a shorter form, or a better handoff after someone gets in touch.

“Build a new one” may answer the wrong question.

There is another problem with the advice in that familiar argument: the business may already have a website. It may need someone to manage it. Suggesting a different builder skips the actual request.

If the offer is outdated, the inquiry process is neglected, or nobody owns the updates, a new platform doesn’t assign responsibility. You can migrate the same confusion into a very attractive new template.

Start by looking at what is failing. Keep what works. Agree who handles content, technical upkeep, and customer-facing problems. Replace the platform when there is a reason the current one cannot reasonably support the work, not because a rebuild is the easiest thing to sell.

DIY can be the right business decision.

A small, straightforward site can be a good DIY project when the stakes are manageable and you have time to write, build, check, and maintain it. You don’t need a custom application to publish your opening hours.

Get help where the uncertainty becomes expensive. That might be positioning and copy, a product catalog, an integration, a buying process, or simply work you never have time to finish. It doesn’t have to mean handing over every part of the website.

Count your time as part of the cost. Compare a realistic scope of professional help with the hours you would spend doing the work and the other work those hours would replace. An affordable tool and an affordable project are two different calculations.

The sensible choice could be DIY, a focused review, ongoing support, or a full build. The recommendation should follow the problem and the budget.

Pay for judgment and clear responsibility.

A useful professional should be able to explain what needs attention, why it matters, what the work includes, and how you will assess it. Ask what they would leave alone. Ask what happens after launch. Ask who owns the accounts and how changes get made.

Be equally skeptical of guaranteed growth and vague promises that everything will be “optimized.” A website cannot rescue an unclear offer by itself. Good work should come with a clear scope and a way to check whether it is helping.

You are allowed to build your own website. You are also allowed to decide your time is better spent elsewhere. Either way, give the site a job, make someone responsible for it, and review what happens.

Looking finished is easy to recognize. Being useful takes a little more thought.