The Blueprint · Hospitality · We win high-value clients

The website blueprint for events, functions and group hospitality.

Function and event business is a high-value enquiry, not a booking. The architecture that qualifies while it converts.

Free, no email gate, no watermark · assembled from a curated matrix, so nothing here is invented

Where this combination usually goes wrong.

Event pages hide capacity, price range and availability, so the enquiry inbox fills with mismatches. Publishing the range qualifies the enquiry before it costs anyone a phone call.

The pack below assumes the most common starting problem for this pairing: the site undersells us: it reads cheaper than we charge. Change it on the live generator.

The blueprint pack

Your blueprint pack · assembled, not generated · steal freely

Hospitality · We win high-value clients · The full site, rebuilt

01 · The positioning brief

A hospitality site is a table of contents to intent: rooms or menu, gallery, location, book. Direct booking is the whole game, so the reserve action stays pinned in view, the incentive to book direct is stated on the page, and the photography does the selling in volume.

Your revenue arrives through high-value enquiries with long sales cycles rather than the motion this industry usually runs on. The architecture below leads with a qualifying form and puts proof beside it, because one enquiry here is worth more than a thousand impressions.

When the site reads cheaper than the price list, buyers feel the gap and negotiate or leave. The brief is restraint: one typeface family used with conviction, real photography over stock, generous space, and a single signature motion idea executed calmly. Premium is what you remove, plus what you prove.

02 · The site architecture
  1. 01Hero: the room, the plate, the view

    Full-bleed photography or film. The imagery is the argument.

  2. 02Qualifying enquiry form

    Short, and it qualifies as it converts: two or three fields that tell you budget, timing or scope without reading as a screening test.

  3. 03Proof beside the ask

    Named results adjacent to the form, never quarantined on a separate page. High-value enquiries need the evidence in the same viewport as the button.

  4. 04Pinned booking action

    Book or reserve stays in view on every scroll position.

  5. 05Rooms or menu, browsable

    Photography in volume per room or dish. More imagery, more bookings.

  6. 06Direct-booking incentive

    The reason to book here and not on a platform, stated plainly near the CTA.

  7. 07Location and arrival

    Map, transport, parking. Kill the pre-visit anxiety questions.

  8. 08Guest proof

    Named reviews woven through, not quarantined in a widget.

Conversion path Impression, evidence, qualified enquiry. The form is the conversion engine; treat it like a product rather than a contact page.

  • Performance: largest contentful paint under 2.5 seconds, layout shift at zero, below-fold media lazy-loaded, modern image formats. Past three seconds the bounce cliff starts.
  • Mobile first: most visits arrive on a phone and mobile-optimised pages convert measurably higher. Design at 390 pixels, then widen.
  • Accessibility: WCAG 2.2 AA. Semantic landmarks, visible focus, 4.5:1 contrast, reduced-motion respected. It is also the cheap route to better speed scores.
  • Motion: one signature idea, executed with restraint. Reveals resolve and hold. Never hijack the scroll.
  • One primary conversion action per page, repeated. Everything else is secondary styling.
03 · The master prompt · paste it into any AI tool
You are a senior web designer and front-end engineer. Build a production-grade website for my business.

CONTEXT
Industry: Hospitality. Revenue arrives through high-value client enquiries with long sales cycles, so the site must qualify as it converts.
The current failure is perceived quality: the site undersells the price point. Design with restraint: one typeface family, real photography, generous whitespace, one calm signature motion idea, nothing decorative.
Scope: the full site. Build the homepage from the sections below, then derive interior pages from the same component system.

PAGE ARCHITECTURE (build in this exact order)
1. Hero: the room, the plate, the view: Full-bleed photography or film. The imagery is the argument.
2. Qualifying enquiry form: Short, and it qualifies as it converts: two or three fields that tell you budget, timing or scope without reading as a screening test.
3. Proof beside the ask: Named results adjacent to the form, never quarantined on a separate page. High-value enquiries need the evidence in the same viewport as the button.
4. Pinned booking action: Book or reserve stays in view on every scroll position.
5. Rooms or menu, browsable: Photography in volume per room or dish. More imagery, more bookings.
6. Direct-booking incentive: The reason to book here and not on a platform, stated plainly near the CTA.
7. Location and arrival: Map, transport, parking. Kill the pre-visit anxiety questions.
8. Guest proof: Named reviews woven through, not quarantined in a widget.

CONVERSION PATH
Impression, evidence, qualified enquiry. The form is the conversion engine; treat it like a product rather than a contact page.

NON-NEGOTIABLE STANDARDS
- Largest contentful paint under 2.5 seconds. Zero layout shift. Lazy-load all below-fold media. Modern image formats (WebP or AVIF).
- Mobile first: design at 390px wide, then scale up. Test every section at that width.
- WCAG 2.2 AA: semantic HTML landmarks, visible focus states, 4.5:1 text contrast minimum, honour prefers-reduced-motion.
- One primary call to action per page, repeated. Do not add secondary CTAs that compete with it.
- Motion: at most one signature animation idea, subtle, resolving into a held state. Never animate on scroll in a way that hijacks scrolling.
- Typography: one display face, one text face, maximum. Real hierarchy through size and weight, not colour.
- No stock-photo cliches, no carousels in the hero, no autoplaying sound.

COPY RULES
- Plain English. Short sentences. Name the buyer and the outcome in the first headline.
- Every claim sits next to its proof. If there is no proof, cut the claim.
- Write placeholder proof slots as [PROOF: description] for me to fill with real numbers and names. Do not invent statistics, testimonials or client names.

DELIVERY
Build it as a fast static site (or the framework of your choice with static output). Show me the homepage first for approval before building further. List any assumptions you made.
04 · The operating plan · how to run it after it ships
01

The Prototyper

Ideates and tests before anything is built properly. Rough pages, quick copy variants, throwaway experiments. Their job is to be wrong fast and cheap so the Builder is right the first time.

Your focus Prototype the homepage and the one money page first. The rest of the site inherits what those two prove.

02

The Builder

Ships the real thing to the standard: the architecture above, the performance budget, the accessibility bar. Takes the winning prototype and makes it production-grade, then stops. Builders who keep building past done create the mess the Sweeper inherits.

Your focus Build from a component system, not page by page. Every page assembles from known blocks so future changes take minutes.

03

The Sweeper

Prunes. Kills the sections nobody scrolls to, the pages nobody visits, the copy that hedges. Most sites fail by addition; the Sweeper is the discipline that keeps the singular message singular.

Your focus Audit quarterly: any page below meaningful traffic gets merged or killed. Fewer, stronger pages rank and convert better.

04

The Grower

Finds product-market fit for the site itself: which messages pull, which channels feed it, which pages earn traffic. Reads the numbers the Builder instrumented, feeds winners back to the Prototyper.

Your focus Map every page to a buyer question and check monthly that each page is winning its question. Gaps become the content plan.

05

The Maintainer

Keeps the ship seaworthy as it scales: dependencies, uptime, performance budgets, broken links, stale proof. Unglamorous, and the reason the site still converts in year three. Every claim on the site has an expiry date; the Maintainer enforces it.

Your focus A standing checklist run monthly: performance budget held, no broken paths, testimonials and numbers still true.

Five archetypes, not five hires. In a small business one person spans all five; the point is knowing which hat is on. Sites rot when the same person builds, grows and prunes in the same sitting without noticing the mode switch.