Step 1 of 4
You ask in natural language
"Top 10 customers by margin this quarter." "Which customers had the most adjustments last month?" "Carrier-cost trend on USPS Priority over the last 90 days?"
The overarching layer
Orbit AI sits across the platform as the overarching analytics layer. Ask the question; get the answer in seconds — without a data-pipeline project, a data engineer, or a dashboard that ships nine months late.
The metering pipeline produces the data Orbit queries — same source of truth.
Flagship Adjustment ReconciliationOrbit answers questions about which clients drive the most adjustments and where margin leaks.
Sibling Claims & DisputesEligible-claims data answers Orbit queries about recovery trends and adjustment categories.
It's a natural-language query interface, not a chatbot. You ask a question; it returns numbers and the rows it ran against. The conversation surface is incidental — the answer is the point.
No. Orbit's schema knowledge ships pre-trained on RocketFuel's billing model. Your customer-specific data is queried at runtime and never sent outside our infrastructure for training.
Orbit returns the rows it queried alongside the numeric answer — verify the math directly. For ambiguous queries, Orbit asks clarifying questions before returning a result.
The standard playbook: pull data out of the WMS and the carrier-billing system, load into a warehouse, build dashboards, train the team. Costs six figures, takes nine months, and the dashboards usually answer questions nobody is asking by the time they ship. The questions 3PL operators actually ask — which customers are priced too thin, what's the margin trend on USPS this quarter — are answerable in real time if the data lives in one place. The metering pipeline is that one place. Orbit is the query surface.