PerspectiveCategory Definition

The Co-Sell Stack, Explained

Every product in the co-sell market operates at one of four layers, and each is defined by one question: what does this software assume already exists when you start using it? Three layers are well served. The fourth — where opportunities come from — is almost entirely unoccupied.

Ravi Paladugu10 min readAugust 7, 2026Partner Leaders, Alliances Directors, GTM Heads, Founders

TL;DR

The co-sell software market has four layers, each defined by what it assumes already exists. Partner data and account mapping assumes two CRMs full of accounts. Co-sell workflow assumes an opportunity exists. Marketplace transaction assumes a buyer has decided. Opportunity creation assumes nothing — and it is the layer almost no software occupies.

Definition — The co-sell stack

A four-layer model of the co-sell software market, ordered by dependency rather than quality: partner data and account mapping, co-sell management and workflow, marketplace transaction and billing, and opportunity creation. Each layer is identified by what must already be true before its software is useful.

Somewhere between 2019 and now, co-sell acquired a software category. There are platforms for it, comparison listicles ranking them, and analyst matrices positioning them against each other. A partner evaluating the space encounters a dozen products that all describe themselves in roughly the same words — cloud GTM, ecosystem revenue, co-sell automation — and struggles to work out what actually distinguishes them.

The distinction is real and it is simple, but almost nobody states it, because stating it means admitting what your product does not do. Every product in this market operates at one of four layers, and each layer is defined by a single question: what does this software assume already exists when you start using it?

Layer 1 — Partner data and account mapping

Assumes: two companies each already have a CRM full of accounts.

These platforms compare your account list against a partner’s account list and tell you where they overlap — shared customers, shared prospects, accounts where your partner is in and you are not. The good ones do this without either side handing over its raw customer list, which is a genuinely hard privacy problem well solved.

What they produce is an intersection. That intersection is often valuable: a warm path into an account where a partner already has credibility is worth more than a cold one. But the intersection can only contain accounts that were already in somebody’s CRM. If neither party knows the company exists, no amount of mapping surfaces it.

Layer 2 — Co-sell management and workflow

Assumes: an opportunity exists and someone needs to move it.

This layer manages the lifecycle of a co-sell deal once it is a deal. Registering it with the provider, syncing stage changes, keeping the partner and the provider looking at the same record, routing it to the right motion, tracking what is owed to whom, reporting on the portfolio at the end of the quarter.

The problem it solves is real and unglamorous: co-sell generates an enormous amount of administrative friction, most of it re-keying the same opportunity into a second system. Removing that friction is worth paying for.

But note the shape of the value. Every hour saved is an hour that would have been spent on an opportunity that already existed. Workflow software makes an existing pipeline cheaper to run. It does not make the pipeline larger.

Layer 3 — Marketplace transaction and billing

Assumes: a buyer has decided to buy.

The most technically demanding layer, and the one with the clearest return. Listing software on a cloud marketplace, constructing private offers, metering usage, handling entitlement and billing, reconciling the provider’s cut. Every one of those is fiddly, every one is easy to get wrong, and getting one wrong costs real money.

Marketplace transaction is also where the strongest commercial argument in this whole market lives: a customer with a negotiated cloud spend commitment can often draw down against it by buying through the marketplace, which changes the procurement conversation entirely.

And still — it begins at a buyer who has decided. The private offer is the last mile. Something has to have happened before it.

Layer 4 — Opportunity creation

Assumes: nothing.

This is the layer that finds the account before it is in anyone’s CRM, opens the conversation, develops it into something real, and produces an opportunity that did not previously exist.

It is also, almost entirely, unoccupied by software. Not because it is unimportant — every one of the three layers above it is idle without its output — but because it is the hardest to build and the least legible to buy. Layers 1 through 3 all have a clean input: an account list, an opportunity record, a purchase decision. Layer 4 has no input. It has to manufacture one.

What partners do instead is fill this layer with people and hope. Relationship-building with a partner manager, in the hope of receiving provider-originated referrals. Conference presence, in the hope of conversations. Inbound, in the hope of arrival. A generic outbound motion, in the hope of volume converting. All of these work occasionally. None of them are systems.

The stack test

Given a co-sell product, one question places it: what has to be true before this is useful?

If the answer is “you and a partner both have accounts loaded,” it is layer 1. If it is “you have opportunities to manage,” layer 2. If it is “you have a customer ready to transact,” layer 3. If the answer is “nothing,” it is layer 4 — and you should check that claim carefully, because it is rare.

The test also explains why demos in this category can feel interchangeable. Nearly every one begins with an opportunity already on screen. The differences that follow are real, but they are differences in what happens to that opportunity — not in where it came from.

Which layer is actually your constraint

Partners routinely buy the wrong layer, and the diagnostic is uncomfortable but quick. Count last quarter’s opportunities and mark each one: provider-originated, inbound, existing-customer expansion, or deliberately created by you.

If the fourth bucket has healthy numbers and the friction is administrative — deals stuck in re-keying, stage mismatches, painful quarter-end reporting — your constraint is layer 2, and workflow software will pay for itself quickly.

If you have a product and buyers keep stalling in procurement, your constraint is layer 3.

If you have partners with overlapping customer bases you are not exploiting, layer 1.

But if the fourth bucket is empty or near it — and for most partners it is — then no amount of layer 1, 2, or 3 changes the outcome. Buying workflow software to fix an empty pipeline is buying a faster conveyor for a factory with no raw material. The conveyor works exactly as advertised. Nothing comes out the other end.

Why layer 4 stayed empty this long

Two reasons, and neither is that nobody noticed.

The first is that it was genuinely not buildable as software until recently. Manufacturing an opportunity requires reading a specific ecosystem — what a company’s hiring, workload, and program behaviour imply about its intentions — and then writing to that company in a way that proves the sender lives in the same world. That was human work, and expensive human work at that.

The second is that the adjacent category solved half of it and declared victory. Outbound automation industrialised the sending. But sending is the cheap half. The expensive half is deciding what to send, to whom, and why now — and doing it well enough that the resulting opportunity survives a partner manager’s scrutiny rather than being rejected as a name pulled off a list.

Which is why generic outbound tooling did not fill layer 4 either. It occupies a strange position: correct that pipeline must be created rather than requested, and missing the intelligence that would let it create pipeline anyone in an ecosystem would take seriously.

The stack is not a ranking

Worth being explicit, because layered diagrams invite the reading that the bottom is best. It is not a hierarchy of quality. A partner running real marketplace volume needs layer 3 and will not get it from layer 4. A partner with a mature ecosystem of co-selling partners needs layer 1. These are different jobs, and the products doing them are, in the main, good at them.

The stack is a dependency order. Layer 4 produces what layers 1 through 3 consume. A partner can operate at three layers with the fourth outsourced to luck — most do — but that is a choice with consequences, and the consequence is that the size of the business is set by someone else’s referral allocation.

The useful question is not which layer is most important. It is which one you have left to chance.

Frequently asked questions

What are the layers of the co-sell software stack?

Four. Partner data and account mapping compares two companies' account lists to find overlap — it assumes both CRMs are already populated. Co-sell management and workflow moves opportunities through registration, sync, and reporting — it assumes an opportunity exists. Marketplace transaction and billing handles listing, private offers, metering, and entitlement — it assumes a buyer has decided. Opportunity creation finds accounts before they are in anyone's CRM — it assumes nothing.

How do I tell which layer a co-sell product operates at?

Ask what has to be true before the product is useful. If the answer is 'you and a partner both have accounts loaded', it is account mapping. If it is 'you have opportunities to manage', it is workflow. If it is 'you have a customer ready to transact', it is marketplace transaction. If the answer is 'nothing', it is opportunity creation — and that claim is worth checking carefully, because it is rare.

Why do co-sell platform demos all feel the same?

Because nearly every one begins with an opportunity already on screen. The differences that follow are real, but they are differences in what happens to that opportunity, not in where it came from. Three of the four layers operate downstream of creation, so their demos necessarily start at the same place.

Which co-sell layer should I buy first?

Diagnose the constraint rather than the category. Mark last quarter's opportunities as provider-originated, inbound, existing-customer expansion, or deliberately created. If the fourth bucket is healthy and your friction is administrative, buy workflow. If buyers stall in procurement, buy marketplace transaction. If you have partners with overlapping customer bases you are not exploiting, buy account mapping. If the fourth bucket is empty, none of the three will change the outcome.

Why is opportunity creation the empty layer?

Two reasons. It was not buildable as software until recently — manufacturing an opportunity requires reading what a company's hiring, workload, and program behaviour imply about its intentions, then writing in a way that proves the sender lives in the same ecosystem. And the adjacent category solved half of it: outbound automation industrialised the sending, which is the cheap half. The expensive half is deciding what to send, to whom, and why now, well enough that the resulting opportunity survives a partner manager's scrutiny.

Is the co-sell stack a ranking of which tools are best?

No — it is a dependency order. A partner running real marketplace volume genuinely needs the transaction layer and will not get it from the creation layer. These are different jobs, and the products doing them are generally good at them. What the stack shows is that layer 4 produces what layers 1 through 3 consume.

Can workflow software fix an empty co-sell pipeline?

No. Workflow software makes an existing pipeline cheaper to run; it does not make it larger. Every hour it saves is an hour that would have been spent on an opportunity that already existed. Buying it to fix an empty pipeline is buying a faster conveyor for a factory with no raw material — the conveyor works exactly as advertised, and nothing comes out the other end.

Does account mapping generate new pipeline?

It surfaces accounts where you and a partner overlap, which is genuinely valuable — a warm path into an account beats a cold one. But the intersection can only contain accounts that were already in somebody's CRM. If neither party knows the company exists, no amount of mapping surfaces it.

Key Takeaways

Layer 1 — partner data and account mapping — assumes two companies each already have a CRM full of accounts. It produces an intersection, and an intersection can only contain accounts somebody already knew about.
Layer 2 — co-sell management and workflow — assumes an opportunity exists and needs moving. It makes an existing pipeline cheaper to run; it does not make it larger.
Layer 3 — marketplace transaction and billing — assumes a buyer has decided to buy. It is the last mile, and something has to happen before it.
Layer 4 — opportunity creation — assumes nothing. It is where opportunities that did not previously exist come from, and it is almost entirely unoccupied by software.
The stack test: given any co-sell product, ask what has to be true before it is useful. The answer places it precisely, and explains why demos in this category feel interchangeable — nearly all of them begin with an opportunity already on screen.
Diagnose your own constraint by marking last quarter's opportunities as provider-originated, inbound, existing-customer expansion, or deliberately created. If the fourth bucket is empty, no amount of layers 1–3 changes the outcome.
The stack is a dependency order, not a ranking. Layer 4 produces what the others consume; a partner who leaves it to chance has their business size set by someone else's referral allocation.

Book a Demo

Related Resources

View all

PerspectiveMeasurement

Partner-Sourced vs Partner-Influenced Pipeline

Two partners report the same eight million. One built a business that compounds; the other has a number that will not survive a change of personnel at the cloud provider. The distinction decides your strategy, and most partner orgs report the two as one figure.

9 min readAugust 7, 2026

PerspectiveEcosystem Mechanics

How to Fill Your ACE Pipeline When You Have Nothing to Register

Every tool in the co-sell market starts from an opportunity that already exists — syncing it, routing it, mapping it, transacting it. None of them help the partner whose ACE pipeline is empty. That is a sourcing problem wearing a co-sell costume, and it has a specific fix.

11 min readAugust 7, 2026