What is a partner battle card?

Short answer: A partner battle card is the one-to-two page AE-facing enablement asset that names the joint value, the named buying personas, the co-sell motion, and the head-to-head competitive position when a host product and a partner product are sold together. It exists because AEs cannot remember the joint story across ten partners, and the partner side cannot remember the host story across fifty co-sell motions. The card is the operating artifact that compresses the joint pitch into something the AE can read on the way to the meeting.

The shortcut is to treat the partner battle card as a sales tool, not a marketing asset. The card has to answer the AE’s three questions before the meeting (who is the buyer, what is the joint pitch, what is the next move) in under three minutes.

Why partner battle cards matter in 2026

Three forces have made the partner battle card central to co-sell execution. First, co-sell motions have stratified across more partners than AEs can carry in their heads; a typical mid-market AE works between three and seven active partner motions and cannot keep them straight without a written reference. Second, the buying committees on co-sell deals have grown, and the AE needs the joint persona map at the meeting, not in a deck back at the office. Third, the partner-side seller is asking for the same card from the host side, and the absence of a working card is a leading indicator of a partner-led motion that will not scale.

A working partner battle card is read in three minutes, lives in the CRM or the PRM, and gets updated quarterly. The teams that produce cards that no AE reads have built marketing assets; the teams that produce cards AEs actually use have built a sales tool.

The shortcut is to write the card with the AE in the room, not for the AE. Co-author the first version with the host AE who has actually run the joint pitch, and iterate against three more AEs before the card ships.

How a partner battle card actually works

A working partner battle card runs on six components. Each component is short, named, and built for AE retention.

1. The joint pitch in two sentences: Not the product pitch, not the partner pitch. The specific outcome the customer gets when the two products are deployed together, in the language the buyer uses.
2. The named buying personas: One to three buyer titles (CRO, head of revenue ops, head of finance) with the named pain each persona owns and the joint move that addresses it. Personas are not generic; they are the specific roles the AE will meet.
3. The co-sell motion: A two-step play. Step one names the partner-side counterpart the AE calls before the customer meeting. Step two names the joint move (joint discovery, technical pre-brief, exec intro, joint pitch deck). The card lists the partner-side rep, the slack channel, and the response SLA.
4. The objection bank: The three objections that come up on co-sell deals (pricing, integration, support model) with a one-sentence response and the named asset to send. Objection bank lives at the bottom of the card so the AE can scroll to it during a call.
5. The competitive position: Where the joint pitch lands against the named competitive alternative the buyer is also evaluating. The position has to be defensible and short; a long competitive section is a leading indicator that the card will not get read.
6. The next move: The action the AE takes after the customer meeting. Usually a joint follow-up, a partner-side technical brief, or a registration in the PRM (Introw, Euler, Impartner, PartnerStack, or Channelscaler).

A card with all six runs at one to two pages, fits on one screen, and reads in under three minutes.

Common pitfalls in building a partner battle card

• Writing the card in marketing voice instead of AE voice: A card written by product marketing reads like a brochure; a card written with an AE in the room reads like a sales tool. AEs ignore brochures.
• Three pages of joint value and one paragraph of co-sell motion: The joint value is the headline, but the co-sell motion is the operating instruction. Most cards over-invest in the headline and under-invest in the named move; the card has to flip the ratio.
• Skipping the named partner-side counterpart: A card that says “engage your partner contact” without naming the rep, the slack channel, and the response SLA produces nothing. The named counterpart is what turns the card into a motion.
• No quarterly refresh: Partner products change, joint pricing changes, partner roster changes. A stale card is worse than no card; the AE reads it, runs the old motion, and the partner side is annoyed. Update quarterly.
• One card per partner with no host-product spine: AEs cannot hold ten different partner narratives in their head. The card has to slot into the AE’s existing product narrative; the partner-specific moves are the variant, not the spine.

What this looks like in practice

A growth-stage B2B SaaS team had thirteen Tier 1 partners and seven Tier 2 partners; AEs were carrying the joint pitches in their heads and the win rate on co-sell deals was inconsistent. The head of partnerships ran a card-building workshop with three AEs in the room, an established Tier 1 SI as the first partner, and the joint customer outcome as the anchor. The first card came in at one and a half pages: two-sentence joint pitch, three buying personas with named pain, a two-step co-sell motion with the SI’s regional MD named, three objections with one-sentence responses, a one-paragraph competitive position against the named alternative, and a next-move section that pointed at the Introw deal registration. The card lived on the partner record in Introw and opened from the opportunity in Salesforce when the partner tag was applied. Within six weeks, AEs were reading the card before partner meetings, the partner-side response SLA had tightened from three days to one, and the win rate on co-sell deals with the SI had moved from forty-six percent to sixty-one percent. Twelve more cards were built over the next quarter on the same template.

Forecastable’s POV on partner battle cards

The partner battle card is the operating artifact that connects the joint pitch to the AE workflow. The teams that produce cards AEs actually use treat the card as a sales tool, build it with an AE in the room, and update it quarterly. The teams that produce cards that sit in a SharePoint folder have built a marketing asset and called it a battle card.

The deeper read is that the card is the most teachable partner enablement artifact a partnerships team can ship in its first year. The unit of work is small (one to two pages per partner), the iteration loop is short (build, test on three AEs, refine, ship), and the impact is measurable in win rate on the partner-tagged opportunities. A team that ships ten working cards in a quarter has installed an AE-side co-sell motion the rest of the program can build on.

The candor on the partner-side card question is that the host has to build the host-side card and the partner has to build the partner-side card, and the two have to align on the joint pitch and the co-sell motion. A one-sided card produces a one-sided motion; the joint planning has to include the partner-side counterpart.

The candor on tooling is that the card lives where the AE works. If AEs live in the CRM, the card lives in the CRM. If AEs live in the PRM, the card lives in the PRM. Putting the card in a wiki or a slide deck that AEs do not open is a leading indicator that the card will not get read.

Forecastable is a partnerships operating platform; the tools above (Crossbeam, Pocus, Common Room, Tackle, Labra, Suger, Clazar, Introw, Euler, Impartner, PartnerStack, Channelscaler) are independent third-party platforms, and naming them is not an endorsement of any specific deployment over another. Evaluate each on your own motion.

Frequently asked questions

What is the right length for a partner battle card?
One to two pages, readable in under three minutes. Longer cards do not get read; shorter cards leave the co-sell motion ambiguous.

Who owns the partner battle card?
The partner manager owns the card; the partner-side counterpart contributes the partner narrative; an AE who has run the joint pitch is the third author. Marketing supports the asset hygiene but does not own the content.

How often should a partner battle card be updated?
Quarterly. Stale cards run stale motions; a partner roster or pricing change without a card update is a leading indicator of a missed quarter on the partner motion.

Where does the partner battle card live?
In the PRM (Introw, Euler, Impartner, PartnerStack, or Channelscaler) on the partner record, with a link from the CRM opportunity when the partner tag is applied. The card opens from the place the AE works.

Should we build one card per partner or one card per joint motion?
One card per partner is the default; if the partner runs multiple distinct joint motions (different products, different segments, different geos), one card per motion. The test is whether the AE would need different content at the meeting.

Should we include pricing on the partner battle card?
Indicative pricing for the joint pitch, not list pricing. The card has to give the AE enough to qualify the deal at the meeting; full pricing lives in the deal record.

How does a partner battle card relate to a joint value proposition?
The joint value proposition is the message; the partner battle card is the operating artifact that carries the message into the AE workflow. The two are different; the card is downstream of the JVP and operationalizes it.

Next step

If a partner battle card is open this quarter, the move this week is to run a card-building workshop with three AEs and the named partner counterpart, anchor the card on a real joint customer outcome, and ship the first version on one partner before scaling.

Start your growth journey now to install a working partner battle card motion in your specific environment, or read the orientation on the partner program for the broader operating model.