01 — SPOSAI
I designed the end-to-end guest experience for a wedding platform born from planning our own.
My focus was the guest-facing experience — turning RSVPs, travel, events, and changing logistics into one clear, personal experience for every guest.
02 — PROJECT OVERVIEW
From firsthand frustration to a shipped product.
ROLE
Product Designer · Founding Team
FOCUS
Guest-Facing Experience · Product Design · Web Design
TIMELINE
2025 - 2026
STATUS
Shipped · 2026
Sposai was built by a two-person product team. I owned the guest-facing experience and visual direction, while my co-founder led the admin dashboard and system architecture. Together, we connected the planning and guest experiences into a single product.
03 — THE PROBLEM
Existing wedding tools managed the pieces but not the overall experience.
While planning our destination wedding, information lived across spreadsheets, vendor conversations, booking details, and separate guest communications. For us, that meant constantly reconciling changes. For our guests, it meant relying on us to find the information they needed.
The problem wasn’t a lack of tools. It was that none of them worked together.
04 — THE INSIGHT
Planning a wedding isn’t one workflow. It’s dozens happening all at once.
Planning our own destination wedding showed me that guests experience complexity differently from the couple planning it. They don't need access to every decision behind the scenes; they need clarity about what affects them.
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.
05 — THE DESIGN DIRECTION
Our guests didn’t need the planning chaos. They needed to feel guided and cared for.
I wanted every page to answer a real question while still feeling like a warm welcome — clear enough to guide guests and personal enough to feel like an extension of our celebration.
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.
06 — THE EXPERIENCE
One system behind the scenes. One seamless experience for our guests.
One place for guests to RSVP, navigate the weekend, plan their travel and accommodation, access the registry, and stay connected to the celebration from arrival to departure.
07 — THE REGISTRY EXPERIENCE
Giving a gift should feel as considered as the rest of the celebration.
Rather than sending our guests to a separate registry website, I designed the gifting experience directly into the wedding website.
The flow guides guests from choosing a gift amount to selecting a digital card and adding a personal message (with suggested messages available when needed) before reviewing their gift and completing checkout through our Stripe integration.
08 — DESIGNING THE SYSTEM
Different weddings need different workflows.
A local wedding and a multi-day destination wedding don't require the same level of planning. We built Sposai around a shared foundation, adding travel and logistics only when they're needed.
LOCAL WEDDING
Guests · Budget · Vendors · Timeline · RSVPs · Website
DESTINATION WEDDING
Everything in a local wedding, plus:
Travel · Accommodation · Transportation · Multi-day events
The result: complexity appears only when it’s useful.
09 — INFORMATION HIERARCHY
Making a three-day wedding easy to follow.
A destination wedding gives guests a lot to keep track of: events, transportation, locations, and free time across several days. I organized the schedule as a chronological timeline so guests could quickly understand what was happening, when it was happening, and where they needed to be.
Day → Time → Event → Location → Essential details
10 — CONNECTED LOGISTICS
One system. The right information in the right place.
Sposai keeps planning and guest communication connected without exposing the complexity behind the scenes. Accommodation, transportation, and event details are managed in one system, while guests see only the information relevant to their experience.
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.
11 — 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 managed through Sposai.
100% RSVP RESPONSE RATE
Guest responses collected and managed directly through the platform.
Guests, events, accommodation, transportation, RSVPs, and the wedding website were all managed in one system.
END-TO-END USE
BEYOND OUR WEDDING
After our wedding, Sposai moved into beta testing with four additional couples, allowing us to validate the product beyond the use case it was originally designed around.
Our wedding · Puglia, Italy · July 2026
12 — REFLECTION
Designing beyond individual screens.
Sposai pushed me to think beyond individual features and consider how decisions across a product connect. Designing the guest experience meant understanding how planning decisions behind the scenes would ultimately shape what guests saw and needed throughout the wedding.
Working on a real product also meant designing within constraints, adapting as requirements evolved, and making decisions that could scale beyond our own wedding.
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.
