Before / After · Case Study
A charity running a 37-bed mission hospital in rural Kenya — and scaling it toward 90 beds — had a website whose homepage was literally titled 'HOME': no story, no way to give, English only. Now donors walk a 14-page journey in English and Swahili, every claim backed by real research, with a complete giving flow built and waiting — locked until it can pay into the charity's own account and nobody else's.
“A 37-bed hospital scaling to 90 deserves better than a template — and donors deserve rails that route to the charity's own account, not a middleman's.”
At a glance
Design
Fourteen pages walk a stranger from 'where is this hospital?' to 'here's my card' — need, then the work, then the impact, then the ask — in English for donors and Swahili for the community the hospital serves.
Selling & payments
The donation flow is fully built and deliberately switched off: a written compliance gate keeps it locked until the charity connects its own payment account, so no donor dollar can ever pass through anyone else's books.
Agents
The entire rebuild — research, page plan, copy, build, and deploy — ran as one autonomous session on our build machine, with human review at the end instead of in the loop.
Receipts — measured
The pixel diff
Left: everything the legacy site shipped — frozen in place. Right: an auto-scrolling tour of the rebuild, from hero to booking. No slider to fight with.
This is everything the legacy site had to offer above the fold. No pricing, no calendar, no booking — the funnel ended at a mailto.
Auto-scrolls through the modern site so you can see the booking surface, the package grid, the pricing table, and the calendar inline — without leaving this page.
The four beats
Scroll past the legacy frame. The four beats land in order. At the end, the modern site fades into the same window.
The legacy site's page title was literally 'HOME'. A 37-bed hospital with a real expansion plan presented like a parked page — no story arc, no giving path, English only.
The site's job is to walk a stranger from 'where is this?' to 'here's my card' without a leap of faith. That takes researched specifics — beds, region, outcomes — in the donor's language and the community's, with the payment rail as the last step, not the first.
Six research artifacts on the hospital and region, then a 14-page EN/Swahili build on Next.js 15 + Neon, donation flow wired to Stripe but compliance-gated. Built end-to-end in a single run on Bruce, reviewed after.
hope-matters-intl.vercel.app is live. The legacy site still answers at the apex — cutover and Stripe connection are the board's call, and the site is ready for both the day they make it.
The legacy site's page title was literally 'HOME'. A 37-bed hospital with a real expansion plan presented like a parked page — no story arc, no giving path, English only.
The site's job is to walk a stranger from 'where is this?' to 'here's my card' without a leap of faith. That takes researched specifics — beds, region, outcomes — in the donor's language and the community's, with the payment rail as the last step, not the first.
Six research artifacts on the hospital and region, then a 14-page EN/Swahili build on Next.js 15 + Neon, donation flow wired to Stripe but compliance-gated. Built end-to-end in a single run on Bruce, reviewed after.
hope-matters-intl.vercel.app is live. The legacy site still answers at the apex — cutover and Stripe connection are the board's call, and the site is ready for both the day they make it.
A legacy site-builder template carrying a working mission hospital: the page title was literally 'HOME', the story was buried below the fold, the site spoke only English, and there was no structured way to give. A 37-bed hospital with a real plan to grow to 90 beds presented like a parked page.
Donor conversion is a narrative problem before it's a payments problem. The site's job is to walk a stranger from 'where is this?' to 'here's my card' without a leap of faith — which takes researched specifics (beds, region, outcomes) in the donor's language and the community's, with the payment rail as the last step, not the first.
Six research artifacts on the hospital and its region grounded the content first, so nothing reads like boilerplate charity copy. Then a 14-page donor-conversion site on our current web stack with a managed database, every page shipped in English and Swahili with auto-translate underneath. The whole run — research, information architecture, copy, build, deploy — executed as a single autonomous session on the operator's build machine, reviewed by a human at the end.
The giving flow is wired to a mainstream payment processor and deliberately stubbed: a compliance document gates activation on the charity connecting its own processor account. That's a feature, not a gap — the honest architecture for third-party nonprofit work is one where donor money can only ever route to the charity's own books.
The rebuilt site is live at a preview address while the legacy template still answers at the charity's main domain. Cutover and connecting the payment account are the board's call — and the site is ready for both the day they make it.
Architecture
What changed, with evidence
The giving flow is built and Stripe-ready, and deliberately stubbed: a compliance doc gates activation on the charity connecting its own Stripe account. No donor dollar can ever route through the builder's books — the honest architecture for third-party nonprofit work.
Every page ships in English and Swahili with auto-translate underneath — the donor audience and the served community read the same site. Fourteen pages walk need → work → impact → give, grounded in six research artifacts on the hospital and region rather than boilerplate charity copy.
The entire rebuild — research, information architecture, copy, build, deploy — ran as a single autonomous session on the operator's build machine (Bruce), with human review at the end rather than in the loop. A live demonstration of the agent pipeline the rest of this catalog is built with.
