Skip to main content

    Logistics, Freight & Transport · project showcase · measurement build

    Project ShowcaseReal client work that shipped. No performance figures are published, because none have been verified and approved for release.

    Instrumenting the numbers nobody publishes for freight

    There's no published cold-email benchmark for freight, no LinkedIn benchmark, no webinar benchmark, no sales-cycle figure and no Google Ads freight category. A freight operator asking how they compare is asking a question the published record hasn't answered. This build makes the operator's own data answer it.

    At a glance

    The engagement in brief

    Services

    • CRM
    • Lead Routing
    • Reporting
    • CRO
    • Web Development

    Stack

    • Quote request forms
    • CRM with source tags
    • First-response clock
    • Win/loss fields
    • Reporting workbook

    The situation

    What we walked into

    Most verticals have a published number to argue with. Freight has three: a cost per lead, a customer acquisition cost, and a ratio, all from one publisher's client data. Everything else an operator would want to know — what a reply rate should look like, how long a decision takes, what a search click costs in this category — is simply not in the record. The instrumentation is therefore not preparation for the marketing work. It is the only way the marketing work can be judged at all.

    Four of the five channel benchmarks a freight operator would want do not exist in any published dataset. The instrumentation is not preparation for the work; it is the work.

    What we found

    The diagnosis

    1. 01

      A missing benchmark is a reason to instrument, not a reason to estimate

      The freight marketing figures in general circulation come from vendor content with no disclosed dataset behind them. Repeating one because a client wants a comparison is how an invented number becomes a target.

    2. 02

      Source attribution has to survive the quote process, not just the form

      A quote request that becomes a phone call and then a three-week email thread loses its origin unless the CRM record carries the source forward through every stage. In freight that journey is normal rather than exceptional, which is why the tag lives on the record and not on the form submission.

    3. 03

      First-response time is the one number that is comparable to something

      Even with no external benchmark, first-response time is comparable across the operator's own lanes, reps and hours of the day. Internal comparability is worth more than an external figure that does not exist.

    4. 04

      Win and loss both need a reason field with a closed list

      Free-text loss reasons cannot be counted, and 'price' written by twelve different people means twelve different things. A closed list of six reasons produces a report; an open field produces an anecdote.

    The number behind it

    What this is built around

    Confirmed — the major cross-industry benchmark reports categorise into ~23 industries and **contain no logistics/freight/transport category** (LocaliQ 2026; WordStream 2026). The honest move is to instrument first-party data and label any borrowed figure (from "Industrial & Commercial") as a proxy.

    What we built

    The system

    Every quote request form writes to the CRM with a source and campaign tag attached to the record rather than to the submission. The record carries lane, mode, and the fields the operator actually prices on, so enquiries can be grouped the way the business thinks rather than the way the website is organised. A first-response clock starts at record creation and stops at first outbound contact, logged automatically rather than reported by the rep. Quote issued, award and loss are separate states, and both win and loss carry a reason from a closed list of six. The reporting workbook reads the CRM rather than a dashboard export, so the definitions cannot drift between what is measured and what is reported.

    Instrumenting the numbers nobody publishes for freight — stackA stack of 8 connected layers, from "Quote request form" through to "Reporting workbook", each feeding the one below it.Quote request formSource and campaign tag on the recordCRM recordLane and mode fieldsFirst-response clockQuote issuedWin / loss with closed-list reasonReporting workbook

    The sequence

    How it was delivered

    1. Week 1

      Field design

      Lane, mode and pricing fields agreed; closed list of win and loss reasons written

      Owner: OmniFlow + operator

    2. Weeks 2–4

      Form and CRM wiring

      Forms writing to the CRM with source and campaign tags carried on the record

      Owner: OmniFlow

    3. Weeks 3–5

      Response clock

      Automatic timing from record creation to first outbound contact

      Owner: OmniFlow

    4. Week 6 onward

      Reporting

      Workbook reading the CRM directly; definitions documented alongside each figure

      Owner: OmniFlow

    Outcome

    What shipped

    This entry makes no performance claim. It documents a measurement build and the condition that made it necessary: a vertical in which almost none of the benchmarks an operator would want to be compared against have ever been published.

    Reporting

    What you would actually see

    These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

    These are demo dashboards. They show the reporting surfaces this engagement is run and measured from, with representative figures generated around the published benchmarks cited on this page — not a client account and not a client result. Live reporting for your own account replaces every number here.

    Google Analytics 4

    Logistics, Freight & Transport · all web data

    Demo
    Acquisition overview
    Last 12 months vs. preceding period

    Sessions

    3,175

    +72.7%

    Key events

    126

    +90.9%

    Session key event rate

    4.0%

    +1.1%

    Engagement rate

    65.6%

    +3.2%

    Sessions by month

    AprJunAugOctDecFeb

    Dashed line marks the month the engagement started.

    Session default channel groupSessionsKey eventsRate
    Organic Search1,272675.3%
    Paid Search725334.6%
    Direct556183.2%
    Referral375174.5%
    Organic Social248124.8%

    CRM pipeline

    Logistics, Freight & Transport · inbound and outbound

    Demo
    Pipeline by source
    Last 12 months

    Leads created

    147

    +85.1%

    Qualified

    61

    +97.9%

    Meetings booked

    27

    +102.1%

    Answered on first attempt

    71.7%

    +9.5%

    Leads created by month

    AprJunAugOctDecFeb

    Dashed line marks the month the engagement started.

    First-touch sourceLeadsQualifiedMeetings
    Google Ads — high intent46199
    Organic search40178
    Business Profile — call28125
    LinkedIn outbound2194
    Referral1352

    Honestly

    What we would do differently

    The first version timed first response from form submission rather than from record creation, which quietly excluded every enquiry that arrived by phone and was entered afterwards — in freight, a large share of them. The clock now starts at record creation regardless of how the enquiry arrived, which made the early numbers worse and the reporting honest.

    Next

    Start the same conversation

    Start the same conversation

    Tell us what you are working on and we will say plainly whether this is the right shape of engagement for it.

    We use your details only to respond to this request. No lists, no resale.