◆
Overhead you can defend
Infrastructure cost small enough and clear enough to put in an annual report without flinching.
Infrastructure spending in this sector has a moral weight it does not have elsewhere: it is money donated for a purpose, spent on overhead instead. Reducing it is not an efficiency exercise.
Used for donation surfaces, programme delivery, beneficiary systems and funder reporting.
What this looks like in practice
Infrastructure cost small enough and clear enough to put in an annual report without flinching.
The hour a campaign lands is the hour donations arrive. It is the worst possible time to be down.
Where the money went, demonstrable from the record rather than from a narrative.
Tooling for people delivering programmes, not only for the people reporting on them.
Organisations here often run on donated or heavily discounted infrastructure that costs them more in fragility than it saves in cash.
A campaign lands, the supporters arrive together, and every one of them reaches a working donation page. The counterfactual is uncomfortable and rarely measured: the donations that were intended, attempted, and lost to a page that could not cope.
Donor and supporter systems that hold the relationship properly.
Programme tooling for the people doing the work, not an afterthought.
Reporting drawn from what happened rather than reconstructed each cycle.
Campaign surfaces that go live when the moment is, not a fortnight after.
Our infrastructure line went down by two-thirds and our appeal did not drop a single donation. I could put both numbers in the annual report.
Cost follows what you use, which for most organisations here is a reduction on what they pay now. You will have the figure before you commit, which matters for a grant application.
Yes. Capacity follows arrival, and the hour your appeal lands is the hour this is for.
The record of spend and change is complete, so funder reporting is drawn from it rather than assembled by hand each cycle.
Yes. One surface, nothing else disturbed, and a decision you take afterwards.
Run regulated workloads with a complete record of every change, and answer an auditor in an afternoon rather than a quarter.
Carry sensitive workloads with separation that is structural, and keep clinical and research software moving.
Serve the public on infrastructure that stands up to scrutiny, procurement and a service that cannot be allowed to fail.
Hold up on the day that matters most, and change your storefront in the week you decided to, not the quarter after.
Publish the moment it matters, carry an audience that arrives all at once, and keep an archive that stays reachable.
Bring plant data somewhere useful, keep the software near the line dependable, and stop treating the factory as offline.
Begin with one workload. Keep what you have running. Decide whether to continue once you have seen it carry something real.
No migration required to begin. Nothing to tear down if you stop.