RevenuePilotby Foxes TechnologyDay tours, boat trips, guided experiences and transfers all sell against a fixed departure time, a fixed vehicle and a fixed guide. RevenuePilot reconciles what your booking system already knows, then returns three ranked, quantified decisions while there is still time to act on them—each bounded by guardrails you configure.
These are the moves a revenue-minded operator already makes by instinct at the end of the week. RevenuePilot's job is to make them earlier, quantified, and defensible.
A departure running ahead of its usual lead-time curve is the one most often left underpriced, because nothing about it looks like a problem. Pace and remaining capacity are compared against cohorts for the same product and window, so a strong departure is surfaced as a decision instead of quietly selling out at the opening price.
A blanket promotion trains the market and drags every other departure down with it. Decisions are scoped to the departure and option that are actually soft, and every proposal is held inside your price floor, so recovering one weak sailing cannot become a permanent reset of the headline price.
The same seat sold direct and through an OTA are different commercial events once commission and variable cost are applied. Where verified cost and commission data exist, decisions are ranked on contribution. Where cost coverage is incomplete, the gap is flagged and the margin view is withheld rather than filled with an assumption.
The cost of a slow departure is fixed the moment the guide and vehicle are committed. Reconciled bookings and cancellations are read on your sync cadence, so a deviation surfaces as a bounded decision with the arithmetic attached rather than as a discovery on the morning of departure.
The queue is deliberately bounded to three decisions so a review stays finishable. Nothing in this loop changes a price by itself.
One canonical source connector per organization in v1. Generic API and CSV are available now; Egypt Excursions Online runs as a controlled pilot and the Foxes Booking Engine is available as a read connector. Rezdy and Bókun are certification-ready.
Products, options, departures, bookings, cancellations, costs and commissions are reconciled as seven canonical contracts. Anything stale or unreconciled is reported as a gap rather than substituted with a default.
The revenue calendar shows pace, remaining capacity and price at departure level. Departure times carry an explicit timezone and a UTC instant, so an early-morning transfer is never off by an hour on a shared screen.
Each decision states the move, the departure and option it applies to, the economics behind it, the uncertainty, and the policy boundary that shaped it. Weakly evidenced signals are withheld instead of shown with false precision.
The operator holds the action. In the current posture that means taking the move in your own booking system; approvals, declines and the reasoning are captured either way, so a decision not taken is still part of the record.
Source, economics, uncertainty, policy boundary and the operator action are stored together in an append-only trail, which is what lets you defend a pricing decision to a partner or a board weeks later.
A product average hides the departure that mattered. Everything RevenuePilot reconciles is keyed to the departure and option a guest actually books.
Effective capacity on a tour is set by vehicle seats, guide availability and the option mix you publish—not by a shelf that can be restocked. RevenuePilot works from the capacity your source system publishes for each departure, reconciled against bookings and cancellations, so the remaining-seat figure behind a decision is the one your operations team is already working to.
Direct and reseller bookings carry different economics for the identical seat. Where verified variable cost and channel commission exist for a product, decisions are ranked on contribution rather than on headline revenue. Where they do not, the coverage gap is named explicitly and the ranking says so.
A decision receipt records the source snapshot, the economics used, the uncertainty, the policy boundary that applied and the operator action required. The audit trail is append-only, so the history of what you were told and what you chose cannot be quietly rewritten.
| Canonical contract | What it establishes | What it unlocks |
|---|---|---|
| Products | The experience you sell and its identity in your source system | Portfolio scope |
| Options | Ticket and seat variants such as adult, child, private or transfer add-on | Option-level pricing lookup |
| Departures | The dated, timed instance with its capacity, timezone and UTC instant | Pace and remaining capacity |
| Bookings | Confirmed demand attributed to a departure and option | Lead-time cohorts |
| Cancellations | Demand that was released back to the departure | Honest remaining capacity |
| Costs | Verified variable cost for the departure | Contribution ranking |
| Commissions | Channel commission applied to the booking | True channel economics |
An operator should be able to evaluate the decision quality without handing over the price list on day one. That is the default, not a concession.
No. External price writes are disabled by default and live price execution is currently disabled globally. Recommendations are advisory: you review the move and take the action in your own system. Turning execution on later requires a certified connector, shadow qualification, policy review and your explicit approval.
Yes, with an honest limit. Pace, capacity and channel mix are reconciled from bookings and departures regardless. Contribution ranking applies only where verified variable cost and commission exist; for everything else the coverage gap is flagged and the margin view is withheld rather than estimated from a default.
Generic API and CSV are available now. Egypt Excursions Online runs as a controlled pilot and the Foxes Booking Engine is available as a read connector. Rezdy and Bókun are certification-ready. RevenuePilot v1 supports one canonical source connector per organization, so the reconciled picture has a single authority.
Yes. Roles cover owner, admin, revenue manager, analyst and viewer, so an analyst or viewer can work the evidence without holding an action. High-impact actions require TOTP step-up. Seat counts run from two users on Starter to five on Growth and fifteen on Scale.
Start read-only with a scoped portfolio and agreed guardrails—no price writes are needed to evaluate the decision quality. Production card collection is currently disabled, and approved founding operators can create a verified account without being charged.