Context
Rarsfound is a Lagos-based community relief NGO I founded in 2021 and continue to lead — including designing, building, and iteratively shipping the public website (rarsfound.org.ng) myself, now in its 14th-plus version.
Problem
A community relief organization needs a public presence that can grow with its programs — new initiatives, updated information, and a credible online face for donors and the community — rather than a static brochure page set up once and left alone.
Opportunity
Owning both the organization and the website end to end meant no handoff lag between a program decision and the site reflecting it — a widows' relief program or a feeding initiative could go from "we're doing this" to "it's on the site" without waiting on anyone else's roadmap.
Research
Each version of the site responded to a specific, real need the organization had at that point — a new program needing a page, donors needing clearer information, the community needing an easier way to find a specific initiative — rather than a redesign for its own sake.
Decision-Making
As the only person accountable for both the organization's leadership and its website, every scope decision about the site was also, implicitly, an operational decision about the organization — there was no separating "the product" from "the business" here.
Prioritization
Program pages — the widows' relief initiative, the "Radiant Kitchen" community feeding program — were built and prioritized as the organization's actual programs matured, not on a fixed content calendar.
Execution
Dedicated program pages for the organization's initiatives, built and maintained as a living site rather than a one-time brochure, across 14+ shipped versions, each responding to what the organization actually needed next as its programs grew.
Collaboration
Founder and sole web owner. I run the organization's leadership day to day and independently own the website end to end, which meant acting as my own stakeholder, reviewer, and approver on every change.
Trade-offs
Owning everything solo meant faster iteration but no second opinion on scope or design calls — appropriate for an early-stage NGO's website, but a trade-off I'm conscious wouldn't scale to a larger product team without adding real review.
Outcome
A real, live public website for an active community relief organization, in continuous use since 2021 and still maintained today.
Reflection
Running both the organization and its website end to end meant every product decision was also an operational one — the same discipline of shipping, reviewing, and revising that shows up in the product work elsewhere in this portfolio started here, with a non-profit's website, not a portfolio exercise.
Lessons Learned
Iterating a site 14+ times without a team taught me to notice when a version genuinely serves the current program versus when it's just accumulated, unnecessary complexity — a filtering instinct that transfers directly to backlog grooming.
Future Improvements
Formal outcome tracking — donor conversion, program-page engagement — is the honest gap. The site has grown with the organization's needs, but not yet with instrumented feedback on which pages actually drive action.
My Contribution
Founder, leader, and sole web owner — design, build, content, and every one of the 14+ revisions are mine.