SolutionsAcquire

A website is where someone decides.

Almost every enquiry has already been through a silent round of checking. By the time the phone rings, the website has done its work — well or badly.

Most business websites are built as brochures and judged as brochures. The visitor is using it as something else entirely: a way to find out whether you do the thing they need, whether you are real, and what happens if they make contact.

Build for that and the site earns enquiries. Build for the brochure and you get a better-looking site that converts exactly as badly as the last one.

What the visitor is actually doing

Not reading. Checking, in roughly this order — and a site that answers these four clearly is working, whatever it looks like.

Is this the right kind of business? Within seconds, not paragraphs
Is this real? Named people, real detail, signs someone is there
Has this been done before? Not always a case study — sometimes just a view
What happens if I make contact? The one nearly everyone leaves unanswered

Why "it looks outdated" is the wrong brief

A dated site does lose trust, but that is a symptom. The enquiries were lost because the visitor could not tell what was on offer, could not find proof, or could not see what contact would lead to. A redesign on the same structure fixes the impression and leaves the cause. We would rather rewrite what the site is trying to say and then build a structure that says it.

What we build

Usually less than people expect. Five pages that do their job beat twenty that hedge, and a small site built properly outperforms an ambitious one built halfway.

One page per thing you genuinely sell, in the words customers use
Proof that is specific enough to be checkable
Contact paths with no friction and a stated next step
Fast on a phone, because that is where the decision happens

The part after the click

A website that converts and an enquiry process that drops the result is a common and expensive combination. We treat the two as one system: where the enquiry lands, who owns it, what state it is in, and whether anyone can see what is stuck. Most conversion problems live in that trail rather than at the top of it.

Recognisable when

Enquiries arrive in more than one place, or get missed
The site explains the company rather than the decision
Nothing tells a visitor what happens after they submit the form
Traffic is fine and enquiries are not

Questions we get

Do we need a website or a landing page?

It depends on how the visitor arrived and what they already know. A landing page serves someone who clicked one specific message and needs the friction removed. A website serves someone orienting — and for anything considered, they need somewhere to check you are real.

How many pages do we need?

Fewer than you think. One page per service you actually sell, something that proves the work, a way to contact you, and a reason to believe. Publishing articles on a site that cannot convert a visitor is pouring water into a bucket with a hole in it.

Will it be good for SEO?

The technical side is not optional and we build it in — fast, crawlable, structured, one honest page per thing you want to be found for. But ranking brings the visit; the page decides the enquiry, and that is the part more often left broken.

Can you work with our existing site?

Often, yes, and it is usually cheaper. If the structure can carry what the site needs to say, rewriting and rebuilding the weak parts beats starting again.

Start with the problem, not the service.

The first conversation is about understanding what is not working, not scoping a build. Sometimes the answer is much smaller than expected, and occasionally it is not software at all.

Start with a problem See Acquire in context