~20% of senior broker hours recovered; new-broker ramp materially faster

Composite example — illustrative of typical Company Brain engagements, not based on a single client.

The starting situation

A mid-market 3PL and brokerage running roughly $200M in annual revenue, with operations split across brokers, customer service, claims, compliance, and accounts receivable. Broker capacity had become the binding constraint on growth: senior brokers were spending materially more time on recurring lane research, rate-quote drafting, and carrier capacity hunts than on the account expansion and exception handling that actually moved revenue. Junior brokers couldn't quickly access the institutional rate and carrier knowledge that lived in senior brokers' heads, which meant onboarding ran long and the quality gap between tenured and new brokers stayed wide. Talent continuity had become a quiet risk — when a senior broker left, their book of knowledge left with them, and the firm had no systematic way to retain it. The strategic question: can we capture senior broker institutional knowledge in a form that's portable, durable, and accessible to the whole team?

What we built

• Ingestion: The carrier rate library (historical quotes by lane, carrier, and customer), the lane history database tracking which carriers had covered which lanes at which capacities, customer contract terms, customer-specific routing preferences, claims documentation templates, and the accessorial rules library.
• Knowledge partitions: Three access-scoped knowledge partitions with strict isolation. The Broker partition holds all rate, lane, carrier, and customer data. The Claims partition holds the claims library, carrier correspondence, and historical resolutions — brokers do not access claims internal correspondence. The AR partition holds accessorial rules, customer contract terms, and dispute history.
• Deployment mode: BuildClub-managed deployment. No regulated-data residency requirements, and speed and cost economics favored the managed deployment over an in-tenant build.
• Integration points: The TMS (read-only access to load, carrier, and customer records) and the email environment for outbound quote drafting context.
• Frontend: A custom UI for brokers, because the broker workflow lives inside the TMS and speed of inline answer mattered more than tool familiarity. Claude for everyone else — claims, AR, and management — querying through their respective partitions.
• What the Brain answers: "What was our last quoted rate on this lane for this customer." "Which carriers have covered this lane in the past 12 months at the right capacity profile." "What are our standard accessorial terms with this customer, and where have we made exceptions historically."

How it evolved

V1 shipped at 60 days with the carrier rate library and lane history ingested, and the Broker partition live. The faster timeline relative to a typical Brain engagement reflected cleaner source data — the rate library was already structured, and the lane history was queryable from the TMS extract on day one. Adoption inside the broker team was immediate because the answers replaced the most common time-leak in the day.

V2 landed at five months. The claims library and customer contract terms came online, and the Claims and AR partitions went live with the appropriate isolation from broker access. By v3, at roughly twelve months, customer-specific routing preferences and historical dispute resolutions had been ingested, and the Brain had become the operational substrate for new-broker onboarding — new hires querying the Brain for context that previously required interrupting a senior broker.

What it changed

• Roughly 20% of senior broker hours recovered, redirected to account growth and exception handling on complex shipments.
• New brokers reaching productivity materially faster, with the gap between tenured and new broker quality narrowing within the first quarter of new-hire tenure.
• Talent continuity risk reduced — when a senior broker departed during the engagement window, the book of institutional knowledge stayed with the firm and was queryable by the broker who picked up the accounts.
• Claims documentation turnaround shortened by several days on average, driven by template access and historical resolution context.

What it didn't change

The TMS stayed as the system of record and continued to handle all load tendering, tracking, and settlement exactly as before. The carrier rate library still got manually updated by AR on a weekly cadence; the Brain consumed the updates but didn't replace the human curation. Customer correspondence still came from a human broker. Carrier relationships still ran through the broker who owned the lane. The Brain provided context and continuity; the broker still owned the relationship and the deal.

The composite lesson

In logistics, talent continuity is one of the strongest reasons to deploy a Company Brain. The economic value of senior broker knowledge is high, the half-life of that knowledge inside one person's head is long but finite, and the cost of losing it when a broker leaves is rarely budgeted. A Brain that captures rate history, lane intelligence, and customer-specific patterns converts an individual asset into an institutional one — durable through turnover, accessible to new hires, and queryable across the team in a way it wasn't when it lived in a Slack DM or a senior broker's inbox. The broader pattern: anywhere a firm's competitive edge depends on tenured-person knowledge, the Brain is how you make that edge survive the people who carry it.