Built around one outcome
Every page has a single job: get the enquiry. Structure, copy order and button placement all follow from that, not from a template.
Available for freelance projects in the US
I help US businesses turn slow, dated websites into fast, mobile-first pages that move a visitor towards a booked call, a form or a sale — not just a nicer looking homepage.
About
Most of the work I do starts with the same complaint: the website is not bringing in enough business. Sometimes the page is too slow on a phone. Sometimes the enquiry button is buried three screens down. Sometimes there is no website at all — just a Facebook page and a phone number.
I work in writing and asynchronously, because it fits a different time zone and because it leaves a record you can check later. Every build starts mobile-first, with a page-weight and load-time target agreed before the first line of code: if a later change makes the page heavier for no gain, it does not go in.
You get plain-language updates at each milestone, working software early — something you can click on in week one, not month two — and no surprises at handover. The code and the domain stay yours.
Every page has a single job: get the enquiry. Structure, copy order and button placement all follow from that, not from a template.
Most local US traffic is a phone on cellular data. That is the case I design and test against first — desktop is the easy part.
A page-weight and load-time target is agreed up front and measured before launch. Speed is a requirement, not a nice-to-have to fix later.
No lock-in and no proprietary builder. You own the domain, the hosting account and the code, and you can hand it to any developer later.
Services
I would rather do three things properly than twenty adequately. If your project is outside these three, I will say so and point you elsewhere.
One page, one goal, built for paid traffic and local search. Fast on a phone, with the enquiry path visible without scrolling and a form that works even when the visitor is in a hurry.
Custom tools for work that is still running on paper, spreadsheets or WhatsApp messages: bookings, job tracking, internal approvals, simple client portals.
For a site that still looks like 2014 and behaves like it. I keep what already works and earns traffic, and rebuild the parts that cost you visitors — starting with whatever is measurably broken.
Work
The mockups below are original concept prototypes — the kind of layout, structure and enquiry path I build. They are labelled as concepts because that is what they are; client projects are added here only with permission, and never with a result I cannot point to.
The problem: a single-location contractor buying local ads, sending that traffic to a homepage with a phone number in the footer. Mobile visitors were leaving before the number loaded.
What the build does: one page for one service, the number and the form above the fold, service areas and proof underneath, and a page weight small enough to open on a weak signal.
Before
After
The problem: eleven pages, none of them answering the visitor's actual question, and a mobile layout that scrolled sideways. The owner wanted to keep the content and lose the weight.
What the build does: keeps the pages that earn search traffic and redirects the rest, rebuilds the layout mobile-first, replaces the image sliders with static optimised images, and puts one clear call to action on every screen.
The problem: a small service team tracking jobs across a whiteboard, a spreadsheet and a group chat. Nobody could answer "what is still open today?" without asking three people.
What the build does: one screen that answers that question — jobs by status, assigned to whom, what is overdue — and works on the phone of the person standing in a driveway.
The problem: a salon taking bookings only by phone during opening hours — which is exactly when the staff are too busy to answer it.
What the build does: three taps from landing to a confirmed slot, no account required, with the available times loaded from the business's real calendar rather than a static list.
Tech stack
No percentages, no skill bars. A bar that says "96%" measures nothing. What matters is which tool fits the job — so here is what I reach for, and what it is for.
Process
Four steps, in writing, so you always know where the project stands without needing a meeting to find out.
A short conversation about the goal, then a written scope: what is being built, what it costs and what "done" means. No surprises later.
You see a working version quickly — a real page on a real URL, not a picture of one. Feedback at this stage is cheap; feedback at the end is not.
I build it mobile-first, then measure: page weight, load time, layout at every screen width, and the path from visit to enquiry.
The site goes live on your domain and hosting, and you get the code, the accounts and a plain-language summary of how it all fits together.
Contact
Open for freelance projects in the US. Describe the problem in a few lines — what the site should be doing and what it does instead — and I will reply with an honest read on whether I am the right person for it.
If a form feels like too much, write to me directly. A sentence about the problem and a link to the current site is enough to start.