Illustrative case study
How a project works — from template site to a real one
Representative example · Commercial trucking compliance · Brand direction + marketing site
A representative walkthrough of how a Refinement Lab Studio project works, shown through the kind of local business this studio is built for. It's drawn from real project patterns. No specific client is named or claimed.
The kind of business
Picture a commercial trucking compliance company — the sort of local business this studio is built for. They keep trucks legal: the fuel-tax filings, registrations, DOT numbers, and permits that owner-operators and fleets can't afford to get wrong. They're good at the work, and well known locally, mostly through word of mouth.
The website is the weak link. It's a generic template — bare service acronyms with no explanation, no trust signals, a broken page or two, and no thought given to the phone screens most of their customers actually use. The work is excellent; the website undersells it.
Here is how I take a business like that from a template site to a real one.
Step one — questions before design
Before anything gets designed, I answer four questions in writing.
- Who actually uses this site?
- Not “customers” in the abstract — specific people. For a compliance company, that's usually three: an independent owner-operator who hates paperwork and decides on his phone between loads; a fleet manager juggling renewals across many trucks and several states; a brand-new operator who doesn't yet know the terms. Each one needs the site to do a different job.
- What's the one thing they all need?
- Here, to know within about ten seconds that this is a local team they can trust to keep them legal and on the road.
- What rules guide the rebuild?
- A short set, agreed up front. Keep the industry acronyms — customers search the exact term they were told — but pair each with plain language about who needs it and why. Lead with the business, not any one person. Make trust visible. Replace a dead-end contact form with a simple “what do you need?” path.
- What does the site need to contain?
- A full page map — home, a services hub with a page per service, an about page, a working reviews page — written down and agreed before a single screen is designed.
That written plan is the part most small businesses never get. It means there's no guessing about scope, and no argument later about what “finished” means.
Step two — decisions made in the open
The platform. I lay out the honest options — typically a familiar low-cost route and a custom build — with real costs and trade-offs for each, and we choose together. For a business that wants room to grow, the custom build usually wins: it costs almost nothing to run, loads fast, and leaves room to add things like a customer login area later without starting over. The studio builds on a modern, fast foundation (Next.js).
The brand.Most local businesses have a genuine story their template site has buried — a place, a history, a reason they're trusted. Part of the work is finding it and bringing it to the surface, in the design and in the words.
Step three — what the project produces
- A written plan — the research, the priorities, and the page map, as a document the client owns
- A brand and design direction, from palette and type to photo treatment
- A custom site, built and launched in working pieces — starting with the home page, then the inner pages on the same foundation
- A simple quote- or contact-request flow that replaces the old dead-end form
Why it works
This is how I work on every project: a written plan before a design, built around the real people who use the site, shipped in working pieces rather than one big reveal. The website becomes a business asset, not a brochure that goes stale.