Reev Travels · Corporate Travel · B2B Platform

Three engineers. One year. A complete corporate travel platform.

My roleFractional CTO. I led the build-vs-buy decision, the architecture and the in-house team.
DurationAbout a year, from the start to a live platform
TeamA backend engineer, a frontend engineer and a DevOps consultant, plus a freelance QA tester
Scale350–500 bookings a month for corporate clients
PlatformA multi-tenant web portal with eleven modules, covering booking, billing and reporting
Live atreev.in/app ↗
Reev platform admin dashboard
The business

Reev Travels is a Bangalore-based travel company that manages flight and hotel bookings for corporate clients.

350–500 bookings a month for corporate clients
The challenge

More people only meant more mistakes.

Every booking was handled over email, WhatsApp and phone calls, and tracked in spreadsheets. It worked while the business was small. As volumes grew to hundreds of bookings a month, adding more people to keep up only led to more mistakes. Reev had reached the point where it could only scale with a proper product.

Email WhatsApp Phone calls → Spreadsheets
What I did
01

Made the build-vs-buy call.

This was the hardest decision. There are plenty of travel booking tools on the market, and most suit a small agency. For a company with Reev's ambitions, they were limiting, and the upfront costs were high. The white-label platforms we spoke to either had poor design or lacked features Reev needed, especially reporting for both its own team and its clients, and support for multiple levels of users. My judgment was that if we bought, within a year the team would be running into the tool's limits and drifting back to spreadsheets. So we built.

Off-the-shelf booking toolsSuit a small agencyLimiting for a company with Reev's ambitions, and high upfront costs.
White-label platformsPoor design or missing featuresEspecially reporting for Reev and its clients, and multiple levels of users.
Chosen · BuildSo we built.Buying would have meant hitting the tool's limits within a year and drifting back to spreadsheets.
02

Designed for many clients from the start.

I architected the platform as multi-tenant. Each corporate client is its own organisation, with separate users, wallet, invoices and billing terms, all run from one system. Four user types control who sees what: Reev's operations staff, each client's travel manager, employees who travel, and external guests.

One systemEach corporate client is its own organisation
Client A
UsersWalletInvoicesBilling terms
Client B
UsersWalletInvoicesBilling terms
Client C
UsersWalletInvoicesBilling terms

Four user types control who sees what

User type 1Reev's operations staff
User type 2Each client's travel manager
User type 3Employees who travel
User type 4External guests
03

Built a lean in-house team.

Instead of handing the project to an agency, I put together a small team: a backend engineer, a frontend engineer and a DevOps consultant, with a freelance QA tester brought in for regular testing. I led the project throughout. That kept costs low and kept the knowledge inside the business.

Backend engineerIn-house
Frontend engineerIn-house
DevOps consultantIn-house team
QA testerFreelance, for regular testing
04

Built the whole back office, not just a booking screen.

The platform covers the full operation:

Booking

Flight and hotel search and booking (one-way, round-trip and multi-city), plus group booking requests and priced quotes for clients.

Offline bookings

Bookings made outside the portal can be recorded one at a time or in bulk, so nothing lives in spreadsheets anymore.

Spend controls

Approval workflows, booking limits for each employee, and credit terms for each client.

Billing

Prepaid and postpaid billing with a wallet ledger for every client, online payments through Razorpay, offline payment recording, invoices and vouchers sent by email or WhatsApp.

Reporting

A live dashboard showing bookings, revenue and margin. Sales, payment, turnover and pending-sales reports can be exported, and a full log records every change.

The result

Reev moved from email, WhatsApp and spreadsheets to its own platform, live and serving its corporate clients.

Bookings, billing, payments and reporting now run in one system instead of across people and sheets.
Clients manage their own travel with approvals, limits and a clear view of spend.
Reev can see revenue, margin and pending payments for each client at any time.
The platform was built in about a year by a team of three plus a part-time tester, and Reev owns it.

Has your business outgrown spreadsheets?

Start a conversation ↗