Request & Quote
Capture the trip once and keep pricing authority visible.
For black car & chauffeur service operators
Run a black car service from quote to completed ride.
Octo HQ is being developed around Octo Prestige Chauffeurs: private passenger rides, airport transfers and hourly chauffeur service. The system design connects customer requests, quotes, reservations, chauffeur and vehicle assignments, affiliate trips and payments.
Portfolio Environment•Development System•Synthetic public-safe views
OCTO HQ / OPERATING MODELDEVELOPMENT SYSTEM
INTAKEDirect + affiliate
SERVICEAirport + hourly rides
CONTROLQuote + coverage
PAYMENTSDue + received
The operating problem
A reservation needs more than a place on the calendar.
A passenger booking can involve a pickup time, flight details, vehicle class, chauffeur, affiliate partner and payment terms. When those details live in separate messages and calendars, the owner has to piece the trip together. The design keeps them attached to the same reservation as it moves from quote to completed ride.
Coverage & Booking
Resolve availability, chauffeur, vehicle and source-specific constraints before commitment.
Trip Identity
Keep one stable reservation or trip reference across the workflow.
Execution
Keep pickup details, chauffeur updates and completion checks attached to the reservation.
Money Evidence
Keep expected, due and actually received states separate.
Retention
Track which past clients are ready for a follow-up or another booking.
See which passenger rides still need coverage.
This Octo HQ development capture shows a synthetic request in the coverage queue. Coverage review is separate from confirming a booking or sending a passenger message. Open the image to inspect the interface.
System design / black car passenger service
One trip lifecycle. Different source rules.
These views use synthetic labels and invented records. They explain the operating model without exposing passenger, reservation, affiliate-pricing or payment data.
Direct bookings and affiliate trips need clear handoffs.
Keep the booking source, passenger itinerary and payment terms attached to the reservation.
DIRECTWebsite / email / account requestOcto controls quote, client relationship and payment path.
→
OCTO TRIP RECORDOne reservation referenceBooking source · passenger itinerary · chauffeur · vehicle · trip status · payment · next step
←
AFFILIATE10X / Savoya reservation contextExternal source remains distinct; Octo preserves its own internal record.
10X and Savoya are shown only as external affiliate / reservation-source context. They are not represented as Ordo clients, endorsers or portfolio companies.
Scheduled time does not automatically mean completed work.
The owner view should show whether the ride is requested, booked, assigned, completed or waiting on payment—and retain the details behind that status.
01RequestTrip need
→
02QuoteRate source + review
→
03CoverageOperator + vehicle
→
04BookReservation confirmed
→
05ReadinessPre-trip checks
→
06TripActive service
→
07CompleteEvidence required
→
08MoneyPayment evidence
→
09RetainRepeat booking
Check the rate, vehicle and coverage before confirming the quote.
Review the service type, applicable rate and any affiliate costs before promising a price to the customer.
RATE SOURCECurrent rate sheetWhich pricing source applies?
→
SERVICE CLASSSUV / Sedan / SprinterWhat is actually being sold?
→
ASSIGNMENTOwner / affiliateWho will cover the ride?
→
ECONOMICSCosts confirmed?Costs and margin available?
→
DECISIONApprove or manual reviewNo automatic commitment when key inputs are unknown.
See the exceptions that need attention, not another wall of status.
The records and counts below are invented solely to demonstrate the intended owner experience.
OCTO HQ / DEMO DATABlack Car Service Exceptions
SYNTHETIC VIEWQUOTE REVIEW2demo requests
STALE STATUS1past scheduled time
MONEY EVIDENCE2pending review
FOLLOW-UP3repeat-booking queue
TripSourceExceptionNext control
DEMO-201AffiliatePayout evidence pendingVerify receipt
DEMO-204DirectAffiliate cost unknownManual quote review
DEMO-208DirectTrip completeRepeat-booking follow-up
DEMO-211AffiliateStatus still confirmedReconcile completion
Synthetic demonstration. IDs, counts and status combinations are invented and are not Octo, 10X or Savoya performance data.
What this example illustrates
What the Octo HQ example shows.
Design scope: the diagrams describe direct and affiliate intake, reservation and trip records, quote review, completion checks and payment evidence. The synthetic views illustrate an intended architecture; they do not verify working integrations or operational records. Implementation and production-readiness claims require separate supporting evidence.
Not claimed yet: quantified time saved, fewer missed trips, higher conversion, increased affiliate profitability, higher repeat-booking rate, or a production-ready unified Octo HQ runtime.
Evidence label
Portfolio Environment + Development System
Octo remains its own operating business and source of truth. Ordo uses the environment to design, test and document reusable operating patterns.
Reuse-first architecture
Build around the realities of passenger service.
Passenger itineraries, chauffeur assignments, flight details and affiliate payment terms belong to the black car business. Shared tools for approvals, customer follow-up and history should support that workflow and keep its records separate.
Request SourceDirect or affiliate
→Octo Trip RecordStable internal identity
→Evidence & ExceptionsCompletion, money, follow-up
→Owner DecisionOnly when authority is needed
Coordinate the operation
Keep the passenger, chauffeur and office working from the same trip details.
Start with your booking process: where requests come from, how rides are assigned, who confirms completion and how you track payment.