Partner teams are usually the first line item a software as a service (SaaS) chief financial officer (CFO) circles when the budget tightens, and the reason is uncomfortable but fair: most of them cannot prove what they returned. They talk about ecosystem momentum, relationship depth, and strategic alignment, while the sales organization next door shows a number. Bryan Mobley, who has spent his career building partner organizations in SaaS, argues the fix is less about storytelling and more about arithmetic. Executive sponsorship is not won in a quarterly business review deck. It is won inside the same return-on-investment (ROI) model finance runs on every other initiative in the company, and partner leaders who refuse to engage with that model should not be surprised when sponsorship evaporates.
Sourced Revenue Is The Only Unarguable Currency
Ask Mobley what single factor secures and keeps executive backing and the answer is not nuanced. “The simple answer is sourced leads,” he says. A partner team contributes to revenue in one of two ways: it brings net new leads, or it influences opportunities the company was already working. Both matter. They do not carry equal weight in the room where funding decisions get made. “The value of sourced leads is unquestionable. If the partner team brings a net new opportunity that is later closed, that is net new revenue the company otherwise would not have had.”
That distinction explains why so many partner leaders feel misunderstood by their own executive teams. Influence is real, but it is contested by definition, because the direct sales rep on that deal has a competing claim to it. Finance resolves the ambiguity with a haircut. Mobley has seen sourced leads credited at full value or better, while influenced opportunities are commonly discounted to a 20 or 30 percent contribution in the model. So a partner leader who builds a case almost entirely on influence is arguing from a position that has already been marked down by two thirds before anyone reads the slide. The practical implication is blunt: a program that cannot source is a program that will always be negotiating from weakness, no matter how much pipeline it touches.
Build The Case Finance Is Already Running
Most partner leaders assume they need to persuade a chief executive officer (CEO) or chief revenue officer (CRO) of something philosophical about ecosystems. Mobley’s view is that the argument has already been framed for them, and the frame is a spreadsheet. “In most SaaS companies, finance will run an ROI calculation on the investment for all initiatives,” he says. “To be funded, the partner team must be contributing an ROI high enough to warrant funding.” The bar he names is specific. “As a partner team you need to deliver ROI of 2–4X your cost as a team.”
Knowing that number changes how a partner leader runs the function. It turns an abstract mandate to build relationships into a budgeted target with a denominator, and it makes every headcount request a question about what that person will source rather than who they will meet. It also reframes the conversation with the CRO. A leader who walks in holding the same model finance uses, with sourced and influenced revenue already weighted the way the company weights them, is no longer asking for faith. The weighting matters as much as the gross figure. Two teams producing identical pipeline numbers can land on opposite sides of a funding decision purely on the sourced-to-influenced mix, and the leader who understands that mix early can build toward the version of the number that survives scrutiny.
Not All Partners Pay The Same Way
The second trap is treating the partner roster as a single undifferentiated asset. They do not contribute identically, and Mobley is direct that the C-suite does not see them identically either. Some partners bring a technical integration or complementary solution that lets a company qualify for a request for proposal (RFP) it previously could not answer at all. Others are genuinely good at generating leads. Others are strongest at co-selling alongside the direct team. “It takes a mix of partner types to accomplish a fully functioning and contributing partner program,” he says. A roster weighted entirely toward one of those motions produces a lopsided contribution that is easy for an executive to dismiss as narrow.
The cloud hyperscalers sit in a category of their own, and Mobley treats them as the most underused lever available to a SaaS company that already consumes cloud resources. Almost every Fortune 500 company has a relationship with Microsoft, AWS, or both. Through their partner programs, a SaaS vendor can access those sales teams to help close deals, and the cloud providers offer incentives to the end customer to buy that SaaS offering through the Marketplace. “This creates a win-win for all three,” he says. For a partner leader trying to show sourced revenue rather than influenced revenue, that path is unusually direct, because the introduction originates outside the company’s own sales motion entirely.
Expectations should scale with maturity, and Mobley is specific about the curve. Once relationships are built and the infrastructure is in place, which means contracts signed and marketplaces stood up, a program can expect to impact roughly 15 to 20 percent of revenue in year one. That figure should grow annually to reach 50 percent or more in a three- to four-year window, and incentives to the direct sales team can accelerate it. Executives who demand half of the revenue in year one will kill the program before the infrastructure exists. Partner leaders who never commit to the curve at all will be defunded for a different reason. Sponsorship survives where both sides agree in advance on what the number should look like each year, and then watch it move.
Follow Bryan Mobley on LinkedIn for more insights on partner strategy, co-selling, and partner-led revenue growth in SaaS.
