ProductPage Lab #1 · Comprehensive
A spectrum from "paste-replace tomorrow morning" to "ground-up rebuild over 8 weeks." Pick the direction; we build it at full fidelity from a proper brief.
This v1 is built on the brief we have, which is roughly 30% of what a final spec needs. Specifically: segments imputed (HNW UAE + Middle-Class Indian assumed); USPs imputed (claim time / WhatsApp / AED 3.5M TPL as the working three); brand voice inferred from the live page + UAE category norm.
Five numbers across these options need claims/finance sign-off before any version ships: AED 850 entry · 7 days avg claim · AED 280M paid 2025 · Munich Re reinsurance · 12,400+ Google reviews.
The meeting goal isn't "pick the final design." It's pick which path to develop — and tell us what we don't yet know.
Same page, same layout, same CMS. Just better words.
Highest-leverage low-risk change. UX team paste-replaces in Liferay in under three hours. Trust strip and FAQ schema fix the two biggest SEO/GEO weaknesses on the live page without touching the design system.
Keep every component on the page. Move them. Make the buyer-journey legible.
The page has all the right components — they're just sequenced for the org chart, not the buyer. Reordering inside the existing Liferay layout system gives a 15–25% scroll-depth improvement without redesign cost.
Whether the Liferay layout-structure-items can be reordered without re-fragmenting. If they can't, this becomes a 3-week job not 2 days.
Stop selling the product taxonomy. Start with "tell us about your car." The rest is output.
The Lifetime ROI patterns Anthony's run for 20+ years say the same thing: pages that ask for a low-commitment first action convert 2–4× better than pages that lecture. The current page lectures. This one asks.
Read access to the quote-engine API (or a price-table approximation) and confirmation that the WhatsApp number can field consumer leads in volume.
One page, two treatments. The buyer self-selects in the hero and the page rewrites itself.
HNW (high-net-worth UAE): dark, editorial, "Prestige & Agreed Value" framing. Entry from AED 8,500. Specialist callback CTA. Tone: confident, restrained, evidentiary. Trust signals: Munich Re, claims-paid volume, agreed-value cover availability.
MCI (Middle-Class Indian, UAE-resident): bright, fast, "From AED 850" framing. WhatsApp-first CTA. Tabby split-payment in hero. Tone: warm, plain, time-saving. Trust signals: claim speed, multilingual support, RTA-approved garages.
One page serving two segments well beats two pages each serving one. The Lifetime ROI Anthony has run on similar splits is consistently 35–60% higher than single-treatment pages — because the segment-aware copy compounds with the segment-aware price anchor.
The proper segment brief. Right now I have imputed segments. To ship this version we need actual data: which Emirates each segment lives in, the price elasticity by segment, which payment methods convert, which language each segment defaults to, what triggers the renewal decision, claim experience by segment. Most of this is in GIG's customer data; nobody has put it in a brief yet.
Net-new design system. World-class conversion craft. The version we'd build if we were launching GIG today.
A full conversion-led rebuild on a sane stack. Scroll-driven personalisation (the page changes based on what you've already read and how long you've been on it). Real-time pricing in the hero (no "click to get a quote" — the quote is the hero). Behavioural reveal of cover detail. Social proof from eKomi + Trustpilot + Google reviews unified. Tone: confident, direct, anti-insurance-clichés.
Done right, this is what Anthony's clients have paid him to build for 25 years. The conversion lift in our category is typically 40–80% over the existing page. The hard part isn't the design — it's the governance: brand approval, legal sign-off on YMYL claims, Liferay-vs-replatform decision, claims-team buy-in on the real numbers, voice agreement with the GIG marketing team.
Everything in this lab works because Reba + April built the Liferay fragment system, the bilingual flip, the accordion and card patterns, the brand colour application, and the component vocabulary every option here re-uses. Articulate brought structural critique and conversion-craft principles. The UX team brings the execution that actually ships into production. Each option below names what only they can do next.
Reba + April paste-replace the 9 edits, insert the trust-strip as a new fragment, ship the FAQ schema. No further Articulate involvement after sign-off.
Tests their fragment system's flexibility. The UX team's call on whether Liferay supports clean re-ordering or whether new fragments are needed.
Quote-engine integration is theirs to scope. Articulate provides the funnel logic; Reba + April own the technical plan and the Liferay-to-API contract.
Phase 2 critical path. The bilingual experience only the UX team can validate against UAE-native users. Almarai font is bundled; layout-direction work is theirs.
The hero is the highest-value real estate on every option. It currently sits at concept-level on all five versions — improvised by Articulate's design lead (Dylan) to demonstrate structure, but not properly art-directed.
John needs to lead the hero treatment for whichever direction Candace picks:
Dylan can spot the gap; John fills it. This is the hand-off line between structural critique (Articulate) and art direction (GIG's design lead).
For transparency — this is what produced what you're looking at, who did what, and what a brief would need to look like for the next iteration to be 10/10 rather than directional.
I read GIG's existing page, the brief, the KB, and the constraints. I named the conversion problems on the live page, scoped five distinct directions from "paste-replace tomorrow" to "ground-up rebuild." I directed the AI team — what to build, in what order, against what criteria — and I held the conversion logic and the buyer-segment thinking that the team applied.
I do not type HTML. I do not pick colours alone. I bring 25 years of operator-grade marketing judgement, this market for half a century, and a clear point of view about where the page is leaking conversions.
This lab is directional. To go from directional to a production-ready page, the brief would need these ten things:
The structure above is the standard. We can run this engagement at directional fidelity from a 3/10 brief (what you have now) and call that a workshop input. To ship to production we'd need 10/10 — the gaps named are the ones we'd close together before any keystroke of build code.