The Partner Paradox

Because of Datafruit, I spend a lot of time talking to founders who run SIs. Many of them are frustrated about their growth, and we often end up discussing what's blocking it.

One thing that has come up a lot now is their partner program—how it isn't producing the deal flow they expected, how the relationship with the vendor feels one-sided, and how they can't quite figure out what to do about it. After hearing the same complaints from a few different founders, I started to suspect there was something structural going on, so I did a deep dive and researched it. I discovered that the partner program is rarely the real problem, but it's a useful place to start because the thing that's broken about it points to a mismatch that shapes almost everything else about how the firm grows.

People often blame the vendor's sales team for not passing leads, or they blame the program structure for being unfair, or they blame the big SIs for hoarding the best deals. These explanations feel true because they contain a grain of truth, but they miss the structural issue underneath.

The reason most technically excellent SIs struggle inside partner ecosystems isn't competitive intensity or bad luck. It's that their business was designed to fulfill demand, not create it. And the vendor's partner program was designed to reward the opposite.

What are partner programs even for?

Vendors build partner programs to make more sales. The whole point, from the vendor's perspective, is to extend their reach by having more people generating pipeline that wouldn't otherwise exist. That's the economic bargain: the vendor gives you access to their platform, their brand, their training, and in return you bring them customers they couldn't have reached on their own.

From the vendor's perspective, they make this distinction very explicit. All vendors track two categories of partner contribution: partner-sourced revenue, where the partner originated the deal, and partner-influenced revenue, where the partner supported a deal already in motion. Vendors consistently allocate their best co-selling support, executive access, and deal routing to partners who source pipeline. This is because a partner who only influences deals is useful but replaceable. Meanwhile, a partner who brings net-new customers is strategic.

Many service partners, however, join with a different expectation. They expect the vendor to be a source of deal flow. This isn't naive at all because it's the logical extension of how SIs are built. After all, an SI's core asset is delivery capability. Technical talent, methodology, domain expertise, and client management are all the capabilities core to running the firm. The entire organizational structure is oriented around one question. "Can we deliver this project well?"

This is the partner paradox. The vendor needs what the firm isn't built to provide, and the firm expects what the vendor isn't incentivized to give.

When SI firm leaders recognize this mismatch, the instinct is to fix it the way a software company would. They try to hire someone to build pipeline, and/or get a BD person, or two. The common thought is, "If we need to generate more sales, why not stand up a sales function?" Unfortunately, this almost always fails. And it fails in a specific, predictable way that's worth describing, because if you've lived through it, knowing the pattern will save you from repeating it.

What usually happens is the firm hires a business development person who was successful at a larger organization. Usually it's a firm with established brand recognition, a documented sales processes, a clear ICP, and a CRM workflow. Then, they arrive at your SI where all of those things exist in the founder's head and nowhere else. For six to nine months, they try to replicate what they do instinctively, while the founder remains the primary closer trying to carry their compensation. Eventually, the relationship ends, at which point the founder concludes that they "hired the wrong person" and either try again or give up. Some firms cycle through this two or three times before recognizing that the problem isn't the hire. This pattern is so common that there are consulting firms built entirely around solving it!

Worst of all, the economics of the attempt are unforgiving, too. Many firms don't have the financial runway to survive this kind of misplaced sales bet.

What phase is your ecosystem in?

Before I discuss how to fix any of these problems, let us first step back and try to diagnose the environment you are in. This is necessary to determine what will work for your firm. This is because the structural mismatch wouldn't matter much if partner ecosystems stayed the way they were when you joined. But ecosystems have a lifecycle, and knowing where yours sits on that curve changes what's rational for you to do.

Phase 1: Talent-constrained. In the early days of any platform, the bottleneck is people who can implement it. If you can deliver a project, you get work from the vendor. They route to pretty much anyone with enough certifications because there aren't enough hands to go around. Therefore, demand generation isn't required; there is more demand than the ecosystem can absorb. This is the golden era for delivery-focused SIs.

Phase 2: Talent-abundant, demand-constrained. As the ecosystem matures, the number of capable delivery partners outpaces the deal flow. The vendor starts choosing where to route work, and the selection criterion shifts from "can they deliver?" to "do they bring us pipeline?" This is where most large platform ecosystems live today, and it's where the partner paradox bites hardest.

Phase 3: Consolidation. The biggest SIs acquire successful smaller ones. The vendor restructures the program to raise barriers and concentrate benefits among fewer, more capable partners. Generalists get squeezed. Specialists survive if they're differentiated enough to generate their own demand.

Given enough time, the shift from phases 1 to 3 is largely inevitable for any partner ecosystem. The Salesforce ecosystem, for example, illustrates the full arc. It now has over 3,800 consulting partner firms worldwide and more than 170,000 certified experts. The ecosystem's revenue is roughly six times the size of Salesforce's own. Earlier this year, Salesforce consolidated from four partner tiers to two, replaced 170 legacy badges with 28 focused competencies, and reoriented the program toward AI-driven delivery and verified customer outcomes. This is phase 3; it explicitly rewards partners who can create their own demand around Salesforce's new products, not partners waiting for implementation work to arrive.

So what do you actually do?

Given all of this, how do you actually solve the partner paradox? The first and most important step is to think about the vendor. Ultimately, if you think about the vendor and ask "how can I make them happy" (a.k.a "how can I make them more revenue"), you will be able to resolve the partner paradox.

To make the vendor happy, there are two main paths, depending on the phase their ecosystem is in. For a genuinely talent-constrained ecosystem, the highest ROI thing a vendor can do is to get more talent. For any other ecosystem, the highest ROI thing a vendor can do is to partner with firms who understand this as the underlying motivation.

Once you know where your ecosystem sits, you have two real options. The first is to find an ecosystem where partner competition is newer and/or less intense (like a newer platform with fewer partners, or a HubSpot-like market that's more friendly to smaller agencies) and execute the delivery path extremely well. The second is to become the kind of partner vendors value most. This is one that actively sells and brings net new deals to the vendor, rather than waiting for the vendor to feed them work.

How you act on either of those depends on what kind of firm you are. The next two sections walk through each of the paths, delivery and specialization, and which fits where.

The delivery path

Delivery is the right strategy when execution itself is the differentiator. As discussed, the obvious case is a Phase 1 ecosystem, where there's more work than capable hands to do it so any firm that ships relatively clean projects gets thrown more work. Of course, a plain delivery model also works in mature ecosystems, especially in more technically demanding ecosystems, but delivery itself is not what is going to make the vendor love you.

The bargain for a pure delivery execution is straightforward. You don't carry the cost of a sales function, your utilization stays high, and a large majority of your pipeline comes from being the firm people want on a difficult project. The margins are slightly thinner than if you sourced the deals yourself, but the revenue is more predictable.

In this model, you really should price for execution, and charge fairly for clean delivery and the risk you take off the table. Trying to price like a sourcing partner will really hurt you down the line and affect your relationships early.

There are, as there are with any strategic bets, some key risks to the delivery approach. The first main one is the vendor's economics. Some platforms are built around partner upside. Microsoft has documented partners earning more than $6 in services for every $1 of software revenue, and the company runs around 95% of its commercial revenue through partner motions. Other vendors flip between partner-first and direct-sales whenever quarterly numbers tighten (Dell is a good example of a company who really screwed over its partners). A good rule of thumb is that a good vendor's behavior doesn't fluctuate with their stock price. The second main risk is over-concentration. When your pipeline comes from someone else, you're vulnerable to their changes like vendor program restructures, big-SI subcontractors who pull work in-house, or referral sources who retire. Ultimately, you don't want to let any single source too much of your revenue, and keep relationships warm with everyone who could send you a project.

The specialization path

The second path is to become the partner who brings deals to the vendor instead of waiting for the vendor to feed you. This, of course, matters in any ecosystem, but it's urgent in Phase 2 or 3, where the delivery-only strategy slowly stops working.

Traditional sales is the obvious response and the one most SIs reach for first, but as I argued earlier, it almost never works for service firms. So if not for sales, how does a firm generate its own demand?

The pattern I've noticed among exceptional firms who don't have issues here is specialization. They pick an extremely narrow domain, become known for that domain, and then make sure their buyers who need them can find them.

The mechanism is simple. When a buyer doesn't know which of forty implementation partners to call, they call the vendor and take whoever the vendor recommends, which means you compete on rate. On the contrary, whenever a buyer knows their problems and can find exactly which firm specializes in their problem, they will call that firm directly. There are studies with decades of research on professional services firms which found that high growth firms do specialization, and high growth firms grow exceptionally faster compared to their peers (more than 4x faster) and are much more profitable (an average of 51% more).

Specialization seems extremely plausible and not to difficult at first glance. However, the truly hard part of it is that specialization requires saying no. No to projects outside your focus. No to the temptation to stay broad because broad feels safer. Most firms are uncomfortable doing that, which is why they stay generalist. One of my favorite questions I like to ask people is "if you had to sit down, what would you write about?" That is to say, if someone asked you to publish a monthly piece on your area of expertise—not a case study, not a "we're hiring" post, but an actual point of view about how buyers should think about a problem you solve—could you produce that consistently? "Yes, we have strong opinions and clients tell us our perspective is unusual" means you genuinely have an asset to convert. "We'd write about Salesforce best practices" means you don't yet.

If you really want to commit to specialization, you have to narrow your positioning into something extremely concrete. "ServiceNow implementation partner" is a capability shared by three thousand firms. "Revenue operations for mid-market manufacturing" or "Health Cloud for community health centers", however, is much better positioning.

Once you make this commitment, if you haven't already you have to develop expertise in the vertical you are focused on. This, really, can only be accomplished through time and multiple projects. Over time, however, you will begin to understand your customers much much better than if you had remained a generalist. This allows you to do something very powerful, which is thought leadership.

Thought leadership involves publishing your insights on the problem on a regular basis. This does not mean hiring a content agency or a social media consultant, but rather can be much simpler. Usually, it is just one senior person at the firm writing or speaking on the topic monthly. The content has to be genuinely useful and real lessons from delivery work, not vendor announcements rephrased. The bar is whether a buyer reads it and thinks "these people understand my world." If they don't, you're producing thought leadership theater, which is worse than producing nothing.

Definitely, this strategy does require a good investment, and a lot of time. It will probably take six to twelve months before content meaningfully affects pipeline, and years before inbound demand is self-sustaining. However, every work you put towards this slowly compounds over time. Each piece of content, each successful project, each conference talk builds on the last, and the firms that get to the other side find they're no longer competing on price for the same work as everyone else.

Over time, this approach scales and—funnily enough—can transition into a larger sales or marketing org at your firm. But trying to stand the sales or marketing org from the beginning never works. It must always start narrow and disciplined, with a single expert publishing their genuine insights.

The takeaway

Most mid-size SIs will not solve the partner paradox by building a traditional sales organization.

But the partner paradox is solvable, for firms willing to do something harder than hiring a salesperson. That something is specialization: choosing a domain narrow enough to own, developing a genuine point of view within it, and sharing that expertise consistently enough that the people who need what you do can find you.

The most dangerous position in a mature partner ecosystem isn't being a pure delivery shop—that's a viable business if you run it well. The most dangerous position is the middle: trying to be a demand-generating partner without committing to the specialization, while investing just enough in BD to feel responsible but not enough to produce results, and interpreting the lack of vendor deal flow as someone else's failure rather than a structural mismatch.

The partner paradox is a structural reality. You can't make it go away. But you can navigate it by getting honest about what kind of firm you are, choosing a path that fits, and then actually committing to it.

For most firms, that path is narrower than they think and more rewarding than they expect.