VowOne wedding. Two countries. Every detail.

Couples juggle Instagram DMs, Pinterest boards, vendor email threads, family group chats, four spreadsheets, and international bank transfers — then self-plan 80% of the work themselves. Every existing tool is a catalogue, not a collaborator. Three findings shaped the strategy:

Twelve 30-minute interviews across UAE, UK, Canada, Brazil, Japan, France, and Egypt. Teardowns of Zafaf, Bridebook, The Knot, and Zola. Shadowed two Dubai and London coordinators through a live nikah-plus-civil-ceremony weekend.

Three archetypes crystallised. They look different; they ask the same kinds of questions.

The shape of the questions they ask — not structural, but situational:

• "Is this quote reasonable for Lake Como in September?"
• "What documents do I need to legalise a nikah in France?"
• "Am I on budget when half my vendors are in EUR and half in SAR?"

Vow is built on a single thesis: an LLM in the loop changes what a planning app can be. Not an "AI feature" on a checklist — a different product category. The couple is the decision-maker; the app is the analyst. Six capabilities carry the weight, each with a cultural use case built in.

Mapped from 12 interviews across 7 countries and 18 months of self-planning a test wedding. Each stage shows the same job-to-be-done in two worlds — what couples do today, and what the same step looks like inside Vow.

Five stages, same job-to-be-done. The shift Vow is built around: from coordinating five tools to inhabiting one.

37% of US couples hired a planner in 2023, up from 29% in 2022 (The Knot 2025). Cross-cultural and destination weddings — Vow's target — almost always require professional coordinators. The existing tools (Aisle Planner, HoneyBook, Dubsado) weren't built for multi-country, multi-ceremony, cross-cultural work. The Planner Portal turns Vow into a B2B2C flywheel: planners bring their couples onto Vow; couples keep planners inside one unified workspace.

Three configurable access levels

Couples pick from three presets. Any payment action — deposit, final payment, FX transfer — always routes to the couple for approval. Non-negotiable, enforced at the database level, not the UI.

Real-time collaboration + planner AI

Monetisation

Couples get planner collaboration free — it's a growth lever. Planners pay for the CRM.

Two additional revenue lines: 8% marketplace referral on a planner's first contract when a couple hires through the Vow Planner Marketplace (no ongoing commission), and a templates marketplace where planners sell reusable checklists and timelines for SAR 50–200 / $15–60, Vow taking 20%.

Every design choice traced back to a cultural or structural finding. These were the calls that shaped the product most.

Following IDEO's four-ring framework: couples at the centre, vendors and payment rails in the next ring, cultural and legal SMEs beyond them, and the sponsors that clear the regulatory runway. Every ring shapes a different surface in the product.

Vow followed the same IDEO loop as Atlas. The six phases shaped what to research, what to build, and what to test — and the Iceberg Model kept the team honest about what the pain actually was underneath the behaviour.

The Iceberg Model. What looks like a WhatsApp folder and nine tabs is a surface symptom. The pain is deeper.

Vow is being stress-tested against a realistic scenario — a test wedding with a real vendor list and a family spanning four countries. What I've learned so far:

• The concierge makes everything else make sense. Without it, Vow is a prettier spreadsheet. With it, Vow is a different product category.
• Multi-currency isn't optional. Every cross-cultural couple stress-tested it within minutes of opening the prototype.
• The parsed-email chips save ~15 minutes per vendor reply — the ambient time-tax that makes wedding planning feel endless.