A Website That Looks Like a Real Company, Loads Fast, and Brings In Business
Sometimes the site itself is the problem: it looks dated next to the competition, takes four seconds to load on a phone, and nobody on staff can change a headline. I design and build websites that fix all three, and I only recommend a rebuild when patching would cost more.
What Is Usually Wrong
- The site was built by an agency three years ago and nobody on staff can change a headline or add a product without calling someone.
- The homepage takes four seconds on a phone, and Google ranks it lower for it.
- It looks fine on the desktop in the office and falls apart on the phone your customers use.
- It says what the company does but not who it is for, so business buyers and consumers both leave.
- Orders live in one system, customers in another, and someone re-types between them every week.
- It has been "getting a refresh" for two years.
It looks fine on the desktop in the office and falls apart on the phone your customers use.
What I Do About It
- Start with the job the site has to do: sell products, generate quote requests, book appointments, or reassure a buyer who found you somewhere else. The design follows the job, not the other way around.
- Design pages that say who you serve and what to do next, in plain language, and look like a company someone would trust with money.
- Build fast and mobile-first, to WCAG 2.1 AA design practices, with the page structure and structured data that search engines and AI assistants can read.
- Connect the tools that should talk to each other, retire the ones that should not exist, and leave the site editable by your own team.
- Patch instead of rebuild when that is the honest answer, quoted flat either way before anything starts.
What Lands on Your Desk, and When
A plain map of what the site has to do, what it does today, how fast it is on a phone, and a decision memo: patch or rebuild, with the number either way.
Design direction agreed, the priority pages designed and reviewed on a phone, and the speed and connection fixes that do not need a rebuild shipped.
Either the patched site live, or the rebuild in production with a fixed end date. Either way, your team shown how to edit it.
Not a promise of a percentage. Month one produces the baseline and the plan; the timeline above is what you judge the work on. Monthly work can stop any time, no notice required.
What This Typically Costs
Most of this work starts as a Checkup ($1,500 to $3,500) or a fixed-scope Fix ($6,000 to $25,000, quoted flat). Ongoing management sits inside the Standing Arrangement at $2,000 to $5,000 a month, cancel any time. Full pricing and terms →
Free Tool
Run the free 12-point audit first. Steps one and two cover how the site works on a phone and how fast it loads. Open it →
Patch or rebuild
A patch keeps the site and fixes the specific things that cost money: speed, the phone layout, the checkout or lead form, the pages that rank. A rebuild replaces it. Patching wins most of the time, and when it does not, I say so in writing with the number that justifies the bigger job.
Asked on nearly every first call
Do you design websites or just advise on them?
Both. I design and build them, and I have led platform builds at much larger scale, so a small one holds no surprises. If you already have a designer or developer you like, I can run the project and keep it on track instead.
Which platforms do you build on?
Shopify for stores; WordPress, Squarespace, Webflow, or HubSpot for service and B2B sites; and hand-built sites when speed matters most. I pick the one your team can maintain, not the one I like.
Will it work for a service business, not just a store?
Yes. Most service businesses need a site that produces quote requests and phone calls, and B2B companies need one that reassures a buyer comparing three vendors. Both are design problems before they are marketing problems.
Can my team maintain it afterward?
That is the goal. You should be able to change a headline, add a product, or edit a page without paying anyone.
What about accessibility?
Every site is built to WCAG 2.1 AA design practices and checked with an automated tool before launch. Nobody credible calls a site fully compliant, and I will not either.
Tell Me What Is Not Working
Tell me what the site does badly and what you want it to do, and I will show up to the call with real observations, not a slide deck about myself.
Mobile Traffic, Desktop Conversion
Contentsquare's 2026 benchmark, built on 99 billion sessions across 6,500 sites, puts mobile at 70 percent of visits and about 2.0 percent conversion, against 3.4 percent on desktop. The gap is rarely traffic quality. It is usually friction in the checkout.
Half a point of mobile conversion is real money at that share of traffic, which is why mobile is where I start on a rebuild.