Account-based marketing for Microsoft Partners: making ABM actually work with a co-sell motion

Standard ABM playbooks were built for software companies selling their own product to a list they drew up on their own. You're a Microsoft Partner - here's how to run ABM with the co-sell motion baked in from day one.

Most of the account-based marketing advice you'll read was written for a software company selling its own product to a list it drew up on its own. Pick the accounts, build the plays, fire the campaigns, measure the pipeline.

You're not that company. You're a Microsoft Partner. Your best accounts aren't just the ones you fancy - they're the ones where Microsoft's own sellers are already leaning in, where the co-sell overlap is real, and where an MCAPS priority gives you air cover you didn't have to manufacture.

So the standard B2B account-based marketing playbook doesn't quite fit. It's close enough to look right and wrong enough to waste a year. Let's sort it properly.

The short answer: why standard ABM playbooks miss for Microsoft Partners

Standard ABM assumes you own the whole buying relationship. You pick the target list, you run the plays, and the only people in the room are you and the buyer.

For a Microsoft Partner, there's a third party in every serious deal - and it's Microsoft. Co-selling is any collaborative engagement between Microsoft and its partners, from building demand to sharing leads to closing a deal together. That changes three things at once.

Your account list isn't yours alone

The accounts worth the effort are the ones where you and a Microsoft seller both have a reason to show up. Pick a list with no co-sell overlap and you've built a lovely campaign that Microsoft has no reason to help you win.

Your best signal often lives in Microsoft's systems, not yours

Whether a solution is co-sell ready, whether an account sits in a priority solution area, whether a seller has already flagged interest - that intent is gold, and most partners ignore it because it doesn't come out of their own CRM.

Your content has to speak to more than the buyer

It has to arm a Microsoft seller to say yes to you, too. More on that below, because it's the bit almost everyone gets wrong.

None of that means throwing out ABM. It means running it with the co-sell motion baked in from the start, not bolted on at the end.

Building the target account list: co-sell overlap plus MCAPS priorities

The target account list is where ABM lives or dies, and it's where the Microsoft-Partner version diverges hardest from the textbook.

A normal list is built from fit and intent. Yours needs a third lens: co-sell overlap. Where do your capabilities, a live customer need, and a Microsoft seller's incentive all point at the same account? That's your gravity. Those accounts pull.

Layer in MCAPS priorities next. MCAPS - Microsoft Customer and Partner Solutions - is essentially how Microsoft decides who gets sold to, how resources get allocated, and which partners get invited to the table. When your target account sits inside a solution area Microsoft is actively pushing that year, you're not asking a seller for a favour. You're helping them hit a number they're already chasing.

So a strong list for a Microsoft Partner is built from three overlapping circles:

Fit

- the accounts you can genuinely serve and win.

Co-sell overlap

- where a Microsoft seller has a reason to co-sell with you, not just tolerate you.

MCAPS priority

- where the account and the workload map to what Microsoft is investing behind right now.

The accounts sitting in the middle of all three are your 1:1 tier. The ones in two circles are your 1:few. The rest are 1:many or not this year. We'll come back to the tiers.

One warning. Don't build the list in a vacuum and then go looking for a friendly seller to bless it. Build it with the co-sell lens on from day one, because a list that ignores where Microsoft is already pointed is just a wish list with a spreadsheet's confidence.

What actually predicts a co-sell-ready account

Here's the useful question. Of all the accounts you could chase, which ones are genuinely ready for a co-sell push - and which just look good on paper?

The signals that actually predict readiness aren't the vanity ones. Firmographic fit and a big logo tell you an account is desirable. They don't tell you it's ready. These do:

A named Microsoft seller already engaged in the account

If there's a seller with the account in their patch and a reason to care, you've got a co-sell partner. If there isn't, you're doing outbound with extra steps.

A live workload that maps to a priority solution play

Co-sell deals now require a Solution Area and Solution Play to be specified - Microsoft made that mandatory for IP co-sell in 2025. If you can name the play the account is a candidate for, you're speaking Microsoft's language. If you can't, the deal's harder to register and easier to ignore.

Consumption or renewal pressure

An account with an Azure commitment to grow, or a renewal moment approaching, gives the seller a clock. Clocks create urgency, and urgency is what turns a polite co-sell into an active one.

A prior touch that went somewhere

An event attendee, an assessment already delivered, a warm intro from another partner. Existing motion beats cold every time.

Notice what's not on that list: how much you'd like to win the logo. Desire is not a signal. Busy is not the same as well directed, and neither is ambitious. Build your tiering on what predicts a co-sell yes, not on what would look best in the board deck.

The three-audience problem: buyer, IT lead, and Microsoft seller

This is the part standard ABM can't help you with, because standard ABM only knows about two audiences and you've got three.

The buyer

The person with the business problem and the budget. They care about the outcome - the cost saved, the risk removed, the thing that finally works. Talk outcomes, not features.

The buyer's IT lead

The person who has to live with what you sell. They care about whether it's secure, whether it fits the Microsoft estate they already run, whether it'll break at 2am. Reassure them on the technical fit, in their language, or the deal stalls in a place the buyer can't see.

The Microsoft seller

The one everyone forgets. They care about one thing above all - does helping you help them hit their targets? Consumption, priority workloads, customer success that reflects well on Microsoft. If your enablement content answers "why should a Microsoft seller care?" in a single clear line, you've done something 90% of partners haven't.

So your content can't be one asset pointed at "the account". It's a small kit, deliberately built for three readers:

A buyer-facing piece about the outcome.

A technical piece the IT lead can trust.

A seller-facing one-pager - crisp value prop, the solution play it maps to, the proof point - that makes it effortless for a Microsoft seller to put you in front of their customer.

Get the seller asset right and you've turned Microsoft's sales teams into a distribution channel. Skip it, and you're carrying the whole deal on your own back.

A tier structure that actually fits a mid-market partner (1:1, 1:few, 1:many)

Big-brand ABM guides love a 1:1 programme with a dedicated pod per account. Lovely if you're an enterprise vendor. Not the reality for a mid-market partner with a lean team and a co-sell motion to feed.

Here's a tier structure that holds up in the real world.

1:1 - strategic (roughly 5 to 10 accounts)

The ones sitting in all three circles: fit, co-sell overlap, MCAPS priority. Each gets a genuinely bespoke plan, a named Microsoft seller relationship, and content built for that specific account's three readers. This is where your best marketing and sales time goes. Guard it.

1:few - clustered (roughly 20 to 40 accounts, in clusters of 5 to 10)

Grouped by a shared trigger - same industry, same solution play, same renewal moment. You personalise the cluster, not the account. One strong narrative and a light layer of tailoring per account. This is the tier that scales without pretending you've got enterprise resources.

1:many - programmatic (a broader list matched to MCAPS priorities)

Light-touch, always-on, mapped to Microsoft's priority workloads. Its job is to warm accounts up so they earn promotion into 1:few, and to keep you visible while co-sell relationships mature. Not glamorous. Quietly essential.

The trick isn't picking one tier. It's the flow between them - accounts earning their way up as co-sell signals strengthen, and dropping back down when they cool. A tier list you set in January and never touch again is a filing system, not a strategy.

Tooling that earns its keep - and tooling that just flatters the CMO

You do not need a six-figure ABM platform to run account-based marketing as a Microsoft Partner. Say it louder for the CMOs at the back.

The category is dominated by big platforms - the 6senses and Demandbases of the world - and they're genuinely good at what they do. But they're built for high-volume, own-product B2B ABM, and a lot of what you're paying for is intent data you can partly get for free from Microsoft's own systems and your co-sell relationships.

Tooling that earns its keep

Partner Center and your co-sell data. This is your best intent source and it's already yours. Registered deals, seller engagement, solution play alignment. Most partners under-use it wildly.

Your CRM, used properly. Account tiering, the three-reader content mapped to each account, next actions logged. Unsexy. Load-bearing.

A basic engagement layer - LinkedIn for reaching named contacts, email, and whatever you already run for events. Enough to reach a focused list of accounts without a platform tax.

Tooling that just flatters the CMO

A platform bought to look serious about ABM, with 80% of the licences dark inside three months.

Intent data you never act on because nobody owns the follow-up.

A dashboard that's beautiful and tells you nothing you'd change a decision over.

Buy tools to remove a bottleneck you can actually name. If you can't name the bottleneck, the tool isn't the answer - the operating rhythm is. This is often where a good account-based marketing agency earns its fee: not by selling you software, but by getting the co-sell motion, the list, and the content working before anyone spends on a platform.

Measuring ABM without pretending pipeline fell from the sky

The fastest way to lose the board's trust in ABM is to claim a pile of pipeline appeared purely because of your clever campaign. In a co-sell world, that's plainly not true - a Microsoft seller touched it, the customer had a live need, and your marketing was one of several hands on the deal. Own that, and your numbers get more credible, not less.

Measure in two layers.

Leading indicators - is the motion healthy?

These move first and you control them:

Number of target accounts with an engaged Microsoft seller.

Co-sell deals registered against your priority list.

Meetings and assessments booked into tier-1 and tier-2 accounts.

Coverage - what share of your list actually maps to a live MCAPS priority.

Lagging indicators - is it working?

Influenced pipeline and closed revenue in your target accounts, reported honestly as influenced, not created out of thin air. Show the account was on the list, show marketing engaged it, show co-sell moved it. That's a story a CFO believes.

And give it time. ABM plus co-sell is a relationship game, and relationships don't close in a quarter. If you judge it at week eight you'll kill something that was about to work.

FAQ: account-based marketing for Microsoft Partners

What is account-based marketing?

Account-based marketing is a B2B approach where you treat a defined list of high-value accounts as markets of one, rather than casting a wide net and hoping. Instead of chasing volume, you concentrate marketing and sales on the specific accounts most likely to become significant customers, and you personalise the effort to each. Done well, it means less wasted spend and tighter alignment between marketing and sales.

How is ABM different for a Microsoft Partner?

Three ways. Your target account list should be shaped by co-sell overlap and MCAPS priorities, not just your own view of fit. Your strongest intent signals often come from Microsoft's systems - Partner Center, co-sell engagement, solution play alignment - rather than only your CRM. And your content has to enable a Microsoft seller, not just persuade a buyer. Standard ABM ignores that third audience entirely.

Do you need an ABM platform to run ABM as a Microsoft Partner?

No. A focused programme runs on Partner Center and your co-sell data, a CRM used properly, and a light engagement layer. Buy a platform only when you can name the specific bottleneck it removes - and you've usually got your co-sell motion and account list working long before you hit that point.

How many accounts should a Microsoft Partner target?

Fewer than you think. For a mid-market partner, roughly 5 to 10 accounts at the 1:1 tier, 20 to 40 in clustered 1:few, and a broader 1:many list mapped to MCAPS priorities behind that. The exact numbers matter less than the discipline of tiering by co-sell readiness and moving accounts between tiers as signals change.

Can Microsoft Co-op or MDF funds pay for ABM activity?

Often, yes - eligible partner marketing funds like Co-op and MDF can typically cover qualifying demand-gen and ABM-style activity, but it depends on your designation, the fund type, and the specific activity, and it usually needs pre-approval and a proper claim. Treat it as a real budget lever with rules, not free money. We cover the detail in our [Co-op and MDF brief](/marketing-insights/making-the-most-of-your-microsoft-partner-coop).

How long before ABM shows real pipeline for a Microsoft Partner?

Expect leading indicators - engaged sellers, registered co-sell deals, booked meetings - within the first quarter, and meaningful influenced pipeline over two to three. It's a relationship game layered on Microsoft's sales cycle, so judging it at week eight is the classic way to kill something that was about to land.

Should marketing or sales own the target account list?

Neither, alone. The list should be built and owned jointly, because it depends on inputs only sales and co-sell relationships can supply and effort only marketing can sustain. If one function owns it in isolation, you get either a wish list with no delivery or a delivery engine pointed at the wrong accounts.