The next in an ongoing series exploring why the strategies that used to work don’t work the same way anymore, and what that means for every decision you’re making right now.
You have two households on your books this year, and they’ve given you the same amount of money.
One has been coming for eleven years. They renew on time, they sit in the same section, they’ve never once brought a guest. The other started last season. They brought four different people to four different shows. They replied to an email asking what almost kept them from renewing. They stayed after a talkback to keep talking.
Every system in your building sees these two households as the same person. Same spend. Same tier. Same line in the same report.
You already know they’re not the same relationship. What you don’t have is a way to tell them apart, at scale, before one of them quietly stops showing up.
Depth Is What Predicts, Spend Is What Records
Spend tells you what someone gave you. It doesn’t tell you how invested they are in you, how likely they are to stay, or how far they’d go to bring someone else in with them.
That gap is why organizations keep discovering people are gone months after they actually left. The dollars looked fine right up until the renewal notice went unanswered. Spend is a record of a transaction that already happened. It’s backward-looking by definition. Depth is what was moving underneath the transaction the whole time, and it’s the thing your dashboards were never built to see.
This isn’t a small distinction. It’s the difference between a system that tells you what happened and a system that could have told you what was coming.
What Depth Actually Leaves Behind
Depth isn’t a feeling you have to guess at. It leaves a trail, and most of that trail is already sitting in data you collect and then throw away.
How often someone shows up. Not how much they spend when they do. A patron who attends four times a year is a different relationship than one who attends once, even if the once is a bigger check.
How many different program types someone engages with. A subscriber who only ever buys the same series is a different relationship than one who also shows up for the family concert, the community night, the one-off recital. Breadth is a sign someone is exploring the whole relationship, not just repeating a habit.
How recently the relationship moved, not how recently the money did. A gift in March and a reply to an email in July are both signs of life. Most systems only have a field for the gift.
Whether the person has ever given something back. A reply. A completed survey. A comment left after a performance. Small, individually. But it’s the difference between someone who receives your programming and someone who’s in an actual conversation with it.
Whether they’ve ever brought someone with them. Bringing a guest is one of the clearest signals of investment a person can hand you, and most CRMs don’t have anywhere to put it.
None of this requires new instrumentation. It requires a place to record what’s already happening in front of you.
Anchoring the Indicators to the Five Needs
Here’s where it would be easy to go sideways. It would be tempting to build “relationship health” as its own framework and set it down next to everything this series has already established. Don’t. That leaves you with two frameworks competing for the same attention, and neither one wins.
Instead, every indicator here gets named as evidence of a specific need being met, or going unmet. That’s the same needs framework earlier articles in this series have already laid out. On the earned side: Connection, Participation, Understanding, Emotion, Escape. On the contributed side: Connection, Legacy, Understanding, Transformation, Vision.
Attendance frequency might be evidence of Escape. Breadth of participation might be evidence of Understanding or Participation. Bringing a guest is almost always evidence of Connection. None of these indicators are freestanding metrics. Each one is a needs signal wearing a number.
This isn’t a new layer sitting on top of the Audience First philosophy. It’s the Audience First philosophy finally getting a way to keep score.
A Set Small Enough to Actually Start
This isn’t a research program. It’s a starter set, small enough that a marketing or development director could create a draft before the next round of performances occurs.
A starting relationship health set
- Attendance frequency: how many times the patron engaged in the trailing 12 months, not how much they spent
- Program breadth: number of distinct program types or series the patron engaged with
- Days since last patron-initiated contact: a reply, a completed survey, an RSVP, not days since last purchase or an email opened
- Guest or referral on file: whether the patron has ever brought someone different than their typical partner
- Two-way response ever logged: whether the patron has ever responded to outreach, at all
Five fields. None of them require new software. All of them require a place to record what’s already happening.
A partial version running this season is worth more than a complete version still stuck in committee next year. Start with what you can capture consistently, and add fields once the habit holds.
None of this is new information. Every one of these signals is already sitting in a system somewhere, your ticketing platform, your donor database, your inbox. They were just never asked to answer this particular question.
You don’t need new data to see relationship health. You need to start asking your existing data a different question.
Next up in the series: These indicators assume your systems can answer questions about people. Most can’t yet.
Standing up relationship health indicators takes two things: systems that capture what you learn, and people who share it. The free Audience First Organizational Alignment Assessment looks at both, along with leadership buy-in and cultural readiness, in about 10 minutes. Your personalized report, with your scores and priority areas, arrives in your inbox as soon as you finish.
Leave a Reply