Pilot Center · Current product tour
Walk every Host, Fleet, and Driver surface. Understand how timber work moves from a landing plan to one confirmed haul — without signing in, changing data, or buying anything.
Fictional operation · synthetic people, loads, landings, routes, and messages
Choose your cockpit
These are content tours, not persona switches. Each route explains the current product with captures from disposable synthetic workspaces.
Host experience
Prepare timber work, publish it to the right audience, commit qualified capacity, coordinate the live day, and confirm what physically moved.
There is no monthly minimum and no fee to post. For separately approved Network work, LogLoads charges the host 5% on top of stated driver pay only after an authoritative physical completion, invoiced monthly in arrears.Fleet experience
Turn drivers, trucks, availability, opportunities, commitments, trips, and exceptions into one operating picture without charging the fleet or reducing driver pay.
Fleet workspace access is free forever. No current subscription enrollment exists, and LogLoads never reduces driver pay.Driver experience
Know what is available, what it pays, whether the rig fits, where to go after assignment, and what happens next — from a phone-first cockpit.
Driver access is free forever. The stated driver pay is a direct host-to-driver obligation and is never reduced by a LogLoads fee.One operating loop
LogLoads gives each participant a different cockpit around the same authoritative day. The handoff remains understandable from end to end.
Define the timber, landing, destination, pay, equipment, timing, and access boundaries before work reaches the board.
Publish a clear opportunity while exact gates, private roads, contacts, and sensitive coordinates remain protected.
Compare work with truck, trailer, capacity, timing, distance, and relationship access before anyone commits.
Turn an accepted request into one accountable assignment with frozen operating and commercial terms.
Keep the schedule, assignment-scoped conversation, current notice, route access, and exception owner together.
Move the physical load with the active trip, field status, and protected route pack visible to the right people.
Record physical completion, host review, direct driver-payment status, and the next repeatable operating decision.
Three honest levels
A product tour is not a live pilot, and a pilot does not silently authorize enrollment, provider mutation, or fee collection.
Explore every current role surface through labeled captures and an end-to-end operating narrative. No sign-in and no product state.
Walk a realistic synthetic day with the LogLoads team. We rehearse decisions, handoffs, privacy, and recovery without touching live providers.
Run a bounded real operation only after the named organization, legal posture, data boundaries, participants, support plan, and commercial gates are separately approved.
What a credible pilot includes
Start with one representative day and enough real participants to expose the handoffs. Expand only after evidence says the loop works.
Choose one real operating lane, name the host lead, fleet coordinator, drivers, equipment, landings, destinations, and the out-of-band fallback.
Agree on required fields, visibility, assignment authority, route-access release, completion truth, direct driver pay responsibility, and exception ownership.
Seed only synthetic records and rehearse the full loop on the devices participants will actually use. Correct confusion before any live work.
Verify every launch gate, approve the exact organization and participants, define the window, and keep a named stop-and-rollback decision owner.
Run a short daily operating review around unowned exceptions, stale status, privacy events, duplicate commitments, support response, and participant comprehension.
Close with evidence: what moved, what still required calls or texts, what users understood, what failed, and whether to stop, repeat, or expand.
Launch gates
A dated counsel-approved operating posture covers the exact commodity, route, relationships, and LogLoads role before Network enrollment.
The exact pilot organization and participants are approved; wildcard enrollment is not accepted and production remains closed to everyone else.
Identity, membership, assignment, route-pack release, private media, and organization boundaries pass a role-by-role rehearsal.
The exact Supabase, Clerk, storage, monitoring, email, and deployment tenancy is verified without borrowing another venture's provider identity.
Host and driver responsibilities for direct driver pay are accepted. LogLoads remains non-custodial and never moves transportation compensation.
Any 5% fee enrollment and collection are separately approved for the exact host after invoice, webhook, refund, support, and rollback evidence. A pilot does not silently activate charging.
Named people own launch, support, incident response, stop authority, fallback coordination, and the end-of-pilot decision.
Proposed scorecard
Agree on thresholds before the live window; do not invent success afterward.
Every participant can explain their next action and complete the rehearsed core task on the device they will use in the field.
Every published pilot load has complete pay, equipment, timing, destination, capacity, visibility, and access-boundary information.
Every commitment resolves to one named driver, truck, schedule, and authoritative assignment without a duplicate booking.
Every active movement has a current state, a visible next action, and an owner for any exception.
At least ten completed pilot movements reconcile assignment, capacity, trip, completion, proof, direct-payment status, and the host fee ledger before scope expands.
At least four of five evaluators in each participating role complete their primary workflow without facilitation.
Every physical completion has an authoritative record; direct driver-pay sent and received markers remain controlled by the host and driver respectively.
No private route, gate, contact, credential, or media detail reaches an unauthorized participant.
No physical movement creates more than one commercial obligation, and no fee is collected unless its separate gate is approved.
The closeout shows whether LogLoads reduced status-chasing calls and ambiguity enough that the cohort chooses to repeat the workflow.
Ready for the next honest step?
Begin with the public tour, then rehearse a realistic synthetic workflow before any separately approved live operation.
