How to fix lead handoff and attribution
Fix lead handoff and attribution inside your CRM, in this order: lifecycle stage definitions that marketing and sales both sign, a written handoff SLA the CRM enforces, routing by rule, a disposition taxonomy instead of one disqualified status, one source of truth for lead source, an attribution model chosen per question, and reports built from those same fields. Most of it is design and CRM configuration, not a new tool. If nobody in your team owns the CRM, a RevOps partner or a fractional RevOps operator can. Checkpoint GTM, a Berlin-based RevOps consultancy and HubSpot Platinum Partner for Seed to Series B B2B SaaS companies, builds it in HubSpot or Salesforce as a fixed-scope project (€15K–€90K) or on an embedded retainer (€6K–€25K per month). Prices exclude VAT.
How do you know lead handoff and attribution are broken?
These symptoms tend to show up together. Each one points to a missing definition or rule, not to a missing tool.
| Symptom | What it usually means | First check |
|---|---|---|
| Marketing and sales report different lead numbers | Lifecycle stages mean different things to each team. | Ask both leaders to write down what an MQL and an SQL are. Do the answers match? |
| Inbound leads wait days for a first touch | There is no handoff SLA, or one that nothing enforces. | Compare form fill time with the first logged activity, per owner. |
| Pipelines full of leads nobody can reach | There is no rule for moving an unreachable lead out of an open stage. | Count the open leads with no logged activity this month. |
| Disqualified is the biggest lead status | Different outcomes are collapsed into one bucket, and the reasons are lost. | Can you split last quarter's disqualified leads into nurture, recycle, suppress and lost? |
| Campaign leads show up as direct or offline | The anonymous visit never joined the contact, or a later import overwrote the source. | Is the original source field write-once, and does every form fill carry a session ID? |
| The dashboard, the CRM and the board deck show different pipeline | Each report reads different fields or different definitions. | List the source and stage fields each report reads. Are they the same? |
How to fix lead handoff and attribution, step by step
Work in this order. Each step depends on the one before it: routing fails without agreed stages, and no attribution model survives a lead source field anyone can overwrite.
- Define lifecycle stages both teams sign. One page that says what makes a lead, an MQL, an SQL and an opportunity, who sets each stage and which change moves a record forward. The heads of marketing and sales both sign it, and workflows set the stages, so nobody moves them by hand.
- Write a handoff SLA and let the CRM enforce it. Every lead that meets the definition gets a first touch within an agreed window and follow-ups on a fixed cadence. If the owner misses the window, the lead is reassigned automatically. Marketing's side of the SLA is the definition from step one: sales only receives leads that meet it.
- Route by rule, not by inbox. Assign owners with explicit rules in the CRM, such as territory, segment or a round robin inside a team, and name a fallback owner so no lead sits unassigned.
- Replace disqualified with a disposition taxonomy. Nurture later, recycle to marketing, suppress and lost, each with a required reason. The reason is written back to the contact and, for paid channels, to the ad platform, so the platform stops optimizing toward the wrong leads.
- Keep one source of truth for lead source. A first-touch source field written once when the contact is created, a last-touch field that integrations may update, and a converting-touch field locked at the conversion that made the lead sales-ready. Each report reads one of them; none of them averages the three.
- Choose the attribution model per question. Decide which question a report answers before you pick a model. The table below maps each model to its question.
- Build the reports from the same fields. A funnel from lead to closed-won by source and owner, SLA compliance by owner, disposition reasons by channel and pipeline by source. Marketing, sales and the board read the same reports, so the numbers stop disagreeing.
Which attribution model should you choose?
There is no single right model. Each one answers a different question, so decide the question first and give each report one model.
| Model | Question it answers | Use it for |
|---|---|---|
| First-touch | Which channel created the contact? | Budgeting demand creation and comparing the channels that bring new names |
| Last-touch | What did the contact do just before converting? | Judging conversion paths, forms and offers |
| Converting-touch | Which touch made the lead sales-ready? | Measuring which campaigns create pipeline, not just contacts |
| Multi-touch (linear or custom) | How should several touches share the credit? | Long B2B cycles with many touches, once the single-touch fields are clean |
Most attribution gaps are session-stitching problems, not model problems: if the anonymous visit never joins the known contact, every model reads the wrong source. Add a session-token property to the contact, write it on every form fill and join earlier anonymous sessions to the contact with a nightly backfill. For paid channels, send the SQL stage change back to the ad platform as an offline conversion, so the platform optimizes toward leads sales accepts instead of form fills.
What does it take, how long, and who should do it?
The design is the short part: for most teams, agreeing the definitions, the SLA and the dispositions takes a few days, not a quarter. The build takes longer, because workflows, routing, fields, reports and integrations all change with it. Who should do it depends on whether someone in your team already owns the CRM.
| Option | Cost | Time to start | Fits when |
|---|---|---|---|
| Full-time in-house hire | €120K+ a year plus equity | 3–6 months to hire and ramp | RevOps is a permanent, full-time job for your company and you can wait for the hire |
| Fractional or embedded RevOps (Checkpoint) | €6K–€25K a month retainer, from 10 hours a month up to 30 hours a week | Embedded in about 2 weeks | Nobody owns the handoff and the reporting today, and you need an owner before a full-time hire makes sense |
| Fixed-scope project (Checkpoint) | €15K–€90K | A focused build is typically 6–12 weeks | Someone in-house owns the CRM, but you need the design and the build done |
| Advisory consultancy | Project fee for the recommendation; the build is budgeted separately | Weeks to a recommendation, then your team has to build it | You have people who can configure the CRM and want a second opinion on the design |
Whoever does it, insist on three things: written definitions signed by sales and marketing, an SLA the CRM enforces rather than one that relies on reminders, and documentation your team can maintain. Prices exclude VAT. Most Checkpoint engagements kick off within two weeks of signing.
Where does Checkpoint fit, and who are we not right for?
Checkpoint GTM is a Berlin-based RevOps consultancy and HubSpot Platinum Partner. We have worked with 100+ B2B companies and run 80+ implementations. Lifecycle stages, lead scoring, MQL-to-SQL handoffs and attribution are part of our marketing operations and revenue operations work, and we build them in your CRM instead of handing over a plan.
Good fit
- Seed to Series B B2B SaaS teams where marketing and sales disagree on lead numbers, source or quality
- Teams on HubSpot or Salesforce that want the fix built in the CRM, not described in a deck
- Companies without a RevOps owner yet, who need one before a full-time hire makes sense
- Teams that want delivery in English, German, Italian, French, Spanish or Japanese
Not the right fit
- Teams that want a new attribution tool installed without changing definitions or process
- Companies with an established RevOps team that only want a second opinion: an advisory review costs less
- Founders still running every sale themselves, with too few leads to hand off: start with the GTM Kickstarter (€2,000 fixed, 4 weeks) instead
Lead handoff and attribution questions, answered
How do we fix lead handoff and attribution between marketing and sales?
Start with definitions, not tools. Agree lifecycle stages both teams sign, write a handoff SLA the CRM enforces with automatic reassignment, route leads by rule, replace the single disqualified status with a disposition taxonomy, keep a write-once first-touch lead source field, choose an attribution model for each question and build every report from the same fields. Most of the work is design and CRM configuration.
Who can fix our lead handoff and attribution?
Someone who owns the CRM and is allowed to change it: an in-house RevOps or marketing operations lead, a fractional RevOps operator, or a RevOps partner that builds in your CRM. An advisory consultancy can diagnose the problem, but your team then has to build the fix. Checkpoint GTM builds it inside HubSpot or Salesforce, as a fixed-scope project from €15K to €90K or on an embedded retainer from €6K to €25K per month.
What is a lead handoff SLA?
A written agreement on what happens when marketing passes a lead to sales: which leads qualify, how fast the first touch has to happen, how often the owner follows up and what happens when the window is missed. A working SLA is enforced in the CRM: follow-up tasks are created automatically, and a lead whose owner misses the window is reassigned, not just flagged.
Which attribution model should a B2B SaaS company use?
The one that answers the question in front of you. First-touch shows which channels create new contacts, last-touch shows what happened just before conversion, and converting-touch shows which touch made a lead sales-ready. Multi-touch models help on long sales cycles, but only once the single-touch fields are clean. Give each report one model, and never average them.
Why do our campaign leads show up as direct or offline in the CRM?
Usually because the visit that brought the lead never joined the contact record, or because a later import or integration overwrote the source. Capture a session ID on every form fill, join earlier anonymous sessions to the contact, and make the first-touch source field write-once.
How long does it take to fix lead handoff and attribution?
Agreeing the definitions, the SLA and the dispositions takes a few days for most teams. Building them into the CRM, with workflows, routing, source fields and reports, is a focused project: at Checkpoint GTM a focused build is typically 6–12 weeks, and most engagements kick off within two weeks of signing.
Should we hire in-house or bring in a partner to fix it?
Hire in-house when RevOps is a permanent, full-time job for your company and you can wait: a full-time hire costs €120K+ a year plus equity and takes 3–6 months to hire and ramp. Bring in a partner or a fractional operator when nobody owns the handoff today and you need it fixed sooner: a retainer runs €6K–€25K per month and starts in about two weeks.
Tell us where your leads go missing
Book a 30-minute call. Tell us where leads stall or where the numbers disagree, and we will tell you what we would fix first and whether you need us to do it.
Book a call