Case Study · One Future Collective
Two websites. One team that keeps both running.
One Future Collective runs two distinct public-facing websites, onefuturecollective.org and SanskaariGirlsBookClub.com, each serving different audiences across advocacy, funder outreach, and community engagement. Both need to be on, clear, and working.
10hrs/mo
Saved across two active public-facing sites.
99.97%
Combined uptime over 5 months
2
Websites, one maintenance relationship
Objectives
Two sites held to one standard.
One Future Collective needed both websites on the same maintenance protocol, so a small team working across justice, gender, and leadership initiatives never had to triage either one. The brief was a single relationship, a single report, and no situation where a funder page or a community signup form is quietly out of action while nobody is looking.
Before NoDrama
Two sites, multiple audiences, and a team whose job is impact, not IT.
One Future Collective's team works across justice, gender, and leadership initiatives. They do not have, and should not need, a person dedicated to watching two websites for plugin conflicts, backup gaps, or forms that quietly stop working.
Both sites were redesigned and launched by Pangolin. NoDrama took over maintenance from day one. The team briefs their content. NoDrama makes sure both sites stay up, stay secure, and keep performing for every audience that lands on them.
The honest audit
What we found when we looked.
The onboarding audit covered both sites simultaneously. Here's what it found.
No staging environment on either site.
Two live sites taking direct updates. For an organisation running funder outreach and community applications, a broken form goes straight to missed contact with the people they serve.
Default backup configurations on both sites.
Hosting-level monthly snapshots on each, neither tested. A restore drill was run within the first two weeks; one confirmed immediately, and one needed a configuration fix before it was reliable.
OFC: Seven plugins due for major version updates.
Two had known vulnerability patches pending that had not been applied at launch. Applied with before-and-after checks.
SGBC: Email signup form misconfigured.
A webhook error meant submissions were being recorded in the CMS but not forwarding to the mailing list. Silent failure, potentially weeks of lost community signups. Fixed in week two.
No uptime monitoring on either site.
Any downtime was being discovered manually, after the fact. For sites serving funder and community audiences, that's not a viable detection method.
The work
What we actually did. Specifically.
Dual audit, both sites.
Both sites were audited together. Five items across the two sites were prioritised and documented as a single brief.
Update checks and backup setup on both sites.
Set up before-and-after checks for both. Upgraded to 12-hour off-site backups on each. Restore tests completed for both. SGBC restore confirmed working on day 12.
Vulnerability patches and form fixes.
Updated the two vulnerable plugins on OFC with before-and-after checks, zero issues. Fixed the webhook misconfiguration on SGBC. Email signups are now delivering correctly.
Remaining plugin updates.
Updated the remaining five major-version plugins on OFC. Before-and-after checks confirmed nothing broke.
Unified weekly cycle.
Both sites are on the same update schedule. Before-and-after checks, one report on the 1st covering both sites.
The results
5 months in.
10hrs/mo
saved per month, across two active public-facing sites.
Hours the OFC team spends on advocacy, programmes, and community work, not on-site administration.
99.97%
Combined uptime across both sites.
Funder and community pages are always available.
0
Emergency calls in 5 months.
Across two live sites.
2
Websites.
One maintenance relationship. Single report, single point of contact.
Business outcome
What the reliability actually bought them.
Two sites came off the team's plate as an operational concern, which for an organisation this size is the difference between programme time and admin time. The webhook fix also means community signups have been reaching the mailing list from week two onwards, rather than sitting in a CMS nobody was checking.
NoDrama Plan
The Higher Standard
$249/mo · cancel anytime · setup free on yearly plan
Start with The Higher Standard- Backups every 12 hours, kept 90 days
- Key pages photographed before and after every update
- Global CDN, caching and image optimization
- Two small jobs at once
- 2-hour response if down or hacked
- Real restore tested twice a year