What’s inside: connections to your systems · assistants
The question this file answersHow many times is the same route priced, typed into an e-mail and then typed again into the TMS?
Fits: logistics operators handling 100–500+ orders a day, where documents still arrive by email.
Unmeasured — the logistics playbook has no quote volume, so none is stated. A customer mails a route; someone hunts the rate card, prices it in a reply and, on acceptance, types the booking into the TMS. It hurts when the only person who knows the rates is out.
Typical, from the industry playbook — not a client's day.
On a Thursday afternoon the pricing desk opens drafts, not blank replies — the repeat routes already priced from the card, the odd ones flagged for a decision. The accepted quote becomes a TMS booking without a second typing, and you can see which routes the card could not price.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
quote drafted from the rate card, booking typed once — same build as our email-order intake file; no published figure for spot quoting
Before: a clerk hunts a rate card, types a reply, then retypes the win into the TMS. After: the reply is drafted from the card and the accepted quote becomes the booking without a second typing. No percentage — pricing a new route stays a person.
No published benchmark covers spot quoting at a forwarder. The McKinsey (2023) / Deloitte (2022) order-intake range is quoted on the parent file only — quoting is not order intake. Not a conversion or win-rate claim.
Your TMS and your rate cards stay where they are — SAP TM, Transporeon, CargoWise or whichever you run. It is our email-order intake build with a drafting step in front:
New routes. Capacity fights. Relationship pricing. Anything the card does not already know.
Not a conversion or win-rate claim.
A rate card that is out of date drafts wrong prices confidently — which is why nothing is sent without the desk, and why the first job is checking the card. Relationship pricing and tight-capacity days are not on any card; those requests go to a person and nothing here shortens them.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Logistics.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.