# Barrett King

Barrett King works on partner programs and partner-led growth, with a focus on measuring customer outcomes rather than partner activity. King says they are working at Ottimate on partner activation and joint go-to-market strategy.

- Profile: https://b2binfluencer.marketing/creators/barrett-king/
- LinkedIn: https://www.linkedin.com/in/barrettjking
- LinkedIn followers: 18,586
- Topics: artificial-intelligence
- Based on 10 dated posts, latest 2026-10-05

## Summary

Barrett King is most useful for partner program leaders who want to measure customer outcomes instead of partner activity.

- Best for: A B2B fintech or accounting partner campaign about outcome measurement and joint go-to-market.
- Not for: High-volume sponsored content, product demo videos, paid ads, or campaigns measured mainly on impressions and clicks.
- Check first: Confirm whether they accept sponsorships and agree on scope, compensation, and deliverables directly.

### Takeaways

- Sourced pipeline and program badges do not show whether customers benefited.
- Compare net revenue retention for partner-attached accounts with other accounts.
- AI shifts partner work from one-time implementation to ongoing operations.

## Main ideas

- **Replace sourced pipeline with net revenue retention on partner-attached accounts**: King argues that sourced pipeline is becoming the least valuable headline number in a partner program: it measures partner activity, not customer outcomes. A program that only counts what a partner brings in is an internal scorecard, not a growth engine. They propose replacing it with net revenue retention on partner-attached accounts compared with NRR on all other accounts, and treating the difference as the program's contribution. King gives three reasons: finance already owns NRR, so no one has to trust a metric the partner team invented; a cohort comparison avoids the sourced-versus-influenced argument; and partner attachment is a recorded fact, not an assertion.
- **The honest version compares the same account before and after attachment**: King raises the objection a CFO quickly reaches and answers it directly: some of the gap between partner-attached and other accounts reflects selection bias, because partners attach to healthier, better-resourced customers, and some of that difference would have appeared anyway. The stronger comparison, they say, looks within a customer segment and tracks the same account before and after partner attachment, rather than comparing partner customers with everyone else and calling it proof. King says plainly that this is harder and has not yet been done cleanly.
- **Large partner programs have already moved from self-attested claims to verified delivery**: King argues that the biggest programs have answered what replaces activity metrics, mostly within the last year. They see the same three moves across four examples: activity to outcome, self-attested to verified, and point-in-time claim to lifecycle measurement.
- **AI moves partner value from installation to operating a system**: King rejects the claim that AI kills the channel and divides the work instead: setup work disappears; keeping things working grows. Implementation was a one-time fee with a defined end, while operating capability is a standing relationship that gains value the longer it runs. King points to integration governance, securing enterprise data flows, and maintaining AI performance over time as areas where partner engagement is growing. Automation remains fragile at the seams, where data quality and timing matter, so manual workarounds persist long after the core workflow is automated. Those seams, they say, are partner territory—and have become more valuable because more now runs through them.
- **Publish the claim, name the counter-question, and ask readers to test it**: The posts follow a consistent shape: state a contrarian position, name the strongest challenge, cite comparable programs or research, and end with a direct question to other practitioners. King invites readers to test the argument in public and credits the people and sources that sharpened it.
- **A vendor's product decision comes before its partner decision**: King argues that what a vendor gives partners to sell determines whether the partner business has a future, making this a product question first. If a program gives partners only something to install, they say, it has handed them a shrinking business and will then blame them for underperforming. King notes that they and most vendors have been slower on this than they would like to admit.

## Work to read

- [Sourced pipeline is becoming the least valuable partner metric](https://www.linkedin.com/posts/barrettjking_sourced-pipeline-is-about-to-become-the-least-activity-7510340178859786240-i3Gx)
- [What CFOs will accept instead of sourced pipeline](https://www.linkedin.com/posts/barrettjking_copilot-activity-7511033432815259648-X80t)
- [AI shifts partner work from implementation to operating capability](https://www.linkedin.com/posts/barrettjking_fintech-accounting-bookkeeping-activity-7509964595722211329-N_ix)

## Brand relationships

- **Ottimate** (employment)
- **Partnership Leaders** (mention)

## Partnerships

Barrett King’s posts list no sponsorship tiers, media kit, rate card, or inquiry form. They publish practitioner commentary on partner programs: partner-attached accounts should be judged on net revenue retention against comparable accounts, not sourced pipeline; and AI shifts partner work from one-time implementation to an operating capability customers keep paying for. They say they are defining partner activation and joint go-to-market at Ottimate, making a direct professional conversation on LinkedIn the clearest route for a brand. A proposal should specify the customer outcome, not what the partner brings—the framing they argue for publicly. They also say a defensible cohort comparison requires measuring the same account before and after partner attachment, using net revenue retention figures finance already trusts; that is harder than comparing partner customers with all customers. Brands seeking their help with measurement should plan for that data access and finance sign-off. Ask directly about available sponsorship formats and the partnership process before committing budget.

## Alternatives

- Chris M.: Chris M. is the better choice when the campaign's hard part is the data plumbing rather than the boardroom pitch. Their posts examine why partnership measurement has been stuck for twenty years: CRM object schemas that cannot record a partner's share of a deal, the gap between what Salesforce, HubSpot, AWS, and Microsoft co-sell APIs actually store, and the counterfactual question of whether a deal would have closed without the partner. A second post argues that partner ecosystems are not sales functions and that forcing them into a sales funnel discards the introductions, delivery capacity, product knowledge, risk absorbed, and trust the funnel was never built to hold. For a brief whose sticking point is whether an outcome-based metric can be recorded in the systems at all, that structural argument is more useful than restating the metric case.
- Sergey Danishevskiy: Sergey Danishevskiy is the stronger pick when the decision is about hiring or evaluating the partner who runs the work, or when the campaign needs the cost and ROI argument. One post models a three-year total cost of ownership for building a custom CRM versus buying HubSpot across three company sizes, with AI-assisted development already assumed, and lands on figures such as SMB at $61K versus $225K and enterprise at $2.8M versus $6M. The other gives a five-part test for choosing a RevOps partner: diagnose before quoting, build rather than advise, plan for the partner's own exit, cover the full revenue loop, and tie accountability to outcomes instead of hours. If the call to action is how to choose a partner accountable to outcomes, that checklist is more directly usable than an argument about which headline metric to use.
- Lela Koopal-Patel: Lela Koopal-Patel is the better choice when the campaign turns on partner org structure, coverage, and reaching the mid-market and SMB through smaller partners. One post traces where the enterprise-SaaS partner-team cuts landed: GSIs and the top 1% of technology partners were largely protected, while the PAMs, PSMs, and enablement leads serving the other 99% were cut. Those partners served the mid-market and SMB; they stop learning how to sell the product and eventually stop thinking about the vendor, while mid-market buyers move to more agile stacks. The second post lays out a Know, Grow, Assess, Measure framework for building an ecosystem, including how partners are tiered and measured and the warning that changing the scoreboard every year leaves you unable to tell what works. For a brief about rebuilding partner coverage or where to put enablement investment, that is closer to the decision than a metric definition.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/