BRAIN OS / USE CASES AND IMPACT
The work it takes.
The time it gives back.
At one freight operation, people use Brain OS to find a load, prepare an order, or check an invoice. Here is what they asked, what the system did, and what the records show. The deployment has been in production since June 2026.
2 hrsto30sec
To plan a truckload from a packing list
Customer reported, for this workflow.
33
People who asked Brain OS something in one week
Week to 18 September 2026.
375
Changes written to the system of record in one week, each a draft first
Monday 21 September to 11:09 Eastern on Friday 25 September 2026, from session logs.
153
Operating rules taught in chat and kept
Since 24 July 2026, counted 21 September.
01 · BEFORE AND AFTER
The same ask.
A different day.
Six familiar requests, with the steps they used to involve and how Brain OS handles them. The figures come from one operation in September 2026.
“Where is my load?”
Dispatch, all day
522 distinct orders read in one week, week to 18 September
THE USUAL
Open the system of record. Find the order. Check the last driver text. Search the inbox for the carrier’s email. Call someone if none of it agrees.
5 stepsOpen the system of recordFind the orderRead the last driver textSearch the inboxCall someone
WITH BRAIN OS
Brain OS brings the order, stops, estimated arrival, latest driver text, and latest email into one answer. Each fact names its source, so the dispatcher can check how the records fit together.
1 askAsk
“How many trucks does this shipment need?”
Open deck planners
Thirty seconds with Brain OS, the blue sliverTwo hours by hand, the whole bar
2 hrs to 30 sec customer reported. Nobody specified this feature; planners started pasting packing lists.
THE USUAL
Print the packing list. Work every piece against legal length, width, height and weight, and against deck heights by trailer type, by hand.
5 stepsPrint the packing listMeasure every pieceCheck legal limitsCheck deck heightsAssign to trailers
WITH BRAIN OS
Paste the packing list to get a plan by trailer type, with oversize and overweight items flagged. The system follows rules captured from the planner’s messages; this customer reported a planning time of thirty seconds.
1 askPaste the list
“Build this load.”
Dispatch, from a load sheet
94 orders created in one week, 21 to 25 September, by five people
THE USUAL
Retype the load sheet into the system of record, field by field. Look up the customer’s rules in a spreadsheet or a memory. Hope nothing was missed.
4 stepsOpen the load sheetRetype each fieldLook up the customer’s rulesCheck for misses
WITH BRAIN OS
Paste the load sheet to prepare a draft from the last order on that lane. Brain OS applies the customer’s rules and flags discrepancies for review before the dispatcher confirms creation.
2 asksPaste the sheetSay yes
“Who should I call for this lane?”
Carrier sales
Nearly ten years of lane history behind every carrier answer, read live
THE USUAL
Ask the room. Search old emails for the last carrier who ran it. Scroll the carrier list and start dialling.
4 stepsAsk the roomSearch old emailsScroll the carrier listStart dialling
WITH BRAIN OS
Nearly ten years of lane history becomes a ranked carrier list, with the last run, equipment, and a contact for each. The broker has enough context to choose whom to call.
1 askAsk
“Post it to the load board.”
Brokers
192 postings made in one week, 21 to 25 September
THE USUAL
Open the board. Retype the stops, the rate and the truck type. Remember to update it when the rate moves and take it down when it covers.
5 stepsOpen the boardRetype the stopsType the rate and truckUpdate when it movesTake it down
WITH BRAIN OS
Preview, then post, under the broker’s own load board login. Updated or taken down in a sentence. Shipper contact details stripped by default.
2 asksSay postSay yes
“What is delivered but not billed?”
Billing, every morning
About forty scheduled jobs run this way, verified on the server 21 August
THE USUAL
A report someone assembles by hand, when there is time. Missing paperwork found when the customer asks why the invoice is late.
3 stepsExport delivered loadsFilter for no bill dateChase paperwork by hand
WITH BRAIN OS
A digest every morning without anyone asking: delivered loads with no bill date, delivered loads missing proof of delivery, and the carrier to chase for each.
1 askRead the digest
02 · ADOPTION
More people.
More questions.
Brain OS opened to the whole company on 12 August 2026, with access tiers in place. Nobody was told to use it. This is what happened next.
People who asked Brain OS something, each week
One operation, from the week the whole company was admitted. The last bar is the seven days to 24 September.
The operation’s usage database. Weeks end on the date shown; the last window is the seven days to 24 September 2026.
The numbers
| Week to | People |
|---|---|
| 21 Aug | 12 |
| 28 Aug | 14 |
| 4 Sep | 24 |
| 11 Sep | 31 |
| 18 Sep | 33 |
| 24 Sep | 35 |
Questions per weekday, two weeks side by side
Monday 14 to Friday 18 September, then Monday 21 to Friday 25 September 2026. Friday of the second week covers the morning only, to 11:09 Eastern.
Messages sent to Brain OS in Teams, credited to the sender, Endurance’s own messages excluded. From the operation’s usage database, 25 September 2026.
The numbers
| Day | Week of 14 Sep | Week of 21 Sep |
|---|---|---|
| Mon | 48 | 198 |
| Tue | 113 | 225 |
| Wed | 180 | 209 |
| Thu | 259 | 335 |
| Fri | 188 | 28 |
Questions per person, ranked, Monday 21 to Friday 25 September 2026
Nineteen people sent 96% of the week’s questions. Names withheld. Ten more people asked between one and eight questions each, 36 in all.
The operation’s usage database, 25 September 2026, 11:09 Eastern.
The numbers
| Person, by rank | Questions |
|---|---|
| 1 | 254 |
| 2 | 101 |
| 3 | 88 |
| 4 | 87 |
| 5 | 59 |
| 6 | 47 |
| 7 | 47 |
| 8 | 42 |
| 9 | 39 |
| 10 | 31 |
| 11 | 30 |
| 12 | 26 |
| 13 | 21 |
| 14 | 20 |
| 15 | 17 |
| 16 | 17 |
| 17 | 13 |
| 18 | 10 |
| 19 | 10 |
437 → 791 → 1,200
questions in the weeks to 11, 18 and 24 September
26%
of questions from the heaviest user in the week of 21 September, down from 69% in August. Concentration moves week to week.
335
questions on Thursday 24 September, the busiest day on record
03 · WHAT THEY ASK
Where the
questions go.
Of 995 questions in the recorded week, nearly half concerned building orders or posting loads. The rest ranged from paperwork and billing to driver updates and carrier outreach.
What 995 questions asked for, Monday 21 to Friday 25 September 2026
Share of the week’s questions by topic, classified by keyword rules, accurate to a few points.
The operation’s usage database, 25 September 2026, 11:09 Eastern. Percent of 995 questions.
The numbers
| Topic | Share |
|---|---|
| Building and editing orders | 24% |
| Posting loads to the load board | 23% |
| Paperwork: proof of delivery, bills of lading, chassis numbers | 9% |
| Margin, revenue and book performance | 8% |
| Email, inbox and carrier outreach | 7% |
| Load status, check calls and drivers | 6% |
| Packing lists and trailer planning | 6% |
| Rates, quotes, lane history and prospecting | 4% |
| Questions about Brain OS itself | 4% |
| Looking up a customer, carrier or agent | 4% |
| Billing, receivables and customer credit | 2% |
| Other, greetings and thanks | 3% |
Truckload planning began with planners pasting packing lists into chat. Their explanations became a page of rules for Brain OS to follow. In the week of 21 September, that work accounted for 6% of questions from five people. A useful capability took shape as the people doing the work taught the system what mattered.
04 · WHAT IT DID
One week of work,
counted.
Actions completed at people’s request in one week. Every one was a draft first and a yes second. Scheduled jobs are excluded, so this is only what people asked for.
Actions completed at people’s request, Monday 21 to Friday 25 September 2026
Counted from session logs, one per successful action, credited to the person whose question triggered it. The window closes at 11:09 Eastern on the Friday.
The operation’s session logs, 25 September 2026. The previous week, same span, had 25 changes in the system of record.
The numbers
| Group | Action | Count |
|---|---|---|
| System of record, 375 changes for 9 people | Stop comments added | 116 |
| System of record, 375 changes for 9 people | Orders created (9 later voided through Brain OS) | 94 |
| System of record, 375 changes for 9 people | Order fields edited | 70 |
| System of record, 375 changes for 9 people | Stops cleared as arrived and departed | 32 |
| System of record, 375 changes for 9 people | Stops rescheduled | 30 |
| System of record, 375 changes for 9 people | Rates changed | 15 |
| System of record, 375 changes for 9 people | Orders voided | 13 |
| System of record, 375 changes for 9 people | Driver texts sent | 4 |
| System of record, 375 changes for 9 people | Driver details updated | 1 |
| Load board | Postings made | 192 |
| Load board | Postings taken down | 91 |
| Load board | Postings updated | 23 |
| Emails sent on someone’s behalf | 51 |
15×
the previous week’s pace of changes in the system of record, 25 to 375
0
changes made without a draft shown first to the person who asked
05 · BY ROLE
What each desk asks,
in its own words.
These examples come from a production deployment; steps still awaiting verification are identified. For a configured user, “my loads” refers to their own book, and financial questions follow their access tier. Choose a role to see the work in context.
“Status on this load?”
Order and movement status, stops and estimated arrival times, merged from the system of record, driver texts and email into one record.
“Are any of my loads running late?”
A late sweep scoped to the asker’s book. Loads cancelled with a truck ordered not used fee are excluded, so it does not false alarm.
“Text the driver on this load. Pickup status?”
Drafts a real text message, sends on a yes, and reads the reply back within about two minutes.
“Clear the pickup, in at 13, out at 15.”
Drafts the stop update with the exact times and writes it to the system of record on confirm.
(pastes a load sheet) “Build this load.”
A full order draft, cloned from the last order on that lane with the changes swapped in, customer rules applied and discrepancies flagged before anything is created.
06 · TIME RETURNED, PRICED
Your numbers.
Our arithmetic.
A model, not a promise. The defaults come from one operation’s own usage in September 2026. The minutes per question and the hourly cost are assumptions, and every input is yours to change.
YOUR OPERATION
WHAT THE MODEL SAYS
Hours returned each week
106hrs
Hours returned each year, over 48 working weeks
5,080
Value of those hours at $40 an hour
$203,200
Brain OS for the year, published band “26 to 45”
$23,400
Return on the year’s fee
8.7×
The arithmetic: people × questions a day × 5 days × minutes ÷ 60, plus plans × (2 hours − 30 seconds), gives hours a week. Times 48 weeks, times the hourly cost, gives the value. The band and its price are the ones published at endurancelabs.ai/brain/pricing.
Published pricing covers the brain: questions and answers, with sources attached. Writes into a system of record, a registered text number, load board posting and specialist desks are scoped and quoted for each operation.
07 · WHERE REVENUE ENTERS
From a quote
to a customer served.
We have not measured revenue attributable to Brain OS. What we can show is how it supports the work around a sale: pricing a lane, finding a carrier, and keeping a customer informed.
QUOTE
Price from history
Seasonality, who hauls it, backhaul potential. Nearly ten years of lane history in the time it takes to ask.
“What does this lane usually do?”
COVER
Call the right carrier
A ranked call list for the lane. Identity for the carrier on the phone. A buy above the sell refused in the draft.
“Who is this MC number?”
MOVE
Fill the empty leg
Cross book reload matching, equipment matched, cancelled and on hold loads excluded.
“Find me a backhaul near Cleveland Thursday, flatbed.”
POST
Put freight on the board
A posting in a sentence, under the broker’s own login. 192 in the week of 21 September.
“Post it at $2,400.”
PROSPECT
Find the next shipper
Shippers in a city, cross checked against the customer list. Customers gone quiet for three months. New in the week of 21 September, unprompted.
“Which shippers in Charlotte are not already ours?”
SERVE
Show the customer
A public tracking link for one load, no login, instead of a promise to call back.
“Give me an update for the customer.”
A SEPARATE PRODUCT, A MEASURED RESULT
The dollars we can show are in Margins.
Margins calculates commissions from defined rules at the same operation. Its production ledger records the amounts below. These are Margins results and should be assessed separately from Brain OS.
Read the Margins ledgerCommission settled through Margins20 closed weekly runs, 29 March to 16 August 2026
$4,015,094Duplicate payments stoppedabout, across 20 loads that would have paid twice, caught before payday
$5,491A misrouted book, caughtabout, before a dollar moved, back to the person who earned it
$39,400
Queried from the operation’s production system on 24 August 2026.
08 · WHO IT IS FOR
A system of record.
And a few people’s heads.
Closest fit: freight brokerages, third party logistics firms and asset carriers of 25 to 140 people, working in Microsoft Teams. Next: any operation where the answers live in a system of record and the rules live in inboxes and spreadsheets.
WHO BUYS IT
- The owner or president
- A way to handle more work with the team already in place.
- The head of operations
- Fewer chases, faster answers, and a team that stops asking “where is it?”
- The finance lead
- Figures that can be checked against their sources, with access controls around financial information.
- A senior operator
- The champion who uses it on live work every day and says bluntly what is wrong. Their corrections are the fastest way the brain grows.
WHAT USUALLY STARTS THE CONVERSATION
- Growth without hiring.
- A key person whose knowledge is not written down.
- Weekly reports someone builds by hand.
- A team drowning in “where is it?”
- A security review that stalled an earlier AI attempt.
WHEN NOT TO BUY
- Your knowledge already lives in one system everyone trusts. Brain OS solves a problem you do not have.
- Important knowledge has not been recorded. It needs to be captured before Brain OS can use it.
- Your system of record has no interface we can connect. Knowledge-based answers may still be possible, but actions need an integration.
09 · THE ROLLOUT
One deployment.
Nine weeks to company access.
The reference deployment began with read access in June 2026 and opened to the company in August. Actions were enabled one at a time, each with its own control. This is the record of that rollout.
From first version to company wide, 2026
Twelve milestones on one axis. Read only first, then one capability at a time.
- First version: the Teams bot, live reads from the system of record, and the knowledge base.
- Daily use by one senior dispatcher on live freight, who became the product owner.
- Rules taught in chat start saving themselves to the brain.
- First orders built in the system of record from a conversation.
- Drivers text photos of signed paperwork to Brain OS’s number; they land in the inbox.
- Opened to everyone with a company mailbox, access tiers unchanged.
- Outbound driver texting on Brain OS’s own registered number.
- Load board screen, per load operations screen, and public customer tracking.
- Load board posting live on production, after the load board certified it.
- Finance questions answered live from the system of record.
- 33 people in one week.
- Specialist desks, with an automated test suite.
Connect
Register the bot in your Microsoft tenant, connect the system of record, and give Brain OS its mailbox. Read only first.
Compile
Ingest what the business already produces. Give every user a page with their book, their tier and their role.
Pilot with a champion
One operator who uses it on live work every day and says what is wrong.
Open the company
Admit the whole domain with tiers in place. Here it went from 12 to 31 weekly users in four weeks.
Turn on actions one at a time
Each write runs in shadow first, reporting what it would have done. Then it is armed with its own switch, under the pause.
NEXT
One workflow.
Your systems.
Your people in control.
Bring one workflow and the people who know it. We’ll look at the systems involved, the decisions that take time, and a useful first step.
Tell us about your workFigures on this page come from one operation’s usage database and session logs in the weeks to 18, 24 and 25 September 2026. Its knowledge base was counted on 22 September 2026. The truckload planning timing is customer reported. The operation is not named here at their request. Read the figures as one deployment’s record, not as a forecast for yours.