Northwind Logistics — a 45-person B2B services company whose sales team was drowning in raw form-fill MQLs — had no scoring, no routing rules, and MQL→SQL conversion stuck at 18%. We rebuilt the HubSpot lead funnel from scoring to routing to behavioral nurture in six weeks.
“Lead response used to be four hours of someone manually sorting through a shared inbox. Now the system scores, routes, and notifies the rep in Slack before they finish their coffee. Pipeline has never been more predictable.” Northwind Logistics · VP of Sales
Northwind Logistics is a regional B2B services firm — roughly 45 people, six account executives, and a marketing team running paid search, content syndication, and a steady trade-show circuit. The sales org was receiving raw form-fill MQLs directly into a shared inbox with no scoring, no routing rules, and no defined handoff between marketing and sales. MQL→SQL conversion had been stuck around 18% for the better part of a year.
The bleed was structural as much as it was tactical. Marketing was generating healthy top-of-funnel activity — roughly 180 form fills a month across paid, organic, and events — but the handoff to sales was a daily triage call. AEs cherry-picked leads informally over Slack DMs; the lower-scored form fills sat untouched for days at a time. Sales-ops was spending ~12 hours a week re-keying contact details, re-assigning ownership, and chasing reps for follow-up status. Average lead-response time sat at four-plus hours, and roughly a third of MQLs were never worked at all.
The HubSpot portal was loosely configured. Lifecycle stages had drifted away from how the sales team actually worked, the built-in HubSpot score was firing on page-view volume rather than fit, and there was no Slack or notification layer between a form submission and a rep noticing it. Leadership had been pushing for “smarter lead routing” for two quarters but couldn't get past discovery without a clear-eyed picture of what the funnel was actually doing.
The engagement ran over six weeks as a fixed-scope HubSpot lead-generation build. The brief covered four interconnected workflows — scoring, routing, nurture, and reporting — with HubSpot at the centre and Slack as the connective tissue between marketing automation and the sales floor:
Workflow 1 — HubSpot lead scoring rewrite. The default HubSpot score was replaced with a custom property-based score combining firmographic signals (industry, company size, job title tier), behavioral signals (pricing-page visits, repeat demo-page visits, webinar attendance, content downloads), and explicit negative-score rules (students, competitors, free-mailbox domains, and out-of-territory geos). Score updates fire in real-time and roll into four grade tiers — A, B, C, D — that drive routing decisions and bubble up on every contact record. The old page-views-based score was suppressing actual buyer intent; the new model surfaced it.
Workflow 2 — Lead routing workflow with Slack notifications. A round-robin + territory-based assignment workflow was built so that grade-A and grade-B leads rotate through the AE roster in defined bands, and that lead owner is notified in a dedicated Slack channel within seconds of a form fill crossing the score threshold. The channel surfaces firmographic context, score, UTM source, and last-touch activity — everything a rep needs to triage in 30 seconds, not 5 minutes. The manual triage email chain that had been eating ~12 hours of sales-ops time per week is gone.
Workflow 3 — Three-track MQL nurture sequences. Behavioral nurture was built around the score, not the form. Cold leads (grade C/D) enter a low-cadence educational track that runs over four weeks with case-study-driven content. Warm leads (grade B) get a mid-cadence track running over two weeks with ROI calculators, comparison guides, and a soft demo CTA. Hot leads (grade A — or any contact whose score crosses the threshold mid-nurture) are routed immediately to an AE with a calendar link and a contextual brief. Any lead whose score crosses the threshold mid-track is automatically passed to sales even if they were previously nurture-only.
Workflow 4 — Reporting dashboard. A weekly HubSpot dashboard ties together MQL source, score band, time-to-SQL, rep acceptance rate, and nurture-stage conversion. Sales-ops reads the dashboard Monday morning instead of pulling a manual report, and the leadership team gets the same view in a shared version keyed to pipeline impact. VP Sales now runs Monday pipeline reviews off the dashboard rather than off anecdotal rep updates.
MQL→SQL conversion moved from 18% to 34% over six months — an 89% lift. The gains weren't attributable to a single workflow; they were the cumulative effect of lead score being tied to actual fit, hot leads being routed inside minutes instead of hours, and the warmer nurture tracks building intent that sales could actually work. The same month the new scoring went live, demo-book rate from MQLs roughly doubled month-over-month and held there.
Demos booked from inbound MQLs went 2.1× month-over-month within the first 60 days, and held at that level through the following quarter. Lead-response time dropped from >4 hours on average to <30 minutes — Slack notifications fire within seconds of a grade-A form submission, and reps have a one-click path to accept or re-route. ~12 hours per week of sales-ops cleanup is gone: there is no manual triage call, no re-keying of contact records, and no chasing reps for follow-up status.
Sales-ops reclaimed that time for higher-leverage work — building out the new-event playbook, auditing the partner-program funnel, and tightening the territory definitions as the team scaled. The Slack notification channel became the AE team's pulse-check for the funnel, and the dashboard became the Monday-morning review artifact for leadership. Sales stopped cherry-picking informally and started working a queue that was, for the first time, actually ranked.