tRAVEL TECH
B2B2B
booking Platform redesign
TravelSales gives family bus operators in Latin America an AI sales agent, Maya, who prices a charter trip in seconds. The screens around her gave that time back: operators needed five tabs to create a quote, and travel agents stalled at a blank prompt. As the only designer, I redesigned the operator calendar, quote creation, and quotation page, and added a manual booking form next to Maya.
Outcome
The operator calendar, quotation page, and agent booking form shipped ahead of launch. The founder built each one in Lovable straight from my Claude Design prototypes, and creating a quote went from five tabs to one screen.
ROLE
Sole Product Designer
TEAM
Founder, Product Manager, AI Specialist, Product Analyst

Quotation overview for bus operators
Why it mattered
Before Maya, a charter quote meant a phone call, handwritten notes, and one to two days of waiting. By then, the agent had often booked someone else. Maya cut pricing to seconds, but that only helps if operators can act on her quote and agents can get a request in.
When the screens are slow, all three sides pay.
Travel agents
Their group waits days for a price they need now.
Travelsales
Revenue is a single-digit commission per completed booking, with no subscription. A quote that never closes earns nothing.
Operators
The bus sits idle and the trip goes elsewhere. Family operators already compete with a few large platforms. They can't also lose trips to a slow callback.
What I owned
Flows and UI
Redesigned the operator calendar, quote creation, and quotation page, and designed a new booking form for travel agents.
Competitive research
Studied how competitor tools handle fleet calendars to fill gaps in what we knew about operators.
Prototypes as the spec
I presented each design as a working prototype in Claude Design and tuned the UI by hand. The founder built the product in Lovable straight from them.
Decisions with the team
Reviewed designs on Slack and made iteration calls in meetings.
Where it broke
Travelsales was pre-launch, so I couldn't interview operators or agents directly. My research came secondhand from the founder, who spent a decade in charter transport and was pitching prospective customers throughout the project. For the operator calendar, I filled the gaps by studying how established scheduling tools in the US and Europe handle fleet bookings.
The calendar hid the essentials
Booking bars showed only a quote number: no times, no status, and no way to show an overnight trip. An operator's first question is which buses are free this week, and the calendar couldn't answer it. It also had no cleaning buffer, which Busify builds into every booking.
Too many tabs to create a quote
Nothing was marked required, so operators couldn't tell what to fill in or in what order. Operators are always rushed, with no time to type line by line.
One quote, two different pages
The quotation page changed depending on whether operators opened it from the calendar or the quote list.
Agents didn't know where to start
Maya opened on a blank prompt with no hint of what she needed. Agents think in groups and routes and plan multi-day, multi-stop trips. Some prospects told the founder they weren't sure how to start with an AI agent.
Key decisions
Before designing any screens, I mapped the redesigned flow end to end. Operators reach one trip page whether they start from the calendar or a button, and agents reach one marketplace whether they use Maya or the form. The magic link joins the two. I walked the founder through the map to confirm the flow, and he backed my rationale.
01) Weekly over daily view for operators
I started with an hourly view that showed times and Busify-style cleaning buffers. It was too granular for multi-day charters. The PM asked for a daily view alongside weekly, but with one person building, every view competed for time. I convinced the founder to build weekly first and put exact times in a hover state, so overnight trips still show when they start and end.
Where it landed: Every booking block ends with its cleaning buffer and leads with what Betterbus taught me to prioritize in a short bar: quote number, times, and status.
Busify's (competitior) booking bar
Betterbus's (competitor) booking bar
Shipped design for Travelsales
02) One screen to quote, not five tabs
I pulled dates, customer, and unit onto one screen and moved route, drivers, and costs to the trip page. Units unlock only after dates are set, so operators only see free buses. An early version listed every unit, which ran too long for large fleets.
Where it landed: Dates arrive prefilled from the calendar, and dropdowns replace long lists.
Quote creation from the calendar
3) Block the bus before sending the link
The MVP showed a different quote page depending on where operators opened it, so I merged the two into one trip page. My first version split it into quick and detailed modes. I cut them, since operators could already type the itinerary directly. The next layout made block and magic link real actions, but nothing said which came first.
I laid out four versions of the action rail and chose the one with block unit at the top. Commercially it matters most: a quote can't close until the bus is held.
Where it landed: The far right version shipped. Block unit leads, then the magic link takes over, and every paid link earns Travelsales its commission. Operators can still adjust Maya's price before confirming.
Exploration of the button layout
4) A form next to Maya, not instead of her
The founder's position was firm: the AI agent is the core feature, and it stays. Meanwhile, agents were stalling at Maya's blank prompt. I pitched a form as a way to protect Maya, not replace her. Maya stays the hero of the entry screen, with a manual form right below as a fallback, and form bookings cut API costs too.
Separate flow for agents who do not want to use AI
5) Direct trip by default, stops on demand
I first built two separate flows, one for direct trips and one for trips with stops. Talking it through with the team, I realized a direct trip is just a trip with no stops yet, so the form should start there and grow.
Booking form for the travel agents
The experience
Final designs were primarily shipped in Spanish because most users are in Latin America.
Artifact 01
Creating availability
One row per vehicle, the whole fleet at a glance, and a quote from one screen.
Artifact 02
Calendar hover
Short bookings reveal quote number, times, and status on hover.
Artifact 03
Handling a quote from Maya
Block the unit first, then send the magic link.
Artifact 04
Agent booking form
Agents enter pickup and drop-off, add stops anywhere along the route, and price the whole trip in one tap.
ouTCOMES
The operator calendar, quotation page, and agent booking form all shipped in early fall 2026.
Tabs to create a quote, now one screen with four required fields, so operators can respond before agents look elsewhere
ways for agents to book, so traditional agents stay in the funnel instead of picking up the phone
Direct, round, and multi-stop trips handled in a single form, so travel agents never pick the wrong one
Learnings and reflections
🔄
With the work
I was wrong three times: the hourly calendar, quick and detailed modes, and two separate trip flows. Each fix was the same move. Fewer modes, sensible default, details on demand.
⚖️
With users
I never spoke to an operator or travel agent directly. Everything I knew about them came through the founder. Next I'd ask him questions more often and get our internal team to test each flow before it's built.
What's next
When the first operators go live, I'd track three things: time from request to quote, the split between Maya and the form, and how many magic links get paid.
Maya was already fast. Now the screens around her keep up.
















