← All articlesWeb Development

Building a Client Website That Doesn't Just Look Good — It Converts

When I started building the website for Kayship, a brand-new truck dispatch business, the brief was simple: “make us look real.” No existing site, no existing brand equity, nothing for a truck owner to Google and find. It’s easy to interpret that brief as purely visual. It isn’t.

Start with the objection, not the layout

Before touching a single design decision, I wrote out every objection a truck owner would have before trusting a brand-new dispatcher: Will I have a dedicated point of contact? Do you handle my truck type? What happens if a load falls through? Every section of the site exists to answer one of those questions before the visitor has to ask it. The homepage isn’t a highlight reel — it’s a rebuttal to hesitation.

SEO structure has to happen at the architecture stage, not after

It’s tempting to build the site first and “do SEO” as a pass afterward. That produces shallow results. Instead, each core service — dedicated dispatcher, route planning, broker communication, paperwork, load booking, factoring — got its own standalone page from the start, built around real search queries truckers actually type in. That decision alone does more for long-term visibility than any amount of after-the-fact optimization.

Trust signals aren’t decoration, they’re the product

Testimonials, stats on loads dispatched, coverage information — none of that is filler. In an industry where the entire relationship depends on trust before a contract exists, these elements are doing real conversion work, not just filling white space.

Mobile isn’t an afterthought when your audience is on the road

A large share of Kayship’s prospective clients would be checking the site from a phone, often from a truck cab. That reshaped decisions I might otherwise have deprioritized — button size, form length, how much text loads above the fold on mobile.

The takeaway

A website that “looks professional” and a website that converts are related, but they’re not the same design problem. The second one starts with objections and search intent, and the visual layer comes after — not before.

Enjoyed this one?

If you're working on something similar, I'd love to help — let's talk.

Get in touch