A partner programme funded on anecdote became a programme funded on 22% of new pipeline, in five months, with the attribution rule written down before the quarter opened.
Partners were influencing deals nobody could count, so the programme was funded on anecdote and cut first in every budget review.
Registered partners
212
On the portal at kick-off; 19 had produced anything in the previous year.
Active-partner ratio
9%
Partners with at least one registered opportunity in a rolling 90 days.
Registration compliance
31%
Partner-involved opportunities carrying an approved registration by stage 2.
Partner-sourced pipeline
Not measurable
No rule existed that separated sourced from influenced, so no reading was defensible.
Programme budget under review
$1.4M annual
Modelled: headcount, portal licence, market development funds.
The seam sat between the partner portal and the CRM. Registrations lived in one system, opportunities in the other, and nothing joined them — so partner-influenced revenue was invisible at exactly the moment the budget was defended.
Deals closed with partner involvement, uncounted
$6.1M
Trailing four quarters, reconstructed by matching portal registrations to closed-won accounts by domain.
Market development funds paid against no traceable outcome
$310K
Claims approved in the same period with no linked opportunity record.
Partner-sourced deals lost to channel conflict
$840K
Opportunities where a direct rep and a partner worked the same account without a registration in force.
$7.25M of revenue the programme could not evidence, against $1.4M of annual spend it was asked to justify.
01
Weeks 1–3
Reconstructed twelve months of partner-involved revenue by hand, then got sales, finance and partnerships to agree one attribution rule — sourced, influenced, or neither — in writing.
What we read
First honest number: partner involvement in 34% of closed-won by count, 0% of it countable in the system.
02
Weeks 4–8
Rebuilt deal registration so an approved registration creates the CRM opportunity rather than shadowing one. Registration approval moved to a two-day SLA with a named owner.
What we read
Compliance moved 31% → 62% inside four weeks, entirely because the path of least resistance changed.
03
Weeks 9–14
Retired the legacy tier model. Rebuilt tiers on registered pipeline produced in a rolling four quarters, with published thresholds so a partner can see what moves them.
What we read
27 partners moved down a tier and 11 moved up. Two escalations; both held, because the thresholds were published first.
04
Weeks 15–20
Installed a fortnightly partner pipeline read with the same two owners and the same four questions. Ran it six times with a Nuvello operator in the room, then twice observing, then left.
What we read
22% of new pipeline partner-sourced on the agreed definition — the first defensible reading the programme had ever published.
Partner-sourced pipeline
22% of new pipeline
First defensible reading; definition held constant since week 3.
Registration compliance
31% → 88%
+57 points, measured at stage 2 on the same population.
Active-partner ratio
9% → 27%
+18 points on a rolling 90-day basis.
Market development funds against traceable outcomes
12% → 91%
Claims linked to a registered opportunity before approval.
The attribution rule, the registration flow and the fortnightly read stayed with the partner team. No Nuvello operator is in the cadence today.
This is an illustrative composite. The numbers, phases and outcomes show how we baseline a motion, read a delta and hand the cadence back — they are modelled on the shape of RevOps work delivered through the network, not lifted from one named client. We publish nothing under a client's name without written sign-off.
A pricing change landed in month four and lifted deal size across all channels. We reported the partner delta on volume rather than value for that quarter and said why.
The partner management in fullWe start the same way every time: one baseline, one written definition, one cadence you keep after we leave.