For small travel agencies
A CRM for the client side of your travel agency.
What independent agencies tell us
Your booking system knows the trip. Nothing knows the traveller.
- Your GDS or booking platform handles fares and reservations — but the client relationship lives in a spreadsheet, your inbox, and your memory.
- Repeat bookings are the business, and they slip: the honeymoon couple who'll want an anniversary trip, the family that travels every August. There's no reminder until it's too late to sell.
- You hold passport numbers and dates of birth in that same spreadsheet. For sensitive traveller data, "it's in a shared sheet" is not a privacy story you want to tell.
Where FlowGrid fits
Track travellers, trips, and suppliers — then take their data seriously.
Model what an agency actually tracks
Travellers, trips, and suppliers — not a generic contact list.
A standard CRM gives you "contacts" and "companies" and expects you to make a travel agency fit. FlowGrid's canvas doesn't. Describe what you track to Nexus — "I need a Traveller object with passport details and preferences, a Trip object linked to each traveller, and a Supplier object for the operators and hotels I book through."
Nexus shapes the canvas around that. Link a trip to the traveller who took it, link suppliers to the trips you ran with them, and build the schema your agency actually uses.
Repeat bookings, on a schedule
Follow up at the right time for the next trip.
Every traveller is a contact with their full history attached — past trips, notes, who they travel with. When a client comes back, you open one record instead of searching three places.
Set a task with a due date against a traveller — "check in about next summer" — and FlowGrid reminds you. The repeat booking stops depending on you remembering it.
Privacy for sensitive traveller data
Passport numbers and dates of birth, encrypted and logged.
Traveller records hold some of the most sensitive personal data a small business handles. FlowGrid encrypts every field at rest with AES-256-GCM and tenant-scoped keys, so your workspace's data is cryptographically separate from every other one. It's GDPR-compliant with a DPA.
The audit log records every access and change — who looked at a passport number, who edited a traveller record, and when. If a client ever asks how you protect their details, you have a concrete answer.
Verifiable, not assumed
We're early. Here's how you can verify us anyway.
How your data is protected
Field-level AES-256-GCM encryption with tenant-scoped keys. Multi-tenant row-level isolation. Every mutation logged.
Read the security details →Legal & compliance
GDPR-compliant with a Data Processing Addendum. Your legal contact can pull it now — not after a sales call.
Read the DPA →Built in public
We don't have customer logos to show you yet.
FlowGrid is early. Instead of borrowed credibility, here's what you can verify yourself:
Honest answers