You are not supposed to judge a book by its cover. Visitors judge websites that way anyway, and the research is old enough to be uncontroversial: in three studies published in Behaviour & Information Technology, people rated the visual appeal of homepages shown for just 50 milliseconds, and their verdicts matched the ratings they gave the same pages with far more time. Half a blink is enough to form an impression.
A dated storefront or a maze of navigation costs you the conversation before you get to make your case. But the harder problem comes later. Building a site is full of decisions that look small and turn out to be structural, and the person you hire will either warn you about them or quietly bill you for them. What you need is not an agreeable supplier. It is a partner who cares more about the outcome than about getting the contract signed this week.
Start by Asking Whether You Need a Website at All
The most expensive mistake in this field is building something elaborate that your business does not need yet. A consultant’s integrity is visible at exactly one moment: when they turn down the larger project because a smaller one would serve you better at your current scale.
Sometimes a single well-built landing page that captures enquiries is the right move. Sometimes it is a lean store, or a rebuild of the site you already have rather than a replacement. A good strategist will question your assumptions and hold the project back until a custom build is clearly the right tool. Budget spent early on the wrong shape of site is budget you cannot spend on the right one.
Instant Agreement Is a Warning Sign
If you describe your plan and the developer immediately says “no problem, we can do that” without a single follow-up question, treat it as information. That reply is not confidence. It means nobody has thought about what happens when your product list triples, when three people need to edit the same page, or when the campaign you are planning needs a landing page in two languages by Friday.
A developer who cannot push back is a liability. The useful ones interrogate the brief: who is this for, what does success look like in numbers, which features earn their place in the first release and which can wait. The most honest answer in this industry is rarely “yes”. It is usually “it depends — here is what I would need to know first.”
Ownership: How to Avoid Digital Handcuffs
Technical decisions are ownership decisions wearing technical clothes. Closed platforms can leave you unable to move: your content in a proprietary format, your templates unusable elsewhere, your migration quoted as a new project. Some agencies go further and bury exit conditions in hosting contracts, so leaving costs more than staying.
Standard, open systems are the insurance policy. You should be able to take your site, your content and your data to another provider without asking permission — and you should know, before you sign, exactly where the code, the domain and the backups live. Ask who holds the keys. If the answer takes more than a sentence, that is your answer.
Beyond the Template: What “Cheap” Really Costs
Drag-and-drop builders have made the first version of a website easy, which makes the fundamentals matter more, not less. A site assembled from a bought template by someone who cannot read its code looks like thousands of others, and it strains as soon as you ask it to do something the template did not anticipate.
Command of HTML, CSS and JavaScript is what decides how a site performs, how accessible it is and how it is indexed. Google’s own thresholds are public: in Core Web Vitals, a Largest Contentful Paint of 2.5 seconds or less is good, and past 4 seconds is poor. Templates loaded with plugins routinely miss that line, and the fix is rarely a setting — it is the code underneath.
Professional work also shows up in maintenance. Changing a brand colour or a phone number across fifty landing pages should be one edit, not fifty. That difference is invisible on launch day and obvious a year later.
The Oil-Change Principle: Plan for the Day After Launch
A website is not furniture. It is closer to a vehicle you drive daily: security updates, dependency upgrades, broken integrations, content that goes stale. Nobody expects a car to run for five years without maintenance, yet websites are routinely handed over with no plan for the week after launch.
Ask what happens when the developer is unavailable. Without documentation, credentials in your own name and a person who knows the system, a single disappearance turns a small problem into an outage. Ask, too, what the site does under load — the traffic you are hoping for is the traffic that breaks a fragile build.
From Pretty Pages to a Strategic Tool
A professional designer does not hand over a set of attractive pages. They hand over an instrument built for one job: turning attention into enquiries, safely and repeatedly. The specialist route often costs more at the start and less over the life of the site, because it does not need to be thrown away in two years.
Design decides whether a visitor stays, but content decides whether they trust you. That order comes from research: in a CHI 2004 study of people choosing health-advice sites, design appeal was what drove rejection, while the credibility and relevance of the information was what earned trust. It was a small, qualitative study — fifteen participants over four weeks — but the pattern is one every agency recognises: looks get you considered, substance gets you chosen. The way that plays out in the first seconds is the subject of the halo effect in web design.
So when you evaluate your next project, look past the portfolio at the reasoning. Our services page explains how we scope work, the portfolio shows the results, and if you already know what you need, the fastest start is to tell us about the project. Is your current site a launchpad, or a pair of digital handcuffs you have learned to live with?
