Co-Selling Motions in Practice
The last article in this series ended with a distinction worth holding onto. Positioning creates the opportunity. Co-selling is what turns it into revenue. That is a straightforward sentence. The practice behind it is considerably less so. Co-selling is one of those terms that gets used freely in channel conversations and defined rarely. It covers everything from a vendor joining a partner's customer call to a fully coordinated joint go-to-market motion with shared pipeline, shared accountability, and aligned field teams. The gap between those two things is enormous, and most channel programmes sit much closer to the first than the second without ever acknowledging it. This article is about what separates co-selling that generates revenue from co-selling that generates activity, with each section anchored to publicly documented examples from mid-market SaaS vendors who have either built the motion well or talked openly about what they had to fix.
What co-selling actually is, and what it is not
A vendor attending a partner's deal review is not co-selling. A vendor sending a partner a pricing sheet and waiting for updates is not co-selling. A vendor joining a customer call to handle the technical questions while the partner watches is not co-selling.
These are all forms of vendor support. They are useful. They are not the same thing.
Co-selling, in its functional form, is a structured collaboration between two field teams - a vendor and a partner - pursuing defined customer outcomes with coordinated roles, shared visibility, and mutual accountability for results. Both sides bring something the other does not have. The coordination is deliberate, not incidental.
That definition has a few implications worth sitting with. The first is that co-selling requires a relationship between individuals, not just an agreement between organisations. A signed partnership agreement does not produce co-selling. Two people who trust each other, understand each other's strengths, and communicate honestly do. The second is that it requires clear role definition. If both the vendor and the partner are trying to own the same conversation, the customer experiences confusion, not collaboration. The clearer the division of labour, the more effective the motion. The third is that it requires mutual benefit. If the vendor consistently extracts value from the partner's relationship without building anything in return, the motion degrades. Partners have learned to be selective about where they invest their access and credibility.
Why most co-selling stalls
In my experience, co-selling breaks down in one of three places.
The first is at the point of account mapping. Partners and vendors often enter joint conversations with no shared view of where the opportunity actually lies. The vendor has a territory plan. The partner has a client base. Neither party has invested time in genuinely understanding where those two things overlap, which means early co-selling conversations are speculative rather than targeted. Account mapping sessions that produce real whitespace analysis - not a hurried exchange of names before a quarterly business review - change this. Gorgias, the e-commerce support platform, reported a 30 percent uplift in partner-influenced revenue inside eight months after running its tech partner programme through structured account mapping, with partnerships eventually accounting for nearly half of company revenue. Intercom built a Partner Prioritization Framework that teaches sales reps to inspect a prospect's tech stack and pattern-match it against the partner ecosystem - the published outcome was 30 percent more partner-sourced revenue and 157 percent growth in partner-influenced revenue. Neither outcome came from a list of partner names. Both came from infrastructure that made overlap visible at the deal level.
The second failure point is at the first deal. The first time a vendor and a partner go into a deal together is almost always the most fragile. Roles have not been tested under real pressure. Communication norms have not been established. The partner does not yet know whether the vendor will protect their relationship with the customer or navigate around it. Vendors who handle that first deal well - who follow through on commitments, who give the partner clear credit in the customer's eyes - create the foundation for everything that follows. Those who do not rarely get a second chance at a meaningful co-sell motion. Tines, the security automation vendor, drove more than fifty percent of year-on-year revenue through the channel with the partner network growing twenty-five percent in fiscal year 2026. None of that scale is achievable if the first deals with each of those partners did not go well. Behaviour at the first joint deal is what creates the conditions for the second, and the second is what creates a programme.
The third is at the commission and credit layer. Co-selling conversations become politically complicated quickly when both sides have internal stakeholders with competing interests. A vendor's account executive who sees a partner-introduced deal as a threat to their number will find ways to minimise the partner's role, consciously or not. A partner who feels the economics do not reflect their contribution will gradually redirect their introductions elsewhere. What separates the vendors who solve this from those who do not is rarely the headline partner margin. It is the discipline of what the vendor's own field team is paid to do. Compensation neutrality - the principle that an account executive earns the same commission whether a deal closes direct or via a partner - removes the most common reason AEs quietly displace partners in late-stage deals.
The motions that actually work
Co-selling is not a single motion. The right approach depends on the partner's maturity, the customer's buying stage, and the nature of the deal. Three patterns appear consistently across the situations where I have seen it work.
Joint discovery: vendor and partner co-design the discovery process for a target account. The partner leads the relationship. The vendor leads the business problem framing relevant to their domain. Neither party conducts separate discovery conversations that the other does not know about. The customer experiences a single coherent conversation, not two vendors fishing in the same pool. This model works particularly well early in the buying cycle, when the goal is to shape requirements rather than respond to them. The Intercom playbook is a useful reference - their reps are trained to map a prospect's existing tech stack early in discovery and identify, in real time, which partners already sit inside that environment. The discovery conversation is then designed jointly with the relevant partner before either party meets the customer.
Coordinated technical proof: the partner owns the commercial relationship and the customer's strategic context. The vendor owns the solution validation layer: demonstrations, reference calls, technical workshops. The handoff between those two roles is explicit and agreed before any customer meeting happens. Snyk's GSI and Consultancy Partner Programme formalises this model clearly - Snyk runs collaborative GTM planning sessions with each strategic services partner, defining the boundary between Snyk-led technical proof and partner-led customer context before any joint deal kicks off. Neither party freelances.
Field alignment at the account level: this is the most intensive model and requires the most trust. Vendor and partner field representatives work specific named accounts together, with shared pipeline visibility, coordinated contact strategies, and a standing cadence for deal review. This does not scale across an entire partner base. It applies to a small number of high-potential partners where the investment is justified by the strategic value of the relationship. Workato reported partner-sourced ARR growing sixty-one percent year on year, driven by twenty-four additional transacting partners rather than a broad expansion of the partner base. The growth came from going deeper with a small set of partners on named accounts, not from signing more partners and hoping. Field alignment is a depth motion, not a width motion.
The role of the vendor in a co-sell motion
Co-selling is sometimes treated as something a vendor enables a partner to do. That framing gets it backwards.
Co-selling is something a vendor does with a partner. The vendor's field team is as much a participant in making the motion work as the partner's. That means vendor account executives need to understand how to work with partners, not just how to leverage them.
In practice, this requires a few things that are easy to describe and genuinely difficult to build. It requires AEs who see partner-sourced deals as genuinely valuable rather than as a threat to their pipeline ownership. It requires leadership that reinforces that posture in practice, not just in principle. And it requires internal process that makes partner involvement visible and protected, particularly in complex sales environments where a deal can move through multiple stages with multiple internal stakeholders.
Crossbeam's own ecosystem team reports deals running 350 percent larger when partner data is applied to the opportunity. The headline number is the deal-size lift. The underlying mechanism is that the vendor's own field team began treating partner ecosystem data as material to the deal, rather than a separate motion bolted on after the fact. The behavioural shift is what moves the number. Everything else is plumbing.
Co-selling is where the friction between channel and direct either manifests or gets managed. Organisations that have done the alignment work upstream find co-selling significantly easier. Those that have not will discover the gap every time a joint deal reaches a critical stage.
What good looks like at the deal level
When a co-selling motion is working, the customer rarely notices the machinery behind it.
They see a partner who understands their situation deeply and brings in expertise precisely when it adds value. They see a vendor who respects the partner's role rather than trying to displace it. They experience a buying process that feels coherent and considered rather than disjointed.
Behind that customer experience is something that takes deliberate effort to build: clarity between vendor and partner on who owns what, a shared understanding of the customer's priorities, and a level of trust between individuals that only develops through repeated interaction.
The signal that tells you a co-selling motion has matured is when the partner brings your solution into a conversation you did not know was happening. Not because they were instructed to, not because there was an incentive attached, but because positioning your solution was genuinely the right answer for their customer. Advisory and commercial interests aligned.
That does not happen because a partner programme exists. It happens because the field relationship is strong enough that the partner trusts the outcome on behalf of their customer.
Co-selling scales when it is designed, not assumed
Partners do not naturally co-sell with vendors any more than any two organisations naturally coordinate well. The motion has to be built: clear roles, shared pipeline visibility, trust established at the individual level, and a credit model that makes the economics honest.
What unites the vendors getting traction is that none of them treated co-selling as a function of partner enthusiasm. They built the infrastructure that makes co-selling the path of least resistance for their own field team.
When that work is done properly, co-selling stops being a channel strategy and starts being a competitive advantage. Partners become a distributed field team with existing customer relationships. The vendor's reach extends in ways that direct sales cannot replicate. Deals that neither party could have closed independently start closing together.
That is where the leverage in channel sales actually lives.
Next, I will look at how to make that success repeatable - specifically how to build a partner sales playbook that transfers what works in one deal into something the whole partner base can apply.
Key Takeaways
- •Co-selling is a structured collaboration with coordinated roles, shared visibility, and mutual accountability - a vendor joining a partner's call to handle technical questions is vendor support, not co-selling
- •Most co-selling stalls at three points: account mapping without genuine whitespace analysis, a poorly handled first joint deal, and a credit model that gives AEs an incentive to displace partners in late-stage deals
- •Three motions work consistently: joint discovery (shape requirements early), coordinated technical proof (explicit role handoff before any customer meeting), and field alignment at named accounts (depth over width)
- •Compensation neutrality - AEs earning the same whether a deal closes direct or via partner - removes the most common structural reason co-selling breaks down
- •The signal that a co-selling motion has matured is when a partner brings your solution into a conversation you did not know was happening, because it was genuinely the right answer for their customer
Real-World Insight
The vendors I have referenced in this article are at very different points on the co-selling journey. What unites the ones getting traction - Gorgias, Intercom, Tines, Snyk, Workato - is that none of them treated co-selling as a function of partner enthusiasm or programme design alone. They built internal infrastructure that made co-selling the path of least resistance for their own field team. The behavioural shift inside the vendor's sales organisation is what moves the number. The partner programme is the context. The field relationship is the mechanism.
Summary
This article examines co-selling in SaaS channel programmes, distinguishing functional co-selling (structured collaboration with coordinated roles and mutual accountability) from vendor support activities. It identifies three common failure points: account mapping without genuine whitespace analysis, mishandled first joint deals, and misaligned credit and commission models. It then presents three co-selling motions that work consistently - joint discovery, coordinated technical proof, and field alignment at named accounts - illustrated with publicly documented examples from Gorgias, Intercom, Tines, Snyk, Workato, and Crossbeam. The article argues that co-selling requires the vendor's own field team to change behaviour, not just the partner's, and that compensation neutrality is the structural foundation most programmes miss. It closes with the signal of a mature co-selling motion: a partner bringing your solution into a conversation you did not initiate.
Found this useful? Connect with me for more on SaaS partnerships.
Follow me on LinkedIn