---
title: "About TourCockpit"
url: https://tourcockpit.com/about
lang: en
description: "TourCockpit is the operating system for tour and excursion companies that sell through tour operators, hotel desks and agencies. It is built by IdeaPlaces, a product company, and it started in a real office that was running its day from a spreadsheet."
---

# About TourCockpit

TourCockpit is the operating system for tour and excursion companies that sell through tour operators, hotel desks and agencies. It is built by IdeaPlaces, a product company, and it started in a real office that was running its day from a spreadsheet.

## Why does TourCockpit exist?

A tour company with its own vehicles and guides does not have a booking problem. It has a coordination problem. The bookings arrive by phone, by WhatsApp and by email from a dozen resellers, and somebody has to turn them into a day: which bus, which guide, which language, which hotel at which minute, and who owes what at the end of the month.

That work was being done in a spreadsheet, the same way it is done in most offices of this size. The spreadsheet was not the wrong tool because it was old. It was the wrong tool because only one person could hold it at a time, resellers could not see it, and the month end had to be rebuilt by hand from rows that had been edited all month.

TourCockpit was written next to that office, screen by screen, keeping the words the office already said out loud. The vocabulary on the daily board is the vocabulary on the sheet, on purpose, so switching costs nothing to relearn.

## What does it do?

- An operator portal. Each reseller books its own seats against live availability, in its own language, and sees only its own bookings.
- A daily operations board. The day as the office actually runs it: vehicles by plate, guides by the language they speak, pickup times by zone, seats left per departure.
- Manifests and exports, printed or sent, with the child seats, the lunches and the payment method the driver needs.
- The month end. One commission settlement per operator, built from the bookings the board already recorded, so it is checked rather than rebuilt.
- An API for a company's own tooling, with the OpenAPI contract published and keys a manager mints.

The product is in six languages end to end: English, Spanish, Italian, German, French and Portuguese. Not the menus alone, the whole product, including what a guest receives.

## How do we sell it?

One published price, the same for every company, on the [pricing page](/pricing). No setup fee, no minimum term, no per-user charge. A company can export its own data at any time, and the API is part of the product rather than an upgrade.

The software ships continuously and what changed is written down: every release a customer would notice is on the [What's new](/changelog) page, in all six languages.

## Where does the product run?

The application and its database run on Microsoft Azure in Canada Central. Each company's data is isolated at two levels: the application scopes every query to the company, and the database enforces the same rule underneath with row-level security, so a bug in the first layer is still refused by the second.

What is collected, where it is processed and who else touches it is set out in full on the [privacy page](/privacy).

## Who builds it?

IdeaPlaces, a product company that builds and runs a portfolio of software products. TourCockpit is one of them, and it has a working office behind it rather than a market study.

The fastest way to reach a person is the [contact page](/contact), or chip@tourcockpit.com.