# Pledge Now, Pay Later — Homepage Conversion Strategy

> Produced: March 2026
> Goal: Maximize free account signups from mixed-intent traffic

---

## 1. PAGE STRATEGY

### Target Persona + Emotional State on Arrival

**Primary persona:** Fatima, 38, Fundraising Manager at a mid-size UK Islamic charity (£200k–£2M annual income). She just finished a gala dinner where £48,000 was pledged. She's sitting at home on Sunday night, dreading Monday. She knows from experience that 30–50% of those pledges will vanish. She's Googling "how to collect charity pledges" or heard about PNPL from another charity manager at the event.

**Emotional state:** Frustrated, slightly anxious, skeptical of yet another tool. She's been burned by CRMs that cost £500/month and require 3 months of setup. She needs something that works *tonight*, not next quarter. She's on her phone.

**Secondary personas:** Personal fundraisers (sharing links on WhatsApp), event volunteers (want credit for their work), treasurers (need compliant records).

### Single Core Promise

**Every pledge tracked. Every donor reminded. Every penny accounted for. Free.**

### 3 Supporting Pillars

1. **60-second mobile pledge flow** — Donor scans QR → picks amount → done. No app, no account, no friction.
2. **Automated follow-up that doesn't feel awkward** — 4-step reminder sequence via WhatsApp/email. Donors pay when ready. You never chase.
3. **Complete visibility + compliance** — Live dashboard, Gift Aid declarations, Zakat tracking, HMRC-ready CSV export. One click.

### Top 5 Friction Points + Design Solutions

| # | Friction Point | How the Design Removes It |
|---|---------------|--------------------------|
| 1 | "What's the catch? Free = limited or sketchy" | Explicit "Free forever — no tiers, no card" messaging in hero. FAQ explains the business model transparently (lead gen for consultancy). |
| 2 | "I don't have time to set up another tool" | "2 minutes to your first pledge link" — specificity beats claims. How-it-works section shows 4 steps with real time estimates. |
| 3 | "My donors are older / not tech-savvy" | Show the 3-screen pledge flow visually. Emphasize: no app download, no account needed, 60 seconds. Address this directly in FAQ. |
| 4 | "Is this legit? Is my data safe?" | HMRC compliance, GDPR, ICO references. UK-based company registration. No vague "enterprise security" — name the specific regulations. |
| 5 | "We already use spreadsheets / JustGiving / LaunchGood" | Position as the *missing layer* between platforms, not a replacement. "Works with your existing setup" section with named platforms. |

---

## 2. WIREFRAME (Section-by-Section)

### Section 1: HERO (Dark — bg-gray-950)
**Goal:** Instant message match + primary CTA within 3 seconds.

**Key message:** You raise pledges. We make sure the money arrives.

**Components:**
- Eyebrow: `Pledge collection for UK charities` (border-l-2 accent, promise-blue)
- H1 (Display): `Turn "I'll donate" into money in the bank.`
- Subhead: `People pledge at events, over dinner, on WhatsApp. We make sure the money actually arrives.`
- Primary CTA: `Start free — takes 2 minutes` (white bg, dark text — high contrast)
- Secondary CTA: `See live demo` (outline, ghost)
- Trust micro-strip: `No card required · HMRC compliant · Free forever`
- Hero image: Documentary photo of charity event (right column on desktop, below on mobile)

**Interaction notes:**
- CTAs use `stagger-children` fade-up on load
- Hero image uses `fadeUp` with 250ms delay
- Primary CTA is white-on-dark for maximum pop (not blue — blue recedes on dark bg)

### Section 2: STAT STRIP (Dark — continuation of hero)
**Goal:** Anchor the problem with specific numbers before the visitor scrolls.

**Key message:** The pledge gap is real, measurable, and expensive.

**Components:**
- 4-column gap-px grid (signature pattern 2)
- Stats: `30–50%` pledges never collected | `60s` pledge flow | `£0` cost | `2 min` setup

**Interaction notes:**
- Numbers use `font-black text-xl md:text-2xl` for visual weight
- Labels are `text-[11px] text-gray-500` — subordinate

### Section 3: PROBLEM AGITATION ("The Pledge Gap")
**Goal:** Make the visitor feel seen. Mirror their exact pain so they think "this is for me."

**Key message:** People don't break promises. Systems do.

**Components:**
- Eyebrow: `The pledge gap` (border-l-2 accent)
- H2: `People don't break promises.` + gray follow: `Systems do.`
- Subhead: `We built the missing system between "I'll donate" and the money arriving.`
- 4 sticky persona cards (image left, text right):
  - Charity organizer: £50k pledged → £22k collected
  - Fundraiser: 23 promised → 8 paid
  - Volunteer: 40 pledges → 0 updates
  - Treasurer: 200 rows, 47 typos, 6 hours

**Interaction notes:**
- Sticky scroll effect on desktop (cards stack with 28px offset)
- Mobile: standard vertical stack (no sticky)
- Each card links to `/for/{persona}` detail page
- Concrete numbers, not vague "lose donations"

### Section 4: HOW IT WORKS (Light bg — gray-50)
**Goal:** Make the mechanism feel simple and inevitable. Remove "is this complicated?" objection.

**Key message:** Four steps. Zero pledges lost.

**Components:**
- H2: `Four steps. Zero pledges lost.`
- 4-column numbered grid (01-04 pattern):
  1. Create a pledge link — "One link per campaign, table, or WhatsApp group."
  2. Donor pledges — "Amount, Gift Aid, schedule. 60-second mobile flow. No app."
  3. Automatic follow-up — "Reminders with bank details. They pay when ready."
  4. Money arrives — "Live dashboard. Who pledged, who paid, who needs a nudge."

**Interaction notes:**
- Numbers use `text-4xl font-black text-gray-200` (signature numbered steps)
- Copy is ruthlessly short — one line title, two line description max

### Section 5: SOCIAL PROOF / TRUST BLOCK
**Goal:** Transfer trust from known entities to PNPL. Answer "who else uses this?"

**Key message:** Built for the charities that can't afford to lose a single pledge.

**Components:**
- H2: `Built for UK charity compliance`
- Image: phone showing pledge form with checkboxes
- 4 border-l-2 items:
  - Gift Aid — HMRC model declaration, timestamped CSV
  - Zakat tracking — per-campaign, separate reporting
  - Email consent — GDPR, never pre-ticked, audit trail
  - WhatsApp consent — PECR, reply STOP, no sends without permission

**Interaction notes:**
- This section doubles as social proof (regulatory bodies = authority proof) AND objection handling
- Specific regulation names (HMRC, GDPR, PECR, ICO) act as trust anchors

### Section 6: BENEFIT STACK — Payment Flexibility
**Goal:** Show outcome-oriented benefits. Answer "but my donors want flexibility."

**Key message:** Donors pay when they're ready. You don't chase.

**Components:**
- H2: `Donors pay when they're ready`
- 3 border-l-2 items:
  - Pay now — bank transfer or redirect to existing page
  - Pick a date — "I'll pay on payday" with auto reminder
  - Monthly instalments — 2–12 payments, each tracked separately
- Image: phone showing schedule options

### Section 7: PLATFORM COMPATIBILITY
**Goal:** Remove "but we already use X" objection. Position as additive, not replacement.

**Key message:** Works alongside what you already have.

**Components:**
- H2: `Works with your existing platform`
- Platform pills: Bank Transfer (UK), LaunchGood, Enthuse, JustGiving, GoFundMe, Any URL

### Section 8: FAQ / OBJECTION HANDLING
**Goal:** Kill remaining objections. Reduce "I'll think about it" exits.

**Key message:** No catch, no risk, no setup headaches.

**Components:**
- H2: `Questions we hear at every charity dinner`
- 6 Q&A items (accordion or simple expand):
  1. "How is this free? What's the catch?"
  2. "Will my donors actually use this?"
  3. "Is this GDPR compliant?"
  4. "We already have a CRM / use JustGiving"
  5. "How long does setup take?"
  6. "What happens to donor data?"

**Interaction notes:**
- Questions written in first person ("Will MY donors...") — similarity principle
- Answers are 2–3 sentences max. Specific. No corporate waffle.

### Section 9: FINAL CTA (Dark — bg-gray-950)
**Goal:** Strong close. Create urgency without fake scarcity.

**Key message:** Every day without this, you're losing pledges.

**Components:**
- H2: `Every day without this, you're losing pledges.`
- Subhead: `Free forever. Two-minute setup. Works tonight.`
- Primary CTA: `Create free account`
- Secondary CTA: `See live demo`

**Interaction notes:**
- No nav links, no footer links visible — minimal distraction
- CTA buttons are larger here (py-4 px-8) — commitment escalation

---

## 3. UI DIRECTION (Design System Guidance)

### Layout Grid + Spacing
- Max content width: `max-w-7xl` (hero), `max-w-5xl` (content sections)
- Section padding: `py-20 md:py-24 px-6`
- Mobile: single column, `gap-8`
- Desktop: `grid md:grid-cols-2` or `md:grid-cols-4`
- Consistent internal spacing: `space-y-6` for text blocks, `gap-10` for grid cards

### Type Scale
| Level | Size | Weight | Tailwind |
|-------|------|--------|----------|
| Display/H1 | 44px / 60-72px | 900 | `text-[2.75rem] md:text-6xl lg:text-7xl font-black tracking-tighter` |
| H2 | 36-48px | 900 | `text-4xl md:text-5xl font-black tracking-tight` |
| H3 | 18-24px | 700 | `text-base font-bold` or `text-xl font-black` |
| Body | 14-16px | 400 | `text-sm` or `text-base` |
| Eyebrow | 11px | 600 | `text-[11px] font-semibold tracking-[0.15em] uppercase` |
| Caption | 11-12px | 500 | `text-[11px] text-gray-500` |

### Button Hierarchy
| Level | Style | Use |
|-------|-------|-----|
| Primary (dark bg) | `bg-white text-gray-900 font-bold px-7 py-3.5` | Hero CTA, final CTA |
| Primary (light bg) | `bg-gray-900 text-white font-bold px-8 py-4` | Mid-page CTAs |
| Secondary | `border border-gray-700 text-gray-400 font-bold px-7 py-3.5` | Demo links |
| Ghost | `text-sm font-semibold text-promise-blue` | "Learn more" inline |

### Form Design
- Signup page (not on landing): email + password only. Name optional. Org name on next screen.
- No forms on the landing page itself — CTA buttons route to `/signup`

### Visual Style
- **Photography:** Documentary candid, shallow DoF, diverse British subjects, never stock
- **Icons:** Not used as section headers. Numbers (01, 02, 03) replace icons.
- **Illustrations:** None. Photography + typography only.
- **Sharp edges everywhere.** Max `rounded-lg` on interactive elements.

### Trust Design
- Named regulations (HMRC, GDPR, PECR, ICO) instead of generic "secure" badges
- Specific numbers instead of vague claims
- Company registration visible in footer (© QuikCue Ltd)
- "Free forever — no card required" repeated 2x on page

---

## 4. CONVERSION PSYCHOLOGY MAPPING

| Section | Component | Principle | Implementation |
|---------|-----------|-----------|---------------|
| Hero | Headline | **Clarity > Persuasion** | "Turn 'I'll donate' into money in the bank" — no jargon, instant understanding |
| Hero | Stat strip | **Anchoring** | "30–50% of pledges never collected" anchors the cost of inaction |
| Hero | Trust line | **Risk Reversal** | "No card · HMRC compliant · Free forever" — 3 objections killed in 8 words |
| Pledge Gap | Persona stats | **Loss Aversion** | "£50k pledged. £22k collected." — gap framing triggers loss aversion |
| Pledge Gap | "Systems do" | **External Attribution** | Blame the system, not the donor — removes shame, creates solvable problem |
| How It Works | 4 steps | **Commitment/Consistency** | Small, numbered steps make action feel inevitable (foot-in-door) |
| How It Works | "60 seconds" | **Specificity = Credibility** | Specific time beats "quick and easy" |
| Compliance | HMRC, GDPR names | **Authority Proof** | Regulatory body names transfer institutional trust |
| Payment Flex | 3 options | **Autonomy** | Giving donors control reduces reactance, increases completion |
| Platforms | Named logos | **Social Proof (similarity)** | "They use LaunchGood too" — similarity reduces perceived risk |
| FAQ | First-person Qs | **Social Proof (similarity)** | "Will MY donors use this?" mirrors exact internal dialogue |
| FAQ | Business model | **Reciprocity + Transparency** | Explaining why it's free creates trust debt |
| Final CTA | "Losing pledges" | **Loss Aversion** | Frame inaction as ongoing loss, not missed gain |
| Final CTA | "Works tonight" | **Immediacy** | Reduces "I'll do it later" deferral |

---

## 5. COPY (Ready to Paste)

### Hero
**Headline:** Turn "I'll donate" into money in the bank.
**Subhead:** People pledge at events, over dinner, on WhatsApp. We make sure the money actually arrives.
**Primary CTA:** Start free — takes 2 minutes
**Secondary CTA:** See live demo
**Trust strip:** No card required · HMRC compliant · Free forever

### 3 Pillar Stats
- `30–50%` of pledges never collected
- `60s` to complete a pledge
- `£0` cost to charities
- `2 min` signup to first link

### Mechanism Section (How It Works)
**H2:** Four steps. Zero pledges lost.

**01 — Create a pledge link**
One link per campaign, table, volunteer, or WhatsApp group. Share anywhere.

**02 — Donor pledges in 60 seconds**
Amount, Gift Aid, Zakat, schedule — mobile flow. No app download. No account.

**03 — Automatic follow-up**
Reminders with your bank details. They pay when ready. You never chase.

**04 — Money arrives**
Live dashboard. Who pledged, who paid, who needs a nudge. Export for Gift Aid.

### Proof / Compliance Captions
- **Gift Aid:** HMRC model declaration, home address, timestamped. One-click CSV for claiming.
- **Zakat:** Per-campaign toggle. Donors tick one checkbox. Tracked separately in reports.
- **Email consent:** GDPR compliant. Separate opt-in, never pre-ticked. Full audit trail.
- **WhatsApp consent:** PECR compliant. Separate opt-in. Reply STOP to opt out.

### FAQ Answers

**Q: How is this free? What's the catch?**
No catch. No tiers. No "upgrade to unlock." The tool is genuinely free because it helps us identify charities that need broader technology support. If your org grows beyond pledge collection, we offer fractional Head of Technology services — but that's a separate conversation you'd start, not us.

**Q: Will my donors actually use this?**
They scan a QR code or tap a link. Three screens: amount, payment method, email or phone. 60 seconds, done. No app download, no account creation. We've designed it for the least tech-confident person at your event.

**Q: Is this GDPR and HMRC compliant?**
Yes. Gift Aid declarations use the exact HMRC model wording with timestamped consent. Email and WhatsApp opt-ins are separate, never pre-ticked, with full audit trails. Data is stored in UK-hosted infrastructure.

**Q: We already use JustGiving / LaunchGood / a CRM.**
We're not replacing any of those. We're the layer between "I'll donate" and the money reaching your platform. Donors can be redirected to your existing fundraising page to pay. We just make sure they don't forget.

**Q: How long does setup take?**
Two minutes. Create an account, name your first event, generate a pledge link. You can test the donor flow on your own phone immediately.

**Q: What happens to donor data?**
You own it. Export everything as CSV anytime. We never sell or share donor data. When you delete your account, the data goes with it.

### Final CTA
**H2:** Every day without this, you're losing pledges.
**Sub:** Free forever. Two-minute setup. Works tonight.
**Primary CTA:** Create free account
**Secondary CTA:** See live demo

---

## 6. EXPERIMENT PLAN (CRO)

### A/B Tests

| # | Hypothesis | Change | Expected Impact | Risk |
|---|-----------|--------|----------------|------|
| 1 | Loss-framed headline converts better than gain-framed | A: "Turn 'I'll donate' into money in the bank" vs B: "Stop losing 40% of your pledged donations" | +15–25% CTA clicks | Low — both on-brand |
| 2 | Single CTA in hero outperforms dual CTA | A: Two buttons vs B: One primary button only | +10% primary clicks, -20% demo clicks | Medium — lose demo traffic |
| 3 | Sticky persona cards hurt mobile conversion (scroll jank) | A: Sticky scroll vs B: Standard card stack on all devices | +5% scroll-to-CTA on mobile | Low — simpler is safer |
| 4 | FAQ section increases signup rate | A: With FAQ vs B: Without FAQ | +8–12% conversion (objection removal) | Low — only adds content |
| 5 | Social proof with specific charity names beats generic compliance | A: Compliance features vs B: "Trusted by 40+ UK charities" with named logos | +10–20% trust signal impact | Medium — need real logos |
| 6 | "Works tonight" urgency in final CTA beats neutral | A: "Works tonight" vs B: "Get started today" | +5% final CTA clicks | Low |

### Tracking Plan

| Event | Trigger | Properties |
|-------|---------|-----------|
| `page_view` | Landing page loads | `source`, `utm_*`, `device` |
| `scroll_25` | 25% scroll depth | `time_on_page` |
| `scroll_50` | 50% scroll depth | `time_on_page` |
| `scroll_75` | 75% scroll depth | `time_on_page` |
| `scroll_100` | Bottom of page reached | `time_on_page` |
| `hero_cta_click` | Primary CTA in hero | `cta_text` |
| `hero_demo_click` | Secondary CTA in hero | — |
| `persona_card_click` | Any persona card tapped | `persona` |
| `faq_expand` | FAQ question opened | `question_index` |
| `final_cta_click` | Bottom CTA clicked | `cta_text` |
| `signup_start` | `/signup` page loads (from landing) | `referrer_section` |
| `signup_complete` | Account created | `time_to_signup` |

### Diagnostic Checklist (If Conversion Is Low)

1. **Hero bounce rate > 60%?** → Message mismatch with traffic source. Check ad copy vs headline alignment.
2. **Scroll depth < 50% for 70%+ visitors?** → Hero isn't compelling enough or page loads slow. Check LCP.
3. **Hero CTA click rate < 3%?** → CTA copy or placement issue. Test button color, copy, position.
4. **Persona cards getting 0 clicks?** → Cards aren't engaging or sticky scroll is broken on mobile. Simplify.
5. **FAQ section has 0 expansions?** → Either placed too low (people leave before reaching it) or questions aren't matching real objections. Move higher or rewrite.
6. **Demo clicks > signup clicks (3:1)?** → Visitors don't trust enough to commit. Add more proof, reduce signup friction.
7. **Signup starts >> signup completes?** → Form friction. Check field count, validation errors, load time.
8. **Mobile conversion < 50% of desktop?** → Touch target issues, slow images, broken layout. Audit on real device.
9. **High time-on-page but low conversion?** → Content is engaging but CTA isn't clear or compelling enough. Make CTAs stickier.
10. **Organic traffic converts but paid doesn't?** → Ad targeting or messaging mismatch. Align ad creative with landing page promise.