For [CHURCH NAME]'s Elder Board
Designed to be presented BY the pastor TO the elder board — not by Stablish. ~10 minutes of presentation + ~10 minutes of Q&A. Each slide below = one slide; convert to Keynote / PowerPoint / Google Slides as needed.
Slide 1 · Title
A proposal for the Elder Board.
Presented by: [PASTOR NAME]
Date: [DATE]
Speaker notes
“I want to present a proposal for a stewardship platform we've been evaluating called Stablish. I'll give you the context, what it would mean for [CHURCH NAME], the financial picture, and the questions our team has already asked. Then I'd love your feedback and input.”
Slide 2 · The problem we're trying to solve
This isn't unique to us. It's the reality at almost every large church in America.
Speaker notes
“Our giving has been steady — but underneath that 'steady' is a hidden reality. About 70% of our attenders give irregularly. They love the church. They want to give faithfully. But the infrastructure for sustained giving — the kind that funds budget predictability and ministry growth — isn't there. We see this in our quarterly giving reports, in member surveys, and in personal conversations. It's the silent pattern.”
Slide 3 · Why this matters now
When recurring giving is healthy:
When recurring giving is fragile:
Speaker notes
“I'm not bringing this to you because we have a giving emergency. I'm bringing it because the math of predictable giving compounds — and the cost of waiting another 12–24 months while the irregular pattern continues is real. Every quarter we don't address this, we miss compound returns we could have had.”
Slide 4 · What Stablish is
Three core elements:
It's not a replacement for our giving platform. It's a discipleship layer that lives in members' phones year-round.
Speaker notes
“Stablish isn't another giving processor like Pushpay or Tithe.ly. It's a behavior layer — software that disciples stewardship in the eleven months a year our members aren't in a small group. It's the bridge between what our pastors preach and what our members actually do.”
Slide 5 · How it works (simply)
A member's experience:
A pastor's experience:
Speaker notes
“Members never see anyone else's data. Pastors only see aggregate giving health — never individual transactions. The whole thing is opt-in. We never see what someone bought; we just see whether their stewardship is healthy.”
Slide 6 · The financial proposal
| Annual cost for [CHURCH NAME] | |
|---|---|
| Stablish (every member, all features) | $[ATTENDANCE × $0.49 × 12] |
| Per attendee per year | $5.88 |
3-year total commitment: ~$[CALC × 3] (locked, no renewal increases)
For comparison:
Speaker notes
“Founding Partner pricing is half the future list price, and locked for life. That's not a marketing promise — it's contractual. Our finance team verified.”
Slide 7 · The expected return
For [CHURCH NAME] at our scale:
This is a target, not a guarantee. Actual results depend on rollout discipline, congregation engagement, and our existing giving culture. But the math should survive any pressure-test.
Speaker notes
“Stablish is honest that the 4x is an aim, not a contractual guarantee. They're a young company building toward proven case studies. Founding Partners get the founding economics partly because we're helping them build the proof points. The math works because the threshold is low — only [X] members need to shift behavior for the cost to clear.”
Slide 8 · Risk mitigation
| Concern | Mitigation |
|---|---|
| What if member adoption is low? | 90-day no-penalty pilot. We can walk away with zero financial commitment if it isn't working. |
| What if the company goes away? | Annual contract; we can leave any year. Member data is portable. We don't lose our giving infrastructure (we'd still have [CURRENT PLATFORM]). |
| What if members don't trust the data sharing? | Stablish uses Plaid (the same security model as Venmo, Robinhood, Mint). Members opt-in individually and control their own data. Pastors only see aggregate health, never individual transactions. |
| What if our existing platform doesn't integrate? | Stablish's Stewardship App layers on top of any platform. Native Planning Center integration today; willing to build for others. |
| What about IRS / 501(c)(3) compliance? | Stablish handles compliant giving rails. All giving receipts, year-end statements, and tax documentation are managed correctly. |
Speaker notes
“We pressure-tested the obvious risks. The pilot structure means our financial exposure for the first 90 days is essentially zero. After 90 days, if it's working, we continue. If it's not, we walk away. That's a very different risk profile than most platform commitments.”
Slide 9 · What we'd be saying yes to
Total financial commitment for 90-day pilot: ~$[ATTENDANCE × $0.49 × 3]
Speaker notes
“We're not asking the board to approve a multi-year commitment tonight. We're asking to approve a 90-day Founding Partner pilot. The financial exposure is minimal. The upside, if it works, is significant — both in budget predictability and in deeper stewardship discipleship across [CHURCH NAME].”
Slide 10 · Why now
Speaker notes
“I'm not bringing urgency for the sake of urgency. The Founding Partner program is genuinely time-bounded — once their first 10 churches are signed, the program closes. The price difference between joining now and joining in 2027 is meaningful at our scale.”
Slide 11 · Recommendation
Speaker notes
“My recommendation is that we approve the pilot. The financial exposure is bounded. The upside, if it works, is meaningful and compounding. And if our pilot data hits the targets, we have the option (not obligation) to convert to long-term Founding Partner status at the locked-in pricing.”
Slide 12 · Questions for the board
Common board questions to expect:
Closing thought to the board
“Whatever we decide tonight — the deeper question Stablish raises is one we should answer regardless: how is [CHURCH NAME] discipling stewardship between Sundays? If the answer is 'we're not, really,' that's a gap worth closing — with Stablish or without. This pilot is the lowest-risk way to start.”