Perspectives, playbooks, and partner stories from the frontier of partner GTM intelligence — grounded in production deployments, not theory.
Showing 33 resources
Two vendors publish the migration deadline as fact, three months apart, neither citing AWS. AWS's own migration guide contains no date at all — and on the day one vendor says the legacy portal shut down, AWS shipped two new managed policies into it.
Product-level PRM measures what your product drives. Deal-level incentives are paid against deals. A Revenue Attribution ID is what connects the two — and the split it uses is a percentage you supply, feeding an approval process with nobody in it.
AWS is replacing a claim with a meter reading. PRM measures the AWS consumption your solutions drive, and from January 2027 it becomes the foundation for how AWS recognises partner impact across every eligible programme. The definitive guide — including Revenue Attribution IDs, the deal-level layer almost nobody has written about.
The 31 July 2026 PRM deadline came and went and nothing happened — no error, no email, no red dashboard. The gate is on funding, so it surfaces weeks later, against a live deal. It is wider than the coverage suggests, the prerequisite people miss has nothing to do with tagging, and AWS benefit guides are already setting PRM conditions today.
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.
A rejection is rarely a verdict on the account. It is a partner manager saying she cannot tell from the submission whether the deal is real, and does not have time to find out. Five failure modes, and the pre-submission test that catches all of them.
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.
Almost every co-sell tool assumes an ISV — something to list, transact, and meter. A large share of every cloud ecosystem is consultancies, SIs, and MSPs who co-sell constantly without any of that machinery. Their motion is different, not lesser, and their delivery record is the asset they waste.
Outbound has a deserved bad reputation in partner organisations — because most partners ran a version built for a different market. When your addressable set is a few hundred accounts rather than a hundred thousand, volume tactics do not merely underperform. They destroy the asset.
Ask a partner why an account is worth co-selling now and the answer usually describes the partner. A why-now is valid only if it survives your removal from the situation — one test that disqualifies most of what partners currently submit as timing.
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.
The playbook didn’t fail because the tactics were wrong. It failed because the tactics were right — until enough teams adopted them to make them noise. Here’s the architecture that replaced it.
Intent data tells you who’s in-market for a category. It doesn’t tell you whether they have a reason to care about your specific offer. That gap is structural — and it’s why reply rates stay flat no matter how you optimize the sequence.
A well-built ICP tells you who could buy. It doesn’t tell you who has a reason to engage right now. That’s a different question — and it’s the one that determines whether anyone responds.
Most go-to-market teams have added AI to their outreach stack. Most haven’t moved their reply rates. The problem isn’t the AI — it’s the three premises that determine what the AI gets pointed at.
Most go-to-market stacks have data, automation, a sequencer, and now an AI writing tool. The reply rates haven’t moved. The missing piece isn’t another execution tool — it’s a layer that doesn’t exist in most stacks yet.
Co-sell frustration has a structural root: most partners collapse two fundamentally different motions — AO (AWS-originated) and PO (partner-originated) — into one, and try to fix both with competency attainment. PDMs evaluate them differently. The fix is different too.
Most alliances directors run the specializations decision as a credentials question. That optimizes for the wrong outcome. Specializations are a signal layer — they filter AO routing, anchor PO credibility, and define the territory where outreach carries genuine authority.
Most ISVs manage their Marketplace listing as a distribution channel. They miss the intelligence layer the listing landscape itself contains — category density, offer structure patterns, partnership gravity, capability gaps, vertical maturity. That map is public. Most ISVs treat it as background.
Narrowing the ICP was the right call. It exposed a problem that broad ICPs had always masked: random timing doesn’t average out at 200 accounts the way it does at 5,000. The fix isn’t more filters. It’s research infrastructure.
Every Director of Alliances at an Azure partner knows Partner Center well. Most also know it isn’t where their GTM happens. This piece names that gap: Partner Center is operational infrastructure — and the intelligence layer partner-led growth requires is built from the partner’s vantage point, not the portal’s.
The GCPN restructure — replacing Partner Advantage with tier thresholds, 21 competencies, and automated Capability tracking — is Google declaring which co-sell conversations it wants to have and making that list shorter. The partners who read it as a compliance exercise and the ones who read it as a GTM signal will be in structurally different positions by end of 2026.
The GTM Intelligence Layer is a new category, and every adjacent vendor is claiming to be in it. Seven questions separate a genuine GTM Intelligence Layer from a data platform, an AI SDR tool, or a CRM add-on using the category’s language.
Most teams that deploy an AI SDR watch their outreach volume go up and their reply rates stay flat — and conclude they need a better AI SDR. The instinct misses the real problem. AI SDRs are execution infrastructure. Here are the five dimensions that actually differentiate them.
Most GTM teams track reply rate as their primary outreach KPI. It’s a useful signal — but it’s an activity metric being used as a quality metric. Pipeline quality inherits from the outreach that sourced it. Most teams never trace the inheritance.
Every outreach target holds a relevance budget with every sender — not consciously, but effectively. Generic outreach makes withdrawals. Research-grounded outreach makes deposits. Most outreach teams are further overdrawn than they know, and the deficit limits what future outreach can accomplish.
Most B2B GTM teams assume cold outreach compliance is a consumer problem. It isn’t. Nine jurisdictions now have meaningful rules governing B2B cold outreach. The teams that navigate this well don’t stop — they structure it correctly.
Running all three channels on every lead is not a multichannel strategy. It is a three-channel spray. This playbook introduces the Channel Decision Model: three factors that determine which channel to lead with, which to follow, and when to introduce calling — so each touchpoint earns the next.
You have the program. The listing. The PDM. The MDF. Six months in, the pipeline is zero. This playbook introduces the ISV Pipeline Motion — three components that turn OEM program access into research-led pipeline: an OEM-Native Offering, an Ecosystem ICP, and an Outreach Motion that runs before co-sell, not after.
Most teams approach onboarding a GTM Intelligence Layer like onboarding a CRM — configure it over a weekend and expect results by Week 2. That’s not how this works. This playbook is the order of operations for your first 90 days: the three-phase sequence that builds the intelligence foundation campaigns actually run on.
The 1–3% benchmark is not a ceiling. It is what happens when you treat every industry the same. This playbook introduces the Vertical Response Model — four structural drivers that create distinct performance profiles across eight verticals, and what research-led outreach changes about each one.
Most AWS partner outreach is generic by design — a capability list with an AWS badge attached. This playbook introduces the Ecosystem Intelligence Framework: three layers that convert generic capability into ecosystem-native execution for both SIs and ISVs.
Most outreach problems are actually offering problems. The fix is not downstream. This playbook defines the three-layer framework for building campaign-ready offerings — from foundation lock to finalization — with quality criteria for all six content dimensions and three worked examples across ecosystems.