SPOSAI · 2026
I designed the guest experience for our own destination wedding.
Every page our 103 guests saw, from the RSVP to the registry, designed and built by me.
01 / MY ROLE
I owned everything our guests saw.
02 / THE PROBLEM
Existing wedding tools managed the pieces but not the overall experience.
We reviewed the tools out there. Each one handled the admin side or the guest site, never both well.
03 / THE INSIGHT
Planning a wedding isn’t one workflow. It’s dozens happening all at once.
BEFORE THE TRIP
Where am I staying?
How do I get there?
What should I wear?
DURING THE WEDDING
Where do I need to be?
When do I need to be there?
How am I getting there?
WHEN PLANS CHANGE
Where’s the latest information?
Has anything changed?
What do I need to do?
The goal was simple: guests should always know what to expect, where to go, and when to be there — without having to ask the couple.
04 / DESIGN DIRECTION
Our guests didn’t need the planning chaos. They needed to feel guided and cared for.
CLEAR AND GUIDED
The right information, at the right time.
PART OF THE EXPERIENCE
An experience that feels like the couple, not a template.
PERSONAL BY DESIGN
The celebration begins before guests arrive.
05 / THE RSVP
One RSVP for a three-day weekend.
61 of the 79 guests who came RSVP’d here themselves. We recorded the rest for relatives without internet access.
06 / THE REGISTRY
Giving a gift should feel as considered as the rest of the celebration.
Built into the wedding site, not a separate registry: amount, card, note, review, then a Stripe checkout.
07 / TRAVEL AND SCHEDULE
Making a three-day wedding easy to follow.
Day → Time → Event → Location → Essential details
08 / CONNECTED LOGISTICS
One system. The right information in the right place.
Each pair shows the admin data behind the scenes and the guest view I designed from it. The dashboard is Cyrus’s design.
ACCOMMODATION
Room assignments and stay logistics are managed behind the scenes, while guests see only what they need to plan their stay.
TRANSPORTATION
Transportation is managed behind the scenes, while guests see the routes, pickup times, and instructions relevant to them.
MULTI-DAY EVENTS
Events are managed in one place, while guests see a clear, up-to-date timeline of the wedding weekend.
09 / HOW I BUILT IT
I designed and built the guest site with Claude Code.
INFORMATION ARCHITECTURE
Each page answers one guest question: where, when, or what to wear.
TWO FLOWS
Type, palette and spacing set like the invitation itself, not a template.
VISUAL SYSTEM
RSVP and registry: one question per step, with a review before anything is sent.
10 / OUTCOME
From a personal planning problem to a product used in the real world.
Sposai was built around our own destination wedding, giving us the opportunity to use the product end-to-end throughout a real three-day celebration, not a simulated scenario.
103 GUESTS INVITED, 79 ATTENDED
A three-day destination wedding in Puglia, July 2026.
100% RSVP RESPONSE RATE
Every invitation answered, nothing left pending. Most guests RSVP’d themselves; we recorded the rest for relatives offline.
Guests, events, accommodation, transportation, RSVPs, and the wedding website were all managed in one system.
END-TO-END USE
BEYOND OUR WEDDING
Sposai is now in beta with four more couples, each at a different stage of planning.
Our wedding · Puglia, Italy · July 2026
11 / REFLECTION
Designing beyond individual screens.
The biggest shift in my thinking was learning to design the connection between systems and experiences, not just the screens in between.
NEXT CASE STUDY — SPOSAI LANDING PAGE
Making a complex product easier to understand.
How I approached the information architecture, hierarchy, and visual storytelling for Sposai’s landing page to communicate a product that serves different users and wedding types without overwhelming them.
