Your best donor and your biggest donor aren't the same person. Does your CRM know that?

The question that kicked this off came from a board member. "Who are our best supporters?" Simple enough. The development director pulled up a report sorted by lifetime giving, top to bottom, and read out the first ten names.

It was a good answer to a different question. That list showed the biggest donors. It said nothing about the best ones.

Because a hundred rows down was a woman who gave $50 a month without fail, opened every email, came to every event, and had quietly brought three friends into the organization. She wasn't in the top ten by dollars. She may well have been the most valuable supporter they had. And the CRM had no way to see her.

That gap, between what a donor gives and what a donor is actually worth to you, is what a donor lifecycle is supposed to close. Most of the ones I open in HubSpot don't. Here's why, and how I think about fixing it.

The default lifecycle was built to sell software, not steward donors

HubSpot's lifecycle stages are a sales model. Subscriber, lead, marketing qualified, sales qualified, opportunity, customer. A straight line with a destination, and the destination is the sale. Once someone becomes a customer, the model has basically done its job.

Donors don't behave that way, in two specific ways that matter.

First, the first gift isn't the finish line. It's the start of the relationship you actually care about. A model that treats "gave money" as the end state, the donor equivalent of "customer," stops paying attention at the exact moment stewardship should begin.

Second, donors move backward. They lapse. They come back. They go quiet for a year and reactivate with a bigger gift than they ever gave before. A linear model built to move in one direction can't describe a relationship that loops. So you end up with everyone parked in "customer," which tells you nothing, or you bolt on custom stages that still quietly assume forward motion.

The default isn't broken. It's just answering a question you're not asking.

Giving and engagement are two different axes

Here's the reframe that changes everything downstream: a donor's relationship with you has two dimensions, not one. How much they give. And how engaged they are. They are not the same thing, and a single lifecycle stage can only ever hold one of them.

Picture it as a grid.

Big gifts, high engagement. Your champions. They give and they show up. Easy to love, easy to steward.

Big gifts, low engagement. The quadrant that should scare you. A major donor who's gone quiet is not a safe donor. They're a lapse waiting to happen, and because the dollars still look fine in the report, nobody notices until the renewal doesn't come.

Small gifts, high engagement. Your most underrated people. The monthly-$50 woman lives here. Engagement is one of the best predictors you have of future giving, which means this quadrant is full of your future major donors and your loudest advocates. Rank by dollars and they're invisible.

Small gifts, low engagement. Genuinely cold, and fine to treat that way.

The point isn't the four boxes. It's that gift size alone puts your quiet major donor and your rising advocate in exactly the wrong place: one looks safer than they are, the other looks less valuable than they are. You can't fix that by sorting the same column a different way. You need the second axis in the system.

The same engagement signal can mean two opposite things

Once engagement is in the model, it does something giving data can't. It predicts. But you have to read it correctly, because the same signal points in opposite directions depending on where the donor already sits.

Rising engagement from someone who hasn't given yet is an opportunity. They're warming up. That's an acquisition signal, the moment to move them toward a first gift.

Falling engagement from an existing donor is a warning. They're drifting. That's an early lapse signal, the moment for a retention play, well before they've technically lapsed.

Same underlying behavior. Opposite meaning. Opposite response.

One concrete version: a spike in email opens from a brand-new subscriber and the same spike from a sustainer who's been fading are not the same event. The first is a prospect raising their hand. The second might be a lapsing donor taking one last look before they go. If your system reads both as "engagement went up, good," you'll cheerfully miss the person you were about to lose.

That's the whole game. Reading a signal against where the donor is, not on an absolute scale. Which brings up the thing nobody selling you an engagement score wants to say out loud.

There's no universal engagement score, and anyone who sells you one is wrong

I went looking for the standard nonprofit engagement model, the way there's a standard RFM model for giving. It doesn't really exist, and there's a good reason.

Engagement scoring only works cleanly when everyone agrees what engagement means. A food bank, an advocacy group, a symphony, and a hospital foundation don't reach their people through the same channels, and the signals don't weigh the same. For an advocacy org, taking an action might matter more than writing a check. For an arts org, attendance is close to everything. An engagement score lifted from someone else's playbook, or from a template, is just their priorities wearing your logo.

This is the part that sounds like bad news and is actually the most useful thing I can tell you. Your engagement model has to be calibrated to your organization. Your channels, your signals, and critically, each donor's own baseline. "Engaged" for a donor who's always been quiet looks nothing like "engaged" for one who's usually in your inbox every week. The score isn't a number you look up. It's a judgment you build.

How I build it in HubSpot, and where the real work actually is

So what does this become inside a portal? The architecture, at least, is nameable.

You redefine the lifecycle into stages that describe a donor relationship, with real entry and exit criteria, including the ability to move backward into lapsed and forward again into reactivated, so the loop is a first-class part of the model rather than an afterthought.

You bring giving data in as properties: recency, frequency, and value, the RFM backbone that's been proven for decades.

You build an engagement score from the signals that genuinely mean something for your organization, email, events, content, volunteering, advocacy, whatever your people actually do, weighted to your reality instead of a default.

And you use workflows to move donors between stages as those signals change, including the at-risk flag that fires when an existing donor's engagement drops against their own baseline.

That's the skeleton. And I'll be straight about where I'm stopping. The specific stages, the exact signals and how much each one counts, the thresholds that separate "quiet" from "at-risk," the baseline each donor is measured against, that's not a template. It's the part that decides whether the whole thing works or just generates noise. That's the calibration, it's the genuinely hard part, and it has to be built for you, because by definition it can't be borrowed.

The reason to do any of this isn't a tidier CRM. It's that the model finally lets your team act at the right moment: cultivate the advocate who's warming up, and catch the major donor who's going quiet before the giving stops, not after. Your best supporters stop being invisible. Your at-risk ones stop being a surprise.

Your biggest donor and your best donor were never the same person. The whole point is a system that can finally tell them apart.