Your Partner Program Signed 47 Partners and Sourced Three Deals This Year

It is Monday, 8:47 AM. Your CRO opens the partner tab in Salesforce with coffee number two. The board reads 47 signed partners since January. Three sourced deals sit in the pipe. One closed in July. The partner ledger grew by 22 logos this quarter and the sourced-pipeline number moved by zero.

The Partner Manager she hired in March at $164K base plus 30 percent variable has closed 22 new partner agreements and shipped 34 co-branded one-pagers. He has not sourced a single deal on the pipeline slide since the June board call. The board deck ships Thursday and the partner-sourced line reads "1 closed, $84K ACV" against a plan that said $2.4M by year end.

She writes into the exec channel "partner update by Wednesday, running the last two co-sell reviews now." The Wednesday update lands with the same 47 logos, the same three deals, and a note that the June cohort of eight partners has not logged a deal-registration form. The founders in this seat keep opening a Partner Manager req and wondering why the sourced-pipeline number stays flat. Partner program is not a headcount. Partner program is a seven-stage queue that starts with a signed MSA and ends with a co-sold deal on the CRO's forecast, and nobody on the org chart owns it end to end.

The 47 partners, by the numbers

Sort the partner tab. 14 partners signed the MSA in January, 12 in February, 8 in March, and the remaining 13 across the last five months. Of the 47, six completed the sales enablement track. Four have live deal-registration credentials in the portal. Three logged a deal in the last 90 days. One partner sourced the $84K closed deal in July, and the AE filed the paperwork by hand because the deal-reg workflow rejected the form twice.

Of the 44 partners with zero sourced pipeline, 22 have not logged into the portal since the week they signed. 14 logged in once to download the one-pager and never returned. Eight opened three sessions and stopped after the enablement quiz failed to load in their region. The onboarding funnel leaks 94 percent of signed partners between countersignature and first deal-registration attempt, and the leak has the same shape every month.

The Partner Manager who signs the MSA does not own the enablement track. The RevOps analyst who owns the portal does not own the enablement content. The PMM who wrote the one-pager does not own the deal-reg workflow. The AE who fields the sourced lead does not own the partner commission split. Four owners across four teams, one queue, zero handoffs on cadence. The forecast slide ships the same "$84K sourced" number every quarter, and the 214-day AE ramp gets the budget the partner queue never earned.

Stage one: the activation runway nobody walks the partner through

The Series B version of this function ships a written 30-day activation runway that lands three artifacts on the partner in the first 72 hours. A named point of contact with a Loom intro and a calendar link. A five-page enablement pack with the ICP, the top three plays, and the objection responses. A working deal-registration credential tested against the partner's own login before the welcome email leaves the door. 41 of 47 partners complete the runway inside 30 days, and the sourced-lead flow turns on in month two.

The version most Series B teams run: the Partner Manager signs the MSA on Tuesday, sends a generic welcome email Thursday, and moves to the next signature. The partner opens the portal Friday, hits a broken enablement quiz, emails the Partner Manager, gets a reply on the following Wednesday with a Zoom link three weeks out. The activation window closes on day 14 with the partner still one Zoom away from a working credential, and the partner's own AEs never hear the pitch.

The stage-one function reads every countersigned MSA landing in the CLM, pulls the partner's ICP and vertical from the intake form, drafts the personalized enablement pack against the two most-relevant plays, provisions the deal-reg credentials against the partner's SSO domain, tests the login flow, and ships the welcome bundle inside 90 minutes of signature. The Partner Manager reviews the pack draft and hits send. 47 partners walk the same runway on the same cadence, and the six-partner activation cohort becomes a 41-partner cohort against the same signed book.

Stage two: the co-sell motion nobody runs on cadence

The four partners with active deal-reg credentials sit in a Slack channel with the Partner Manager and three AEs. Partners drop deal notes into the channel on their own cadence. The Partner Manager reads the notes Tuesday and Thursday. The AEs pick up the notes when the Partner Manager tags them. The partner who logged a $340K opportunity on the second Monday of June waited six days for the first AE reply and the deal never made it to a joint call.

The Series B version runs a weekly co-sell cadence with a shared pipeline view that both sides open. The partner sees the AE-owned deals where their product is a fit. The AE sees the partner-sourced deals where a joint call moves the buyer forward. Both sides open the same view Monday, work the same seven deals, and close the loop on the same Slack channel by Friday. The four active partners generate 14 sourced opportunities a quarter instead of three, and the AE-partner joint-call rate runs 60 percent of touched opportunities instead of 8 percent.

The stage-two function reads every deal note the partner drops into the channel, matches the account against the CRM to check for existing coverage and last-touch history, builds the joint-call brief with the partner's product fit and the two most-similar closed deals from the AE's book, drafts the outreach in the AE's voice with the partner's name in the intro, and drops the brief into the AE's DM within the hour. The AE opens 14 briefs a week and picks up the top five. The joint-call motion runs on cadence and the sourced pipeline compounds against the same signed partner book.

Stage three: the deal-registration and attribution loop

The one closed sourced deal in July got attributed to the partner because the AE filed the paperwork by hand. The three deals in the current pipe have partner-source tags on two of them and a "no partner" tag on the third that the partner sourced. The partner will read the Q3 commission statement in October, see a zero on the deal they sourced in May, and stop returning the Partner Manager's calls. The 47-partner book becomes a 34-partner book by December and the signed-logo line on the board slide runs the other direction.

The stage-three function reads every closed-won opportunity, cross-references the account against the partner-registered lead list from the trailing 12 months, joins against the Gong call transcripts to catch the partner mention the AE forgot to tag, drafts the attribution decision with the source evidence, and routes the split to the CFO for the commission run. The nine-day sales comp cycle closes on partner splits without the manual reconciliation, and the partner sees a payout on the deal they sourced instead of a zero.

The math against the next Partner Manager hire

Run two paths against the second Partner Manager req sitting in the drafts folder at $164K base plus 30 percent variable. Path A closes the req in October, ramps the hire through Q1, and adds a second Partner Manager to a program that produces one closed sourced deal a quarter. Loaded year-one cost lands $260K to $310K against a partner book that grows to 84 logos and sources six deals instead of three. Same shape, twice the signature count, same sourced-pipeline number on the board slide.

Path B ships a three-sprint fractional AI partner function at $84K to $132K in build across the first 60 days and $6K to $10K a month to run. Sprint one lands the activation runway. Sprint two lands the co-sell brief motion. Sprint three lands the attribution loop against the commission run. The 47 signed partners walk the runway inside 60 days, 22 of them log a deal in the next 90, and the sourced-pipeline number moves from $84K closed to $1.2M to $2.1M in the pipe by the January board call. Same partner book, different sourced-line story. The 14-day sprints that ship this function cost less than the fully loaded search retainer for the second Partner Manager.

The four numbers a CRO runs before the next Partner Manager req

The founders reading this posted a second Partner Manager req in August on the strength of the "grow the signed book" narrative. Before the offer letter goes out, run four numbers against the partner function, not the headcount. Score the queue, not the hire.

Signed to activated ratio. Divide the count of partners who completed the enablement track and hold a live deal-reg credential by the count of partners who signed the MSA in the trailing 90 days. A healthy function runs 70 to 85 percent. A stuck function runs 8 to 14 percent, and 40 of every 47 signatures land in a folder nobody reopens.

Partner-sourced pipeline per active partner. Divide the total partner-sourced pipeline in the trailing 90 days by the count of partners with at least one logged deal in the same window. A healthy function runs $180K to $340K per active partner per quarter. A stuck function runs $20K to $40K, and the CRO's forecast slide never crosses the plan number.

Deal-reg to AE first-touch. Measure the median business hours between a partner logging a deal in the portal and the AE booking the first joint call. A healthy function runs under 24 hours. A stuck function runs 5 to 9 business days, and the partner stops logging deals by the second miss.

Attribution accuracy. Divide the count of closed-won deals with the correct partner-source tag by the count of closed-won deals where a partner touched the opportunity in Gong or email in the trailing 90 days. A healthy function runs 90 percent plus. A stuck function runs 40 to 60 percent, and the Q3 commission statement kills the top five partners on the roster. Any two numbers in the stuck zone means the queue is the problem, not the headcount, and you can scope the partner function in a 30-minute call this week.