Keep your reservation core. Own everything around it.
Your reservation, ticketing, and check-in platform is the right core, and it should stay. The competitive difference lives in the layer around it: the apps, disruption communications, integrations, and analytics your passengers and teams actually touch. We build that layer, and you own it.
16M+
Passenger journeys powered
ISO 27001
Information security certified
Microsoft
Solutions Partner
The core in the centre, the value around it.
Bookings, inventory, and pricing belong in your reservation platform. Experience, communications, analytics, and partner revenue belong in a layer you own. This is how systems integrators have always worked around large enterprise platforms.
Stays in the core
Your reservation platform
- Bookings and amendments
- Inventory and capacity
- Pricing and fares
- Ticketing and check-in
The operator-owned layer
Customer apps and portals
Branded booking flows, mobile apps, and account portals that match your routes and your standards, not a generic template.
Disruption communications
Real-time sailing status, proactive notifications, and self-service rebooking that write back into the core through the API layer.
Integration and API layer
A layer you own that connects ports, ANPR and gate hardware, CRM, finance, and government reporting, instead of point-to-point links into the core.
Analytics and forecasting
Your own reporting layer, blending reservation data with weather, tourism, and operational data for demand forecasting and yield insight.
Ancillary and partner revenue
Accommodation, attractions, events, and freight value-adds captured through partner integrations the reservation core does not know about.
Accessibility and assisted travel
Assisted-travel booking and workflow tooling built to statutory standards, for routes and communities the standard product treats generically.
The core is not the problem. The gap around it is.
Leading ferry operators run on enterprise reservation platforms, and for good reason. A mature booking, ticketing, and check-in core is mission-critical, hard to build, and expensive to get wrong. It should stay.
The difficulty is structural, not a fault of the platform. A product shared across many operators cannot prioritise one operator's routes, contracts, or customers, and should not try to. So the work that differentiates you, from a branded app to weather-driven rebooking, tends to queue behind a roadmap you do not control.
The answer is not to replace the core. It is to build an operator-owned layer around it, connected through an API layer you control. We already support this pattern for CalMac Ferries, the UK's largest ferry network, whose reservation core is the e-Dea platform. We extend the systems around the core; we never replace it.
Talk Think Do is an Azure-native software consultancy founded in 2014. We are ISO 27001 certified, a Microsoft Solutions Partner, and we deliver with AI-augmented practices that are publicly evidenced at 40 to 50% faster in our AI Velocity Report.
Proof this works
Application support and integration enhancements for the UK's largest ferry network
Consumer-grade digital platform delivered at scale with 99.99% uptime
Serverless partner and loyalty backend for the IAG customer loyalty platform
Our credentials
- ISO 27001 certified
- Cyber Essentials Plus accredited
- Microsoft Solutions Partner
- Government Commercial Agency (GCA) supplier (G-Cloud 14)
Seven pains that live outside the reservation core.
These are true of operators on any enterprise reservation platform. Each one belongs in a layer you own, and each links to a deeper guide.
Roadmap dependency
A shared reservation core serves many operators, so anything unique to your routes, contracts, or customers queues behind the vendor's product roadmap. An owned API layer decouples your roadmap from theirs without touching the core.
Read the anchor guide on extending a reservation systemUndifferentiated customer experience
Booking flows and apps built into the core look and behave like every other operator's. Brand, accessibility, and route-specific journeys for islands, freight, pets, and dangerous goods need a bespoke experience layer.
See how we build consumer-grade apps at scaleDisruption communication
Weather-driven cancellations are the single biggest driver of contact-centre load and customer anger, especially on lifeline island routes. Real-time status, proactive notifications, and self-service rebooking sit naturally outside the core.
Read the guide to ferry disruption communicationsIntegration sprawl
Ports, gate hardware, CRM, loyalty, finance, and government and PSO reporting each need a connection. Operators need an integration layer they own, rather than a growing web of point-to-point links into the core.
Explore our API and integration servicesData locked in the core
Reporting exists, but operators want their own analytics: demand forecasting, yield insight, and route performance that blend reservation data with weather, tourism, and operational data.
See how an owned API layer frees your dataAncillary and partner revenue
Accommodation, attractions, events, and freight value-adds are revenue the core booking flow does not naturally capture. The crossing is the anchor purchase for a whole trip.
Read the guide to ferry ancillary revenueAccessibility and assisted travel
Statutory obligations and ageing coastal demographics make assisted travel a priority. Standard products treat these workflows generically, where a bespoke layer can serve them properly.
See our approach to extending the coreWork that de-risks the layer around your core.
Mission-critical ferry support, consumer-grade app quality, and partner and loyalty integration, all delivered and published.
Discovery, an API assessment, then incremental delivery.
Discovery
We map your routes, customers, and operational context, and agree which pains matter most to your roadmap this year.
API assessment of the current core
We assess what your reservation platform already exposes, what it does well, and where an owned layer adds the most value fastest.
Incremental delivery
We build the layer in slices, starting with the highest-value capability, so you see working software early and the core stays untouched.
Guides for ferry operators
In-depth guidance for building the operator-owned layer around your reservation core. This list grows as we publish.
Frequently asked questions
How do ferry operators build custom apps on top of their reservation system?
By adding an operator-owned API layer between the reservation core and everything else. The core keeps ownership of bookings, inventory, and pricing. Custom apps, portals, and disruption tools read and write through that layer, so an operator can build route-specific and brand-specific experiences without waiting on the vendor roadmap. Our guide to extending a ferry reservation system sets out the architecture.
Who integrates with ferry booking platforms?
Talk Think Do builds and supports the integration and experience layer around ferry reservation platforms. We already provide application support and integration enhancements for CalMac Ferries, the UK's largest ferry network. We extend the systems around the core; we do not replace it.
How can we improve ferry customer experience without replacing the booking system?
Keep the reservation core and own the layer around it. The booking engine is the right place for inventory and pricing, but brand, accessibility, disruption communications, and route-specific journeys belong in software the operator controls. That layer is where the customer experience is won, and it can be delivered incrementally without touching the core.
Does Talk Think Do compete with reservation platform vendors?
No. We are a complementor, not a competitor. The reservation, ticketing, and check-in core is mission-critical and should stay. We build the operator-specific layer around it: customer apps, disruption communications, integrations, analytics, and ancillary revenue. This is the same pattern systems integrators use around large enterprise platforms.
What technology stack do you use for ferry software?
We are Azure-native. We build with C#/.NET and React on the backend and web, React Native for mobile, and Bicep and GitHub Actions for infrastructure and delivery. We are ISO 27001 certified, Cyber Essentials Plus accredited, and a Microsoft Solutions Partner, and we use AI-augmented delivery to move faster without cutting quality.
Which of these are on your roadmap?
If any of the seven pains above are queuing behind a shared product roadmap, they belong in a layer you own. Book a consultation and we will assess what your reservation core exposes and where an owned layer adds the most value fastest.
or call 01202 006729