# Launch your airline in **eight weeks**

From contract signing to first commercial flight. Sales channels live by week three. Every integration - payments, CUPPS, regulators, distribution - handled by us.

## What slows down<br/>every airline launch
AOC dates are committed. Aircraft are leased. Routes are filed.<br/>Then the PSS conversation starts, and everything moves in slow motion.

### Five vendors, five contracts

Legacy PSS, separate RMS, separate DCS, separate IBE, separate payment integration. Five SLAs, five timelines, five teams pointing at each other when something breaks.

### No team to wire the integrations

Payment gateways, CUPPS at every airport, PNRGOV and APIS to your regulator, SMS, accounting exports. Startup airlines don't have the integration engineers, and most vendors don't include it.

### Legacy timelines kill runway

Traditional PSS implementations run 12-18 months. Most startups can't afford a year of burn before generating revenue.

### AOC date is fixed. Your vendor's isn't

Your launch date is committed to a regulator, to lessors, to passengers. When the vendor slips, you slip, and the slip is invisible until it's too late.

## How we start
Three steps to a signed contract and a launch date you can plan against.

### Discovery call

Thirty minutes. We walk through your stage, fleet, routes, and target launch dates. By the end of the call we know whether the timeline is feasible and what lead-time items - CUPPS access, regulatory approvals - need to start moving.

### Detailed scoping

We gather the technical and operational details that determine cost and timeline - payment providers, airport infrastructure, regulators, distribution channels, and the full integration list. Every dependency surfaced before we quote.

### Proposal

Fixed timeline. Fixed implementation fee. Defined deliverables and milestones. Sign-off and you're on the calendar.

## Before you decide
Answers to the questions we hear most from startup airline teams.

### We don't have AOC yet. Can you still work with us?

Yes. We've worked with airlines at every stage from formal AOC application to post-certification. The eight-week timeline starts at contract signing, regardless of where you are in certification. We'll match the build schedule to your AOC and route launch dates.

### What does "every integration" actually include?

Payment service providers (Stripe, regional PSPs, mobile money), CUTE/CUPPS at your airports, regulatory messaging (PNRGOV, APIS, PAXLST, PNL/ADL), SMS providers, accounting software, OTAs and metasearch, and GDS if needed. We map your specific list during scoping and contract them into the implementation. No change orders.

### What if our launch date slips because of AOC or aircraft delivery?

The Farel timeline is built around your launch date, not against a generic schedule. If your AOC slips or aircraft delivery moves, we can shift the operations launch phase accordingly. The sales launch phase can also be brought forward - selling tickets ahead of AOC is often advantageous.

### Who handles training for our staff?

We do. Booking agents, customer support, finance, and airport ground staff all receive role-specific training - online for the platform-side roles, on-site for airport staff working with DCS and ground equipment. Most users are operational after a single 15-minute session.

### What happens at go-live?

Two weeks of hypercare with accelerated-response support starting the day of your first flight - dedicated channel, sub-hour response on critical issues. After that, standard SLA: 24/7 critical support with 10-minute to 2-hour response, and 90% of all tickets closed within two business days.

### Can we name customers you've launched this way?

Asman Airlines launched as Kyrgyzstan's national carrier on Farel - full system go-live in 8 weeks, 13 routes at launch.