Morphos / Journal

The questions couples ask before they call

A couple is not browsing. They are eliminating. The site's job is to survive the shortlist, not to win the visit.

By the time a couple looks at your site, they have already seen a dozen. They are not arriving to be impressed — they are arriving to cross you off, quickly, and only if you survive that do they start imagining the day.

The elimination questions, in order

The first three are answered in seconds or the venue is gone.

What has to be answered immediately

Then, and only then, the story

Once a couple has established that the venue fits, they will read everything: the history, the food, the grounds, the actual weddings. This is where the photography and the writing earn their place — but they only get read by couples who survived the numbers.

Where venues put things versus where they work

What couples needWhere most venues put itWhere it belongs
CapacityA PDF or an email replyThe first screen, plainly stated
AvailabilityA phone numberA date check or an honest "enquire and we will reply today"
A wedding set-up photoPage four, after the empty ballroomImmediately after capacity
Price indicationNowhereA range, or a clear explanation of what changes it
The storyThe heroAfter the numbers have qualified them

The form, specifically

Ask for the date, the guest number and one sentence from the couple. That single sentence tells the venue more than any dropdown, and it lets the first reply be specific — which is the difference between a reply and a brochure.

The question behind the question

Almost every enquiry a venue receives is really asking something else. 'Can we bring our own caterer?' is usually 'will this feel like our wedding or yours'. 'Is the date available?' is 'are we too late'. 'How many can you seat?' is 'will our family fit and still feel intimate'.

Answering the literal question is table stakes. Answering the one behind it is what makes a venue feel understood before the first site visit — and it is a copy problem, not a design one.

The practical move is to write the FAQ from the site-visit transcript rather than from the sales sheet. The questions people actually ask when they are standing in the room are different from the ones the venue thinks it needs to answer on a website, and they are more useful.

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