ENES
One conversation
Agents/LuckyClient agent · Wedding planning

Lucky

A destination wedding planner's whole office, rebuilt around how she actually plans. It took us more than one try, and that is the point.

ClientUnique Cabo Weddings
IndustryDestination weddings, Los Cabos
StartedSpring 2026, with their website
What it isUniqueOS and Lucky, their agent
[ 01 ] HOW IT STARTED

It started with a website.

Our work with Unique Cabo Weddings began the way a lot of our relationships do: a new website for a planner who had been doing this a long time and deserved a site that looked like it.

Spending time inside the business to build that site showed us the real job. A destination wedding is hundreds of moving parts: couples in another country, guest lists that change by the day, venues, florists, photographers, shuttles, timelines and contracts. Most of it lived in inboxes, folders and one person's head.

[ 02 ] WHAT WE BUILT FIRST

Then we built too much.

Our first operating system for them was ambitious. It synced everything, modelled everything and tried to be everything. It was also built on the wrong premise: it asked a planner to work the way the software wanted.

So we broke it down. Then we rebuilt it, and broke parts of it again. Each pass taught us something about how a wedding actually gets planned, and each one got smaller, simpler and closer to her.

We'd rather rebuild three times than hand someone a system they have to fight.

[ 03 ] HOW LONG IT TOOK

Months of learning, then days of building.

  1. Spring 2026A new website for the business, and the first conversations about the work behind it.
  2. Summer 2026The first operating system. Too big, built around the software instead of the planner. We stepped back.
  3. Early SeptemberRebuilt from scratch as UniqueOS: weddings, couples, vendors and venues in one simple web app, live in a matter of days.
  4. Late SeptemberA public catalog for their decor rental, and Lucky's own rulebook so the agent works the way the team does.
  5. OctoberA daily log so nothing said in a conversation is lost, and the system keeps growing with them.
[ 04 ] WHAT THEY HAVE NOW

UniqueOS, and an agent named Lucky.

01Weddings board

Every wedding, its date, its couple and where it stands, at a glance.

02Couple pages

Guests, RSVPs, the venue, the vendors and the timeline for each couple in one place.

03Lucky, their agent

Drafts the emails, updates the guest list, creates and shares the files. Nothing goes out until a person sends it.

04Files that keep up

Run of show, seating plans and vendor sheets created, edited and shared from the conversation.

05Vendors and venues

Who is confirmed, who is waiting, and every detail of each venue.

06A public catalog

Their decor rental, online for couples to browse.

[ 05 ] WHAT CHANGED

The planner plans weddings again.

Status questions answered from memory→Answered from the system, in seconds
Vendor emails written one by one→Drafted together, sent with one tap
Files scattered across inboxes→Created and shared from one place
A system to adapt to→A system that adapted to her
[ 06 ] WHERE IT GOES NEXT

What we learned, for planners like her.

Every planner we have met works differently, and that is exactly why off-the-shelf tools never quite fit. What carries over is the method: sit down first, learn the real workflow, build the smallest system that fits it, and let the agent do the paperwork while the people do the people part.

Wedding planners, event producers and anyone who coordinates many vendors for one big day can start from what we built here, then make it theirs.

MORE STORIES
[ NEXT ] ONE CONVERSATION

Bring the business as it is.

We'll tell you, honestly, what we would build first and what we wouldn't. No deck, no pitch.

Start in 30 seconds