Design-partner program · Core donor operations in active build

See the roadmap
Skip to content
Beneora

Operating model

Operating a recurring giving programme with two staff

Owners, cadences and escalation rules for a monthly programme that does not depend on heroics.

9 min readBeneora product team

Takeaway

Assign three recurring responsibilities — recovery, stewardship and reporting — with a named owner and a weekly cadence each.

Small teams do not fail at recurring giving because they lack strategy. They fail because nobody owns the boring weekly work when a campaign is running.

Three standing responsibilities

  • Recovery: work the decline queue weekly. Bounded retries, then a human message.
  • Stewardship: acknowledge new recurring donors within 48 hours and touch the cohort quarterly.
  • Reporting: review retention, recovery and net new monthly revenue on a fixed monthly date.

Escalation rules worth writing down

  • Two consecutive failures on a gift above your major-gift threshold becomes a phone call, not an email.
  • A cancellation with a stated reason goes to the programme owner the same week.
  • A decline rate above your normal range is a systems question before it is a donor question.

Keep reading

Related to this

GuideReconciliation

The nonprofit month-end close playbook

A sequenced close for organizations taking online, offline and recurring gifts across multiple funds.

12 min
GuideDonor data

Migrating donor data without inheriting its errors

A dry-run-first approach to imports, duplicates, households and recognition preferences.

10 min
GuideRecurring & pledges

The pledge lifecycle, from commitment to write-off

Seven states, the decision at each one, and who owns it — including the two states most teams skip.

9 min

Design-partner program

We write these from partner sessions

If this matches your week, a working session is the fastest way to make the product fit it. Partners see the honest status of every module and are never charged for a prototype.