Best of LinkedIn: Channel Marketing CW 15/ 16

00:00:00: This episode is provided by Thomas Allgaier and Freeness, based on the most relevant LinkedIn posts about channel marketing in calendar weeks fifteen-and-sixteen.

00:00:21: You

00:00:29: probably have a spreadsheet open somewhere.

00:00:31: Oh,

00:00:31: definitely.

00:00:31: or dashboard

00:00:32: exactly the dashboard that claims your partners are driving you know millions of dollars in pipeline.

00:00:37: yeah.

00:00:37: but I mean If you were to actually audit those numbers like really look closely at the underlying data, You'd probably find that a massive chunk of that pipeline is a complete hallucination.

00:00:47: It's totally fake.

00:00:48: and That Is exactly what we are tearing down today.

00:00:51: over The last two weeks calendar weeks fifteen and sixteen We've pulled the absolute most critical channel marketing insights from LinkedIn.

00:00:58: no

00:00:58: fluff Just the actual mechanics Of What's Working

00:01:01: right?

00:01:02: We're going to look at how to turn ecosystem motions from a sort of nice-to-have side project into your primary predictable revenue engine.

00:01:11: And that transition, by the way, From Nice To Have to Core Infrastructure... That is the defining shift in market right now.

00:01:18: Yeah!

00:01:18: Organizations are finally demanding that ecosystems operate with exact same rigor as direct

00:01:23: sales.

00:01:24: But friction there.

00:01:25: you can't just mandate Revenue from an Ecosystem When the well, the foundational mechanics of how you track things are fundamentally broken.

00:01:33: which brings us right into our first major theme from The Sources revenue discipline.

00:01:38: Yes

00:01:38: Revenue Discipline I mean we have to start here.

00:01:41: There is this persistent habit Of confusing partner engagement with actual mathematical pipeline.

00:01:47: Oh i see This all the time.

00:01:47: teams Are high-fiving over a partner sending A slack message asking for a pitch

00:01:52: deck Right or they co host one webinar and suddenly that gets logged as a sourcing signal.

00:01:58: But engagement is not revenue.

00:02:00: Jamie Art called this out recently on LinkedIn, and he described it perfectly as fluffing the funnel.

00:02:05: Fluffing The Funnel?

00:02:06: That's so accurate!

00:02:07: Eric basically argues that real partner pipeline Is math Not magic.

00:02:12: It needs to be a strict formula

00:02:14: Like X number of partners actively co-selling right

00:02:16: Exactly touching Y specific accounts per week And converting at Z percent To qualified pipeline.

00:02:23: If you can't articulate that specific math, you do not have a forecast.

00:02:27: No!

00:02:27: You have a wish list and getting to the math requires an entirely different operational mindset.

00:02:34: Rob Moyer was talking about this.

00:02:35: he describes it as shifting into operator

00:02:37: mode.

00:02:37: Operator Mode right.

00:02:38: so treating like Revov

00:02:40: Exactly.

00:02:40: He argues that partnership teams need adopt exact same discipline as Revovs.

00:02:45: So that means you have to physically engineer your CRM, to handle partner attribution.

00:02:50: Which nobody wants to do because it's

00:02:51: hard!

00:02:52: It is.

00:02:52: but you have build tiered attribution frameworks You have restructure into POD models.

00:02:57: Wait

00:02:57: explain the POD Models in this context?

00:02:59: so its where marketing sales and alliances aren't siloed anymore.

00:03:03: They operate as a single cross-functional unit dedicated to specific partner portfolio.

00:03:08: That makes alot of sense

00:03:10: Because... I mean, if the finance department looks at your Salesforce instance and they can't trust the data.

00:03:16: Your partner program essentially doesn't exist.

00:03:19: it's

00:03:19: just a vanity project.

00:03:20: At that point let's dig into why?

00:03:22: That CRM engineering is so critical because i think A lot of partner deals actually fail right in The middle Of the process.

00:03:28: oh

00:03:29: the Middle Is where Deals go to die.

00:03:31: Managing the middle of a Partner Deal Without a Connected Tech Stack It's like two construction crews building a bridge from opposite sides of the river, but one is using metric measurements and other is using imperial.

00:03:43: That's

00:03:43: great analogy!

00:03:44: Right?

00:03:44: They're both working incredibly hard...but they are never going to connect in the center.

00:03:49: Orlando Nato highlighted this exact structural flaw.

00:03:52: Yeah you get all that excitement at the beginning.

00:03:54: The Handshake's the shared vision Yep

00:03:56: And then intense focus when revenue was about close.

00:04:00: But middle is just black hole Unclear ownership fuzzy handoffs between the alliances team and the direct sales team.

00:04:07: And literally zero inspection cadence to see who's actually driving the next step.

00:04:13: Yeah, exactly!

00:04:14: That middle management failure is almost always a reflection of disjointed architecture.

00:04:19: George Vitko was talking about this.

00:04:21: He's audited hundreds of these partnership programs.

00:04:24: What did he find?

00:04:25: He noted that an alarming number of them quietly die because The entire motion literally lives in a notion document or a static spreadsheet.

00:04:34: Oh man, you cannot run an ecosystem out of a NotionDoc.

00:04:38: You just can't!

00:04:39: When you rely on static documents the handoff inevitably breaks.

00:04:42: Vicco points out...you need a purpose built

00:04:45: stack.

00:04:46: So functionally what does that look like?

00:04:47: He says it looks like using a tool like Crossbeam for secure account mapping where your hashing emails and matching lists in a data escrow so you aren't guessing when the accounts overlap.

00:04:57: Right, and then that data has to route directly into a central CRM like HubSpot or Salesforce.

00:05:03: To actually trigger the co-sale motion

00:05:05: while platform like partner stack handles The actual enablement in the payout.

00:05:09: if you don't have That mechanical plumbing in place You don't really Have a partnership problem?

00:05:14: You have assistance architecture problem.

00:05:16: Okay.

00:05:16: So let's say you fix the planning.

00:05:18: the CRM is engineered The account mapping is automated.

00:05:21: The metrics finally align,

00:05:23: the dream scenario

00:05:24: right?

00:05:25: But the immediate temptation then Is to just turn around and blast out invitations To five hundred potential partners to scale the ecosystem.

00:05:34: Which is the fastest way to break the exact system?

00:05:37: you just built exactly

00:05:38: the impulse to go wide And scale assumptions as a massive trap.

00:05:42: The data strongly suggests you have to do the exact opposite.

00:05:45: You have

00:05:45: to test the plumbing first!

00:05:47: A Kreeti Shrivastava framed this brilliantly on LinkedIn by taking the MVP concept from product development and applying it to alliances.

00:05:54: Minimum

00:05:55: viable partnerships?

00:05:56: Minimums viable partnership exactly because traditional approach is invest heavy resources up front, build portals draft all collateral...

00:06:04: And then just hope they can actually sell.

00:06:06: Right

00:06:07: Travastava argues for running a literal pipeline test first.

00:06:10: Take just one or two real active deals, run the co-sell motion manually with the partner...

00:06:16: Just to see where the friction is?

00:06:18: Exactly!

00:06:19: Find the friction in contract and handoff in customer conversation.

00:06:24: Prove that this specific partner profile can actually create and close pipeline before you spend single dime trying to stale them.

00:06:33: And granular testing critical because the mechanics of how different partners make money very wildly.

00:06:40: They really do, you can't build a single monolithic enablement process for

00:06:44: everyone!

00:06:45: David Euber broke this down recently showing why A One-Size Fits All Playbook actively creates channel conflict.

00:06:51: Give

00:06:51: me an example.

00:06:52: We'll take a global system integrator – a GSI.

00:06:55: Their economic engine is built on large scale transformation projects.

00:06:58: they want massive services pulled through

00:07:00: Right.

00:07:00: so if your software doesn't require like deep implementation consulting, they probably won't touch it.

00:07:05: Exactly

00:07:06: whereas a managed service provider in MSP operates into completely different reality

00:07:11: entirely different.

00:07:12: They need multi-tenant capabilities.

00:07:14: right if an msp has to log in and out of fifty different instances To manage fifty different clients your product is a liability to their margins.

00:07:21: They need operational efficiency

00:07:22: and recurring revenue

00:07:23: Yes.

00:07:24: And then you have independent software vendors ISVs who scale through product alignment.

00:07:30: They need a better together integration story, where the two tools just share data natively.

00:07:35: So if your partner program doesn't mechanically support how each of these specific models generates value you just become overhead to them?

00:07:42: You're just a nuisance and supporting those distinct models takes heavy lifting internally.

00:07:47: Greg Portnoy laid out very sobering rule-of-thumb regarding resource allocation.

00:07:52: Oh,

00:07:52: I saw this the thirty percent rule.

00:07:54: Yeah

00:07:55: if you expect thirty percent of your company's revenue to come from partners You have to dedicate thirty percent Your internal resources to partnerships

00:08:02: which is a tough pill to swallow for A lot of execs.

00:08:04: it Is that means thirty percent Of your direct sales teams time has spent co-selling.

00:08:09: Thirty percent of Your marketing budget goes To joint go-to market content

00:08:12: and thirty Percent of customer success is dedicated to uncovering Mutual expansion opportunities.

00:08:18: Ecosystems are not just a passive lead channel you turn on.

00:08:21: They require serious infrastructural commitment, and we're seeing massive market signals validating that exact level of commitment.

00:08:29: Like

00:08:29: what?

00:08:30: Well Will Taylor highlighted a pivotal shift recently with AppDirect acquiring partner stack.

00:08:35: Oh yeah!

00:08:36: That was huge news.

00:08:37: It wasn't just standard merger it's really fundamental rewiring of BDB commerce.

00:08:43: Let us unpack the mechanics for the listener.

00:08:46: Why does combining those two specific companies actually change the buyer journey?

00:08:50: Okay, so AppDirect provides the infrastructure for how B to B software is provisioned and transacted.

00:08:57: So literally the shopping cart and subscription management Right And PartnerStack manages the affiliate data.

00:09:02: The partner tracking the incentive payouts.

00:09:05: By merging them you are connecting the transaction data directly with the incentive data in real time.

00:09:10: So the partners no longer just handing off a lead and hoping for a check-in ninety days Exactly.

00:09:15: their integration is part of the native checkout flow.

00:09:18: The ecosystem partner essentially becomes the storefront, when infrastructure providers consolidate a commerce layer with the Partner Layer like that it proves that Ecosystem led growth.

00:09:33: So, the technology is maturing.

00:09:34: The data is closing the loop and market expectation is clearly shifting from vague promises to highly tracked proven revenue?

00:09:43: Yes And that actually brings us into the biggest players in the room – the hyperscalers because they are enforcing this shift aggressively.

00:09:50: Oh!

00:09:50: They're not messing around anymore.

00:09:52: If you think your internal CRM discipline needs work, wait until you see what AWS and Microsoft are mandating.

00:09:58: The days of earning a badge putting it on your website And waiting for leads Are entirely dead

00:10:03: Totally Dead.

00:10:04: Latifam Lani shared A major update regarding AWS's new twenty-twenty six rules.

00:10:09: Don't have the New Rules.

00:10:10: To even renew a specialization, AWS is now requiring actual launched ACE opportunities tied to specific solutions.

00:10:18: And we should probably clarify what launched ASEE opportunities functionally means for anyone who doesn't live in the AWS

00:10:25: portal, right?

00:10:25: So a CE stands for APN customer engagement.

00:10:28: Yeah, it's aws is Portal.

00:10:30: AWS is no longer just asking if you passed a technical certification.

00:10:33: they won't prove.

00:10:34: They are demanding that you formally register of the cosale pipeline and their specific system proving with hard data That you were actively working a deal together.

00:10:43: So if that pipeline isn't logged and validated in

00:10:45: A.C.E.,

00:10:46: you essentially do not exist to them.

00:10:47: You

00:10:47: lose your visibility, you lose your marketplace benefits.

00:10:51: Proof is officially replacing promises

00:10:53: But securing that proof means you have to navigate their internal hierarchy which I mean, let's be honest.

00:10:59: It is incredibly complex!

00:11:01: Pete Sarris actually calls this the Zoo Framework.

00:11:03: The zoo

00:11:04: framework?

00:11:04: Yeah it a mental model for ISVs to understand the hyper-specific roles within a behemoth like AWS You have map your ideal customer profile directly into the specific AWS roles that are already selling in at exact same customer base.

00:11:20: Right because an AWS account manager has completely different compensation incentives than say an ISV Success Manager.

00:11:27: Exactly If you pitch the wrong rep or just don't understand how your deal accelerates their specific quote of retirement, Your co-sell motion is going to stall immediately.

00:11:36: And Microsoft operates with a very similar level of rigor right now.

00:11:41: Deidre Jones pointed out that Microsoft partners frequently fail but it's rarely because they're underlying.

00:11:46: technology is flawed.

00:11:48: Why

00:11:48: do they fail then?

00:11:49: She says they failed because an evidence gap.

00:11:51: They show up without structured customer win wires.

00:11:55: Ah!

00:11:56: Win wires Yeah.

00:11:57: And a wind wire is not a marketing fluff piece.

00:12:00: It's a technical structured document that proves to Microsoft field sellers exactly how a joint solution was deployed and what specific Microsoft consumption metrics it drove.

00:12:10: Because without the technical proof of execution, Microsoft Sellers just won't risk bringing you into their accounts

00:12:16: Exactly!

00:12:17: Which totally reframes how companies should be spending their marketing dollars.

00:12:21: I mean think about this A lot.

00:12:22: organizations will drop hundreds or thousands team and set up a giant booth at an AWS

00:12:29: summit.

00:12:30: But if these hyperscalers require surgical registered pipeline, specific technical wind wires then just standing on the trade show floor pitching your product to anyone who walks by seems like massive misallocation of

00:12:42: capital.".

00:12:44: And Andrew Morris addressed this exact disconnect.

00:12:47: he says is because they treat it like a traditional trade show.

00:12:53: Right,

00:12:54: trying to scan as many badges as possible

00:12:56: Exactly!

00:12:57: But hyperscaler summits are not designed for your product pitch.

00:13:01: They're designed around AWS growth initiatives

00:13:05: So you have to align with their goals.

00:13:06: If your booth messaging and team's conversations cannot explicitly translate how your software accelerates AWS' specific strategic priorities For that quarter You were just expensive noise on the floor.

00:13:18: So what is the actual playbook then?

00:13:20: If broad event marketing and generic enablement don't work with hyperscalars, how do you actually get those first deals registered.

00:13:28: Well, Delhany Pellehipitia laid out an incredibly focused strategy for AWS co-selling.

00:13:34: she advises stripping away The Broad Enablement.

00:13:36: entirely okay.

00:13:37: instead You pick one single geographic region.

00:13:40: you find One early champion within that specific AWS CEO who was hungry and relentless

00:13:46: And Then you just hyper focus on them.

00:13:47: Yes.

00:13:48: You throw all your resources at getting that first joint win across the line fast, you document the exact mechanics of what Windwire we just talked about and then use single proven GEO as a blueprint to scale for the next region.

00:14:02: So it's really about engineering proof points that scale rather than scaling assumptions around the whole map

00:14:08: Exactly.

00:14:09: But this level requires intense manual discipline which is exactly why the entire industry's currently scrambling to find a shortcut.

00:14:19: And let me guess... The assumed shortcut for managing all this complexity, the CRMs, the hyperscaler portals... ...the different partner models is artificial intelligence.

00:14:27: Of course it is!

00:14:28: AI is a gravitational pull of literally every B-to-B conversation.

00:14:32: right now Everyone wants to layer AI over their ecosystem To just automate the pipeline math.

00:14:38: But Kyle E posted massive red flag about this approach on LinkedIn.

00:14:41: He warned that if you apply AI Over broken attribution models and scattered spreadsheets we talked earlier You do not get digital transformation.

00:14:49: No, you get a mask

00:14:50: right because AI cannot magically invent partner data that was never entered into the CRM in the first place.

00:14:57: if The deal source field is blank Ai will just hallucinate.

00:15:01: A narrative.

00:15:02: Kyle called it expensive Kion with a better user interface.

00:15:06: That Is such a good line?

00:15:07: You are literally Just generating bad partner insights at a much faster speed.

00:15:12: the tool only accelerates the underlying reality.

00:15:15: But even when the data foundation is solid, you know The human implementation of AI and partnerships has often deeply flawed.

00:15:21: How so?

00:15:22: Teresa Carragall highlighted a massive disconnect in how ecosystem teams are adopting these tools.

00:15:28: Leadership buys an AI license They run a generic training session on how to write prompts And two weeks later the partner managers are right back To their old manual workflows

00:15:36: Because generic training doesn't actually solve daily friction.

00:15:40: Carragall argues that AI enablement has to be tied to hyper specific role level workflows.

00:15:45: Yes, you can't just teach them to ask chat GPT or at a poem

00:15:48: right?

00:15:48: You have to teach a partner manager how to use AI to physically prep for a nine AM Tuesday orderly business review with a top tier MSP.

00:15:56: exactly show them How the AI can pull usage data from Salesforce cross-reference it was support tickets in Zendesk and synthesize The account overlaps from cross beam

00:16:06: To generate a working actionable brief in thirty minutes, if AI isn't an operational lever for their daily reality it's just a distraction.

00:16:15: And we have to remember the context of that Daily Reality too because B-to-B revenue is inherently a multiplayer game.

00:16:21: Shugata Sanyal shared a fascinating conversation with Martek expert Scott Brinker who gets to core this multiplayer concept.

00:16:29: Yeah coordinating network of ISVs resellers and GSIs across different regions logistical puzzle.

00:16:36: Sineal and Brinker point out that AI should not be viewed as just a single player productivity tool to help OneRep write better email.

00:16:43: Right, the true power of AI in EtoSystems is at coordination layer.

00:16:46: so partner relationship management systems The CRM

00:16:50: AI can encode program logic Monitor compliance And govern multi-party workflows At scale Ensuring everyone on network Is actually operating off same data.

00:16:59: And we are seeing that multiplayer coordination layer being built in real time right now.

00:17:04: Chris Simula and Sager T both analyzed a massive pivot happening at Salesforce with the launch of Agent Exchange.

00:17:11: Oh,

00:17:11: Agent Exchange is fascinating!

00:17:13: Yeah, Salesforce is bringing thousands of apps and autonomous agents into a single marketplace.

00:17:18: but The Real Story's how they're changing partner evaluation.

00:17:21: Right.

00:17:21: historically you were evaluated on How many certifications your team held?

00:17:27: But Salesforce is shifting that evaluation model entirely toward AI-driven customer outcomes.

00:17:32: The metric isn't did you deploy the software, it's can you orchestrate AI data and automation to drive a measurable business result for the client?

00:17:42: So

00:17:42: the technical bar is rising exponentially at the orchestration of agents ,the rigorous CRM discipline, the hyperscaler portals in this very heavy highly technical load

00:17:52: It Is!

00:17:52: But amidst all of this automation and infrastructure, Amos Avenue provided a really vital grounding thought.

00:17:58: What did he say?

00:17:59: He reminded the market that while AI will inevitably automate the account mapping and QBR prep in context analysis, it can never replace human element of a partnership.

00:18:09: Absolutely true!

00:18:10: AI cannot sit-in room read emotional temperature client build trust required to forge compelling co story.

00:18:18: technology just exist remove friction.

00:18:20: so humans connect create value.

00:18:24: The systems orchestrate network but humans still have close

00:18:27: gap.

00:18:27: Exactly We have covered a tremendous amount of ground today, from engineering your CRM for operator mode to navigating the strict new realities of AWS and Microsoft all the way to utilizing AI at the coordination layer.

00:18:42: It's a lot to process

00:18:43: it is.

00:18:44: so I want to leave you with a final thought to mull over as you audit your own strategy this week.

00:18:48: that comes from Mohit Bist and it just perfect synthesis where market heading.

00:18:53: let hear he said partner program dead.

00:18:56: AI hasn't told yet.

00:18:57: wow It is a stark warning, but it really captures the reality of.

00:19:12: Are you building the infrastructure to lead your ecosystem or are you moving so slowly that you're going get replaced by

00:19:27: it?

00:19:27: That's a question right there.

00:19:28: If you enjoyed this episode, new episodes drop every two weeks!

00:19:32: Also check out our other editions on account-based marketing field marketing AI and Betabee Marketing Martech.

00:19:38: Go To Market & Social Selling.

00:19:40: Keep pushing the boundaries of your Ecosystem And Stay Disciplined With Your Data.

00:19:44: Thank

00:19:44: You So Much For Joining Us.

00:19:46: Don't Forget To Subscribe.