Porting hyattinclusivecollection.com onto the platform that already runs resortsbyhyatt.com.
PlatformVoix
Already live onresortsbyhyatt.com
Scopehyattinclusivecollection.com
GoalIncrease conversion
StructurePurpose · Means · Results · Cost
Prepared for Hyatt Inclusive CollectionLogicbomb Media
00 The premise
The platform is already proven.
resortsbyhyatt.com runs on Voix today. This brief is about bringing hyattinclusivecollection.com onto the same system.
Same CMS, same admin, one team. Nothing here is a bet on new technology. It is a port onto a platform Hyatt already runs in production. The risk of "will it work" is off the table. What is left is the work of making the Inclusive Collection convert better.
A port, not an experiment02
01 Purpose
The one goal
Increase conversion.
Every change in this brief earns more booked stays from the traffic you already have.
Guests find what they came forThe right resort surfaces fast, not after ten clicks.
Experiences segmented to how they travelCouples, families, and wellness guests each see their version.
The product lineup made clearEleven brands, explained in plain terms at the moment of choice.
A booking flow with nothing in the wayNo broken imagery, no busy pages between the guest and the reservation.
One goal, four levers03
01.1 Where conversion leaks
Eleven brands. Three ways to travel. One guest deciding fast.
The Inclusive Collection spans eleven brands plus independent properties, across adults-only, family, and wellness.
Secrets, Dreams, Breathless, Zoetry, Ziva, Zilara, Vivid, and the rest each mean something specific. A first-time guest has to learn that vocabulary before they can book with confidence. When the site makes them do that work, some of them leave. Broken imagery and busy pages add friction at the exact moment the decision is made. That leak is what we close.
The gap between traffic and booking04
02 Means · discovery and conversion
Drives conversion
Get guests to the right resort, faster.
AI-aligned contextual searchResults that understand intent. "Adults-only in Cancun with a swim-up suite" returns exactly that.
Real findabilityBrowse and filter by how people actually decide: audience, vibe, destination, amenities.
Segmented experiencesThe site adapts to preference, so each guest sees the version that fits them.
Product clarityThe eleven brands made easy to tell apart, right where the guest is choosing.
Cleaner UI and UXLess busy. The path to book stays in front of the guest, not buried.
No broken imageryMedia managed in Voix. What renders in preview renders in production.
Means · discovery and conversion05
02.1 Means · publishing and the proof layer
Drives output and assurance
A small team that ships like a big one.
A publishing experience built for speedEditors change any screen or content without a developer. Smaller teams do more.
Nightly SEO and GEO checksContent graded for search and generative answer engines every night, with fixes surfaced.
Nightly performance checksCore Web Vitals watched every night. Regressions get caught before guests feel them.
Advanced analytics, built inFalloff and user flow visible in the platform, without bolting on a third tool.
The proof layer
Session playback to watch real guests move through the flow, and heatmaps on every page to see what earns attention and what gets skipped. This is how we find the falloff and fix it.
Means · publishing and the proof layer06
03 Results
We set the number together, then we hit it.
No vanity metrics. One agreed baseline, one growth target, for every Inclusive Collection property.
This happens at the very start, in the planning phase. First we baseline today's conversion across the portfolio. Then we agree a growth target we both sign. Then we commit to reaching it for all HIC properties inside the roadmap. The nightly checks and the proof layer are how we show the line moving, not just claim it.
You will always know where the number stands.
That is why we build the measurement layer first. Growth you can see is growth you can defend.
Baseline, target, commitment07
04 Timeline
August to launch, then we tune it live.
Aug 2026
Planning
Agree final structure and establish conversion goals. Assets blended from resortsbyplaya.com.
Aug-Sep
Infrastructure
Meet with IT to lock final infrastructure.
Nov 1
Prototype
Working prototype for internal review.
Nov-Jan
Booking & graphics
Booking engine and final graphics built out.
Jan 15
Certification
Booking engine and graphics done, into certification.
Feb 2027
Launch
New site goes live.
Feb-Apr
Tune on metrics
Heavy attention on tweaks as the numbers roll in.
May 2027 →
Taper
Hours step back as performance stabilizes.
Planning comes first, on purpose
We settle the site structure, the asset pipeline from resortsbyplaya.com, and the infrastructure with IT before a line of the new site gets built. That is what keeps Nov 1 and the February launch real.
Delivery calendar08
04.1 The retainer
Raise the retainer to 210 hours.
210hrs / mo
210 hours a month for roughly nine months, August through the post-launch tuning window in April, where the work is heaviest. Once the site is live and stable and your team is publishing on their own, hours taper toward about 140, adjusted to demand. Planning, build, launch, and the tuning window are all inside this level. We reassess from there.
Front-loaded now, tapers as the site stabilizes09
05 Infrastructure
It lives wherever Hyatt needs it to.
We work hand in hand with your IT team, and have for years. The final product runs on the cloud Hyatt already trusts.
Fully supported. Deployed and running today.
Fully supported. Ready when it is the right call.
Azure
Fully supported. No compromise either way.
We plan this with Lior Collins and your IT team
The same working relationship we have relied on for years. We settle infrastructure together in the planning phase, so wherever the final product lives, it works for Hyatt.
Cloud-agnostic, decided with IT10
06 Why this is low risk
You have already seen it work.
HIC on Voix
Rebuild elsewhere
The platform
✓Proven on resortsbyhyatt.com today
Unproven, built to spec
The team
✓Already knows the stack and the brand
Procurement, ramp-up, discovery
Publishing
✓Editors ship without a developer
A ticket queue to a vendor
Measurement
✓Playback, heatmaps, nightly checks
Bolt-on tools at extra cost
Performance
✓We convert, and prove it every night
Slow pages, found in production
Timeline
✓Migrate onto a running system
Build the system first
The nature of it
✓A port
A bet
Why this is low risk11
07 Next steps
From yes to moving.
Approve the retainer at 210Eight months at the migration rate, then it steps down.
Grant analytics and site accessWe need it to baseline conversion. The sooner it lands, the sooner the number is real.
We baseline, then we buildAgree the target, port onto Voix, and start moving the line.
Let's port it onto what already works.
Logicbomb Media · for Hyatt Inclusive Collection12