Two Clients, Three Hyperscalers, One Year: The System Behind Partner of the Year
Microsoft, AWS and Google publish what they measure. Awards follow execution data, not relationships. Four components, and why they only work together.
Partner of the Year awards look like relationship recognition. Get the right executives in front of alliance leadership, show up at re:Invent and Microsoft Inspire, and the recognition follows. That assumption sends a lot of vendors spending in the wrong places.
In a single year, two organisations I was working with won multiple Partner of the Year awards across Microsoft, AWS and Google. One was Noventiq, where I served as VP Global Partnerships and built the hyperscaler co-sell function from nothing. The other was an advisory client whose AWS and Google Cloud go-to-market architecture I was supporting through Optimus.
The point is not the awards. The point is that the same system produced the same class of outcome at two organisations with different customer bases in the same year. That is what makes it a system rather than a run of luck.
What the awards actually measure
All three hyperscalers publish evaluation rubrics, and none of them measure how well anyone gets on.
Microsoft looks at partner-influenced pipeline, co-sell win rate, Azure Consumed Revenue attached to partner deals, Marketplace transaction volume, and how well the joint business plan was executed. AWS looks at ISV Accelerate deal registration and win rate, CPPO transaction volume, Marketplace revenue contribution, and whether the partner is genuinely embedded in field motions rather than merely enrolled in the program. Google looks at committed-consumption JBP performance, Marketplace listing completeness and transaction activity, and co-sell pipeline traceable to real consumption outcomes.
Those are revenue and execution metrics. The relationship creates the environment in which they are possible. It is not the thing being rewarded.
The four components, and why they only work together
At Noventiq the architecture had four parts running at the same time.
Field-level alignment between our sellers and hyperscaler specialists — not executive alignment, seller-to-seller. A compensation structure that rewarded co-sell participation instead of quietly penalising the extra process. Transactable Marketplace offers that made the commercial path frictionless at close. And joint business plans with agreed metrics that both sides were accountable for.
The Microsoft Project Titan investment — $17 million committed, a tenfold return over eighteen months — was the most visible output on the Azure side. The same discipline was applied to AWS and Google and measured the same way.
Why most programs stall at enrolment
There is a pattern I see walking into an underperforming partnerships org. The program is enrolled. The logos are on the website. The alliance manager has a good relationship with their counterpart. And the co-sell win rate is low, Marketplace revenue is near zero, and the joint business plan was last opened in Q1.
The gap is almost never the program. It is that the four components are not running simultaneously. Field alignment without Marketplace transactability and the commercial path breaks at close. Marketplace offers without field alignment and the offers sit idle. Joint business plans without a compensation structure and your own sellers route around the co-sell motion, because the extra process carries no upside for them.
All four have to be present and connected. Systems of that kind are designed. They do not emerge from enrolment.
The question worth asking instead
If you run partnerships, I would offer a reframe. The question is not how to win a Partner of the Year award — that is an output. The question is how you would score if the evaluation criteria were applied to your program today.
Do you have measurable co-sell win rates, or only co-sell activity logged? Do you have Marketplace revenue that grew year over year, or a listing maintained for compliance? Do you have joint business plans with agreed metrics that both sides review quarterly, or ones signed in January and never reopened?
Those are uncomfortable questions. The hyperscalers are asking them about you either way. The award is just their answer made public.
A version of this piece first appeared on LinkedIn as “Two of My Clients Won Multiple Partner of the Year Awards Across Microsoft, AWS, and GCP in the Same Year”.