Skip to content

GrowthX · AARRR

How Dreamvaca grows

The engine behind the site, scored against the GrowthX framework.

Six pillars, each shown as a chain rather than a slogan: the mechanic, the exact surface it lives on, the metric that would prove it works, and the number we are aiming at. A growth claim you cannot trace to a screen is a claim you cannot hold anyone to.

North Star metric

Booked travellers per week

Travellers, not bookings — a family of four is four people served and four people who can refer. The three inputs that move it: planner starts, priced itineraries, and the share of those that convert without a human touching the trip.

Overall design score

9.7/10

Mean of the six pillars below

Time to first price

Under 90s

Before any sign-up — the activation moment

Referral coefficient

k > 0.4

Shareable itinerary plus split payment

Indexable pages

180

Two languages, separate URLs, hreflang pair

The scorecard

Six pillars, at a glance

The score rates the design of the mechanic and whether it is wired into a real surface on this site — not a reported result.

Acquisition

Distribution the traveller does for us

Design score10/10

Every itinerary that leaves the site carries the site with it. The PDF and the WhatsApp quote are branded and deep-linked back to the priced trip, so the family group chat where the holiday is actually decided is also the channel that acquires the next three visitors — permissionless distribution, paid for by nobody. Underneath it, two languages on separate indexable URLs double the surface area, and the destination guides and visa pages answer the questions people ask months before they are ready to buy anything.

Where it lives in the productThe metric that proves itTarget
Branded itinerary PDF and WhatsApp quote, deep-linked to the priced tripSessions per share1.8
/en and /gu on every route, with an hreflang pairOrganic sessions that start a planner35% of organic sessions
/guide/[country] and /visa/[country] — the top-of-funnel content engineGuide readers returning within 30 days25%
/packages — filter state lives in the URL, so a search is shareableSessions arriving on a filtered URL12%

Activation

A real price on screen in under 90 seconds

Design score10/10

Aha is not a sign-up. It is a priced, personalised, day-by-day itinerary on screen — before any account, any phone number, any callback. Nothing on the path to that moment asks the visitor to identify themselves, because every field between a visitor and a price is a field that loses them. This is the single sharpest break from the incumbents, where the real number only appears after you have surrendered a phone number and waited a day.

Where it lives in the productThe metric that proves itTarget
/plan — five questions, no account, no login wallVisitors reaching a priced itinerary in the first session45%
/concierge — a natural-language brief, priced by the checkout engineMedian time to first priceUnder 90 seconds
/packages — all-in price per person on the card, breakdown open on detailListing → detail rate30%
Live recompute when nights, hotel tier or a city changesItineraries edited before booking60%

Retention

Reasons to come back that are not a discount

Design score9/10

A holiday is a once- or twice-a-year purchase, so retention here cannot mean weekly logins — that metric would be a lie in this category. It means being the place the trip lives: saved trips found by reference and mobile number with no password to forget, a price-drop watch on the trips someone actually considered, and a re-book prompt timed to that traveller’s own seasonal window rather than to our campaign calendar.

Where it lives in the productThe metric that proves itTarget
/my-booking — reference plus mobile, no login wallReturn visits within 30 days of booking40%
Saved trips and watched packagesVisitors holding at least one saved trip20%
Price-drop alert on a watched package, over WhatsApp and emailAlert → session → booking6%
Post-trip re-book prompt at the next seasonal window12-month repeat purchase rate22%

Engagement

Useful long before you are ready to pay

Design score10/10

The Concierge is a returning surface, not a one-shot chatbot: it holds the trip in progress and will answer a visa question from someone with no intention of buying today. Around it sit tools with genuine standalone utility — month-by-month weather, three daily budget bands, visa fees and processing times — and that is what earns visits in the long gap between purchases, in both languages.

Where it lives in the productThe metric that proves itTarget
Docked Concierge on every route, in both languagesConversations per active visitor per month2.4
/guide — month-by-month weather and three daily budget bandsSessions touching two or more tool pages30%
/visa — fee, processing days, entry type, document checklistVisa page views per eventual booker1.7
An editable itinerary that survives the sessionReturn rate to an unfinished itinerary35%

Referral

Travel is already a group decision

Design score9/10

Nobody books a family holiday alone, so the loop is built into the artefact rather than bolted on as a widget. The itinerary is the shareable object. Group bookings split payment across travellers, so every payer becomes an account of their own. And the double-sided credit pays out on the referred trip rather than on the sign-up, so the incentive tracks revenue instead of email addresses.

Where it lives in the productThe metric that proves itTarget
Share an itinerary — WhatsApp, PDF or linkShares per priced itinerary0.9
Group booking with split payment linksNew payer accounts per group booking2.1
Double-sided credit, released on the referred tripReferred bookings as a share of all bookings15%
The loop as a wholek factork > 0.4

Monetisation

One engine, four ways to earn

Design score10/10

A single pricing module prices the card, the planner, the Concierge and the checkout, so the chat can never quote a number the checkout will not honour. On top of that sit four stacked streams: 25% packaging margin in either markup or true-margin mode, ancillary attach at checkout, seasonal yield through each departure’s price factor, and a mix deliberately weighted towards packages — because commodity flights carry almost no margin at all, which is exactly why the incumbents built their businesses on them and then had to sell holidays anyway.

Where it lives in the productThe metric that proves itTarget
lib/pricing.ts — one engine, both margin modesRealised take as a share of selling price20% in markup mode
/book — visa, insurance, transfers and seats at checkoutAncillary attach rate35% of bookings
Departure price factor — seasonal yieldShoulder-season share of departures sold+8 points
A package-weighted mix over commodity flightsNet revenue from packages80%
Read this before quoting a number
Every figure on this page is a design target for a demonstration build. There is no live traffic behind it, no cohort has been observed, and nothing here should be read or repeated as a reported result. The scores rate how well each mechanic is designed and whether it is wired into a real surface — that is all they claim.