articles — digital growth
The service website's one job: turn a visit into an enquiry.
The visit lasts about thirty seconds, happens on a phone, and often happens in the middle of something else. Increasingly, the first reader may not be a person at all, but an assistant checking the page for someone before they ever see it. Everything on the page either moves that visitor toward an enquiry or loses them to the next tab, or the next name on a shortlist. Design for both readers, and most website debates answer themselves.
skeelx — updated oct 2026 · 5 min read
The 30-second visit
Picture the actual customer: a problem they want solved this week, three tabs open from the same search, no loyalty to any of them. They arrived from the map or an ad, and they're asking three questions in order — do you do what I need, here; can I trust you; how do I get a price. A service website is those three answers with the shortest possible path between them. It is not a brand experience, and it is not a brochure; it's the last step of a search, and every step of it is a place to lose the customer.
Proof that converts
Trust is specific: the registrations or accreditations your field requires, stated plainly; insurance named where it applies; the areas or markets you serve; and photographs of your actual work — the team, the premises, finished projects. A stock photo of a smiling team around a laptop is worse than no photo; every customer has seen it on four other sites, and it reads as having something to hide. Reviews belong here too, quoted honestly and linked to where they live. None of this needs design flair. It needs to be true, visible, and above the fold on a phone.
The next step: call, book or form
Urgent needs phone; considered ones fill in a form or book a time — most service sites need more than one path, and each fails differently. The call path fails by burying the number: it belongs at the top of every page as a tap-to-call link, not on a contact page one navigation away. The form path fails by asking too much: every field is a toll, and a form that demands twelve answers before a price conversation loses the visitor who only wanted to describe the problem. Name, contact, location if it matters, what they need, a file or photo if they have one — enough to triage, nothing more. And the enquiry is only as good as what happens next: a form that lands in an inbox nobody watches after 4pm is a decoration.
Speed is a business requirement
The visit happens on a phone, frequently on a train, in a car park or at the back of a warehouse, where the signal is one bar of hope. A page that takes long seconds to become readable has already lost to the competitor whose page didn't — the customer doesn't wait, they back out to the results and tap the next name. Speed isn't a vanity metric or a developer's hobby; it's the first gap on the path, and it's decided by restraint: modest images, no plugin zoo, no autoplay video of drone footage. We treat performance as an agreed target, measured on cheap phones on bad networks, because that's where the customer is standing.
The agent-native lens: the same visit, read by software
When an assistant makes the visit. The three questions stay the same when an assistant asks them; the reading changes. Software checking your site for someone may not reliably read a photo of a certificate, or work out your service area from a map image. Put the answers in text: what you do and where, the credentials that matter in your field, any prices you're willing to publish, and how to start. Mark up the business and its services in schema.org JSON-LD so they match your profile. Then look at the form as a machine would. Real labels, no step that depends on hovering or dragging, a clear confirmation: accessible forms need these anyway, and they let an assistant fill in an enquiry that a person then confirms. Reply to the person it was sent for, not only to the software.
When the inbox runs on agents. The inbox nobody watches after 4pm is a gap an agent can close. An agent can read each enquiry as it lands, check it has what triage needs, ask for the missing detail, answer routine questions from approved content and offer real times from the calendar. Anything that touches price, scope or a commitment goes to a person, with the agent's summary attached. It can test the path too: a marked test enquiry each week to prove it still arrives, and a slow-phone speed check after every release. Keep each automated reply in the CRM beside the content it drew on, so you can see what a customer was told, and why.
What not to build
The honest list is long. The blog nobody will write — a "News" page whose last post is two years old testifies against you, so don't build it until the writing habit exists. The customer portal nobody asked for. The animated anything. An AI assistant on the site can earn its place when it answers from your own content and hands over to a person cleanly; one that stands between an urgent customer and your phone number is the old chatbot problem with better grammar. Most service websites don't fail for lacking features; they fail for hiding the phone number under features. If a proposal adds a step between the search and the enquiry, it's not a feature — it's a gap. Spend the difference on photography of real work; it converts harder than anything else on the page. Whoever reads the page next, a person on one bar of signal or an assistant working for them, the same discipline serves both: the answers in plain words, a short path, nothing hidden.