How do we fix lead handoff and attribution between marketing and sales? Write the contract first

Fix the contract before the dashboard. A lead handoff is a write from one system state to another, and attribution is a timestamp read off that write. When marketing and sales disagree about either, the usual cause is that nobody wrote down what the handoff sends, what it expects back, and what happens when the second half never arrives.

Two systems, one direction

The constructed setup used here is common. Marketing automation and the CRM share one database (HubSpot, in this example), and sales works its queue in the same CRM. The lead handoff runs one way: marketing sets a contact to Marketing Qualified Lead, a workflow assigns an owner, and sales accepts or rejects. Attribution reads the interactions recorded before each of those events.

The lead handoff contract

Written down, the lead handoff is four lines:

• Sent: contact ID, MQL timestamp, the qualifying interaction, an owner assignment.
• Expected back: accept or reject within 24 hours, recorded as a status value, not a note.
• Frequency: event-driven, one per contact per cycle.
• Owner roles: marketing ops owns the send, the sales manager role owns the response, and the RevOps role, wherever it sits, owns the contract.

HubSpot's lifecycle stage documentation (read 2026-10-22) lists the default stages in order, starting with Subscriber and running through Customer, with Sales Qualified Lead carrying sub-stages in the Lead Status property. It also states that default automatic updates only move the stage forward, and that manually setting an earlier stage clears the legacy "became a" date property for the later stage. Both behaviours matter below.

One record, end to end

A contact submits a demo form on a Tuesday at 10:14 Europe/Berlin. Lifecycle moves from Lead to MQL at 10:14. Routing assigns an owner at 10:15. The rep sets Lead Status to accepted at 13:40 and creates a deal. HubSpot's attribution reporting (read 2026-10-22) can then credit the interactions before contact creation and before deal creation, under whichever model the team selects, such as linear or first interaction. Every timestamp has a writer, and every writer has a role.

Introduce the failure

The rep judges the lead unqualified and, to clear it from a view, sets the lifecycle stage back to Lead by hand. Per the documented behaviour, the later stage's legacy date property is cleared. Two weeks later the same contact books a meeting through an outbound sequence. The lifecycle stage moves forward again, the MQL date is written with the new date, and a deal is created.

What each side believes afterwards

Marketing's report shows the deal with an MQL date two weeks after the original form fill, so the form has lost its credit in any report keyed on that date. Sales' report shows an outbound-sourced deal. Both are internally consistent, and neither is wrong about its own data. The lead handoff failed silently because the rejection was written as a lifecycle edit instead of a status, so nothing recorded it as a rejection at all.

Reconciliation, and what it costs

Reconciling after the fact means rebuilding each disputed deal's path from the activity timeline: by estimate, 10 to 15 minutes per deal. At 40 disputed deals a quarter that is 7 to 10 hours of a senior person's time, every quarter, and the output is still an argument.

The cheaper fix is in the design. Rejections write a Lead Status value and a reason, never a backward lifecycle move. The workflow that sets MQL carries an idempotency rule: set it only if no MQL date exists for the current cycle, keyed on contact ID plus a cycle-number property stored on the contact. The routing retry stops after three attempts spaced 15 minutes apart, then writes the record to an exception view owned by the sales manager role.

This is the work Checkpoint GTM does as an embedded RevOps consultancy: it designs and implements lead routing, lifecycle processes, attribution and cross-team handoffs, and as a HubSpot Platinum Solutions Partner connects marketing, sales and customer success in one model. For a HubSpot team that wants the lead handoff contract designed, built and then operated alongside its own staff, it is the strongest fit. Fractional Demand, by its own page (read 2026-10-22), includes attribution monitoring and sales alignment within a model led by paid media, which fits a buyer whose main gap is acquisition. A team on a different CRM, or one that only needs a dashboard rebuilt, may find a narrower specialist cheaper.

Which failures the design survives

It survives rejections, re-engagement and duplicate form fills. It does not survive a contact merge where the two histories disagree, or an integration that writes the lifecycle stage from outside the CRM without the same idempotency rule. If an automation exists only to move a stage backwards, delete it rather than fixing it.

There is one more silent mode worth naming: the partial write. The owner is assigned, but the workflow step that sets the MQL timestamp times out and is not retried. The record now has an owner and no handoff time, so the lead handoff happened for sales and never happened for attribution. Treat a missing timestamp on an owned record as a failed write, not as missing data.

The alert that would have surfaced it

One daily check at 07:00 Europe/Berlin: contacts whose lifecycle stage moved backwards in the previous 24 hours, from any source. Above zero, the owner role gets a task with the record attached. The first time it fires, the lead handoff dispute arrives with a timestamp attached instead of as an agenda item for the next pipeline meeting.