JetVoya cut lead-to-itinerary time by 90% with a custom CRM delivered in 4 weeks

JetVoya had been attempting to configure a standard CRM for 6 months without success. The tool required extensive customisation that never quite fit their sales workflow, tracking leads, building itineraries, and converting prospects into bookings. Their team was working across spreadsheets, emails, and the half-built CRM, losing context and losing leads in the process.

The root problem was that JetVoya's sales process did not follow a standard lead-to-close funnel. Their workflow is fundamentally different from most B2B or B2C sales: a prospect inquires about a trip, the team builds a custom itinerary with flights, hotels, transfers, and activities, the prospect reviews and requests changes, and only then does a booking happen. This iterative, consultative cycle meant that a generic CRM's pipeline stages, Lead, Qualified, Proposal, Negotiation, Closed, were meaningless in their context.

The team had tried to adapt Zoho CRM by creating custom modules, fields, and automations. Six months and a significant consulting spend later, the system was half-built and already creaking. Itinerary data lived in Google Docs linked from CRM records. Pricing calculations were done in Excel sheets that had to be manually attached. Customer communication happened in Gmail threads that nobody remembered to log. The CRM had become another silo rather than the single source of truth it was supposed to be.

Meanwhile, the business was growing. JetVoya was handling 80 to 100 active inquiries at any given time, and the team had no reliable way to see which prospects were waiting for an itinerary, which had received one and not responded, and which were ready to book. Leads fell through the cracks weekly. The founder estimated they were losing 15 to 20 potential bookings per month simply because follow-ups were missed or itineraries were sent too late.

We built a custom CRM and customer-facing app from scratch, designed around JetVoya's actual workflow rather than forcing their process into a generic tool's assumptions. The project started with a one-week intensive discovery sprint where we shadowed the sales team through their daily workflow, documented every touchpoint from initial inquiry to final booking confirmation, and mapped the data relationships between leads, itineraries, pricing components, and bookings.

The CRM was built on a Next.js and PostgreSQL stack, deployed on Vercel with a Supabase backend. It tracks leads from first inquiry through itinerary build to booking confirmation, with pipeline stages that mirror JetVoya's real process: New Inquiry, Requirements Gathered, Itinerary Drafting, Sent to Client, Revision Requested, Approved, Payment Pending, Booked. Each stage has defined entry criteria and automated time-based alerts, if a prospect has been in "Sent to Client" for more than 48 hours without a response, the assigned agent receives a follow-up nudge.

The itinerary builder is the core of the system. Agents construct itineraries directly inside the CRM using a drag-and-drop interface that pulls from a database of pre-negotiated flights, hotel rates, transfer options, and activity packages. Pricing calculates automatically based on component costs, markup rules, and seasonal adjustments. The entire itinerary, with day-by-day breakdown, imagery, maps, and pricing, renders as a polished, branded page that the agent sends to the client with one click.

The customer-facing app is where the real advantage comes in. Instead of sending a PDF or a long email, prospects receive a link to a dedicated itinerary page. They can review each day of the trip, leave comments on specific components, request changes inline, and approve the final version with a single button. Every interaction on the customer app writes back to the CRM in real time, agents can see exactly when a client opened their itinerary, which sections they spent time on, and what changes they requested, all without a single email exchange.

Both systems sync bidirectionally through a real-time event bus. When a client approves an itinerary, the CRM record advances to Payment Pending automatically. When an agent updates pricing, the customer app reflects the change instantly. We also integrated Stripe for payment processing and built an automated booking confirmation flow that generates a final travel document upon payment.

The custom CRM went live in 4 weeks, a fraction of the 6 months spent on the off-the-shelf tool. The speed was possible because we were building for one specific workflow rather than trying to configure a general-purpose platform. The team was onboarded in a single afternoon session, and adoption was immediate because every screen and interaction mapped directly to what they were already doing, just faster.

Lead-to-itinerary time dropped by 90%. What previously took 24 to 48 hours, gathering requirements via email, building an itinerary in Google Docs, calculating pricing in Excel, formatting a presentable document, now took under two hours. The drag-and-drop itinerary builder with pre-loaded components and automatic pricing eliminated the most time-consuming manual steps. Agents could build and send a polished, branded itinerary before a prospect's attention moved elsewhere.

Conversion rates improved by 145% as the team responded faster and prospects had a cleaner buying experience. The customer app was a major driver of this improvement. Prospects could review itineraries on their phone, leave specific feedback without composing an email, and approve with a single tap. The average number of revision cycles dropped from 3.2 to 1.4, because the inline commenting system made it easy for clients to be precise about what they wanted changed. The entire back-and-forth that used to stretch over a week of email threads now resolved in a day or two.

The team also gained visibility they had never had before. A real-time dashboard shows how many inquiries are in each stage, which agents are carrying the heaviest load, average time-to-itinerary, and conversion rates by source channel. The founder uses this data to make staffing decisions and to identify which marketing channels produce the highest-quality leads. JetVoya has since expanded the system to support group travel and corporate bookings, using the same underlying architecture with additional workflow modules.