Platform48

Customer story · Swoop Adventures

From 2+ days to a 30 minute itinerary.

Swoop Adventures creates highly bespoke trips to remote destinations, including Patagonia, Antarctica and the Arctic, across multiple travel brands.

Every single step can be customised: where you stay, how you travel, what you do and how long you spend in each place. Each itinerary is built around the individual traveller, with every accommodation, transfer and activity shaped to fit their trip.

Putting all of that together used to take more than two days. We brought data from across the company into one structured database and built a visual itinerary builder around it.

The result is a beautifully presented, bespoke itinerary, tailored to the traveller and ready to share. The same job now takes 30 minutes.

Swoop Adventures

Before
2+ days per itinerary
Now
30 minutes
Project
Data integration and itinerary building
Scope
Multiple travel brands, one shared foundation

Before

The trip was bespoke. So was all the work behind it.

Every trip can be customised step by step. Changing a stay, a transfer or an activity means making the surrounding plans fit too. Building that itinerary meant bringing together information held across the business. With multiple brands and many different kinds of travel product, a faster way to assemble the trip needed a better way to organise the data first.

  • Data spread across the company

    The information needed for a trip lived in different places. Bringing it together was part of the work every time an itinerary was created.

  • Multiple brands

    The solution had to support more than one travel brand, with different destinations and products, while giving the team a shared way to work.

  • Lots of moving parts

    Accommodation, transfers, flights, excursions, cruises and multi-day journeys all need to fit into one trip, with dates, travellers and prices attached.

  • More than a calendar

    A trip also needs a price and a proposal the customer can read. Speeding up the planning alone would leave the rest of the job to do.

The foundation

One structured home for the travel data.

We pulled data from across the company into a single, well-formed database. A shared library gives the builder reusable travel components, with defined fields and relationships instead of a different structure for every source.

  • A common structure

    Templates define what each kind of travel component contains. Data is checked against those definitions, so the builder can work with it consistently.

  • Reusable building blocks

    An accommodation, transfer or excursion can be held once in the library and used in different itineraries. Components can also be grouped into packages and multi-day journeys.

  • The context stays attached

    Components carry their partner, region, dates, duration, price and currency. The team can find the right product without starting with an unstructured list.

  • A library the team can maintain

    A separate editing tool manages templates and components. The shared data has its own home, rather than being buried inside individual customer itineraries.

The itinerary builder

Find it. Drop it into the trip. Make it fit.

The builder turns that shared data into a practical workspace. The team searches the library, arranges the trip on a calendar, works through pricing and prepares the customer quote in the same application.

  • Search the shared library

    Filter components by destination, type and partner, then drag them onto the itinerary. The calendar makes the shape of the trip visible as it comes together.

  • Plan the details

    Build around dates and travellers, with accommodation, transport, activities and longer packages in the same itinerary. A map gives the team the location context alongside the plan.

  • Price the trip

    Pull in dynamic pricing from external data sources, then work through commissions, discounts, fees and extras. Pricing and quote views use the same itinerary data, with changes fed back into the trip.

  • Keep alternatives

    Branch an itinerary to explore another option, with versions and snapshots to keep track of the work. A different proposal does not have to start from scratch.

Across the business

One workflow, from enquiry to customer proposal.

The itinerary builder connects to Swoop’s existing systems. It brings the enquiry, the trip and the customer-facing proposal into a connected workflow, while supporting the destinations and products behind multiple brands.

  • Connected to the enquiry

    Itineraries are linked to a customer enquiry, with integrations into Swoop’s existing API and CRM workflow.

  • Destination-aware

    Shared destination data covers Patagonia, Antarctica and the Arctic. Region and partner information helps the team find the right products for a trip.

  • A proposal to share

    Create a beautifully presented, bespoke itinerary for the customer and share it as a web link. Each proposal brings their personalised trip together in one place, while the team can continue working on the itinerary.

  • A shared foundation

    The product library, itinerary, pricing and quote are connected through shared data models and APIs. Each stage builds on the work already done.

The result

An itinerary in 30 minutes. Previously, 2+ days.

The time saving comes from the whole system: company data brought together, products made reusable, and planning, pricing and proposals connected. The team still shapes a trip for each customer, with far less time spent assembling the information behind it.

  • Less time assembling

    The builder draws on a structured product library, so creating a trip starts with usable information already in place.

  • More time for the customer

    Moving from days to minutes gives the team more room to consider the trip itself, explore alternatives and respond to the customer.

Under the hood

A visual workspace on a structured data platform.

A Next.js and React application, Go services and MongoDB, with schema validation for the shared library and APIs connecting the builder to Swoop’s existing systems.

  • Next.js
  • React
  • TypeScript
  • Go
  • MongoDB
  • JSON Schema
  • API integration

Does a half-hour job take your team days?

Tell us where the information lives and what your team has to assemble. We’ll talk through how to bring it together and build a better way to work.

Contact us