No definition of an MQL
Marketing delivers "leads" of variable quality. Sales accepts a fraction. The debate about "this one isn't an MQL" is rehashed for every lead, without the scoring model ever changing.
The average B2B lead waits 42 hours for a first response. Your best leads have already clicked through to a competitor. We design lead routing and qualification on fit and intent, with an SLA that is no longer just a suggestion and a feedback loop back to marketing.
Lead flow problems are rarely a single mistake. It is a chain where something goes wrong at four points. We do it differently: we build scoring, routing and SLA in a closed loop, with marketing and sales at the same table. This connects to your broader marketing automation.
Once you close these four patterns, you get 15 to 25 per cent more SQLs from the same marketing spend, landing directly in the Sales CRM setup.
Marketing delivers "leads" of variable quality. Sales accepts a fraction. The debate about "this one isn't an MQL" is rehashed for every lead, without the scoring model ever changing.
The head of sales distributes leads via Slack or verbally. Hot accounts go to the favourite rep, other leads are a mess.
"We call within 24 hours" lives in a Figma file. Nobody measures it. Leads sit untouched for three days and reassignment never happens automatically.
Sales complains about lead quality, marketing does not know which campaigns brought good leads. Both teams improve independently, in opposite directions.
We build routing and scoring together with marketing and sales at the same table. Otherwise you end up with a marketing model and a sales model that have nothing to do with each other.
Workshop with marketing and sales: what is an MQL for us. Which fit criteria (role, industry, size) and intent signals (demo, download, page view) apply. Weight and threshold for SQL.
Routing rules in HubSpot or Salesforce. Round-robin, territory or account ownership. SLA per lead type: five minutes for demo requests, four hours for lower intent. Workflow reassigns on SLA breach.
Sales flags each lead as qualified, junk or not a match. The marketing dashboard shows acceptance rate by campaign and source. Weekly cadence between the marketing lead and sales lead.
Routing and scoring is people work at the boundary of marketing and sales. We bring both sides to the same table and connect to Addmark's broader sales engine.
A B2B SaaS client had marketing and sales in structural conflict. Marketing delivered leads of variable quality, sales accepted a fraction and debated each lead individually. The SLA lived in a Figma file nobody opened. Average response time on a demo request was 42 hours.
In five weeks we set up a shared scoring model, signed off on MQL and SQL definitions and built routing in HubSpot. The workflow reassigns on SLA breach. Acceptance rate from MQL to SQL went from 28 to 52 per cent, and demo requests now reach a rep within 5 minutes.
Honest answers to the questions we hear before almost every project.
Scoring measures how well a lead matches, based on fit (does it match your ICP) and intent (is it showing buying signals). Routing determines who it goes to, based on territory, account ownership or round-robin. Scoring is the measurement, routing is the action. You need both, but they are two separate questions.
That depends on your deal size. A lighter qualification approach for SMB and transactional deals, a more detailed one for mid-market and enterprise. We do not prescribe a fixed framework, but tailor it to your deal cycle. Often a lighter variant than the textbook version.
For demo requests and high intent: within 5 minutes. Research shows the probability of contact drops by half for every 30 minutes of delay. For lower intent (whitepaper downloads) 4 hours or the same business day is fine. We set the SLA per lead type.
Four to six weeks. Two weeks for scoring design and MQL/SQL definitions, two weeks for routing workflows and SLA monitoring, two weeks for the feedback loop and reporting. For enterprise with multiple business units or regions it may extend to eight weeks.
Our services are bespoke and usually sit within a RevOps-as-a-Service retainer where strategy and execution come together. Book a call and we will put together a proposal based on your situation.
Eventually, yes. But setting up scoring and routing requires an outside perspective on your ICP and your sales process. We deliver the first blueprint in four to six weeks. After that an internal RevOps role can take it over and refine it on data.
Three signs: marketing complains that sales does not follow up leads, sales complains about lead quality, and your MQL-to-SQL acceptance rate is below 30 per cent. Our Maturity scan gives an initial indication.
An agent can help with intent detection and initial follow-up, but only on a data model that is correct. We build the scoring and routing foundation, after which you can deploy AI for refinement and speed.
Start with a conversation. We look at your current lead flow, MQL acceptance rate and SLA discipline. Then a focused scope and initial direction.