Revenue does not usually leak in one dramatic moment.

It leaks between teams.

Marketing generates demand that sales does not trust. Sales accepts leads but does not follow up consistently. Account executives close deals with promises customer success discovers too late. CS identifies expansion signals that sales never acts on. Finance finds contract details after the customer has already been told something else.

Everyone can be working hard and the system can still leak.

The handoff is where local effort becomes company execution. If handoffs are vague, revenue depends on heroics and personal relationships.

A handoff is a contract

A handoff is not "I sent you the thing."

A handoff is an operating contract between teams. It defines:

  • What qualifies work to move
  • What information must be included
  • Who accepts ownership
  • How quickly action is required
  • What happens if the handoff is incomplete
  • How feedback flows back to the previous team
  • Which metric shows whether the handoff works

Without those rules, teams argue from their own incentives.

Marketing says the lead was qualified. Sales says it was junk. Sales says the deal was clean. CS says the customer was mis-sold. CS says the account has expansion potential. Sales says there is no budget. Finance says the contract does not match the order.

RevOps should turn those arguments into explicit agreements.

Marketing to sales: quality and speed

The marketing-to-sales handoff needs two things: quality standards and response standards.

A useful lead handoff defines:

  • Fit criteria: segment, company size, geography, use case, excluded categories
  • Intent criteria: requested demo, product signal, event attendance, content sequence, partner referral
  • Required fields: company, contact, source, campaign, use case, consent status
  • Acceptance criteria: what sales must do to accept or reject
  • Follow-up SLA: time to first touch, number of attempts, channel mix
  • Feedback loop: rejected reason, disqualification reason, outcome by source

The important part is not whether the company uses MQL, PQL, SQL, or another acronym. The important part is whether the work is accepted, acted on, and learned from.

Sales to customer success: promises become obligations

The sales-to-CS handoff is where many companies discover the real deal.

The customer bought one thing. The deck implied another. The contract says something specific. The implementation team hears about a critical requirement for the first time after signature.

A clean handoff should include:

  • Customer goals and success criteria
  • Primary use case
  • Stakeholders and power map
  • Contract terms and commercial commitments
  • Promises made during sales
  • Known risks or product gaps
  • Implementation timeline assumptions
  • Expansion hypothesis, if relevant
  • Support or service expectations

CS should not have to reverse-engineer the sale from call recordings and Slack threads.

CS to finance: commercial reality has to match billing reality

Finance is often treated as the final administrative step. That is risky.

Billing terms, contract dates, renewal terms, usage commitments, discounts, ramp schedules, and special conditions all affect revenue recognition, cash collection, and customer experience.

If finance gets incomplete information, the customer experience suffers and the business loses control.

A practical handoff to finance includes:

  • Signed order form or contract
  • Billing entity and contact
  • Start date and renewal date
  • Payment terms
  • Discounts and approvals
  • Usage or consumption commitments
  • Implementation fees
  • Non-standard clauses
  • Renewal or cancellation terms

This is not bureaucracy. It is how the company avoids promising one thing, billing another, and reporting a third.

Exceptions need a path

Every handoff will have exceptions. The mistake is pretending otherwise.

RevOps should define exception paths:

  • What happens if required fields are missing?
  • Who can override qualification rules?
  • When can sales accept a lead outside ICP?
  • What deal terms require finance approval?
  • What promises require product or CS sign-off?
  • Who resolves ownership disputes?

If there is no exception path, exceptions become politics.

The artifact: handoff contract

A simple handoff contract can fit on one page:

From team: Marketing

To team: Sales

Object: Qualified lead

Entry criteria: Fit plus intent threshold met

Required information: Source, use case, company size, contact role, campaign, consent

Receiving owner: SDR or AE based on routing rules

SLA: First touch within defined window; sequence started or rejection logged

Rejection reasons: Bad fit, student/vendor, duplicate, no intent, missing required data

Feedback metric: Acceptance rate, conversion to opportunity, response time, disqualification reason quality

Exception owner: RevOps plus sales/marketing leaders

The format matters less than the clarity.

Bottom line

Handoffs are not administrative details. They are the connective tissue of the revenue system.

When handoffs are implicit, teams blame each other. When they are explicit, the company can see where work breaks and fix the operating rule.

Revenue leaks where ownership changes.

RevOps should make those moments impossible to ignore.