Services

Software development with AI

Custom software for airlines and charter operators, written with AI tools and checked by engineers who know aviation.

For Federal Aviation Administration (FAA) Part 135 and 121 operators and Canadian Aviation Regulations (CAR) 704 and 705 operators who need software that no off-the-shelf product provides.

Our engineers write software with Claude Code, Cursor and Copilot. The AI writes most of the code. Our engineers decide what gets built, review every change, and own the result once it runs in production.

That changes the economics of custom software for an operator. The part that used to take a team of developers months now takes one engineer and a person who knows the operation a few weeks. Websites a traditional agency quotes in months, we ship in weeks: the WM Aviation site went live in four. A charter quoting process that used to mean up to four days of spreadsheet work now reads the request from email, prices the trip and produces a customer-ready Portable Document Format (PDF) quote in minutes.

It also changes what is worth building. For thirty years the answer for an aviation operator was to rent, because building was expensive and the market was too small for anyone to build for it. Now the hard part of good aviation software is knowing how dispatch actually thinks and what your quoting logic really is. You already have that. We turn it into software you own.

What we build

Websites and web apps

Public sites and signed-in portals hosted in Azure, which your team updates without calling us.

Internal tools

Apps shaped around how your operation runs, so staff stop copying data between spreadsheets and systems.

Minimum equipment list (MEL) and compliance documents

AI that reads and cross-checks MEL revisions and other technical documents, with a qualified person approving the result.

How our MEL passed Transport Canada

Charter quoting

Software that reads each trip request from email, prices it against airport fees, crew overnight costs and cross-border tax rules, and produces a customer-ready PDF quote in minutes.

How AI does the work

The AI writes the code

We describe the tool in plain language, the way you would explain it to a sharp new hire, and the AI writes working code. Most of the typing in a ForIT project is done by Claude Code.

An engineer steers and checks

A ForIT engineer decides what gets built, reviews every change before it ships, and tests that it works, does not break anything else, and is ready for production. A person is accountable for every line that goes into use.

Guardrails, not trust

Our own development environment runs Claude Code under lifecycle hooks that block dangerous operations, such as a Domain Name System (DNS) change or a write to a production mailbox, until a person confirms them. Client work runs under the same rules.

The same tools run ForIT

We run our own company on AI agents: Claude Code sessions on one server, a gateway of custom tools they can call, and one consolidated database. We build for clients the way we build for ourselves.

How it works

  • 1We start from a real task that is slow or error-prone today, not from a feature list.
  • 2An engineer builds a working version with AI tools and reviews every change before it ships.
  • 3We deploy it in your environment and keep it running, or hand it to your team with the code and documentation.

Where we have done it

WM Aviation

Their Power Pages site was slow and hard to update. We replaced it with a Next.js site on Azure that went live in four weeks.

Transport Canada MEL approval

Transport Canada approved our AI-generated MEL after two rounds of feedback. The reconciliation step found discrepancies that manual review had missed.

Charter quoting at Great North Airlines

Quotes were built by hand across a set of Excel files and could take up to four days. Now they take minutes.

Questions operators ask

What does ForIT build with AI tools?

Websites and signed-in portals hosted in Azure, internal tools, Minimum Equipment List (MEL) and compliance document tools, and charter quoting software. The AI writes most of the code; our engineers decide what gets built and review every change.

Is AI-written code safe to run an aviation operation on?

The code is reviewed and tested by an engineer before it ships, and a person is accountable for it. Transport Canada approved a Minimum Equipment List that was primarily AI-written, after two rounds of feedback and with a qualified person approving the result, and the reconciliation step found discrepancies that manual review had missed. That is the standard we hold the rest of our work to.

Which AI tools do you use?

Claude Code is our default development environment. We also use Cursor and Copilot, and other models where they are stronger, such as image work. The assistant on this site runs on Anthropic models. We keep the choice open because the tools change every few months.

Who owns the code, and who runs it after launch?

You do. The code lives in a repository you can take with you, hosted in your own Azure environment or ours, and we hand over the documentation with it. After launch we keep it running in your environment, or hand it to your team with the code and documentation. Nothing about the way we build locks you into ForIT.

How long does a project take?

A public website, weeks rather than months. WM Aviation's went live in four. An internal tool, a few weeks from the first task to something your team is using, with adjustments after that. A longer build, such as a quoting or crew system, is done in stages that each go into use on their own.

What does it cost compared with a traditional developer?

A fraction. AI removes most of the typing, so we bill for engineering judgment and time on your operation rather than hours of code. On the first call we tell you where we would begin and what it would cost, and ongoing work is month to month.

Should we build, or keep buying?

Build when the tool touches what makes your operation different: your dispatch workflow, your pricing logic, the data you want to hold yourself. Buy when it is a commodity that already works, such as email or accounting. We are vendor agnostic and will tell you when buying is the better answer.

Talk through what's slowing your team down

Start with a 30-minute call. We'll tell you where we'd begin and what it would cost.