Search "MQL to SQL conversion consultant" and you will mostly find playbooks about fixing the handoff yourself, SLAs, scoring models, joint definition workshops. Useful, but it skips the actual question a founder or VP of marketing has when they type that phrase into a search bar: what does it look like to hire someone for this, what do they actually do in the first month, what does it cost, and how do you tell a consultant worth paying from one who will hand you a slide deck and disappear. This is the buyer's version of that question, not another version of the playbook.
What you are actually paying for
An MQL-to-SQL conversion consultant is not paid to write a definition of a qualified lead on a whiteboard, most internal teams could do that in an afternoon if they had the bandwidth and the neutrality to referee the argument between marketing and sales. What you are paying for is the analysis underneath that definition: a review of 12 months of closed-won and closed-lost deals to identify which signals actually predicted a real opportunity versus which signals felt intuitively important but didn't hold up against the data, and the neutral authority to get both departments to agree to a definition based on that evidence instead of whichever department argues more forcefully in the room. You are also paying for the technical implementation that turns an agreement into something automatic: CRM workflow rules, SLA enforcement, and a scoring model that keeps working after the consultant leaves, rather than a document that gets referenced once and forgotten.
What the first month of the engagement actually involves
The first two to three weeks are almost entirely diagnostic, and if a consultant skips this and starts recommending fixes in week one, that is a warning sign rather than a sign of efficiency. Expect a pull of closed-won and closed-lost deal data going back a year, interviews with both the marketing team that generates leads and the sales reps who work them, and a review of how leads currently move through your CRM, where they sit longest, and where they get dropped. By the end of the first month you should have a written diagnosis: the actual MQL-to-SQL conversion rate broken out by lead source, the specific point in the handoff where deals are being lost, and whether the root cause is lead quality, response speed, missing context in the handoff, or a definitional disagreement that has never been resolved. If a consultant cannot show you this diagnosis in writing before proposing a fix, they are guessing rather than diagnosing.
The deliverables that separate a real engagement from a workshop
A single joint workshop that produces an agreed MQL definition is useful, but it is not the whole engagement, and a consultant who stops there has sold you half the work. The full scope should include a scoring model calibrated against your closed-won data rather than assumed intent signals, CRM automation that enforces the agreed handoff SLA without relying on either team remembering it, a shared reporting dashboard both marketing and sales look at in the same meeting, and a documented rejection-reason process so when sales sends a lead back as not ready, that reason feeds into recalibrating the score instead of disappearing into an email thread. The test for whether the engagement was done properly is simple: six months later, does the definition still hold, or has it silently drifted back into the same disagreement because nothing was built to enforce it.
What it costs and how the pricing usually breaks down
Pricing for this kind of engagement is typically structured as a fixed-fee build phase, commonly running two to five months depending on data quality and how entangled the CRM already is, followed by a monthly retainer for ongoing optimization as the scoring model needs recalibrating against new closed-won data and as the business's ICP shifts. Be cautious of a consultant quoting a flat number without first seeing your CRM data or asking about your current MQL volume, since the actual effort depends heavily on how messy the existing setup is, a company migrating from spreadsheets with clean discipline is a very different project from a company with three years of unmaintained HubSpot data and no agreed definitions. The retainer phase matters more than most buyers expect going in, because a scoring model built once and never revisited degrades as your business and buyer profile evolve.
How to vet a consultant before you sign anything
Ask to see how they approach the closed-won analysis specifically, not just the workshop facilitation, because the facilitation is the easy, visible part and the data analysis is the part that actually determines whether the new definition holds up. Ask what happens to the definition and scoring model after the engagement ends, if the answer is a document with no CRM automation behind it, you are buying a workshop, not a system. Ask for a specific example of a rejection-reason loop they built for a past client, and what changed in the scoring model as a result, a consultant who cannot describe a concrete before-and-after has likely not run this loop in practice. And ask directly what your current MQL-to-SQL conversion rate would need to be before this engagement makes sense for your stage, a consultant confident in the work will tell you honestly if you are too early for it rather than sell you the engagement regardless.
Red flags that mean you should walk away
A few signals reliably predict a disappointing engagement. A consultant who proposes a fixed scoring model and workshop agenda before ever asking to see your CRM data is selling a template, not a diagnosis. A proposal that never mentions your existing sales cycle length, deal size, or current MQL volume is not built around your business, generic frameworks copy-pasted across clients rarely survive contact with a real, idiosyncratic sales process. A consultant unwilling to commit to a written diagnosis before recommending a fix is asking you to trust their instincts over your own data, which defeats the purpose of hiring someone to build a model around evidence rather than opinion. And if a proposal has no language at all about what happens to the scoring model and SLA enforcement after the engagement ends, assume the answer is nothing, and budget separately for maintaining it yourself.
FAQ
They diagnose why leads are being lost between marketing and sales using your own closed-won and closed-lost data, then build a scoring model, CRM automation, and a joint definition that the two teams actually keep using, rather than facilitating a one-time workshop.
Most engagements are priced as a fixed-fee build phase of two to five months, followed by a monthly retainer for ongoing optimization. The exact cost depends heavily on how much CRM cleanup and historical data analysis is required before the definition work can even start.
An internal workshop can produce an agreed definition, but it usually lacks the neutral authority to resolve a long-running disagreement and the closed-won data analysis to base the definition on evidence rather than opinion. It also rarely results in CRM automation that keeps the definition enforced after the meeting ends.
If you are running under roughly 50 leads a month or don't yet have a full year of closed-won data to analyze, the engagement doesn't have enough signal to work from. The honest move at that stage is basic CRM discipline first, then this engagement once volume and data catch up.