Journal / Weddings

Rebuilding a venue's enquiry flow without touching the design

The venue had no shortage of enquiries. It had a shortage of replies that arrived before the couple had already booked somewhere else.

A wedding venue in the south of England came to us convinced its website was the problem. The site was dated but functional, and the enquiry numbers were healthy — around forty a month in season.

Forty enquiries a month is not a website problem. It is an operations problem wearing a website costume.

We asked one question: how long between an enquiry arriving and a reply going out?

The answer was two to four days in season, because enquiries arrived at the weekend and were handled on Monday or Tuesday. By then the couple had usually heard from two other venues, and often had a site visit booked.

Nothing on the website could fix that. But the website was where the fix had to live, because it was the only part of the process the venue controlled end to end.

The gap we found

Three things, none of them visible on the homepage.

A confirmation screen that repeats the date, the guest count and what happens next — so the couple has something concrete within seconds of pressing send.

An automatic reply, written in the venue's own voice, that answers the three questions every couple asks on a first visit and links to the pages that answer them. It goes out in under a minute, at eleven at night, on a Saturday.

A queued follow-up for Tuesday morning, for anyone who has not replied, with one specific question rather than a chase.

What we built

We could have rebuilt the site. It would have looked better and it would not have changed the number that mattered, which was the time between enquiry and reply.

The pages that did change were the ones the automatic reply links to: the wet-weather option, the accommodation, the pricing shape. Those got honest answers instead of a brochure.

Why the design did not change

Time to first reply went from days to under a minute, with a human reply following inside a working day. The venue reported that site visits were better qualified — couples arrived already knowing the price shape and the date constraints, so the visit became a conversation about the day rather than a discovery call.

The design was untouched. The site looks the same today as it did before the project started.

What changed

Chase the delay before the design. Any business that answers enquiries slowly has a conversion problem that no amount of typography will solve, and the fix is usually a form confirmation, an honest automatic reply and one well-written follow-up.

It is not a redesign. It is a Saturday-night problem, and it can be solved in a week.

The general lesson

If the shape of this is familiar, the first call is a conversation rather than a pitch.

Start a project

Three things, not one

Web design is where most projects start. The other two are what clients stay for.

01

Web design

Sites that carry the place, and make the next step obvious

Design and build, from the first conversation about a place to the day it goes live — hand-written front end, real photography, motion where it carries meaning.

  • Website design and build for hospitality, heritage and culture
  • Brand systems and storefronts
  • Redesigns that keep your existing search visibility

See what a project includes

02

Forward-deployed engineering

Embedded inside your operation, not at arm’s length

Someone who sits inside your tools and your weekly rhythm, and fixes the thing in front of you rather than writing a report about it.

  • Working inside your repository, dashboard and stack
  • Internal tooling for a small team that has to move fast
  • Integrations, automation and the middle layer

How the studio works

03

AI systems

Applied narrowly, where it saves a real hour

No AI for its own sake, and none of it near copy that goes out under your name without review. Only the parts that measurably remove work from a week.

  • Enquiry triage and content pipelines
  • Comment and review monitoring
  • An eight-source opportunity radar and follow-up sequencing

How the AI layer is scoped