Aviation — aircraft components trading and MRO
Aircraft parts procurement: from inbox chaos to a managed pipeline
An AI agent reads incoming RFQs, compares supplier quotes and checks trace documents; an operations system moves each deal through mandatory stages.
- Status
- Pilot
- Timeline
- two phases: AI loop, then the operations system
- Stack
- n8n
- IMAP
- Telegram Bot API
- Google Sheets API
- React/TypeScript
- Supabase (PostgreSQL, RLS)
The task
Aircraft component procurement ran on email and spreadsheets: RFQs were parsed by hand, quotes compared manually, and five departments worked in parallel with no stage control or access rules. Delays are expensive here — an AOG request means a grounded aircraft, and every shipment needs FAA 8130-3, EASA Form 1 or COC paperwork checked and alternate P/Ns considered.
What we built
- We put an AI agent on the working mailbox: it monitors incoming mail over IMAP and extracts component requests — P/Ns, alternates and analogs across Rotables, Expendables and LLP.
- The agent collects supplier quotes, compares price, lead time and terms, verifies trace documents and notifies the team in Telegram. This loop ran on a live procurement process.
- Industry specifics are built in: AOG priority, exchange programs, Incoterms and logistics handling.
- We designed a procurement operations system: each deal passes mandatory stages — manager, procurement, logistics, customs, finance — with stage order and role access enforced at the database level.
- We shipped a working interface prototype: 11 screens, 6 roles, an order audit log, a full-text parts catalog and management analytics.
Outcome
- Full loop
- full AI loop on a live procurement process — from incoming RFQ to team notification; confirmed by the owner
- 3
- types of trace documents checked by the agent: FAA 8130-3, EASA Form 1, COC; counted from the owner's brief
- 6 × 6
- roles and deal stages in the operations system, enforced in the database schema; counted from prototype code
- 11
- screens in the working prototype — from order card with action history to management analytics; counted from code
More cases
Distribution · Partner networks
In productionA sales and support platform for a distributed partner network
Partners ask who on their team is inactive and what blocks the next level — and get numbers for their own part of the network only, enforced at the SQL level.
- 20 of 21
- UAT checks passed on the client's live back-office database (reconciliation protocol); one partial — no last-activity date in the data
- 10 of 10
- question categories from the assistant behaviour spec (~25 scenarios) implemented; one sub-item outstanding (checklist count)
Music tech · SaaS
MVP in operation (closed launch)Music releases without missed deadlines
Release ops for independent labels: 9-stage lifecycle, pitching deadlines for 12 stores, AI drafts with human approval. Zero to production-grade in 7 weeks.
- 7 weeks
- from first commit to a production-grade stack with Vault, encrypted backups, SLOs and a move to a Russian data centre (265 commits)
- 16 days
- from project start to an investor presentation with a live product demo
IT consulting · Lead qualification
In-house productA pilot plan for the visitor, a qualified lead for sales
We replaced the contact form with an AI consultant: it interviews the visitor, returns a pilot plan with KPIs and risks, and sales gets a lead with budget and timeline.
- 1 day
- Working MVP — frontend, backend and deploy configs — built in a single day
- 16 days
- From first commit to production with HTTPS and an issued certificate on its own domain
Estimate the impact on your own figures
AVA is a process-economics calculator. In a couple of minutes it shows whether a similar task pays off in your case — before any call and with no commitment.
Estimate the impact with AVAHave a similar task?
Describe the process and the data you have. We will tell you what can be measured in money and what cannot — before any work starts.
or email us directly: hello@xteam.pro