This is the module to show people who ask "why not just use Squarespace?" A small interactive quiz on the homepage — pick your group size, pick your experience level, get an instant room recommendation — is the kind of feature that's a natural afternoon's work on Next.js and a genuine fight on a drag‑and‑drop builder. It also does real conversion work: it turns "there are four rooms and I don't know which one" (a reason to leave and think about it) into "they told me to book Operation Beehive" (a reason to book now).
1. What this feature is for
Kill choice paralysis. An undecided visitor is a visitor who closes the tab "to decide later." Two taps and a confident recommendation keeps them moving toward a booking instead of stalling on the room list.
2. How it works (the anatomy)
It's deliberately tiny — two questions, no forms, no page reloads:
- A short prompt — "Not sure where to start? Help me choose a room."
- Question 1: How big is your group? — 2–3 / 4–6 / 7 or more.
- Question 2: How much escape‑room experience? — First‑timers / Done a few / Experienced.
- The result — the moment both are chosen, a recommended room appears instantly with a one‑line reason and a Book button. No "submit," no waiting.
The recommendation logic is simple and editable — a small set of rules mapping the two answers to a room. For example: first‑timers in a small group are pointed to the most welcoming room; experienced players are sent to the hardest; large groups are routed to the room that runs as two head‑to‑head spaces. You can tune these rules in minutes as you learn what actually suits each group.
Two questions, no form: pick group size and experience.
Both answers chosen — the recommended room appears instantly, with a Book button.
3. Imagery & media
Almost none — and that's the point. The widget is UI, not photography: accent‑coloured buttons, clear type, maybe the recommended room's small card image in the result. Keep it clean so the interaction is the hero, not decoration.
4. The show‑off feature (this whole module is the show‑off)
Why this is easy here and hard elsewhere:
- Instant, no‑reload interactivity. The widget holds the two answers in memory and updates the result the instant both are chosen. On a static builder you'd be bolting on a clunky third‑party form or an embed that reloads; here it's a small, self‑contained interactive component that lives right in the page.
- Editable logic in plain code. The "which answer → which room" rules are a few readable lines. Changing the recommendation is a one‑line edit, shipped in seconds — not a support ticket to a plugin vendor.
- It's fast and free. No external service, no extra load, no monthly plugin fee. It's part of your site.
- It composes with everything else. The result's Book button is the same booking action used everywhere, so a recommendation flows straight into the same booking path.
This is the clearest example in the series of the stack's core advantage: custom interactive ideas are cheap. If you can describe the behaviour, Claude‑Code can build it as a native part of the page.
5. Copy & SEO notes
Keep the questions in plain, friendly language ("How big is your group?"). The widget isn't an SEO asset itself, but it lifts the whole page by reducing bounce and increasing clicks to room and booking pages — engagement signals that indirectly help.
6. How I built it
- Claude‑Chat proposed the two‑axis quiz (group size × experience) as the antidote to choice paralysis and sketched the recommendation rules.
- Claude‑Design styled it into the homepage mockup — the prompt, the two rows of choice buttons, the result card.
- Claude‑Code built it as a small interactive component holding the two answers and rendering the matched room instantly, and wired the result's Book button to the standard booking path.
- Later, a quick tweak through Claude‑Code changed which room first‑timers get recommended — a one‑line logic change, committed and live in under a minute. That speed of iteration is the feature.
7. The principle
The best conversion features are often small, custom interactions that a generic builder can't quite do. Don't reach for a bloated plugin — describe the behaviour you want and build it natively. A two‑tap "which room?" helper is worth more than a dozen paragraphs of "our rooms are great," because it does the visitor's hardest job for them.