Controlled demo access
BackOfficeFleet is easiest to understand when each visitor follows the workflow they own: dispatch movement, carrier readiness, packet verification, finance release, or executive triage.
Marketing, positioning, and a guided entry into the BOF operating model.
Best for first-time visitors who need the story before the full workflow.
Open exploration of dashboard, dispatch, carrier readiness, documents, safety, and settlements.
Best for fleet owners who want to inspect the system without a walkthrough.
A controlled route through the flagship operating stories and escalation logic.
Best for buyers evaluating how BOF enforces workflow consequences.
Deeper operating views for implementation partners and serious founding fleet review.
Best for workflow owners reviewing packet, finance, and compliance details.
Setup, workspace, and source-of-truth surfaces that should be explained in context.
Best kept out of unguided buyer demos until the owner frames the purpose.
Persona-based exploration
See the command center, money at risk, carrier readiness, and executive operating picture.
Guided prompt
Start with triage, then follow the finance and carrier readiness consequences.
Work through dispatch gates, proof obligations, reload fit, and operational thread decisions.
Guided prompt
Use the dispatch board to see what can move, what is blocked, and who owns the next action.
Inspect packet completeness, insurance, authority, dispatch gates, and reload eligibility.
Guided prompt
Compare ready, review, watch, blocked, and payment-control carriers before assignment.
Follow driver readiness, safety events, document status, and proof-chain consequences.
Guided prompt
Use L008 and L009 to show how BOF separates claim escalation from pre-trip readiness failure.
Frame BOF as an enforcement-driven operating system with carrier, dispatch, proof, and finance depth.
Guided prompt
Start broad, then use command center and carrier gates to prove workflow depth.
Guided access
BOF remains open for self-guided review, but workspace and setup-style routes are better shown with context so buyers see the enforcement engine instead of raw scaffolding.
Template pack workspace
/documents/template-packs
Show only when explaining document generation workflow ownership.
Template artifact workspace
/documents/template-packs/artifact
Keep behind guided context because this is a workspace surface, not a buyer entry point.
Source-of-truth diagnostics
/source-of-truth
Use only when explaining the static/generated demo architecture.
Dispatch intake workspace
/dispatch/intake
Use after the main dispatch board so the intake workflow has operational context.
Legacy load request
/load-request
Avoid as a primary path; use only to explain legacy intake continuity.