A partner signs in March. In June someone asks what the partnership has delivered, and the honest answer is: nothing yet. Everyone in the room hears failure. Most of the time it is not failure. It is the scoreboard measuring the wrong thing at the wrong moment.
Partner revenue is the last thing to move. Before a partner brings you a deal, their sales team has to know your product exists, believe it will make them look good, meet a customer who needs it, and get through both companies’ processes to close it. Each of those takes months, and none of them shows up on a revenue chart. So the program looks dead exactly when it is doing the work that will make it alive, and the people funding it start to pull back at the moment they should hold steady.
The scoreboard lags. It always has.
Amazon’s stock fell by more than ninety percent in the dot-com crash. Analysts wanted profit, and they wanted it that quarter. Bezos kept measuring the things he could control and that he believed would compound: customer experience, logistics, the systems underneath the store. The scoreboard caught up two decades later, and it caught up in a way the quarterly critics could not have imagined.
A partner program is the same shape, on a smaller scale and a shorter clock. The results you want are downstream of work you can measure now. If you only look at the result, you will make the wrong decision about the work.
What a partnership does before it can pay
I led a partner ecosystem of twenty partners generating $25M+ a year. None of them started paying the day it signed. The ones that paid best had something in common long before the first deal, and it was visible if you knew where to look.
The exchange was written down. Both sides could say, in a sentence, what they gave and what they got, and the sentence held when you tested it against their systems, their knowledge and their processes. A partnership where one side of that page is empty will not be rescued by activity.
Someone owned it. One name on each side, with the time to do the job, not a person who touched partners in the gaps between three other roles.
The first joint conversation with a customer happened early, before anyone had polished a deck. That conversation told you more about whether the partnership would work than a year of forecasting.
And the small things were kept: introductions answered, commitments from the last call done before the next, the partner’s own review prepared from real data instead of memory. Those are the inputs. Partner-sourced and partner-influenced pipeline, time to the first joint deal, whether every partner is reviewed on a rhythm, whether a signal was caught before the date it mattered. They move within weeks, they are inside your control, and they predict the revenue better than the revenue predicts itself.
The full-execution test
Measuring inputs is not an excuse for a program that never pays. It is what makes the judgement honest. If the exchange was agreed, the owner did the work, the joint conversations happened and the follow-through held, and after a reasonable run the partner still brings nothing, then only two explanations are left: the exchange was wrong, or something outside both companies changed. Either way, the answer is to fix the exchange or end the partnership, not to add three more partners and hope the average improves.
That is a very different conversation from “revenue is flat, the program is failing.” One leads to a decision. The other leads to a reorganisation.
Where programs actually die
Rarely at the start. They die in month five, when the launch energy has gone, the partner manager has been pulled onto a customer escalation, the monthly review slips to quarterly and then to never, and the partner quietly concludes that nobody on your side is home. Twenty partners was the right number for us because every one of them had a reason to work and a person on our side whose job it was. A longer list would have been a longer list of quiet partners.
Persistence in a partner program does not mean waiting. It means doing the same unglamorous things every week, for every partner, after the point where it stopped being interesting. Most of that work can now be carried by a system: the research, the preparation, the follow-ups, the records. What cannot be carried is the decision to keep going when the scoreboard says stop.
The rule
Measure what a partnership does before it can pay, and judge it on that until it has had a fair run. Then judge it hard. The scoreboard catches up with the inputs. It always does, in both directions.
What does your partner scoreboard show for a partnership that signed three months ago, and does it tell you anything you could act on this week?