# Message test — https://www.planningcenter.com/

After reading your page, 13 of 15 personas could name a reason to pick you over a similar option — and differentiation was the weakest of the four.

- **Page tested:** https://www.planningcenter.com/
- **Audience tested against:** Admins and staff members of churches of all size. Mainly christian faith-based churches of all denominations and theology.
- **Personas:** 15 simulated
- **Report:** https://grader.wynter.com/r/planning-center-church-management-software-D_AT6cU

> These answers are generated by AI, scored on Wynter's B2B Message
> Layers framework using behaviorally-diverse simulated personas. The
> methodology is real and the critique is directional. What a simulated
> persona cannot have is a live budget, a renewal coming up, or a boss
> asking about this quarter.

---

## 01 · The scores

Every persona answered all four questions. These are four independent
proportions of the same panel, not stages of a funnel.

| Layer | Question | Cleared the bar | Strength | Of those who passed |
| --- | --- | --- | --- | --- |
| 1. Clarity | Do they understand what you do? | 15/15 | 96% | 12 without hesitation, 3 with reservations |
| 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 96% | 12 without hesitation, 3 with reservations |
| 3. Value | Do they actually want it? | 14/15 | 74% | all with reservations |
| 4. Differentiation | Is there a reason to pick you over the alternatives? | 13/15 | 70% | all with reservations |

**Brand alignment** (a side metric, not one of the four layers) — 15/15, 78% strength (all with reservations). Does the page read like the company you actually are?

**Fix first: Differentiation.** Earliest failing layer, walking the sequence in order — not simply the lowest score.

---

## 02 · What to change, layer by layer

Ordered worst-first. Specific edits, not a restatement of the score.

### Differentiation

**Publish a support response time next to the support quote.**

"Planning Center support takes minutes" is one customer's anecdote; any competitor with a published response target beats it. State the actual median first-response time or hours of coverage.

*effort low · impact high · tested against Proof next to the claim*

**Move the fee numbers into the hero as a named figure.**

"Low giving rates" sits as a bare badge while the fee structure is the only difference readers could name. Print the actual card and ACH percentages high on the page where the comparison happens.

*effort low · impact high · tested against Specifics beat superlatives*

**Explain what "No outside investors" means for buyers.**

The badge reads as trivia, not a reason to choose. Tie it to something the buyer feels — pricing that has not risen after an acquisition, no forced migrations.

*effort low · impact medium · tested against Give a reason to choose you*

### Value

**Replace vague savings quotes with the actual fee numbers.**

"We have saved a significant amount of money" gives no baseline, church size or starting cost, so no one can do the math. The published processing fees were the claim readers believed — put those percentages next to the savings testimonials.

*effort medium · impact high · tested against Specifics beat superlatives*

**Add church size and before/after numbers to testimonials.**

Greg Dietrich's "we save so much time" and Stacey Leighty's ACH savings have no starting point. Add attendance count and prior fee rate so a reader can translate the claim into their own budget.

*effort medium · impact high · tested against Proof next to the claim*

**Show what the automation removes, with a concrete example.**

"Everything in sync" and "schedule volunteers" assert coordination disappears without showing it. Name the manual task that ends — the weekly spreadsheet re-keyed between giving, check-in and volunteer rosters.

*effort medium · impact medium · tested against Tie the feature to the outcome*

### Clarity

**Rank the feature blocks: core system first, extras after.**

Service plans, volunteer scheduling, check-in, giving and Church Center arrive as one flat list with no hierarchy. Lead with the two products a church ops lead adopts first and label the rest as add-ons.

*effort medium · impact medium · tested against Headings stand alone*

### Relevance

**Address the switch from a standalone giving platform directly.**

Nothing on the page names the reader who already uses a separate giving tool, though the fee comparison is aimed at them. Add a subhead about moving giving off a standalone platform without losing donor history.

*effort medium · impact medium · tested against Answer the live objection*

---

## 03 · What is working

### The page names the audience and the fragmented-tools problem in the first screen

Nine points credit the headline and subheads for stating who this is for — church ops staff at mid-size churches — and the problem of scattered systems, without generic filler.

> It was obvious immediately — the H1 "Every part of your church, finally in sync" plus the subhead "Planning Center is the flexible system that brings ministry details together. Made for churches of every kind and size" tells me the problem (fragmented ministry tools/data) and the audience (churches) in the first two lines.
> 
> — Church Administrator, Faith-Based Organizations, 501-1000

> so within about ten seconds I knew this was ChMS for church staff consolidating separate systems, which matches my own situation with fragmented giving platforms
> 
> — Administrative Staff Member, Religious Organizations, 11-50

> It's church management software — scheduling volunteers, planning service plans, check-ins, and giving/donations all bundled into one system.
> 
> — Church Admin, Faith-Based Organizations, 1-10

> It's church management software - one system that handles service planning, volunteer scheduling, check-ins, giving/donations, and event registration for churches, all tied together so the data connects automatically instead of living in separate tools.
> 
> — Church Staff, Churches, 201-500

### Published processing fees are the proof point respondents believed and could act on

Eight points singled out the concrete fee numbers as verifiable and directly comparable against their current provider, contrasting them with vague savings claims elsewhere on the page.

> the fee structure is the one thing here concrete enough to act on
> 
> — Administrative Staff Member, Non-Profit Religious Services, 11-50

> The processing fee numbers are the one thing with real teeth: "2.15% + $0.30" and "0% + $0.30 via ACH" are specific enough to check against what we're paying now
> 
> — Church Operations Manager, Religious Organizations, 51-200

> The processing fee numbers are concrete enough to matter: 2.15%+$0.30 on cards and 0%+$0.30 on ACH, plus that $26,000/year saved quote from ChurchLV — if our transaction volume is comparable, that's real budget I can point to when I sign off, not fluff.
> 
> — Church Administrator, Faith-Based Organizations, 501-1000

> "2.15% + $0.30 per transaction via credit and debit cards" and "0% + $0.30 per transaction via ACH" is a real, checkable number I can put against a competitor's rate sheet, not a vague "low fees" claim.
> 
> — Church Admin, Non-Profit Religious Services, 1-10

> What actually sold it for me wasn't the headline though, it was the named quotes further down — Steven Terrones from ChurchLV saving $26K, the Financial Administrator mentioning ACH fee savings — that's where it clicked this is specifically for church admin/finance/ops staff drowning in separate systems
> 
> — Church Staff, Churches, 201-500

---

## 04 · What the personas said

### Feature copy does not explain how anything works or what matters most

Four points flag a flat feature list with no hierarchy between core and nice-to-have, unclear mechanics, soft metaphors like "connect the dots," and sub-brand names that must be decoded first.

> if anything got in the way it was that the list reads as a grab-bag ('annotate music in real time,' 'coordinate rehearsals') without a clear hierarchy of what's core versus nice-to-have
> 
> — Church Operations Manager, Religious Organizations, 51-200

> "connect the dots" and "in sync" are the kind of soft metaphors that sound nice but don't tell me if it's a shared database, real-time webhooks, or just shared login screens
> 
> — Church Administrator, Non-Profit Religious Services, 501-1000

> It's phrases like "annotate music in real time" and "coordinate rehearsals" and "assign people to roles" that sound specific but leave me guessing at the actual mechanics
> 
> — Administrative Staff Member, Churches, 11-50

> the only friction was that the product is split across sub-brand names like 'Church Center' and 'Services,' so it took a beat to realize those are modules of one system rather than separate products
> 
> — Administrative Staff Member, Religious Organizations, 11-50

### Cost savings and the switching scenario are placed where respondents nearly missed them

Three points say the cost-savings message sits below the hero, the Church Admin role is never addressed by name, and the move from standalone giving platforms is not called out directly.

> the actual pain point I care about, cost, wasn't in the hero copy at all; I had to scroll down to "Low giving rates" and the fee section to find the cost angle
> 
> — Church Administrator, Non-Profit Religious Services, 501-1000

> I'd need to see our situation named directly — something like 'switching from a standalone giving platform' or 'consolidating from multiple ChMS tools'
> 
> — Administrative Staff Member, Religious Organizations, 11-50

> I'd need a line or section addressed to "Church Admin" specifically - what I'm responsible for day to day, like managing volunteer rosters or reconciling giving records - rather than having to infer my role from a rotating cast of Worship Pastor and Financial Administrator quotes.
> 
> — Church Admin, Non-Profit Religious Services, 1-10

### Testimonial savings claims lack the baseline needed to be usable

Four points say the time and cost claims in testimonials have no starting context or church-size detail, so respondents could not translate them into their own numbers before a demo.

> The testimonial claiming $26,000/year saved is dangling but useless without knowing their transaction volume
> 
> — Administrative Staff Member, Non-Profit Religious Services, 11-50

> testimonials say things like "saved so much time" and "$26,000 a year in processing fees" but with no baseline or context, so I'd want a real case study with before/after numbers before I'd trust it
> 
> — Church Staff, Faith-Based Organizations, 201-500

> I'd want to see our actual processing volume run through their 2.15%+$0.30 card / 0%+$0.30 ACH numbers to know if the $26K ChurchLV story is realistic for a church our size, not just a flashy outlier. So: worth a short call to get real numbers, not worth a demo yet.
> 
> — Church Staff, Churches, 201-500

> A real total-cost comparison showing our current spend on manual scheduling plus whatever giving processor we use now against Planning Center's subscription plus fees - if that number is clearly lower, it's worth my time; if it's just implied by testimonials, it isn't.
> 
> — Church Admin, Non-Profit Religious Services, 1-10

### Support is asserted without an SLA, and a competitor with a real one would win

One point notes the support claim carries no guarantee or response number, making it lose to any competitor publishing an actual SLA.

> if a competitor on my shortlist has a support SLA with a number and a guarantee behind it instead of a tilde, that beats this page outright, because right now this is the exact thing I'm trying to fix and Planning Center's proof point is softer than the number they're using to sell fee savings
> 
> — Church Operations Manager, Religious Organizations, 51-200

### Fees are the only differentiator respondents could name

Three points state outright that the fee structure is the sole concrete difference versus competitors, and one dismisses the investor status and changelog as reassurance rather than differentiation.

> The thing that would actually swing it is the stated fee structure — "2.15% + $0.30" on cards and "0% + $0.30" on ACH — because that's a number I can put against our actual giving volume
> 
> — Administrative Staff Member, Religious Organizations, 11-50

> The "no outside investors" / privately-owned pitch and the changelog of "63 features... in the last 90 days" don't move me either way for a shortlist decision — they're reassurance, not differentiators
> 
> — Administrative Staff Member, Religious Organizations, 11-50

### The automation promise is unproven

One point makes the value contingent on demonstrating that automation actually removes manual coordination work.

> That volunteer no-shows or scheduling scrambles actually drop — if a sign-up or schedule change automatically notifies the right people without me manually chasing texts and emails, that's the time savings I'd measure before/after.
> 
> — Church Admin, Faith-Based Organizations, 1-10

---

## 05 · The hardest read

An adversarial pass over the findings. Every claim below was checked
against the panel's own answers; unsupported ones were dropped.

- **The page has one real differentiator — price — and that is a position any competitor can undercut next quarter.** *(high)*
  Fees are the only concrete difference respondents could name, with investor status and changelog dismissed as reassurance, while published fee numbers are the single believed proof point. A messaging platform resting entirely on a number invites a race to…
- **Every claim on the page that isn't a fee number failed to land as proof.** *(high)*
  Testimonial savings claims lack baselines or church size, support is asserted with no SLA, and automation value is contingent on an unshown demonstration. Only the published fee figures were called verifiable.
- **The page wins the first screen and loses everything after it.** *(high)*
  Seven respondents credit the headline and subheads for naming the audience and the fragmented-tools problem, but cost savings sit below the hero where respondents nearly missed them and feature copy reads as a flat list with no hierarchy.
- **Respondents cannot do the arithmetic that would justify a demo, so the page stalls at interest.** *(high)*
  Four points say testimonial time and cost claims have no starting context or church-size detail, leaving respondents unable to translate them into their own numbers before a demo.
- **The page never names the buyer or the trigger event it is actually built to win.** *(medium)*
  The Church Admin role is never addressed by name and the move from standalone giving platforms is not called out directly, despite that switch being the exact scenario the fee comparison serves.
- **Sub-brand names and metaphors make the reader do decoding work before any value registers.** *(medium)*
  Four points flag unclear mechanics, soft metaphors like "connect the dots," and sub-brand names that must be decoded first — friction placed directly in front of the feature story.

---

## 06 · Who answered

| # | Role | Industry | Company size |
| --- | --- | --- | --- |
| 1 | Church Admin | Faith-Based Organizations | 1-10 |
| 2 | Administrative Staff Member | Non-Profit Religious Services | 11-50 |
| 3 | Church Operations Manager | Religious Organizations | 51-200 |
| 4 | Church Staff | Churches | 201-500 |
| 5 | Church Administrator | Faith-Based Organizations | 501-1000 |
| 6 | Church Admin | Non-Profit Religious Services | 1-10 |
| 7 | Administrative Staff Member | Religious Organizations | 11-50 |
| 8 | Church Operations Manager | Churches | 51-200 |
| 9 | Church Staff | Faith-Based Organizations | 201-500 |
| 10 | Church Administrator | Non-Profit Religious Services | 501-1000 |
| 11 | Church Admin | Religious Organizations | 1-10 |
| 12 | Administrative Staff Member | Churches | 11-50 |
| 13 | Church Operations Manager | Faith-Based Organizations | 51-200 |
| 14 | Church Staff | Non-Profit Religious Services | 201-500 |
| 15 | Church Administrator | Religious Organizations | 501-1000 |

---

## 07 · Before you act on this

The methodology is real, and the critique is directional. What a
simulated persona cannot have is a live budget, a renewal coming up, or
a boss asking about this quarter. **Validate anything you're betting on
with real ICPs who are actually in-market.** Being wrong is more
expensive than you think. Finding out is cheaper than you'd guess.

Wynter runs message testing with verified B2B professionals — trusted
by HubSpot, RingCentral, Shopify, Cognism, Paddle, Veeam, Rippling and
Miro. <https://wynter.com>

This report is kept for 60 days from 2026-09-01, then deleted along with the personas and their answers.

