Board reporting for partnerships: the few numbers that hold up

Boards do not need a partner update. They need to know whether the channel is producing, whether the production is real, and whether you are about to spend more people or more engineering on it. Most partnership slides fail that test. They show logos, meetings, MOUs, and a pipeline number that mixes sourced with influenced. The first follow-up from a finance-minded director, "show me the deals," is where the slide dies.

This post is the board version of a partnerships report for a seed-to-Series-B company: a small set of numbers, two definitions you will not change, a health read on the integrations, and an explicit list of what you will not show. For the exec screen those numbers live on, see building a partnerships dashboard. For the metric menu, see partnership metrics. For the cost side, see partner program ROI. Here the question is narrower: what holds up in the room.

The 60-second version

If you only read one section, read this one:

• Four numbers, same every time: sourced pipeline (and won), influenced pipeline (and won), adoption on live integrations, cost or capacity of the program.
• Sourced and influenced never share a cell. Sourced is origin. Influenced is a touch on a deal that already existed. Do not add them.
• Adoption is the health number. Active use, not listings, not signed partners.
• Leave off logos, meeting counts, MOUs, and "ecosystem reach." They do not survive a question.
• Write the definitions on the slide, in one line each. If you cannot, you are not ready to report the figure.
• Trends beat a record quarter. Four quarters of the same definition is the product.
• Say what you want. A board update without an ask (keep, add a slot, hire, pause) is a screenshot.

What a board actually wants

A director is trying to decide whether partnerships is a working motion, a science project, or a cost that should wait. They can do that with a short story: we staffed this capacity; this is what it produced that would not have existed (sourced); this is where it helped deals we already had (influenced); this is whether the technical work is used; this is what we will do next half.

That story maps to partnership OKRs and partnership targets you should already be running. If the board slide introduces new metrics the operating team does not use, you will scramble before every meeting and the numbers will drift.

They do not want a tour of the ecosystem. They have seen logo walls before. They know how cheap a logo is. Give them the same four tiles every meeting. If a tile is zero, show zero. Zero is information. A replacement metric that happens to be up is not.

Won numbers will lag. At seed they may be empty while pipeline and adoption are not. That is allowed if you say so. Filling the empty tile with activity is not.

Sourced vs influenced, in language that survives a question

These two words are where partnership reporting loses the room. Use them as if a skeptical CFO will sample three deals.

Sourced. The partner originated the opportunity. Without that partner, the deal is not in your CRM. Registration exists, with a timestamp at entry. Your AE may still have closed it. The origin is the partner.

Influenced. The opportunity already existed. The partner touched it in a way you can describe: joint call, technical validation, attached integration as a requirement. You would still have the row in the CRM without them.

A deal is one or the other, never both. If you cannot tell, it is influenced, or it is untagged. Untagged is allowed. Inflated sourced is not.

Write those two sentences on the slide. When someone asks "is the Acme deal sourced," you open the CRM, not a footnote. If you cannot open the CRM, do not show the number. Partner pipeline in the CRM is the plumbing. Board reporting is not a second set of books.

Do not report "partner pipeline" as a single sum. A director who has lived through one channel argument will assume you double-counted. Two columns, every time. Discounting influenced in an ROI model is a separate, conservative choice. On the board slide, show influenced at face value of the tagged deals, labeled as influenced, and be ready to say you do not claim 100 percent of that revenue as caused by the partner.

Adoption, what not to show, and definitions that hold

Adoption tells the board whether the partnership is a product fact. Pipeline can be theater. Active accounts on a live integration are harder to fake.

Pick one definition and keep it. Example: accounts with a successful connection and use in the last 28 days. Not "enabled." Not "installed once." If you have two or three live integrations, show them separately or show a total plus a note if one of them is carrying the number. Time-to-live is a useful supporting number when you are asking for more slots. Error rate belongs in an appendix unless health is the story.

What not to show, and what to say if someone asks why it is missing:

Partners signed / logos. "We can list them. Live and used is the outcome."

Meetings, events, touches. "Operating metrics. Appendix if you want them."

MOUs, LOIs, 'strategic alignment.' "Paper. We report when something ships or a deal is tagged."

Marketplace rank, impressions, badge scans. "Distribution trivia unless we can tie it to tagged pipeline or adoption."

A combined 'partner-sourced ARR' that includes influenced at 100 percent. "We will not report that. Here are the two columns."

If a director wants the logo list, put it in the appendix. Leading with it trains the board to grade you on business development theater, which is a different job (see partnerships vs business development).

The test: a director picks a number. You say the definition in one breath. You show a report that lists the deals or the accounts. The definition matches last quarter's.

Write a definitions box. Four lines is plenty:

• Sourced: registered origin, tagged at creation, not at close.
• Influenced: existing opportunity, partner role documented, tagged at the time of the touch.
• Adopted: active connection in the last N days (state N).
• Capacity: named people and named build slots this half, including maintenance.

If finance uses different words (bookings vs pipeline, ARR vs ACV), use their words on the tiles. OKRs that do not match the board language will be ignored. Change a definition in public. If you have to retag history, show old and new, once. Quietly widening "influenced" is how you lose the next four meetings.

Bring a sample. Three sourced deals and three influenced deals, with the tag reason. End with the ask: keep the current capacity, add a slot, hire, or pause net-new. A board that sees numbers without a decision will invent one for you.

Common mistakes, and the fix

One 'partner pipeline' number. The fix: two columns, sourced and influenced. Never summed as new demand.

Tagging at close. The fix: tag at entry. Memory is not a source system.

Leading with logos. The fix: adoption and tagged pipeline first. Logos in the appendix if at all.

Changing the metric when the story is weak. The fix: same four tiles. Explain the zero.

Hiding cost. The fix: people and slots on the same slide as production. See how to budget a partner program.

No deal sample. The fix: six rows you can open in the CRM during the meeting.

Reporting a record quarter without a trend. The fix: four quarters, same definition.

FAQ

How many slides should this be? One primary slide with four tiles, a one-line definition each, a four-quarter table, and an ask. Appendix for samples and for anyone who wants the logo list.

What if sourced is zero but influenced is real? Show it. Many technology partnerships help you win existing deals before they originate new ones. Zero sourced is a stage, or a motion choice, not a reason to relabel influenced.

Do we report partner-attributed retention? If you can define it and the sample is large enough not to be noise, it is a strong health number. If it is three accounts, keep it qualitative.

Should the partner manager present this or the CEO? Whoever owns the function. The CEO should be able to defend the definitions. If only the partner manager can, the company does not own the number yet.

How do we handle a director who wants more logos? Offer the appendix, then return to adoption. "We can sign ten. We can staff two. We report the two."

What about marketplace-sourced revenue? If you can tag it with the same discipline, it can sit in sourced. If you cannot, do not mix it in. A footnote that "marketplace is not yet tagged" is better than a blended number.

What if the CRM cannot produce the report live? Then the number is not board-ready. Fix the fields. Do not paste a spreadsheet you cannot reconcile. Report on the same board cadence as the rest of GTM. Do not create a special partnerships meeting.

Further reading

• Partnership metrics for the menu these tiles were picked from.
• Building a partnerships dashboard for the exec view that should match this slide.
• Partner program ROI for putting cost next to sourced and discounted influenced.
• OKR on Wikipedia, for keeping the board story on outcomes rather than activity.

The short version

Report technology partnerships to a board as four tiles you will not swap: sourced, influenced, adoption, and capacity. Define sourced and influenced in sentences a CFO can sample. Never add them. Show active use, not a catalog. Leave logos and meeting counts off the primary slide. Keep four quarters of the same definition. Bring a deal sample. End with an ask.

A slide that holds up is a slide you could present if every director opened the CRM. If you would not like that test this quarter, the problem is not the design of the deck. It is the tags.

If you want a board-ready read of what you can honestly claim, that is what a Partner Audit is for. We look at the motion, the tags, and the few numbers that will still be true after the follow-up question.