Websites · The front door

Websites stop at the enquiry. Mine don’t.

When an enquiry lands, something has to happen to it: a record created, a reply sent, a slot held. I build the front door and the system behind it in one go, so the enquiry that arrives at 9pm is recorded, answered and offered a booking before you’ve picked up your phone. A website is one service here, not the whole business.

Book a 20-minute call See how I build →

20 minutes. You leave with a clear view of what to build first, whether you hire me or not.

Two websites, one difference

Both look fine. Only one does anything.

Design gets the credit, but the difference that pays is invisible: what happens in the minute after someone fills in the form.

A site that captures an enquiry and stops

The enquiry lands in an inbox and waits its turn
No record of who asked, when, or what they wanted
Follow-up depends on somebody remembering
The 9pm enquiry sits unanswered until morning
The first sign it isn’t working is a quiet phone

A site that starts the workflow

The enquiry becomes a record the moment it’s submitted
Your CRM knows who asked, from where, and about what
Follow-up goes out within the minute, automatically
An assistant answers and qualifies at 9pm, not 11am
You see the whole funnel, from visit to booked job

The first sixty seconds

What happens after someone enquires.

This is what I wire in behind the front door. Nobody has to notice it, remember it or forward anything.

01

Enquiry in

Form, assistant or WhatsApp. The details arrive structured: name, contact, what they need, where they came from.
02

Record created

Straight into the CRM you already run, or the one I build you. Nothing lives in an inbox.
03

Reply sent

An acknowledgement goes out from your own domain within the minute, and the follow-up sequence is queued behind it.
04

Booking offered

Real slots from your real calendar, confirmed and reminded automatically. Not “we’ll get back to you”.
05

You see all of it

Analytics across the whole funnel: visit, enquiry, follow-up, booked job. You learn which source pays from data, not gut feel.

Included in every build

The connections are standard, not extras.

Most web projects sell you pages and treat the plumbing as an upgrade. Here the plumbing is the point.

Enquiries routed into a CRM

Every enquiry creates a record with a source and a history. In the CRM you already use, or the one I build you.

Follow-up from first contact

Acknowledgement, reminders and the chase sequence run automatically, so no lead dies waiting for a reply.

An assistant briefed on your business

Like the one running on this page: it answers real questions, qualifies the enquiry and routes it. Not a canned widget.

Booking wired to your calendar

Visitors book real slots in your real diary. Confirmations and reminders go out without you touching anything.

Analytics across the whole funnel

Not just page views. You see the journey from visit to enquiry to booked job, and which source actually earns.

Hooks for what comes next

Every build leaves clean connection points for the next automation, so the system can grow without a rebuild.

And the craft underneath it

Designed from a blank page around your customers, not a theme
Fast and light, built mobile-first and tested on real phones
Copy written to convert, with every line earning its place

A proper SEO foundation: clean structure, honest meta, speed
Full handover docs and a walkthrough at launch
You own everything that gets built

An honest sorting

Sometimes the front door really is the problem.

Part of the job is telling you when it isn’t. Websites are one service here, and I’d rather point you at the right build than sell you the wrong one.

Start here when

Your site is slow, dated or broken on a phone
Visitors can’t book, so they call, hit voicemail, and try the next name on the list
Enquiries from the site arrive somewhere nobody owns
You’re invisible on the searches that should find you

Start elsewhere when

Enquiries arrive fine and die in the inbox afterwards: that’s automation, not design
Your records live in four places and none of them agree: that’s a systems problem
Answering speed is the bottleneck, not attention: an assistant fixes more than a redesign

Process & AI automation → Custom CRMs & internal tools →

Cutting Edge Hair Salon homepage with the booking flow in view

Live client project

The front door I’ll show you first.

Cutting Edge Hair Salon is the one client build that’s live today. I hand-coded the replacement around the thing that pays the bills: the booking enquiry. The pages answer what clients actually ring up to ask, and there is a clear path to book on every screen.

It is also the honest version of the argument on this page. That salon takes its work by phone, so I built for the phone and turned down the online booking system, the CMS and the chatbot. I gave them a front door and left everything behind it manual. Today I’d wire the follow-up in on day one, and the case study says so in those words.

See it running at cuttingedgehairsalon.co.uk.

Read the full case study →

Start a project

If the front door is the problem, start there.

Every build is scoped and priced individually, because it depends on what your workflow actually needs. The discovery call is where that gets nailed down, and you get a fixed written price before any work starts.