The quiet salesperson: what a website is actually for

The payroll test

Imagine your website is an employee. It greets every prospect you will ever meet, usually before you know they exist. It works nights, weekends and public holidays. Now ask the only question that matters about any hire: what has it closed lately? Most businesses cannot answer, because the site was never given a job. It was given a look. It got a hero image, a paragraph of adjectives and a contact form nobody monitors with intent — and then everyone went back to referrals and cold calls, quietly accepting that the most visible thing the company owns produces nothing.

A job description for a homepage

A selling page needs what a seller needs: a clear offer, proof, and a next step that costs the visitor little. The offer belongs in the first screen, in the language a buyer would use, not the language of your org chart. Proof means specifics — numbers, named clients, real screenshots — because a claim without a number is decoration. And the next step should be graduated: a call for the ready, a short audit or a WhatsApp message for the curious. When a page holds all three, it stops being a brochure and starts being a funnel.

Speed and structure do the invisible selling

Before a single word is read, the visitor has already judged you twice: once on load time, once on whether the page structure makes sense on a phone. Both judgments happen in about two seconds and neither is appealable. This is why we treat performance budgets and information hierarchy as sales tools, not engineering hygiene. A beautiful page that arrives late loses to a plain page that arrives instantly — and a page that forces a customer to hunt for the price, the proof or the button has chosen aesthetics over revenue.

Measure it like a rep

Reps have quotas; pages should have baselines. Enquiries per hundred visitors, calls booked per week, the share of revenue that begins with organic search — pick the two or three numbers that match your model and put them on a dashboard someone actually opens. The moment a site is measured this way, redesign conversations change completely: you stop arguing about colours and start testing headlines, offers and forms. That is the difference between a site you paid for once and an asset that keeps paying you.

When to rebuild, when to repair

Not every underperforming site needs to be torn down. If the foundations are sound — fast, indexable, sensibly structured — a new offer block and a rebuilt enquiry path can double output in weeks. If the foundations are rotten, no amount of copy will save it, and the honest move is a rebuild with conversion designed in from the first wireframe. Either way, begin with the payroll test, write the job description, and hold the page to it. Websites make poor art but excellent employees.