Client-safe proposals
Broker pricing separated from supplier cost. Immutable revisions.
Platform capabilities
From trip intake and operator records to private reply links, comparable quotes, client proposals, airport services and booking handoff. One workflow a broker can explain to a client.
Quote truth layer
All-in, conditional and indicative pricing stay distinct. Unresolved costs stay visible. The sourcing record supports commercial judgement instead of replacing it.
Broker pricing separated from supplier cost. Immutable revisions.
Revocable links with view and decision evidence.
Acceptance becomes an operations checklist on the same trip.
These are separate from the operator API. Each one is attached to the airports on the enquiry.
Airport handling is matched to the trip airports and kept with the same enquiry.
Flight-support providers sit beside the operator shortlist. They are not mixed into the operator list.
Catering is requested for the itinerary airport, not from a second inbox.
Passenger and crew transport stays with the airports already on the enquiry.
More across the same trip
Create branded proposals without exposing protected supplier relationships or internal cost.
Every commercial revision is versioned so margin and client pricing changes remain traceable.
Generate a client-ready PDF from the exact released proposal snapshot.
Send revocable, expiring proposal links with view and decision evidence.
Capture questions, acceptance or rejection as explicit workflow events.
Turn an accepted option into an operations handoff without recreating the trip manually.
Passenger manifest, permits, handling, catering, transport, insurance and payment evidence live in one checklist.
Match reviewed handling providers directly to the airports in the trip.
Keep catering options separate from aircraft sourcing and attach them to the exact itinerary airport.
Source flight-support providers alongside operators without mixing service companies into the operator database.
Retain source, import batch, version and review context for normalized supply records.
Merge repeat operator identities while preserving the evidence that created the canonical record.
Broker organizations remain isolated while approved platform supply can be shared securely through the network.
Critical sourcing, response, proposal and operations actions create durable evidence.
Outbound communication is designed around preview, suppression, frequency limits and explicit approval.
Trip, supplier and response workflows are designed to remain usable away from the office.
The data model is prepared for integrations and licensed enrichment without sacrificing source evidence.
Licensed enrichment is separated from owned truth and cannot silently overwrite reviewed data.
Suggestions only include operators whose aircraft can fly the trip: distance, capacity, runway length, paved or not, operating hours, and other airport limits.
Jet Intelligence tracks thousands of private jets and can reach operators outside the area when they have an empty leg or can add the flight, only if their aircraft can operate it.
Runway length, paved or unpaved surface, operating hours, slots, and customs context are on the desk before an operator is asked.
A departure time can be checked against known airport limits. Dispatch stays with the operator.
Instrument approaches on file for an airport are listed when a licensed record includes them.
Material changes to airport facts can be reviewed on the desk, and a broker can subscribe to those changes.
Questions
Core features include trip intake, operator and aircraft sourcing, RFQ waves, secure operator responses, quote comparison, client proposals, airport services and booking handoff.
Yes. Trip and proposal revisions preserve earlier evidence rather than silently overwriting it.
It distinguishes all-in, conditional and indicative pricing and keeps unresolved cost items visible.
Yes. They are modeled as separate airport service supply and can be attached to trip airports.