RecordBook guide
The Co-Sell Operating Model: Roles, Cadences and Metrics
Co-selling works when it runs like a system: clear roles on both sides, a short meeting rhythm and a few metrics everyone trusts. Here's the model.
Most co-sell programs don’t fail on strategy. They fail on a Tuesday, when a joint deal needs a follow-up and each side assumes the other one is sending it. The partnership looks great in the kickoff deck and stalls in the day-to-day.
What separates the partner teams that make co-selling work is a co-sell operating model: who owns what, when the two sides meet, and how they measure progress. Co-Selling 101 covered what co-selling is and why it broke. This is the model that keeps it running.
What an operating model is, and what it isn’t
It isn’t a partner program document, a tiering scheme or a marketing plan. It’s the working agreement between two sales teams: the roles each side fills, the meetings they hold, the rules they follow and the few numbers they watch.
A good one fits on a page. If both teams can’t explain it in two minutes, nobody is following it.
The roles
Each company needs the same four roles. In a small team one person may wear two hats, but every role needs a name next to it.
- Partner or alliance manager. Owns the relationship and the joint pipeline process. Runs the meetings, chases hygiene and handles escalations. Doesn’t own every deal.
- A deal owner on each side. A named seller for every joint opportunity, responsible for their company’s next step and close plan.
- Partner ops or RevOps. Keeps the shared record clean, maps the two sides’ stages, builds the reports and enforces the rules of engagement.
- An executive sponsor. One per side. Unblocks deals, attends the quarterly review and signs off on joint goals.
The most common failure is fuzzy deal ownership. Set the rule on day one: every joint deal has one named owner per company before it counts as pipeline. It’s the first hygiene rule in partner pipeline management for a reason.
Write down the rules of engagement
Before deals start flowing, agree on the rules in writing. One page is enough. It should answer five questions:
- How does a deal become a joint deal? Usually through deal registration, with a clear approval step.
- Who leads which accounts? Which segments, regions or named accounts each side drives.
- How are conflicts resolved? Who decides, and how fast.
- How is credit assigned? Define partner-sourced and partner-influenced before the first deal closes, not after.
- What gets shared? Joint deals, yes. Each side’s full pipeline, no.
Revisit the page every quarter. Rules that nobody has read in a year are rules nobody follows.
The cadence
Keep the meetings few and short. The aim is to catch problems while a deal can still move, not to read each other a status report.
- Weekly, 20–30 minutes: a joint pipeline scan. Deals with no next step, close dates that just slipped, deals that haven’t changed in two weeks.
- Every two weeks: a forecast review of commit and best-case deals, using the same stage definitions on both sides. See joint revenue forecasting.
- Monthly: a partner business review. New pipeline, wins and losses, and what’s blocking deals.
- Quarterly: joint planning with the executive sponsors. Targets, target accounts and any program or marketplace motions, such as AWS ACE.
The weekly scan matters most. If it runs off a shared pipeline that both sides keep current, prep time drops to nearly zero and the meeting is about decisions instead of data gathering.
The metrics
Pick a handful, define each one once, and track them the same way every period. These cover most programs:
- Partner-sourced pipeline: new opportunities the partner brought to you.
- Partner-influenced pipeline: existing opportunities the partner materially helped move.
- Joint win rate: how co-sell deals close compared with your solo deals.
- Cycle length: days to close for joint deals versus solo ones.
- Stalled rate: the share of joint deals with no meaningful change in the last few weeks.
- Time to accept: how long a registered deal waits for a decision.
Resist tracking thirty numbers. If a metric moving wouldn’t change a decision, drop it.
Where the operating model lives
A document can hold the rules. It can’t hold the pipeline. The model only works if the deals it governs are visible to both teams and current, and that’s exactly what breaks when each side’s deals live in its own CRM and the joint view is a spreadsheet rebuilt every Friday.
Put the joint deals in one shared record that both CRMs feed, and the roles, the cadence and the metrics all read from the same place. The weekly scan becomes a filter, the forecast is a live number and the metrics calculate themselves.
Common questions
Who should own co-selling: partnerships or sales?
Both, in different ways. The partnerships team owns the relationship, the rules and the process. Sales owns the deals. Co-selling breaks when partnerships owns deals it can’t close, or when sales ignores a process it never agreed to.
How many partners should run this model?
Start with one or two strategic partners and run the full model with them. Give the long tail a lighter version: registration, a named contact and a monthly check-in. Expand the full model when a partner’s pipeline justifies it.
How long before a co-sell program shows results?
New pipeline usually appears in the first quarter. Closed revenue lags by roughly one sales cycle. Judge the early months by leading indicators instead: registrations submitted, time to accept, stalled rate and joint pipeline created.
Run co-selling on one shared pipeline
RecordBook connects your CRM and your partner’s into one shared pipeline, flags stalled co-sell deals and keeps the joint forecast current, so your operating model runs on data instead of status calls. Try it free, no credit card required.