Fundraise Up

Partner Enablement · Agency partners

First Opportunity

Anton Silaev Getting a newly signed nonprofit agency to its first partner-sourced opportunity, by reaching more of the people inside it who influence what the client buys. One partner type, one motion. The advisor count is my estimate; the book size is yours.

40
Client-facing advisors inside one agency1
50–80
Partners in one manager's book2
30 days
To the first module live and an advisor able to enrol
1My estimate: one agency you named runs 350–400 people 2Your number, from our first conversation
Anton Silaev · Partner Enablement Manager ←→ to move through the deck 01 / 09
Fundraise Up

The premise

Agencies don't have sellers. They have advisors.

Most of these agencies have little to no sales organisation1. The people who move a nonprofit's decision are the account managers and strategists who speak to that client every week and carry no bag.

Signed
Agency principal: the agreement
Sellers
no sales organisation to hand a quota to
Advisors ×40
Each dot is one client-facing advisor. The whole job of the program is to turn dots green.
In the building Reached and able to source

Who actually decides

Not always the founder who signed the agreement. The advisor sitting with the client on a Tuesday is a better bet.

Why they would bother

Not the referral fee. When a client moves platform, the migration and optimisation work belongs to the agency.2

So what changes

Enable people, not logos. One advisor with a few client accounts is the smallest unit that produces anything.

It is also the likeliest reason strong executive alignment at an agency does not turn into pipeline on its own.
1From our prior conversation, not my characterisation 2My inference: the first thing I would test with two agencies, because the whole incentive rests on it
Part 1 · Pitch to leadership 02 / 09
Fundraise Up

The program

Three ways in, because advisors will not all take the same one.

AsyncReaches everyone

The core, always on

  • Positioning module: 20 minutes, recorded, with a workbook
  • The trigger card: three signals, three questions, the introduction drafted
  • Discovery guide: what good sounds like, and the two objections
  • Referral mechanics: intro template, registration path, what happens next and by when
Live and 1:1Reaches the willing

Practice, not presentation

  • One 60-minute working session per cohort, anonymised client scenarios, said out loud
  • Account mapping 1:1, and never by asking for their client list: Crossbeam already shows the overlap1
  • A standing fifteen minutes with advisors who have something moving
  • Weekly office hours, open to advisors and partner managers, for questions or personalised enablement
AutomatedReaches the rest

The long tail, without a calendar

  • Overlap and enrichment surface advisors nobody has reached
  • Enrolment runs itself, configured in the stack we already pay for
  • A personalised brief per advisor, built on their own client base
  • A twice-monthly sector read that keeps us present until a signal fires
Certification drafted A ten-minute scenario check that gates benefits, never permission. Certification unlocks what an agency actually wants: inbound implementation work routed to them2, a directory listing, priority support for their clients, co-marketing.
Two instruments keep it targeted rather than broadcast: a fit diagnostic that asks how an advisor is paid before it recommends anything, and an account map scored on two axes only: client fit and relationship strength drafted. Most of this is assembly, not authorship3, and three of these are written already.
1Crossbeam is in the stack you gave me 2Assumes you have inbound nonprofits needing an implementer: if not, this benefit comes out 3Assumes usable positioning material exists in Partner Fleet, Notion or product marketing
Part 1 · Pitch to leadership 03 / 09
Fundraise Up

The design

The partner manager keeps the relationship, and moves deals forward. The program carries the rest.

Stays with the partner manager

  • The agency relationship
  • Meeting more advisors inside it over time
  • Short pipeline conversations with the ones who are active
  • Supporting Sales team with live deals

Runs as a program

  • Enrolment and certification
  • Positioning, discovery content, and an exceptional partner experience
  • Matching each advisor to their best client accounts
  • Systems that keep advisors engaged, and surface the influencers we have not reached yet
A partner manager can build real relationships with an agency and with a lot of people inside it. What they cannot also do is onboard, train and chase every advisor across a book of agencies. The program takes that part off their plate, not them out of the relationship.
Part 1 · Pitch to leadership 04 / 09
Fundraise Up

Measurement

Judged on advisors activated, not courses completed.

Accountable · speed

Time to first accepted opportunity

Measured from enrolment. The committed target gets set from your baseline.

Accountable · breadth

Active advisors per agency

People with client accounts in play, not logos signed or seats filled.

Accountable · depth

Opportunities per active advisor

Judged on production, not reach.

Reported · not accountable

Completion and satisfaction

Worth reporting, but an agency can finish everything and source nothing. Same test for my certification: if certified advisors do not out-produce the rest, I would kill it.

Days to first accepted opportunityNo holdout
Signed in the 12 months before launch median TBD
Enrolled cohort: my stated goal
60 days
0 30 60 90
Attribution

Which person inside the agency sourced the deal: a contact-level field in Salesforce1.

Comparison

No holdout: every new agency gets the program. The control is historical: agencies signed in the prior twelve months, same clock, same definition2.

The caveat

If the enrolled median beats theirs, something moved. It is not a randomised test, and I would say so.

My own goal, said out loud: an advisor-sourced opportunity accepted within 60 days of enrolment. That is the clock for a partner starting from zero. Inside agencies we have already signed it should be faster: the trust is there and nobody has asked.
1Assumes attribution stops at the agency today: I asked this in round one and it is still open 2Assumes enough agencies signed in that window to make a median mean anything
Part 1 · Pitch to leadership 05 / 09
Fundraise Up

Getting there

Ship in 30. Run it in 60. Prove it in 90.

Day 0 Day 30 Day 60 Day 90
Days 1 – 30

Baseline and first shipment, in parallel

  • Interview sprint in weeks one and two: partner managers, AEs, and three to five agency advisors, to a fixed question set so the answers are comparable
  • Contact-level attribution agreed with RevOps in writing, and the trailing twelve months pulled as the comparison cohort
  • Shipped: trigger card, positioning module, enrolment live in the stack we already own1

OutcomeA baseline that exists, and an advisor who can enrol.

Days 31 – 60

The motion actually runs

  • Certification live, wired to benefits rather than permission
  • Working session delivered to the first cohort; mapping run 1:1 off Crossbeam overlap with whoever is willing
  • Fit diagnostic and account map in use
  • Registration tested end to end on a real registration, not a sandbox

OutcomeThe first advisor-sourced meeting. That is the 60-day goal.

Days 61 – 90

Prove it, then automate it out of my hands

  • Find what the LMS and PRM already report before building anything, then build only the missing join, progress through to registered and accepted
  • QBR readout, including what the day-30 model got wrong
  • The long-tail variant ships: surfacing and enrolment running with no partner manager's calendar in the loop, pointed at the next ten agencies

OutcomeA motion that runs without me in the room.

Three dependencies, and how I would carry them: the attribution field goes to RevOps as a spec and a working prototype, not a ticket · the rules for what an accepted referral looks like get settled with sales leadership directly, in week two, rather than escalated · and I would need two partner managers' judgement, plus introductions into a couple of agencies.
1Assumes enrolment and nudges are configurable in Partner Fleet or PartnerStack rather than a build
Part 1 · Pitch to leadership 06 / 09
Fundraise Up

Part 2 · switching audiences

You are the advisors now.

The first piece I would build is the trigger card: one page an agency account manager keeps open during a client call. What to listen for, what to ask, and the one sentence that hands it to us. The smallest thing that changes what an advisor does on Monday, delivered the way I would deliver it to a room of them.

What's on the cardOpen the trigger card

01Three signalsWhat a client says 02Three questionsWhat you ask 03One sentenceThree endings, one per question 04After yesWho does what, and what is yours
Part 2 · Deliver a slice to partners Switch to the trigger card 07 / 09
Fundraise Up

Part 3 · AI retrospective

I have already built this machine once. Here is what it got wrong.

Scout is my own outreach engine. It finds local businesses, reads their current outdated website, builds a personalised website for each one, and writes the email campaign that leads to a multi-step value-ladder marketing funnel. That is the same four steps the day-90 long-tail plan needs: find the advisors nobody has reached, learn something real about each one, write to them personally, create an interactive "lead magnet," and keep going. 173 real prospects have been through it so far. Two things went wrong:

Scout · what went wrong → what I changed Google Places · Grok 4.3 · Cloudflare · Smartlead Live · 173 prospects
✕

It made things up

It wrote “licensed and insured” onto a plumber's page. That was nowhere on their website. It put an Ontario business in New York, because the name resembled a New York company's. I had already told it not to do either.

✓

So I stopped asking it nicely

Now anything that sounds like a promise has to appear word for word in what I gave it (in code), or the sentence is dropped. An instruction is not a control. I only found it by reading five real ones end to end.

✕

I trusted its own quality check

A second AI reviewed the finished pages and held back 11 of 84 good leads, and it misread phone numbers off the screen. Asked three times about the same page, it gave three different answers.

✓

So I let it advise, not decide

It can flag something for a person to look at. It cannot stop a send. All eleven went out. And one of them had a real problem the AI never mentioned.

Why this is really the day-90 slide. The long-tail motion is this same machine pointed at advisors instead of businesses, and personalised at volume is both the whole point and exactly where it goes wrong. So before it touches a live agency: anything that reads like a promise has to be checkable against something we actually know, a person signs off on the first send to every new agency, and when the machine is unsure it says so loudly instead of guessing. And the honest part: AI was never my bottleneck. Getting the email delivered was. See the live dashboard
Part 3 · AI retrospective 08 / 09
Fundraise Up

In one line

Reach more of the right people
inside every agency we have already signed.

The partner manager keeps the relationship. The program carries the repeatable work. And I would be measured on how many advisors are actually producing, not on how many finished the course.

Have questions?

Anton Silaev · Partner Enablement Manager Q&A 09 / 09
Fundraise Up

Appendix · not presented

The rest of what is
already written.

Three of the program's instruments, built rather than described. They are here in case you want to see one, not to be walked through, so rather than slides about them, each one opens the artifact itself.

Core module · delivered live in Part 2

The Trigger Card

Three signals, three questions, and the one sentence that hands it to us.

Open Working session · 1:1, once a quarter

The Advisor Account Map

Two axes only: client fit and relationship strength. Four names out.

Open Readiness check · about ten minutes

Certified Fundraise Up Advisor

Ten scenarios. Gates benefits, never permission.

Open
Appendix · Artifacts Reference only A