SupplierKit · Travel operations · decision-support AI
Making operational decision-support AI trustworthy
Travel coordinators sat on a quiet operational risk: supplier documentation, insurance, and verifications scattered across inboxes, shared drives, and individual employees’ memories. Chasing renewals and proving a supplier was actually ready was slow, manual, and easy to drop, and a lapse often surfaced at the worst possible moment.
Domain
Travel operations
Type
Operational system + managed service
Focus
Readiness, verification, continuity
In one line
SupplierKit is an operational readiness and supplier documentation system for travel teams whose coordinators are buried in scattered paperwork, renewals, and supplier verification.
What it demonstrates
The system we built
We built an operational readiness system organized around a clear model: chase, review, monitor. SupplierKit collects supplier documentation, moves it through human-in-the-loop review, then monitors status and renewal timelines so nothing silently expires. It pairs a software layer with a managed service, so the system helps carry the work, not just display it.
Why AI was useful
Most of this work is coordination, extraction, and follow-through at scale. AI is useful for reading and classifying documents, drafting the chase, flagging what is missing or expiring, and summarizing readiness, while humans stay on the judgment calls of verification and exceptions. The result is leverage on the parts that drain coordinators, with the human check kept where it matters.
What made it trust-sensitive
This is compliance-adjacent work, so the bar is high. SupplierKit is built to be a system of record: every document, decision, and status change is traceable, human review sits on verification, and the system fits alongside the operational tools a team already uses. Trust here comes from accuracy, auditability, and respecting the workflows people depend on.
The outcome
A system of record travel teams trust. Documents move through human-in-the-loop review, status and renewal timelines are monitored, and the team finds out what is expiring before it becomes a problem.
Product decisions
The choices that shaped how it behaves
Chase, review, monitor
The whole product is organized around a workflow coordinators already recognize, which makes adoption feel like relief.
Human-in-the-loop verification
Automation handles collection and chasing; a human stays on the verification decision, because that is where accountability lives.
System-of-record thinking
Status, history, and documentation are treated as a durable record, so the knowledge stops living in inboxes and heads.
Built around existing systems
SupplierKit wraps and coordinates the tools a team already runs on.
Architecture
How it is put together
Documentation pipeline
Intake, extraction, and classification of supplier documents, with chasing automated where it is repetitive.
Review workflow
A human-in-the-loop review layer where coordinators verify, approve, and resolve exceptions.
Monitoring and status
Readiness and renewal tracking that surfaces what is expiring or missing before it becomes a problem.
Managed service layer
A service operation that runs alongside the software so the workload is genuinely reduced.
Current status
SupplierKit is an active Hunter Green system, built for travel teams managing supplier documentation, verification, and renewal workflows.
What this proves about Hunter Green
SupplierKit shows Hunter Green can build practical systems for complex operational work: mapping messy real-world workflows, creating visibility, reducing coordination burden, and preserving knowledge that would otherwise live in inboxes, shared drives, and individual employees’ heads.
More work