A digital chief of staff for impact organisations, holding the team's shared memory.

What Enact is

Enact is being built as a digital chief of staff for impact organisations: a tool an organisation owns and runs itself, holding everything the organisation knows and helping put it to work. It starts with a private, human-only page where staff write messy notes and meeting minutes through the day, with no AI reading over their shoulder. One click files those notes into the organisation's own record, alongside its vision, its theory of change, its monitoring and evaluation results, and every past proposal and evaluation, so all of it sits in one place as a shared memory. Enact reads that record and helps design programs, draft proposals and write reports, with every line checked against the organisation's own evidence and its own principles.

OpenImpact Studio already runs an early version of this pattern on its own work: a written memory of decisions, relationships and how the studio speaks, which sits behind everything the studio writes. Enact is that pattern, to be built out as a tool other organisations can run themselves.

What it will do

Ask a general AI chatbot about an organisation's work and it answers confidently, whether or not it knows anything true. Enact answers from the organisation's own material. A claim in a draft proposal, an outcome from a past evaluation, a figure from a monitoring report: each carries a link back to the document it came from, and a claim with no source is flagged rather than invented.

The organisation's own rules run alongside. Say the board has decided which funders it will not take money from. Enact checks a new funder against that list before anyone drafts a word. The same goes for a guide to how the organisation writes, or a safeguarding policy that a program design has to pass before it goes any further. Enact stops at set points for a person to approve: a concept, a draft, a submission, and any decision that affects people's lives. It keeps a record of who approved what.

Two jobs anchor it: developing a proposal, from a funder's call through to submission, and designing a program, from community input through to a budget and a list of risks. Both draw on the same record, so the second proposal starts from the first, and a program design can lean on the same evidence the proposal used.

Who it's for

NGOs, civil society organisations and community groups of any size, campaigns, coalitions and networks across the Asia-Pacific, and OpenImpact Studio itself, which will run it on its own work first. It is meant for organisations where staff turn over fast, what they knew leaves with them, and a proposal or program design usually starts from a blank page instead of the last one.

How it's held

Everything Enact knows will live as plain text files the organisation writes and owns, from the daily page of notes to the finished proposal, readable in any text editor with the AI switched off entirely. An organisation runs its own copy, plugs in whichever AI service it already uses, and decides what, if anything, gets sent outside the organisation. It can walk away at any point with every file intact. Nothing about it depends on OpenImpact Studio staying involved.

Where it's up to

Enact starts from a pattern already proven inside OpenImpact Studio's own daily work, not from a blank page. The next step is opening that pattern up: publishing how it works, and finding a handful of organisations willing to run it against their own material and tell us where it breaks. What we learn shapes the tool itself, before a line of the dedicated product gets built.

Get involved

We are looking for a handful of organisations willing to try the underlying pattern early, on real proposals and program designs, and tell us where it breaks. If that's you, or you'd like to be kept posted as Enact develops, write to hello@openimpact.studio.