The problem to solve
A donation happens when three conditions line up: the person understands the value, trusts the route, and can act with low effort. Fail any one and the donation does not happen. The task is to engineer these three conditions on the End GBV South Africa page.
A simple model
Think of donations as a flow through a pipe.
- Attention enters at the top.
- Comprehension converts attention into intent.
- Trust permits intent to become action.
- Friction resists flow at every step.
Output = Visitors × Comprehension rate × Trust rate × Payment success rate.
Stability comes from Recurring share × Retention.
Optimise the pipe, not anecdotes.
Invariants
- Clarity beats persuasion. People support what they can explain to themselves in one line.
- Proof beats promise. Evidence removes mental risk.
- Fewer steps beat clever design. Each extra field or click leaks donors.
- Recurring donors beat once-off spikes. Stability funds real work.
These rules hold regardless of copy style, colour palette, or trend.
What the donor must know in 10 seconds
- The job: fund survivor support and prevention in South Africa.
- The unit: rands buy concrete outcomes, not vague activity.
- The ledger: money in, money out, dates, and vendors.
- The result: lives made safer this month.
If any of the four is missing, comprehension drops and trust weakens.
Trust, built like a circuit
Trust is binary at the checkout point. It is either complete enough to transact or it is not.
- Identity: who operates the fund, legal entity, contact details.
- Accountability: monthly public ledger, independent review notes, strict privacy.
- Specificity: unit costs with ranges, not slogans.
- Recency: last three deployments with timestamps.
- Consistency: same message in page, receipt, and reports.
One weak component breaks the circuit.
Friction, measured not guessed
Every step, field, or mental calculation adds cost.
- Load time under two seconds on low bandwidth.
- Above the fold: purpose, allocation mix, three priority units, primary donate widget.
- Guest checkout and modern wallets.
- Strong defaults: monthly preselected, meaningful presets linked to units, custom option always visible.
- Receipt and reporting preferences in one step, not a new flow.
Remove anything that does not change a decision.
Units beat stories
Stories are variable. Units are computable.
- Safe night in shelter: RX to RY.
- Trauma counselling session: RX to RY.
- Transport to safety: RX to RY.
- Protection-order assistance: RX to RY.
Publish ranges with sources and update them as prices shift. Link donation presets to these units so the value is obvious.
Recurring by design
Recurring giving transforms a fragile project into an operational programme.
- Default to monthly. Explain stability in one sentence near the toggle.
- Soft upgrade path in receipts: convert once-off to monthly in one click.
- Card-expiry prevention: nudge at T-14 days with a secure update link.
- Churn management: optional pause instead of cancel.
You are maximising days of funded cover, not raw rand volume.
Social proof without noise
- Show verified counters only: total safe nights, counselling sessions, transports, legal assists.
- Display a rolling feed of deployments with timestamps and unit labels.
- Enable micro-campaigns for creators, SMEs, and schools that roll up into the same counters.
- Avoid dark patterns. Credibility compounds faster than likes.
Measurement that matters
Track a small set of rates and treat them like a control panel.
- Visitor to donate start.
- Donate start to pay success.
- Monthly share of all donations.
- Donor retention at 30, 90, 180 days.
- Time to deploy funds to units.
- Coverage ratio: units funded this month divided by required units.
Dashboards must show trends and variance, not just totals.
Experiments that actually change outcomes
Run short, clean tests. Change one lever at a time. Ship the winner.
- Preset mapping - Compare plain amounts vs amounts labelled by unit. Expect higher conversion with labelled presets.
- Ledger position - Place the monthly ledger summary above the fold vs below. Expect improved trust rate when above.
- Copy length - 150-word value summary vs 300-word summary. Expect a sweet spot where comprehension rises before attention drops.
- Payment options - Wallets on by default vs card only. Expect improved pay success rate, especially on mobile.
- Recurring default - Monthly preselected vs once-off. Expect higher recurring share with minimal drop in initial conversion if value is clear.
- Micro-campaign launcher - Button on page vs a separate hub. Expect higher community activation when visible in context.
Document hypothesis, metric, expected lift, stop rule, and outcome. Keep tests under two weeks.
Failure modes to avoid
- Vague promises with no units. Looks good, converts poorly.
- Heavy media and scripts. Looks modern, starves low-end phones.
- Donation choices without meaning. More options, less action.
- Retargeting of survivors or sensitive audiences. Ethically wrong and reputationally fatal.
- Overhead creep disguised as impact. Trust once lost is expensive to reacquire.
Page structure that does the job
- Header: purpose, allocation pie, three priority units.
- Primary widget: donate monthly presets tied to units, custom field, wallet support.
- Secondary tab: once-off with identical UX.
- Proof strip: live deployments and cumulative counters.
- Ledger and reviews: latest month summary and link to independent note.
- Micro-campaign launcher: create your own page that rolls up to the fund.
- Accessibility: keyboard navigation, high contrast, readable type on small screens.
Why this works
It aligns human limits and machine constraints. People decide with simple causal stories and concrete trade-offs. The web punishes latency, ambiguity, and extra clicks. Units and ledgers compress uncertainty. Clean flows compress time to action. Recurring compresses volatility. Proof compresses doubt. Put these together and donations rise for the right reason: the value is obvious and the path is clean.