← All work
2026 · Systems design · Nonprofit sector

Riot Ooru

A world-model platform I built under Purple Borders. It maps global needs at sub-national resolution, assembles a coalition for each from hundreds of organisations across ten roles, and plans the path from a need to the funding that can carry it. The same instinct as my strategy work, pointed at coordination instead of positioning.

What it is
World-model platform
Sector
Nonprofit funding
Status
Live, in build
Stack
React · Vite · Postgres

The nonprofit world has a structural problem no product serves well. A need exists somewhere at real geographic resolution, and the capacity to meet it exists somewhere else, in an organisation, a funder, an expert, a government plan, but the two have no reliable way to find each other at the moment the work requires. Enterprise resource tools assume a company's shape and a company's budget. This sector has neither. Riot is built around the way it genuinely operates.

It began inside my work at Purple Borders, a facilitation initiative, and grew into a real build. The approach was the same one I bring to any ambiguous problem: start from how the people actually work, model that as a system, then write the code. It is live, on React, Vite and a Postgres data layer, with accounts, teams and automatic saving, built and iterated by me from the structure up.

Riot Ooru world model: a need in Eastern India lit up on the map with its coalition pins, beside a dossier showing SDG targets, a deployability score and the coalition across ten roles
The world model. Pick a need and the map shows where it sits and where each coalition member works, coloured by role, beside a dossier of SDG targets, deployability and coalition strength.
01

A need, read at real resolution

Every need sits at sub-national resolution with a summary, its SDG targets, and a deployability score built from impact, ease and investment need. The platform then assembles a coalition for it across ten roles, from the mandate holder and re-granter to the witness, solver, connector and steward, and scores how complete that coalition is. It is a directory turned into a considered reading of who can actually move the work.

02

Planning, from scoping to scale

Each need runs a six-stage path, scoping, validation, mapping, co-design, pilot and scaling, with a readiness score that counts nine checks: coalition, local witness, member quality, pilot site, funding, government alignment, tender route, experts and evidence. The board shows the whole portfolio at once and surfaces the common blockers, so a team can see exactly what stands between a need and the money that would move it.

Riot Ooru planning board: needs on a six-stage path from scoping to scale, each with a readiness score, and the most common blockers across the portfolio
The planning board. Every need on the six-stage path to funding, each with a readiness score and the checks still blocking it.
03

A desk for large mandate funding

A funder states a mandate, a budget, a geography, themes and a timeline, and the desk ranks the needs that fit, surfaces adjacent ones, builds a coalition for each across the ten roles, and drafts every document and message the mandate needs. It is where the world model turns into a fundable portfolio, built for the people who hold a mandate and have to place it well.

Riot Ooru mandate desk: a 2.5M USD, 24-month mandate for skill development in India, with themes, geography and the needs that fit ranked by score
The mandate desk. State a budget, geography and theme, and the desk ranks the needs that fit and builds the coalition and documents around them.
What this demonstrates
★

What it shows about the way I work

The method

  • An ambiguous coordination problem given a structure others can use
  • Ten coalition roles and a nine-check readiness model, designed from the domain up
  • Built live, with accounts, teams and a real data layer, by me

A note on scope

  • Riot is a live, in-build project; the deeper intelligence stays private
  • Shown here through its public world model as evidence of systems thinking
  • Built under Purple Borders, a facilitation initiative
Next project
Content engine →