# Run your airline on a system, not a **spreadsheet**

Bookings, payments, manifests, and regulatory messages in one record. Live in 2–8 weeks, run by the team you already have.

## What running by hand<br/>costs you
Paper, spreadsheets, and phone calls work until the day you add a route, a station, or an aircraft.

### One book, one desk

Availability lives in one place. Three agents on three calls wait for the same page.

### Demand you never see

A full flight or a missed call leaves no trace. You can't add a rotation for passengers you never counted.

### Compliance by hand

Manifests, load sheets, and API/PNR typed per flight. It holds until the first warning letter.

### Growth means headcount

What worked at two aircraft breaks at four. Every new station needs another person on the phone.

## What changes, function by function
The same airline and the same team, working from one record.

## From the last paper booking<br/>to the first live flight
Your flights keep operating while we build. Passengers notice the change the day online booking opens.

### Scoping

Routes, stations, fare rules, passenger categories, payment provider, and regulators mapped before we quote.

### Configuration

Schedule, aircraft layouts, fares, and ancillaries loaded. Payments and regulatory messaging connected.

### Open bookings moved

Forward bookings from the book or the sheet are loaded into Farel by our onboarding team before cutover.

### Training

Role-specific sessions for reservations, airport, and finance staff. On-site for airport teams.

### Go-live and hypercare

Online sales open and every station switches to the live record. Two weeks of accelerated support follow.

## Three airlines that started<br/>where you are
Paper, email, and spreadsheets on day one. One system at go-live.

## Before you decide
Answers to the questions we hear most from airlines moving off manual processes.

### We have no IT team. Who does the setup?

We do. Configuration, payment and regulatory integrations, migration of active bookings, and staff training are part of the implementation. You don't need engineers on your side.

### What happens to the bookings we already hold?

We move them. Active bookings are loaded into Farel from your paper records or spreadsheets as part of implementation, so passengers booked before cutover check in like everyone else.

### Do we have to stop selling during the switch?

No. Cutover is planned around your schedule, with a parallel run if you want one.

### Our operation has rules a standard system won't know. Can Farel handle them?

Usually it already does. PSO passenger categories, resident and student fares, actual passenger weights, charter blocks, and tour operator allotments run in production today. If something is missing, we scope it before we quote.

### How long does training take?

A new operator can run the full check-in and boarding flow after a single 15-minute session. Reservations and finance staff train online. Airport staff train on-site.

### How is it priced for a small carrier?

You pay per boarded passenger plus a one-time implementation fee. Every module is included, so your cost follows your traffic. The pricing page has the full model.