Guided workflow builder for aviation MRO teams

The moment this becomes a real problem is when an airline brings on a new line maintenance tech or a regional MRO hires a planning coordinator — and that person spends their first three weeks reading manuals instead of doing the job they were hired for. The training gap isn't just slow; it creates scheduling risk when you're short-staffed and the new person can't yet navigate the system independently.

The gap persists because the MRO software vendors are primarily sold to IT directors and operations VPs, not to the technicians and planners who actually live in the system daily. The buyer signs off on the contract; the user suffers through the learning curve. Nobody in the decision chain has enough pain to push vendors to invest in better onboarding — so the vendors ship more features instead.

What's missing isn't documentation — there's plenty of that, which is exactly the complaint: 'extensive manual reading is required.' What's missing is context-sensitive guidance that maps to what a specific role needs to do today, not a full system overview. A planning coordinator doesn't need to learn the parts inventory module in week one. A line tech doesn't need the financial reporting screens. But all existing onboarding treats every user as if they need to learn everything.

This is a recurring business because every MRO operation has turnover, every implementation brings new staff, and every software upgrade resets part of the learning curve. A training and guided-workflow layer that sits on top of AMOS or AirData — without requiring the vendor's cooperation — would recur as a seat-based subscription every time headcount changes.

What to build

Build a browser-extension-based overlay that detects which MRO software screen a user is on and surfaces role-specific step-by-step guidance and checklists, pulling context from a configurable task library that MRO training coordinators maintain without writing code.

Where to start

Start exclusively with AMOS, which has the loudest complaints about implementation difficulty and the largest installed base, so your first ten customers are findable in the same user communities and conferences.

The hard part

Detecting screen context reliably across different MRO software versions without official API access — any DOM-level change in a vendor's UI update could break the overlay, forcing you into a constant maintenance cycle that kills your margins.

How it makes money

Per-seat monthly subscription charged to the MRO operator, with a one-time setup fee for the initial task library configuration — expansion revenue comes when customers add seats after a new hire cohort.