Case study · Private partner pilot

From side-hustle to travel brand in nine days.

How Maya B., a Viago ambassador specializing in honeymoon and romance travel, went from a link-in-bio page to a professional website with an organized pipeline behind it — as part of the Horizons OS founding pilot.

Maya B. · Honeymoon & romance travel · Founding pilot member

9 days from questionnaire to launch-ready website Build timeline
24 leads captured and organized in her first month First 30 days
0 spreadsheets every inquiry, call, and proposal in one workspace Workflow

Results from our private partner pilot. Individual results vary with niche, audience, and effort.

The starting point

Maya had the hardest part figured out: people trusted her. Friends, followers, and referrals kept asking her to plan their honeymoons. What she didn't have was anywhere credible to send them. Her "website" was a link-in-bio page, her CRM was a notes app, and her follow-up system was memory and good intentions.

Inquiries arrived through Instagram DMs, text messages, and a form that emailed her — sometimes. When a couple asked "can I see your website?", the honest answer was no.

“I was losing people in the gap between 'I'm interested' and 'let's talk.' Not because I wasn't good — because I looked like a hobby.” Maya B., founding pilot member

The build: nine days, five steps

Maya joined the Horizons OS pilot on a Monday. Her workspace was live the same day, with the website questionnaire waiting on her dashboard. She spent about forty minutes on it — her niche, her story, the trips she loves planning, the couples she wants to attract.

From there, the process ran on rails. Our team built her draft; she reviewed it inside her workspace and requested revisions — tighter copy on the homepage, a warmer photo direction, a dedicated honeymoon planning page. Every step showed its status on her dashboard, so she never had to email anyone to ask "where are we?"

The build timeline

Questionnaire to launch.

1
Day 1

Workspace live, questionnaire in

Maya's private workspace was provisioned at signup. She completed the guided brand questionnaire the same evening.

2
Days 2–4

Draft designed and built

The Horizons OS team designed her site around her niche and voice — structure, copy, and imagery direction included.

3
Days 5–7

Revisions, tracked in-workspace

Maya requested two rounds of refinements from her dashboard and watched each one move from "requested" to "done."

4
Day 8

Review call

A scheduled walkthrough — booked through her own Horizons OS calendar — to approve the final build together.

5
Day 9

Launch-ready

Domain connected, lead capture wired to her CRM, booking link live. Maya announced her site that weekend.

app.horizonsos.com
Live workspace capture — Maya's pipeline Placeholder. Screenshot of the real pilot workspace (with permission) drops in here.

What changed after launch

The website was the visible win — but the workflow underneath it changed how Maya works. Inquiries from her site now land directly in her CRM with trip details attached. Discovery calls book against her real Google Calendar availability, with a two-day buffer so nothing ambushes her. Every couple moves through the same pipeline: inquiry, discovery, proposal, booked.

The quiet difference is what's gone: the spreadsheet, the notes app, the screenshot-a-DM-so-you-don't-forget system. When she opens her dashboard in the morning, she knows exactly who's new, who's waiting on her, and what's on the calendar.

“The site makes me look like a real business. The workspace makes me run like one. I didn't expect the second part to matter more.” Maya B., founding pilot member

The takeaway

Maya's story is the pattern the pilot was designed to prove: ambassadors and independent advisors don't need more tools — they need one system where the pieces already know about each other. A website that feeds a CRM. A CRM that feeds a pipeline. A pipeline that books onto a real calendar. That's the product.

Your turn

Nine days from now, this could be your launch story.