Aerospace operations softwareTurn parts requests into work the team can act on.
Homarjo builds software for aerospace parts teams. Triage structures RFQs, purchase orders, status requests, warranty claims and AOG messages; we fit the rules, data and integrations to each operation.
- Case
- Action
- P/N
- SA-2210-4
- Qty
- 2
- A/C
- ATR 72-600
- MSN
- 1234
Dear Laura, thank you for your request. Our quotation:
• SA-2210-4 × 2 — {{ price }}
The problem
The urgent email looks like every other email.
Aerospace parts support teams run on a shared inbox: requests for quote (RFQ), purchase orders, “where is my order?” chases, warranty claims — all mixed together, all day, often in multiple languages.
The urgent ones are buried. An aircraft-on-ground request can look like every other message until somebody reads it.
Teams re-read, re-type, re-key into spreadsheets and ERPs; quotes take days; deadlines live in people's heads.
First module
Homarjo Triage
Triage with AOG priority
Every inbound email is read the moment it arrives and classified: RFQ, Purchase Order, Status Update, Warranty Claim. AOG urgency is flagged and a response deadline is computed from your own lead-time rules — AOG always jumps the queue.
Replies drafted, prices one click away
The reply is drafted in the customer's language, greeting them by first name. RFQ replies arrive as a fill-in quote; click a quantity tier from your own Excel price lists and the price drops into the draft — with its provenance (file → sheet → cell) shown for verification.
A workbench for the whole team
Assign cases, track status, share notes and to-do checklists. Focus mode gives each agent a personal queue, most urgent first — work one case at a time, mark done, next.
Works alongside Outlook and Gmail
Categories appear as labels and folders in the inbox the team already uses. Adoption can be gradual — value starts on day one even if agents never open the dashboard.
How we work
Working software, fitted to the operation.
Choose the workflow costing the team the most time
Connect the mailbox and the data it depends on
Fit categories, rules, approvals and roles to the operation
Run it with the team, then extend what proves useful
The core stays common. The fit is yours.
How deployments workProduct core
What stays standard. What adapts.
We maintain one product foundation instead of rebuilding from scratch for every company. Each deployment is configured around the parts operation it serves.
Shared core
- Email, case and task workflow
- Roles, audit history and access control
- Isolated company data
- A maintained interface and runtime
Fitted to the operation
- Categories, priorities and deadlines
- Reply and approval rules
- Pricing, terms and commercial data
- Mailbox, ERP and workflow integrations
Security & data
One isolated data store per company.
Your emails, prices and CRM data live in their own separate store — physically separate files, not rows in a shared database. Never shared, never sold, never used for other customers. EU hosting; self-hosting available on request.
How we handle your dataAerospace parts operations
Built for the desk where RFQs become orders.
Suppliers, parts traders and MROs all work with different rules, but the pressure is familiar: shared inboxes, spreadsheets, time-sensitive requests and context spread across systems.
How Triage fits parts tradersMost parts teams do not need another system of record. They need the work between their existing systems to move. Read why →
Bring us the workflow that slows the team down.
Start with Triage or a closely related aerospace parts operation. We will show what stays standard and what should be adapted.
See it on synthetic data first — nothing of yours leaves your inbox until you say so.