3PL Sales-Ops Desk on a CRM OS
Representative architecture: the CRM-as-operating-system build we delivered for a real-estate brokerage (EspoCRM + n8n: WhatsApp lead intake, routing, e-sign and collateral), adapted for a freight or 3PL sales desk. Not yet deployed for a freight broker; no TMS or load-board integration.
- Logistics/3PL
- EspoCRM
- n8n
- DocuSign
- Sales Ops
Overview
The project at a glance
Brokerage and 3PL sales desks juggle WhatsApp enquiries, spreadsheets, e-sign links and a website that is always out of date. This representative architecture adapts a CRM-as-operating-system build we delivered for a real-estate brokerage: one self-hostable CRM holds leads, accounts, deals and documents, with n8n handling WhatsApp lead intake, routing, e-signing, collateral generation and CRM-driven web feeds.
It has not yet been deployed for a freight broker or 3PL. The original build had no TMS, load-board, Extensiv or NetSuite integration; adding one would be scoped per project.
What the engagement had to achieve
- Make the CRM the single system of record for leads, deals and documents
- Capture WhatsApp enquiries into CRM even when reps are off shift
- Route leads, e-sign agreements and generate collateral from CRM data
- Keep public service pages in sync from CRM feeds
- Keep scope to sales operations: load tendering, rate engines and TMS are not included.
The story
The pipeline lives in WhatsApp and spreadsheets
What was at risk
The Challenge
A small freight-brokerage or 3PL sales desk runs on a CRM nobody trusts, a WhatsApp group per rep, and spreadsheets that hold the real pipeline. Enquiries come in over WhatsApp at all hours and go unanswered or unlogged. Rate sheets, capability decks and agreements are rebuilt by hand. The website goes stale. When a rep leaves, their WhatsApp history and half the pipeline go with them.
Leads arrive on personal chats and never become CRM records.
Capability packs and agreements are rebuilt from old Word files for each prospect.
This page does not include load tendering, carrier matching, rate engines, TMS integration or load-board posting.
How we responded
The Solution
One self-hostable CRM (EspoCRM) holds leads, accounts, deals and documents. Other tools read from and write to it.
An AI-assisted WhatsApp bot captures and qualifies the enquiry, creates or updates the CRM lead, and routing rules assign it to the right desk.
Agreements e-signed from the CRM record. Collateral generated from CRM data (capability sheets or proposal packs — not rate calculation).
Public service or capacity pages update from the CRM instead of by hand. Posting to load boards was not built.
Many freight brokers run Salesforce, HubSpot or GoHighLevel alongside a brokerage TMS and load boards. This build did not integrate a TMS, load board, Extensiv or NetSuite; that would be new work.
What we built
The concrete capabilities designed, built, and shipped in this engagement.
EspoCRM as the operating system
One self-hostable CRM holds leads, accounts, deals and documents. Other tools read from and write to it — not the other way round.
WhatsApp lead capture and qualification
AI-assisted WhatsApp bot captures the enquiry, qualifies it, and creates or updates the CRM lead so the conversation is logged even when the rep is off shift.
Lead routing to the right desk
Routing rules assign enquiries to the right rep or desk from the CRM record.
E-sign of agreements from the CRM
Agreements e-signed from the CRM deal record without leaving the desk.
Collateral generation from CRM data
Capability sheets or proposal packs generated from CRM fields — not rate calculation. Load tendering and load-board posting were not built.
CRM-driven web feeds and media performance
Public service or capacity pages update from the CRM; media-store rework so images load fast inside the CRM; reliable Sheets sync for teams that still report from spreadsheets.
The stack
The tools behind the build, and the role each one played.
EspoCRM
n8n
DocuSign
Google Sheets
What changed
Representative architecture: there are no freight or brokerage results to report yet. The design guarantees below come from the original real-estate brokerage build.
Beyond the launch
Lasting improvements
The changes that keep paying off after the engagement ended.
- CRM-as-OS pattern — leads, deals and documents live in one self-hostable CRM other tools write into
- WhatsApp enquiry logged to CRM even when the rep is off shift
- Each enquiry is routed to the right rep or desk from the CRM record
Swipe to see more
All case studies
Want an outcome like this one?
A short introductory call covers what's holding you up, whether we can help, and the first thing worth building.