The Pitch Questions That Expose Fake Travel Tech Experts

You have outgrown your off-the-shelf booking engine, mapped out your internal workflows, and decided it is time to commission a bespoke system. You put out a brief. You get three agency proposals back.

On paper, they all look entirely capable. The agencies have beautiful portfolios, glowing client testimonials, and slick pitch decks. They nod when you talk about APIs, payment gateways, and user experience. They promise to deliver a modern booking platform in four months.

Then month six arrives. The project is stalled. The developers cannot figure out why a group booking from an Online Travel Agency (OTA) is overriding your direct website inventory. They are manually patching code to handle partial deposit refunds. They are asking you basic questions about cut-off times that should have been settled on day one.

You are not just paying for software; you are paying to educate a generalist agency on the mechanics of the travel industry.

Booking software is structurally hostile to generalist developers. It looks like e-commerce on the surface, but underneath, it is a high-stakes logistics and scheduling engine. If an agency has never built for tours and activities, they will underquote the job, build the wrong architecture, and leave you holding a broken system.

Here is how operators across Australia, the UK, Europe, the US, and India can screen developers before signing a statement of work.

You Are Buying a Logistics Engine, Not a Shopping Cart

The most dangerous assumption a software agency can make is that a tour is just a product.

If you ask a generalist developer how they plan to build your system, they will describe an e-commerce architecture. E-commerce is simple math: you have 50 coffee mugs in a warehouse. A customer buys one. You now have 49 coffee mugs. The stock count goes down by one.

Travel inventory does not work like this. You are selling time, capacity, and overlapping physical resources.

Imagine you operate a 20-seat minibus and employ one driver. On a Tuesday, you offer three products on your website: a morning wine tour, a half-day express tour, and a full-day private charter.

If a corporate group books the private charter, the morning wine tour and the half-day express tour must instantly drop to zero availability. The resource (the bus and the driver) is consumed. If you try to build this using standard e-commerce logic, the system will look at the wine tour, see it has 20 seats left, and happily sell them to a tourist in London while the bus is already booked out.

If an agency pitches you a system without immediately asking how your physical resources map to your tour variants, walk away. They are going to build a shopping cart when you need a dispatch system. We have covered why generalist developers fail at travel booking software repeatedly—this fundamental misunderstanding of inventory is almost always the root cause.

The Litmus Test: Three Questions to Ask in the Pitch Room

Do not wait for the technical discovery phase to find out if your agency understands travel. Ask these three questions during their pitch.

1. "How do you handle concurrent booking locks?"

The Scenario: It is a busy Friday. You have exactly two seats left on a highly profitable sunset cruise. A couple in New York clicks "Book Now" on your website. Ten seconds later, a concierge at a partner hotel clicks "Book" on their portal for the same two seats.

The Generalist Answer: "We use standard database updates. The first person to complete their payment gets the seats, and the second person gets an error message after they put in their credit card."

The Specialist Answer: "We implement a temporary inventory lock. The moment the New York couple hits the checkout page, those two seats are held in a pending state for 10 minutes. The hotel concierge will immediately see those seats as unavailable. If the New York couple abandons the cart or their payment fails, the seats are automatically released back into the live pool."

Without a session-based inventory lock, your operations team will spend their summers dealing with angry customers and issuing apologies for double bookings.

2. "What is your plan for OTA distribution?"

The Scenario: You rely on Viator, GetYourGuide, and a network of local DMCs to fill your remaining capacity. You need your new custom system to talk to them.

The Generalist Answer: "We will just connect to their APIs. We build custom API integrations all the time."

The Specialist Answer: "Building direct API connections to five different OTAs is a maintenance nightmare because they all format availability differently and change their endpoints constantly. We recommend integrating your system with a specialized channel manager, or adopting an industry-standard specification like Octo, so you only have to maintain one connection for external distribution."

Generalist agencies severely underestimate OTA connectivity. They think it is a simple data push. They do not anticipate API rate limits, webhook failures during peak booking hours, or the fact that OTAs require availability mapping down to the individual ticket tier (Adult, Child, Senior). When picking a travel tech build partner in specific regions like Australia or the UK, their understanding of regional channel managers is a mandatory requirement.

3. "How do you model our cut-off times?"

The Scenario: Your multi-day hiking tour requires a final manifest 48 hours before departure to organize food rations and permits.

The Generalist Answer: "We will just put a rule in the code that removes the tour from the website two days before the start date."

The Specialist Answer: "We build dynamic cut-off windows into the resource logic. But we also need to know your manual override policy. If a VIP partner calls 24 hours before departure, how does your ops team bypass the hard cut-off to force a booking through without breaking the manifest logic?"

Operators do not live in a rigid world. Rules exist, but operations managers break them daily to accommodate high-value partners or fix mistakes. A hardcoded cut-off rule will force your staff to physically alter database records just to squeeze one extra person onto a bus.

The Multi-Currency and Split Payment Trap

If you operate tours in Europe or process inbound travel to the US and Australia, payments are rarely a single, clean transaction.

Standard web developers are used to a simple flow: Customer clicks buy -> Stripe charges $100 -> Order is complete.

Travel businesses collect a 20% non-refundable deposit today. They collect the remaining balance 30 days before departure. If the customer adds an optional helicopter flight two weeks out, the final balance changes. If the customer cancels 14 days out, they might be entitled to a 50% refund on the balance, but no refund on the deposit.

When reviewing proposals, look at the timeline allocated to the payment gateway integration. If the agency has allocated 20 hours for "Stripe Setup," they do not understand what they are building.

Ask them directly how the system handles scheduled balance chasing. Does the software automatically email a secure payment link 30 days out? If that card declines, does the system automatically cancel the booking and release the inventory, or does it flag it for a human operator to chase? The answers will tell you immediately if they are thinking like a travel operator or a web designer.

How AI-Assisted Scoping Derisks the Build

Historically, the only way to map out all these edge cases was a brutal, months-long discovery phase that cost tens of thousands of dollars before a single line of code was written. Operators had to sit in endless workshops trying to explain the reality of supplier operations to business analysts.

This is where the model is shifting. Agencies that actually understand this sector use AI-assisted product delivery to radically compress the requirements phase.

Rather than starting from a blank page, technical teams use AI tools trained on established travel architectures to instantly generate the core data models for resource pooling, OTA mapping, and split payments. They are not using AI to write production code blind; they are using it to rapidly prototype the complex relationships between a tour variant, a guide, a vehicle, and a channel manager.

This means that when you sit down for discovery, you are not explaining what a "cut-off time" is. You are reviewing a working logic map of your operations and adjusting the specific rules for your business. It allows operators to figure out who should actually build a bespoke tour booking system based on the speed and accuracy of their initial scoping, rather than guessing based on a slide deck.

The Verdict on Agency Pitches

You are commissioning software to remove friction from your business. If you hire a team that does not understand the fundamental mechanics of travel inventory, you are just moving the friction from your operations desk to your IT budget.

Demand proof of domain expertise. Ask the hard logistical questions in the very first meeting. If the agency stumbles on resource mapping, dismisses the complexity of OTA API connections, or pitches an out-of-the-box e-commerce flow, thank them for their time and move on.