Issue 03 | The Budget is the Design

Here's something we don't say enough: the budget is not the admin part of program design. It is the design.

Every line item is a decision about whose time is valued. Whose knowledge counts. What kind of participation is actually resourced — and what kind is just rhetorical.

You can have the most beautifully facilitated co-design process in the world. But if the budget was determined before anyone from the community sat down with you, the co-design was theatre.

The honest truth about predetermined budgets

Let's hold a tension here, because flattening it would be dishonest.

Predetermined budgets aren't always sinister. Sometimes they're genuinely useful — they provide scaffolding, reduce decision fatigue, give smaller organisations a framework to work within. A template that says "you need a budget line for M&E" can actually protect against programs that never evaluate anything.

But predetermined budgets are also instruments of control. When a funder's template pre-decides the categories, the ratios, the acceptable cost-per-beneficiary — they are making ideological decisions dressed up as administrative ones. They are deciding in advance what kind of work is legitimate, what kind of relationships are fundable, and what kind of knowledge counts as an "activity."

Log frames, ECHO templates, UKAID budget formats — these aren't neutral containers. They carry assumptions about how change happens, who drives it, and what it's worth. And once you're working inside them, those assumptions are very hard to challenge.

What feminist funders are showing us

Some of the most generative thinking on budget design right now is coming from feminist funders — organisations that have been asking for decades what it would look like to embed care, relationality, and community wellbeing into the financial architecture of programs rather than treating them as afterthoughts.

Organisations like Mama Cash, African Women's Development Fund, and JASS have been modelling what this looks like in practice — funding the conditions that make genuine participation possible, not just the activities that produce deliverables.

What does that mean concretely? It means budget lines for:

• Community stipends — paying people for their time and expertise in co-design, not just their "beneficiary" status
• Translation and accessibility — so participation isn't limited to whoever speaks the funder's language
• Childcare and food — the material conditions that determine whether caregivers can actually show up
• Rest and facilitator wellbeing — because burnout is not a program design feature, it's a program design failure
• Relationship-building time — before a single activity begins

These aren't extras. They are the infrastructure of genuine participation. And when they're absent from a budget, participation becomes something only certain people — those without caregiving responsibilities, those who speak English, those who can afford to volunteer their expertise — can actually access.

The wisdom fund: a subversive budget move

Here's something practical you can do inside even the most constrained budget template.

Build in a wisdom fund — a dedicated, flexible budget line designed to resource and amplify what already exists in a community, rather than importing new solutions.

It might be called "community knowledge stipends," "local expertise fees," "participatory review processes," or "community advisory costs" depending on what your funder template will accept. The name matters less than the function: it creates a protected space in the financial architecture for community-led decision-making.

Once it's in the budget, it's much harder to remove. And it signals — from the very first document — that this program treats community knowledge as real knowledge worth resourcing.

Try it in your next proposal. See what happens.