Live · Booking + audit in one platform · Onboarding design partners

Book it like a text.
Audit it like a ledger.

Glidr is the booking + audit platform for B2B travel. Employees book in plain language — and every trip is born with its approval, policy check, and spend record attached. Immutable, queryable, export-ready.

100%
Of bookings audit-ready by default — not reconstructed later.
12 min
From request to booked — fully documented, on average.
10–15%
Agency markup returned to your P&L.
1 record
Per trip: approval, policy, price, actor — immutable.
01 / The Problem

Booking the trip was never the hard part. Proving it was.

Consumer travel solved booking a decade ago. B2B never did — because a corporate trip isn't a transaction, it's a financial event: money spent on someone's behalf, against a policy, that finance has to reconcile later. Today that proof lives in inboxes, WhatsApp groups, and an agency's reply-all. Un-auditable by design.

Step 01
The traveler
Texts preferences to a manager. The ask is now trapped in a personal chat.
Step 02
The line manager
Re-types it into an email and escalates. The original request is already lost.
Step 03
The approver
Approves in a reply. The sign-off now lives in an inbox no auditor can search.
Step 04
The coordinator
Forwards a cleaned-up version to an agency — a third copy, none of them canonical.
Step 05
The agency
Books off-platform. Price, fare rules, and markup never come back queryable.
Step 06
Confirmation
Pasted back into the chat. The "record" is a screenshot.
Step 07
Plans change.
The whole loop repeats — and the trail forks again.
The gap between booking and bookkeeping is where corporate travel spend goes dark. When finance asks "who approved this, against what policy?" — the answer is scattered across five inboxes and a screenshot.
— The Glidr thesis
02 / The Platform

Booking on the front. An audit ledger underneath.

Most tools bolt reporting onto a booking flow after the fact. Glidr inverts it: the audit record is minted at the instant of booking, so there's never a gap between what happened and what's on file.

A · The front

Book like it's 2026, not 2006.

No GDS terminal, no procurement portal, no agency middleman. Travelers ask in plain language inside WhatsApp; approvers tap once; admins set the rules in a console. Each role gets a purpose-built surface — never a generic dashboard pretending to fit everyone.

Travelers
Book in plain language. "Dubai Mar 15–18, mornings."
Approvers
A structured summary, one tap to approve. No app, no login.
Admins
Roles, approval chains, policy, spend limits — in a dedicated console.
Finance
Export the ledger. Every booking already reconciled to a record.
B · The underneath

Every booking, born documented.

Request, approver, timestamp, policy result, price, and fare rules are captured as one immutable record the moment they happen — not a report you assemble from inboxes the week before an audit.

Who
Requester & full approver chain, by name and role.
When
A timestamp on every state change. Nothing backfilled.
Policy
Pass / breach + the reason, evaluated live.
Price
Quoted vs. booked fare, drift, and any override.
Proof
Sealed, queryable, export-ready from message one.
03 / The Ledger

Anatomy of an audited booking.

One trip. Every state change captured the moment it happens — not reconstructed from inboxes later. This is the same record finance exports and an auditor reads, end to end.

Record  TRIP-2026-0315-DXB
Policy pass Immutable Export-ready
Requested
Karim H. · Athlete
"Dubai Mar 15–18, mornings if possible." — captured verbatim, structured into a request.
WhatsAppintent parsed
09:41
Routed
→ Anita R. · Manager
Auto-routed on the org's approval graph. SLA timer started; escalation path on standby.
SLA 12 min1 approval required
09:42
Price drift
Live fare moved +1.4%
Fare re-priced between request and approval. Surfaced to the approver with the delta — never absorbed silently.
+$18within 2% tolerance
09:52
Approved
Anita R. · one tap
Accepted the live price. The override reason is written to the record — not a memory.
approved + drift acceptedreason logged
09:53
Policy check
Pass
Class of travel, vendor, and budget evaluated against the versioned policy in force at this minute.
economy ✓budget $1,500 ✓policy v14
09:53
Booked
Emirates EK 506 · $1,310
Booked via vendor API at the approved fare. Quoted vs. booked price stored side by side.
fare lockedPNR attached
09:54
Reconciled
Finance export · GL-tagged
The record flows to finance already reconciled. Nothing to chase, nothing to rebuild before the next audit.
cost centre mappedexport queued
live
7 events · 2 actors · 0 gaps sealed sha256 · a4f1…9c02
04 / The Engine

The engine that makes booking feel like texting.

Underneath the simple chat is a chain of models and deterministic tools. Cheap, fast models classify and format; the best models reason; real tools touch the real world — the agent never fabricates a price, a policy result, or an approval.

A · The pipeline

Four stages.
Each one swappable.

The agent isn't one big call. It's a chain — fast cheap models for classification and formatting, the best models for the actual reasoning, deterministic tools for everything that touches money or makes a booking.

B · What it keeps

The record outlives the conversation.

An agent is only as trustworthy as what it can prove. Glidr keeps four kinds of memory — and the one that matters for audit never lives inside the model.

Conversation
Last 24h of thread — enough to feel like a colleague, never enough to drift.
The record
Request state as structured data in the database, not the model. Auditable, recoverable.
Profile
Seat, loyalty, dietary, frequent routes — every trip makes the next shorter.
Policy
Versioned company rules, loaded fresh per request. A change applies the next minute.
05 / The Moat

Travel is the way in. The ledger is what they can't leave.

The defenses aren't price or inventory. They're structural — six layers that get harder to dislodge every quarter the platform is in use, led by the one no spreadsheet can recreate: years of provable history.

i.
Audit & compliance
Years of bookings, approvals, policy results, and spend patterns — captured at the source. Cannot be migrated. Becomes a compliance dependency the company won't risk losing.
Regulatory
ii.
Cost elimination
10–15% agency markup returned to the company, with the receipts to prove it. The CFO has hard-dollar ROI — an easy procurement decision.
Financial
iii.
Workflow lock-in
The approval graph is configured, trained, and adopted by the whole org. Rebuilding it elsewhere is slow and risky.
Behavioral
iv.
Duty of care
Real-time traveler location, emergency contact, advisories — tied to the same record. A procurement requirement in enterprise contracts.
Procurement
v.
Profile memory
Traveler preferences grow richer with every trip. Switching means starting from zero. Powerful retention.
Compounding
vi.
Per-role UX
Each persona gets a purpose-built experience. No generic tool can match purpose-built depth.
Product
"We do everything your coordinator and agency do — in seconds, for less — and we hand you the audit trail they never could."
The one-line test · 2026
Pilot testing phase · invite-only

Glide in.

Glidr is in its pilot testing phase — we're working hands-on with a small set of design partners. If your travel spend lives in inboxes and screenshots, and someone still has to prove who approved it, send us an enquiry.

deepak@goglidr.com
Founder-led conversations · Reply within 24h