Before / After · Case Study
Hope Matters International runs a 37-bed mission hospital in rural Kenya, scaling toward 90 beds. Its legacy site buried that story in a dated builder template with no clear giving path. The rebuild — built autonomously end-to-end in a single run on the operator's build machine — is a 14-page donor-conversion site in English and Swahili, grounded in six research artifacts on the hospital and region. Donation rails are Stripe-ready and deliberately stubbed: a compliance doc gates real payments on the charity connecting its own Stripe account, so donor money can never route through anyone else's books.
“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.”
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.
Architecture
What changed
Each claim ships with concrete evidence — env vars, table names, cadence chips. No marketing fluff.
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.
