HubSpot CRM implementation for a logistics company

Context

Z Nation Transport LLC, a US trucking and logistics company, was growing faster than its systems could keep up. Two engines ran the business, and both were held together by manual effort:

• Driver recruitment ran out of inboxes and spreadsheets, with follow-up depending on whoever remembered.
• Business development for freight lived in separate threads, with no shared view of who had been contacted.
• The website was a static brochure, disconnected from either funnel and capturing nothing.

Challenge

Two funnels with opposite dynamics had to run through one system a small team could actually operate:

1. Driver recruitment — high volume, fast decisions, heavy follow-up.
2. B2B freight — lower volume, high value, long relationships.

The hard part was serving both with one coherent model without drowning the team in admin.

Constraints

• No CRM discipline to build on: starting from zero process.
• A high-volume contact database carrying significant duplication.
• A team whose tolerance for manual admin was, reasonably, near zero — anything that added clicks would go unused.

Strategy

Implement HubSpot as the single operating system for both funnels:

1. Separate pipelines, each with its own lifecycle-stage definitions.
2. Automated capture from a rebuilt, conversion-focused website.
3. Routing and nurture automated end to end, so the team only touched leads worth touching.

Implementation

Website. Rebuilt on Drupal with dedicated recruitment and freight pages, each feeding HubSpot forms directly.

CRM core. Inside HubSpot:

• Custom properties and lifecycle stages per funnel.
• Deduplication and cleanup of the historical database.
• Lead scoring to surface priority contacts automatically.
• Automated nurture sequences for both drivers and freight prospects.

Acquisition. Paid campaigns fed the same measured system, so every source was comparable.

Results

• Over 42,000 contacts managed with automated capture, routing and nurture.
• Revenue roughly doubled (+110%) across the growth programme.
• The CRM and website became the infrastructure that made growth manageable, not just bigger.

Lessons

For a lean team, a CRM has to earn its keep by removing work, not adding process. The decision that made adoption stick was an automation-first build: every stage change triggers the next action automatically, so the system does the chasing instead of the team.