How many prospects is too many?

Your Portfolio Is Shaping How Your Team Thinks

Issue #38
4-minute read

Hi Reader,

Last week, I asked why board connections stall.

A — They don't know the prospect well enough and won't admit it.

B — They know them, but the ask feels too risky.

Here's what those of you who replied said: mostly A.

Board connections stall for the same reason portfolios stall. Wrong design. Not wrong people.

Let's start with a question.

What is your portfolio actually built to produce?

Revenue - of course.

But, is it?

Most portfolios are built to stay busy. Calls made. Visits completed. Proposals submitted. The dashboard fills up. The pipeline looks full.

Then the revenue lags.

Usually, it’s not a people issue. It’s the architecture behind the system.

What Producer-Thinking Costs You

Our frontline fundraiser’s portfolio crept up to 200 prospects.

You can predict what happened.

It becomes impossible to manage. Math instead of relationships.

Optimized for coverage.
Busy-ness.
Surface touches.

That behavior is rational. The system rewards it.

If success is defined as touches and meetings, you will get them.

You will not get meaningful gifts.

The Decision That Changed the Thinking

200 prospects in a portfolio.

On paper, it looked strong. High activity. Plenty of movement logged in the CRM.

In reality, all that time allowed was polite conversations.

We cut it to 50. A 75% reduction.

The other 150 didn’t disappear. They moved into a structured communications funnel. More consistent touchpoints than a single officer could manage. Clear signals for when to re-enter personal management.

The portfolio cut wasn’t a retreat. It was a trade.

Depth for the 50. Velocity for the 150.

It’s early. We don’t have revenue data yet. But the thinking shifted instantly. She said she finally feels like she has a clear vision for her work.

Clarity changes behavior faster than incentives ever will.

With 200 prospects, her job was to stay in contact. With 50, the work is to know them deeply, advance them deliberately, and close in a way that helps them live their dream.

Large portfolios reward producer-thinking.
Small portfolios demand enterprise-thinking.

That one number changed how success was defined.

We're nearing the completion of the Chief Fundraiser Operating System. Here's System Ten.

The Portfolio Performance System

We're nearing the end of the Chief Fundraiser Operating System series. Here's System Ten.

To create revenue-generating portfolios, four design choices must work together.

1. Portfolio rules answer how many prospects per officer. The real answer is: fewer than you think. Ruthless qualification is the discipline most teams skip.

2. Pipeline velocity standards answer how long is too long in each stage. If someone has been in cultivation for 18 months with no movement, that's not cultivation. That's drift. Define what forward motion looks like — then hold to it.

3. Accountability rituals are the 15-minute weekly conversations that look ahead rather than back. Reporting asks what happened. Rituals ask what's next. That distinction builds revenue muscle.

4. Incentive structures answer the question nobody asks out loud: what gets celebrated here? Activity or movement? Teams do what gets recognized.

Four elements. Most operations have one.

The Shift You're Building Toward

Producer-thinking asks:
How many calls do I need to make today?

Enterprise-thinking asks:
What does this portfolio need to produce this year, and what must happen this week to make that true?

Both are legitimate. Only one scales.

Put It Into Practice

Pick one portfolio and answer four questions:

1. How many prospects are in it?
2. What is your velocity standard at each stage?
3. When was the last forward-looking portfolio conversation?
4. What gets recognized — activity or movement?

The gaps in those answers are your design work.

On My Radar

I'm watching the push to create autonomous AI fundraisers — agents designed to manage donor portfolios, communicate with donors, and move gifts forward with minimal staff involvement. Working 24/7 across email, text, and video. The technology is moving fast.

My current thinking is that the question isn't whether to deploy them. It's where human judgment, compassion, and empathy have to enter the room.

Coming Next Week

Operating systems work in stable conditions. Very few hold under pressure.

Next Sunday: System Eleven — The Risk & Resilience Engine. How to build early-warning signals and scenario planning into your operation before the disruption finds you.

Your Turn

Quick question about your top gift officer.

A — Large portfolio. 100+ prospects.

B — Focused portfolio. Fewer than 75.

Hit reply with A or B. Next week I'll share the breakdown — and what the number predicts about where your pipeline pressure is coming from.

Until next week,
Christine

PS - Two issues left in the Chief Fundraiser Operating System series. If you're just finding this, System Zero is where it starts — and where everything else makes sense.

Chief Fundraiser Weekly goes out every Sunday for chief fundraisers building from $10M to $25M. If someone forwarded this to you, subscribe here.


I’m Christine Bork, Chief Development Officer at the American Academy of Pediatrics. I write Chief Fundraiser Weekly to share what I’m learning as I lead a growing team and try to do the work in a way that’s sustainable and thoughtful.

Written by a practicing Chief Fundraiser

Most fundraising content is written for people who haven't done this job. This is different. I'm Christine Bork, Chief Development Officer at American Academy of Pediatrics, leading a $27M operation. Chief Fundraiser Weekly is a short Sunday brief for experienced fundraisers who want peer-level thinking, not vendor pitches. One clear idea. Real systems. Nothing theoretical.