Chris M.

The findings are specific: Salesforce’s OpportunitySplit percent field is validated to total 100%, and its owner field points to a user—an internal employee seat, not a partner company.

• The Salesforce object named Partner holds only a boolean, and its documentation says only one account can be marked primary for an opportunity.
• HubSpot ships 33 standard objects, none of them a partner.
• Oracle offers a partner percentage but defines it as credit unrelated to the sale, exempt from the 100% rule, and off by default.
• Chris argues that the apparatus for splitting value works right up to the property line between companies.
• The counterfactual question—whether a deal would have closed without the partner—never appears in the documents reviewed.

Microsoft routes multi-partner deals out of automatic approval and to a human council because its rules cannot divide value among more than one party. Chris calls this the most sophisticated partner-classification system on the planet breaking down exactly where value must be shared.

Chris says they build tools in this space, then spends much of the piece arguing against their own “just measure it faster” position. They cite pharmaceutical regulatory attempts that ran for forty years and mostly failed.

Read original

Capital allocation asks which partners deserve another dollar, another hour, or another person, given expected return, risk, and time to results—and whether the investment paid off.

• Chris argues that partner decisions based on sourced pipeline, activity counts, executive relationships, or whichever partner is loudest that quarter miss value spread across sales, marketing, product, customer success, marketplaces, and services.
• In this framing, the CFO sees the partner investment clearly and the return through fog.

If your CFO asked today which three partners deserve more investment and which three deserve less, could you answer with evidence? Chris says that if not, you don’t need another dashboard; you need a decision system.

Read original · Original 2

A sale has a buyer, an owner, a sequence, and a close, so the sales funnel compresses well.

• Ecosystems, by contrast, involve many parties holding different information and making different bets, with value moving across boundaries in both directions and relationships changing in value long after an opportunity has left the radar.
• Every time an ecosystem is forced back into the sales model, Chris writes, the instrument keeps revenue, attribution, and the quarter—and throws away introductions, delivery capacity, product knowledge, risk absorbed, trust spent, outside options created, and value that landed on someone else’s ledger.

A sales funnel compresses the market until it looks like a pipeline. Value the funnel can’t recognize gets flattened into stories—easy to cut when a CFO asks what to cut.

Read original

The usual answers—pipeline, influenced revenue, partner-sourced revenue, engagement, new integrations, campaigns launched—are valuable signals, but they can’t show whether partnerships create measurable financial value.

• Chris says partner teams track direct spend on MDF, headcount, events, enablement, integrations, incentives, and marketplace programs, but can’t prove that spending produced the expected return.
• Decisions then fall back on instinct, history, politics, partner size, or the strongest internal champion.
• Without the numbers, a CFO meeting means bringing stories, not evidence.

Two versions of the question recur: What would you put on the screen if your CFO asked for the ROI on your partner program tomorrow morning? And if you had $1M to invest in partnerships, could you defend that decision with numbers six months later?

Read original · Original 2 · Original 3

It is described as giving partnership leaders evidence instead of anecdotes and answering two questions: where to spend time and investment, and how to prove the investment was worth it.

• Posts describe a CFO layer intended to show that investing in the ecosystem is rational and ideal, and position the product as a decision system rather than another dashboard.
• The product pitch draws on the same measurement arguments as the non-promotional posts.

Chris announces a Tuesday series of executive questions tied to QuarqAI. Another post offers CROs a visual guide with ten steps to make a partner program measurable, accountable, and aligned with the rest of the revenue motion.

Read original · Original 2 · Original 3 · Original 4 · Original 5

Chris says most CROs they have worked with know partnerships have value but can’t see, measure, or forecast it, so partner work gets deprioritized or handed off and forgotten.

• The post offers a visual guide with ten steps to make a partner program measurable, accountable, and aligned with the rest of the revenue motion.
• The post announces the guide but doesn’t show the steps; ask for the guide to assess its substance.

The CRO-focused post presents the guide as a way for revenue leaders tired of guessing to make partner programs measurable and aligned.

Read original

It’s the closest thing in this material to primary-source technical digging, and it explains the constraint underlying every other post.

Messina dug into the data schemas behind the tools partner teams use every day — Salesforce’s object reference, HubSpot’s object list, the AWS and Microsoft co-sell APIs, and vendor admin documentation — to find out why partner measurement has stayed stuck for twenty years.

• The findings are specific: Salesforce’s OpportunitySplit percent field is validated to total 100%, and its owner field points to a user, meaning an employee with a login, so a partner company does not fit; the Salesforce object literally named Partner holds only a boolean, and its documentation says only one account can be marked primary for an opportunity; HubSpot ships 33 standard objects, none of them a partner; Oracle does give a partner percentage but defines it as credit ‘unrelated to the sale itself,’ exempt from the 100% rule and off by default.
• The question that would settle an argument — whether a deal would have closed without the partner, the counterfactual — does not appear in the posts.
• Microsoft, Messina notes, routes multi-partner deals out of automatic approval and into a human council because the rules cannot divide value among more than one party.
• Messina says they build tools in this space and spend much of the piece arguing against their own ‘just measure it faster’ position.

For brands planning a campaign

For a measurement brief, this diagnostic piece shows where a company’s own stack may be unable to record partner contribution. An expert call could start by asking which objects and fields the company uses and whether the blocker is configuration, process, or investment.

A newcomer can judge whether this reframing matches their own experience in one piece.

Messina’s thesis is direct: partner ecosystems were never sales functions and never will be.

• They explain why ecosystems ended up inside sales without calling anyone stupid: the org chart needed somewhere to put them, revenue was the nearest available language, and pipeline gave people something to report on a Tuesday.
• A sale has a buyer, an owner, a sequence, and a close, so the model compresses well; ecosystems do not resolve deterministically, involve many parties holding different information and making different bets, and keep changing in value long after any opportunity they touched has left the radar.
• Each time the ecosystem is forced back into the sales model, Messina writes, the instrument keeps revenue and attribution and throws away introductions, delivery capacity, product knowledge, risk absorbed, trust spent, outside options created, and value that landed on someone else’s ledger.
• They add that the funnel’s original instructions are more than a century old and candid about what the machine discards.

For brands planning a campaign

Use this as the opening frame for a call if the company’s partner team reports through a pipeline number. It names the tension — what the sales model can and cannot see — before turning to tooling.

If you read one post to understand their advice, this is a strong candidate.

Messina poses a concrete test: your CFO calls tomorrow and says there is $1M for partnerships.

• Where should it be invested?
• Most partner organisations, they argue, can say where money went — MDF, headcount, events, enablement, integrations, incentives, marketplace programs — because direct spend is tracked well, but they cannot prove that the spend produced the expected return.
• The decision then gets made on instinct, history, politics, partner size, or whichever partner has the strongest internal champion; six months later, activity and pipeline get read as confirmation.
• Messina separates two capabilities: deciding where the next dollar should go and proving afterwards whether that decision was right.
• The questions they list are investment questions — which partner created the return, which motion paid back, how long it took, what it cost, what would have happened if the money had gone elsewhere — and they name QuarqAI as the product they are building to address that gap.

For brands planning a campaign

This maps almost one-to-one onto the need to allocate partner investment. A short advisory engagement could focus on the two capabilities Messina separates: making a defensible allocation decision, then creating a clear trail that withstands CFO scrutiny.

Useful if you want to follow the thread rather than read one piece in isolation.

Opening with the question every partner leader eventually faces — what is the ROI on our partner program? — Messina lists the answers most teams give: pipeline, influenced revenue, partner-sourced revenue, engagement, new integrations, campaigns launched.

• They say these are valuable signals that cannot answer the question, which is whether partnerships create measurable financial value.
• Messina describes the trap: years of defending programs with spreadsheets, screenshots, and stories because the economics are invisible, belong to other teams, or both.
• When budgets tighten, invisible value is easy to cut.
• They then announce a series: every Tuesday, one executive question every partnership leader should be able to answer, starting with what you would put on the screen if the CFO asked tomorrow morning.
• Messina says this is why they built QuarqAI, which provides substantiation rather than anecdotes.

For brands planning a campaign

The Tuesday question format is a ready-made structure for a call or workshop agenda. These posts also market QuarqAI, so expect the conversation to include Messina’s product as well as independent advice.

It’s the sharpest conceptual piece in the set.

Messina argues the profession borrowed a scorecard from everyone else — pipeline from sales, attribution from marketing, retention from customer success, adoption from product — and called the mix partner ROI.

• The problem, they write, is that partner ecosystems do not create value in a straight line: a single technical integration might accelerate pipeline, increase product adoption, improve retention, reduce support costs, strengthen another partner relationship, and create expansion revenue at the same time.
• Credit then spreads to everyone and effectively to no one, ‘especially anyone showing up without receipts.’ Messina’s central distinction is between attribution, which asks who gets the credit, and contribution, which asks how value was created.
• Ecosystems are networks rather than funnels, where value moves in multiple directions, compounds over time, and often surfaces somewhere other than where it started.
• Messina points to QuarqAI as the product they have built against that idea.

For brands planning a campaign

Pair this with the capital-allocation post when briefing a call. If a company is stuck arguing over credit, this provides language to shift the discussion to how value is created and where it lands.

Readers who already track attribution will find the shift in question useful.

Messina argues that being told you have an attribution problem is only part of the story; the deeper issue is capital allocation.

• Attribution asks how much credit a partner should receive for an outcome; capital allocation asks which partners deserve another dollar, another hour, or another person, given expected return, risk, and the time it takes to see results — and whether the investment paid off.
• One explains past results; the other determines what gets funded next.
• Messina says partner decisions that lean on sourced pipeline, activity counts, executive relationships, and whichever partner is making the most noise that quarter miss the broader picture: value is scattered across sales, marketing, product, customer success, marketplaces, and services.
• Their image is of a CFO who sees the investment clearly and the return through fog.
• Ecosystem technology, Messina concludes, cannot stop at recording activity; it must help estimate which partners create financial value, what each relationship consumes, and where the next dollar is most likely to produce a return.
• If you cannot answer which three partners deserve more investment and which three deserve less, they write, you do not need another dashboard; you need a decision system.

For brands planning a campaign

This is the strongest fit for a need to allocate partner investment. A short engagement could focus on building the decision system Messina describes — expected return, risk, and time-to-results per partner — rather than producing another measurement report.

They examine the object references and admin documentation behind Salesforce, HubSpot, the AWS and Microsoft co-sell APIs, and Oracle, and report what the fields actually permit.

• Salesforce's OpportunitySplit carries a percent field validated to total 100%, and its owner field points to an internal user seat, not another company.
• The Salesforce object named Partner has no quantitative field, only a boolean, and the documentation states that only one account can be marked primary for an opportunity.
• HubSpot ships 33 standard objects, none of them a partner.
• Oracle offers a partner percentage but defines it as credit unrelated to the sale, exempt from the 100% rule and off by default.
• Microsoft routes multi-partner deals out of automatic approval and to a human council.
• Chris concludes that the apparatus for splitting value works right up to the property line between companies, and that no schema asks the question that would settle the argument: the counterfactual of whether the deal would have closed without the partner.

Primary-source document review rather than vendor marketing claims. Chris says they examined what the fields contain rather than what the website says is possible, and argues against their own proposed fix, citing pharmaceutical regulatory attempts as a forty-year failure.

For brands planning a campaign

For a company trying to improve partner investment measurement, the most useful question to ask on a call is which objects its CRM, PRM, and co-sell systems actually expose, and what evidence those fields can produce. The post offers a diagnostic approach a brand could apply to its own stack, but it does not test any vendor's implementation or show that every deployment shares the same limits.

Examples: Source 1

Attribution asks how much credit a partner deserves for an outcome.

• Capital allocation asks which partners deserve another dollar, hour, or person, given expected return, risk, and time to results—and whether that investment paid off.
• Chris argues that partner decisions based on sourced pipeline, activity counts, executive relationships, or whoever is loudest that quarter miss value scattered across sales, marketing, product, customer success, marketplaces, and services.
• In their framing, the CFO sees the partner investment clearly and the return through fog.

Reframes a familiar problem rather than adding a metric.

• Across posts, the same idea appears twice in different words: once as attribution versus capital allocation, and once as attribution versus contribution.
• Contribution asks how value was created rather than who gets credit.

For brands planning a campaign

This is the clearest entry point for an advisory or expert-call brief about allocating partner spend.

• It gives a brand a concrete question to bring into the conversation: which three partners deserve more investment and which three deserve less, and what evidence supports each call.
• The posts assert the framework's value but do not show it applied to a named company's numbers, so a call should test it against the brand's own data.

Examples: Source 1 · Source 2

Sales has a buyer, an owner, a sequence, and a close.

• Ecosystems, in their description, involve many parties holding different information and making different bets, with value moving across boundaries in both directions and relationships changing in value long after an opportunity has left the radar.
• Forcing ecosystems into the sales model flattens introductions, delivery capacity, product knowledge, absorbed risk, spent trust, and value landing outside the company's ledger into stories—easy to cut when a CFO asks what to cut.

For brands planning a campaign

Useful for a brand whose partner organization is fighting for budget or scope inside a sales-led structure.

• It points toward a framing conversation rather than a campaign asset, and cautions against briefs that assume the brand wants partner work validated strictly through pipeline and sourced revenue.
• The argument is a position, not one supported by company cases.

Examples: Source 1

Two examples: what would you put on the screen if your CFO asked for the ROI on your partner program tomorrow morning, and if you had $1M to invest in partnerships, could you defend that decision with numbers six months later?

• Chris writes that partner teams track direct spend such as MDF, headcount, events, enablement, integrations, incentives, and marketplace programs, but cannot prove whether the spend created the expected return.
• Decisions then fall back on instinct, history, politics, partner size, or the strongest internal champion.
• A related post states the standard bluntly: walking into a CFO meeting without the numbers means walking in with stories, not evidence.

Question-led posts name the executive audience, reject vanity metrics, and end with a question for the reader. Chris says they intend to publish one executive question every Tuesday, making this a deliberate series rather than a one-off.

For brands planning a campaign

This is a repeatable content format a brand could sponsor or co-create, suited to a thought-leadership or webinar series for partner and revenue leaders.

• The questions are practical prompts a brand could adapt for its own audience.
• Because the series explicitly promotes Chris's product, a sponsored version should separate the framework from the product pitch.

Examples: Source 1 · Source 2 · Source 3

It starts from the observation that most CROs Chris has worked with know partnerships have value but cannot see, measure, or forecast it, so the work gets deprioritized or handed off and forgotten.

Checklist-and-guide format rather than argument, aimed at a specific executive role.

Promotional announcement for the guide, not the guide itself. Chris's claim about CROs comes from their own experience, with no supporting examples in the post.

For brands planning a campaign

Shows a second content register beyond long-form argument: short, role-targeted, practical assets.

• A brand selling to revenue leaders could consider a checklist or guide collaboration.
• Check the guide's substance before building a joint asset around it.

Examples: Source 1

Posts describe a CFO layer intended to show that investing in the ecosystem is rational and ideal, and frame the product as a decision system rather than another dashboard.

Product framing carried by the same measurement arguments used in the non-promotional posts.

For brands planning a campaign

Any engagement should account for the fact that Chris is building and promoting a commercial product in the same space the brand would be asking about.

• That can be an asset for a working session on measurement, but the brand should expect the conversation to include the product and keep product claims separate from claims independently checked in the posts.
• Before relying on product claims, ask for evidence from its use and results.

Examples: Source 1 · Source 2 · Source 3 · Source 4

The posts position QuarqAI as a tool for partnership leaders to answer CFO-level questions about where to invest and how to prove return. The posts don't specify their title, ownership share or launch date; ask Chris to clarify those before assessing the relationship.

View example

Lela offers a structured framework for defining what a company owns, aligning partner types with growth plans, assessing readiness, and measuring results.

Lela’s examples focus on ecosystem design and operating choices; Chris’s posts focus on measuring partner contribution and deciding where investment goes.

Read original · Original 2

Barrett proposes comparing net revenue retention for partner-attached accounts with other accounts, while noting selection bias and the need for more careful comparisons.

Barrett’s examples include a cohort-comparison approach and the changing economics of channel work in AI; Chris emphasizes ecosystem-wide contribution, CRM data limitations, and capital allocation across partners.

Read original · Original 2

The posts set out a four-part sequence: know what you own versus what partners extend; grow with partner types that match the revenue model; assess internal readiness, including product scalability, documentation and co-sell preparedness; then measure contribution and use-case depth.

• They argue that partner programs underperform slowly rather than fail loudly.
• The second post traces where enterprise SaaS partner cuts landed: dedicated support for global systems integrators and top-tier technology partners survived, while partner account and partner success roles covering the remaining partners were cut.
• Those were the roles serving mid-market and SMB buyers.
• Companies whose mid-market coverage has thinned, or that are designing a first ecosystem, will get more here than from a measurement critique.

The posts focus on program design and coverage strategy, not measurement mechanics.

• They do not explain what a CRM or PRM can record, give field-level examples, or propose a metric to put before a CFO.
• Companies already running a program and needing to show which partner investments pay back will find less here than in a schema audit or a metric-replacement argument.
• The assessment draws on two posts, so its scope is narrow.

Examples: Source 1 · Source 2

The posts describe Google Cloud, Salesforce, Microsoft and WRITER moving from activity-based to outcome-based tiers, self-attested references to independent verification, and point-in-time claims to lifecycle measurement.

• They then propose reporting net revenue retention on partner-attached accounts against net revenue retention everywhere else, treating the delta as the program's contribution.
• The stated reasons: finance already owns net revenue retention; a cohort comparison avoids relitigating sourced versus influenced; and attachment is a recorded fact rather than an assertion.
• The second post argues that AI removes setup work and grows operating capability, leaving partners who sold implementation hours with a shrinking floor while partners who operate something on a customer's behalf have more room.
• Better suited to companies that need a defensible metric or are repricing partner offers around ongoing operation.

The metric is presented as a personal position, and the post acknowledges its weakness: part of the delta reflects selection bias, while a stronger within-segment, before-and-after comparison is harder and is not done cleanly in these posts.

• There is no field-level account of why partner contribution cannot be recorded, the distinctive detail on this page, nor any schema or systems detail.
• The two posts summarize programme changes at Google Cloud, Salesforce, Microsoft and WRITER rather than documenting them from primary sources.

Examples: Source 1 · Source 2

The posts describe that reconciliation happening quietly in a spreadsheet, usually by a senior commercial person before a meeting.

• They argue that the constraint is a decision problem, not a technical one: it requires someone senior enough to be believed and close enough to the commercial side to know what is at stake.
• The companion post argues that clean commercial data should shape what a business sells, to whom and through which channel, not just improve reporting.
• It cites a 2025 survey finding that 58% of respondents named efficiency as the primary value of data, against 10% who named business growth.

This is not partner-ecosystem work.

• There is no partner program measurement model, co-sell, marketplace or channel-partner detail, or partner-leader-versus-CFO framing.
• Choose this when the partner-spend question is really about reconciling multi-channel data in a consumer-facing or wholesale business.
• It is a weaker fit when the partners are technology, reseller or co-sell partners in a SaaS motion.
• The survey figure is cited rather than reproduced.

Examples: Source 1 · Source 2