The ForIT Collective · what we're cooking

SaaS code is dead. The services firm wins.

AI now builds apps cheaply. The hard part — the only part worth paying for — is running them well in your operation. The Collective is the apps we're actively building together with operators in our network. Code stays in your tenant; we run it with you.

What we're building

01
Active build · FAA reviewed

SMS — safety reports drafted by AI

Our pre-ForIT FAA review of an RPA + GenAI safety pipeline (email → WBAT report drafting) was called "best in class" — explicit green light to keep going. We're rebuilding it now as a platform. The Transport Canada AI-MEL approval at Great North uses the same toolkit; combined, that's the regulatory track record to ship safely.

  • Status: actively building — leveraging the FAA-reviewed pipeline
  • Replaces $25K+/yr safety vendors at most operators
  • Multiple operators in our network have flagged this as a top-three priority
02
Now scoping

Fueler AI — one brain across your scheduling, trip-support, and fuel-price stack

One AI agent reads the scheduling system's legs, trip-support handler quotes, and fuel-price services, then recommends the optimal fuel stop in the dispatcher's existing tool — not in another dashboard nobody opens. Pilot scope: pick 5 routes, ship in 30 days, prove the per-leg savings.

  • Status: scoping with an anchor operator
  • Multi-vendor fuel/handler price normalization
  • Per-leg fuel-stop suggestions inside the existing ops view
03
Early concept · operator interest

MRO — break the per-tail/per-month CAMP model

Maintenance tracking is one of the highest per-tail SaaS line items in the industry, and the incumbent UX is two decades old. Multiple operators have expressed interest in a Collective-funded rebuild; ForIT runs the program with their DOM, the early operators shape the spec because they're early.

  • Status: early concept — looking for 2–3 operators to shape v1
  • Cost target: significantly under the incumbent per-tail rate
  • AI-native: structured records, audit trail, work-card automation

How it differs from the shipped portfolio

Shipped software runs in production today. The Collective is the next layer.

Manuals, CrewRecords, Quoting, and Support are running in production at our existing clients today. The Collective is what's next: aviation platforms we're actively building, with input from the operators who'll use them first.

The thesis is the same — code has no moat; the services firm that runs it well does — but the difference between "shipped" and "cooking" matters when you're picking what to bet on. That's why the status badge on each card is honest.

How the Collective works

Operator-funded. Built in your tenant. Run with you.

Tenant-resident

Your code in your cloud

Collective platforms are deployed into your Microsoft tenant. No vendor lock-in, no data exfil, no "we shut down and your workflow dies."

Peer-funded

Tech Leaders Group economics

Build costs split across early operators. You get enterprise-grade aviation software at the marginal cost of running it, not the fully-loaded cost of building it alone.

Services-led

We run it, you use it

ForIT handles the upkeep, the integrations, the AI model changes, the regulator conversations. Your ops team uses the product; our team runs the platform.

Want to shape the next one?

Early operators get input on scope, priority features, and integration targets. If any of the three above solve a problem you're living with, there's room at the table.

No pricing commitment · operator-funded model · code stays in your tenant

Cart (0)

Your cart is empty

Browse Store