2-week trial - no integrations required

Use the trial to test BOF against real operating records.

The Founding Fleet trial starts with the work your team already chases: driver files, document packets, release blockers, owner follow-up, and the decision about whether a load is ready, conditional, or held.

Trial promise

No live integrations required

  • Start with records your team can describe or share in conversation
  • Review how BOF organizes readiness, blockers, and next actions
  • Use the demo to inspect the operating model before deeper onboarding
  • Keep sensitive implementation details out of the first trial conversation

What BOF reviews first

The trial is record-backed from day one.

Each trial area answers the same buyer question: what is cleared, what is blocked, who owns it, and what should happen next?

01

Driver files

Driver eligibility, medical-card status, license evidence, safety review, emergency contact, and dispatch eligibility are opened as inspectable records.

Open driver files
02

Document packets

BOL, POD state, pickup instructions, delivery proof, dock photos, settlement watch items, and claim-support evidence stay tied to release consequence.

Open documents
03

Release blockers

BOF separates ready, watch, conditional, and hold states so dispatch does not guess from scattered emails or vague rows.

Open command center
04

Follow-up ownership

Each issue gets an owner, required record, consequence, next action, and audit note so the back office can keep moving.

Inspect release note
Trial planFounding Fleet packet2-week review window

Trial Operating Packet - Records Before Release

Starting pointOne real fleet pressure: release issue, driver file, document hold, or carrier packet
BOF outputReadiness view with owner, blocker, consequence, and next action
Trial supportPriority onboarding for accepted Founding Fleets
Commercial offer20% off forever for the first 10 fleets
Trial weekFocusBOF operating answerNext step
Week 1Record reviewWhich driver, document, carrier, or release records control movement.Choose the most useful operating path.
Week 1Demo inspectionWhether BOF's command center and document records are clear enough for your team.Open driver and document packets.
Week 2Workflow feedbackWhich BOF views, records, and handoffs would matter most for your fleet.Prioritize onboarding scope.
Week 2Founding decisionWhether your fleet should reserve one of the first 10 Founding Fleet slots.Confirm discount and next onboarding step.

Trial entry

Start with one record your team already cares about.

The fastest way to test BOF is to bring one release issue, driver file, document packet, or follow-up problem into the Founding Fleet trial.

Apply for trial access →