Right person. Right amount. Right time. Right purpose. Miss one.


The Ask You Should Not Make (Yet)

Issue #47
3-minute read

Hi Reader,

Jerold Panas spent decades studying why major gifts succeed and why they don't. His framework was deceptively simple:

Ask the right person, for the right amount, at the right time, for the right purpose.

People often compress it to three variables. Panas was intentional about the fourth. Purpose is what separates technique from judgment.

The real signal isn't just getting all four variables right. It's knowing when one of them isn't. And choosing not to ask.

What "The Work Isn't Done" Looks Like

Budget pressure has a way of making relationships feel more ready than they are.

The ask is premature when:

The donor hasn't initiated contact recently.

In a relationship that's building toward something, the donor starts reaching out — forwarding articles, asking questions, checking in. Passive responsiveness is not the same thing.

The purpose conversation hasn't happened.

You know what they care about broadly. But you haven't talked directly about what a gift from them would need to accomplish for it to feel right to them. That conversation is not the solicitation. It comes before it.

You're matching them to a program, not to a purpose.

If the honest answer to "why this fund" is "because it fits our timeline" or "because it's what we have available," you're not ready. The donor will feel the mismatch even if they can't name it.

When all three are true — the donor is initiating, the purpose conversation has happened, and the fit is genuine — timing almost takes care of itself.

Managing Internal Pressure Without Blowing Up the Relationship

Here's the harder problem. You know the ask is premature. Your VP or CEO disagrees — or doesn't know, because pipeline pressure flattens the nuance out of portfolio reviews.

The move that works: reframe from readiness to risk.

Not "I don't think they're ready." That's a judgment call your leadership can override.

Instead: "If we ask now and they say yes to something smaller than they're capable of, we've closed that conversation. Here's what I think the relationship can become if we take another 60 days."

That's not resistance. That's stewardship. It gives leadership something to weigh rather than something to override.

If the pressure is coming from a board deadline or a campaign close, name that too.

You won't win every one of these conversations. But you'll win more when you're arguing from relationship data, not instinct.

The Decision Test

Here's the test to run before every solicitation. Three questions. If any answer is soft, consider whether you're ready.

What has the donor done — not said — in the last 90 days that signals they're moving toward a decision?

Have we had a direct conversation about what this gift would need to accomplish for them, not for us?

If they say yes to the number we're planning to ask for, will we feel like we got it right, or like we left something on the table?

We may still ask when the timeline isn't ours to control. But we go in knowing what we're trading.

If you know a Chief Fundraiser being pushed to ask before the relationship is ready, forward this. It might be the right week for them to read it. If you’re reading a forwarded copy, you can subscribe here.

The Restraint is the Craft

Panas's framework isn't just a preparation checklist. It's a diagnostic you run in real time, on the way to the ask.

The exceptional gift officers I've worked with aren't the ones who ask fearlessly. They're the ones who know when not to.

That requires something our field doesn't always reward: patience over pipeline pressure, relationship over revenue cycle, long game over quarterly close.

The ask you don't make protects something more valuable than this fiscal year.

On My Radar

I was recently introduced to Practivated, and I'm impressed. It lets your major gift officers practice donor conversations with AI simulations that push back, go quiet, and say no, so the first time they hear a hard question isn't in the actual meeting.

Your Turn

Before Friday, pull up one active solicitation on your calendar. Run the three questions from the Decision Test. Write down which answer is soft. That’s what to address before you go in.

Coming Next Week

You’ve done the work. The strategy is right. Your org isn’t ready to run it.

Next Sunday: what to do when the gap between your thinking and your organization’s capacity is the problem.

Cheers,
Christine

PS — If you’re managing early-ask pressure right now from leadership, a board deadline, or a campaign close, reply and share what you’re navigating. I respond to every message.

PPS — If this hits for you, Issue 38 is worth circling back to. It's about portfolio design and why the conditions that produce premature asks are usually built into the system long before the solicitation meeting.


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.

Chief Fundraiser Weekly

You know how to fundraise. What you're dealing with now — the pressure, the team, the strategic decisions — that's not in any newsletter. So I started writing it down. Sundays. Free.

Read more from Chief Fundraiser Weekly

The Donor You Should Not Chase Issue #463-minute read We have a prospect who can't decide. Not because they aren't interested. Not because the mission doesn't resonate. But every time we come back with a program idea, it's not quite right. Too broad. Too specific. Not the right population. Not the right geography. We've generated four or five compelling options. Each one grounded in real need. Each one a genuine fit for what they told us mattered to them. Still not quite right. At some point,...

A KPI System People Can Stand Inside Issue #453-minute read Hi Reader, My management team pushed back. Not hard. Not angrily. But clearly. I'd brought them the final piece of a two-year EOS journey: setting our department's One Number. The structure works in three layers: company, department, and individual. The ask was to pick one number that defines development's contribution to the organization. They couldn't do it. Not because they didn't understand. Because one number couldn't hold a...

When the Problem Isn’t Performance Issue #443-minute read Hi Reader, Last week, I wrote about developing your team one level deep — and promised to come back to what happens when a direct report isn’t doing it. Here’s what I’ve learned: the conversation you think you need to have is rarely the one that moves things. Two patterns show up most often when a direct report isn’t developing their team. The first: a fundraising generalist I promoted to lead a team of specialists. Smart. Committed....