Skip to content

Workflow

Codex Fundraising Pipeline

Fundraising Pipeline walkthrough preview
How we will use Codex for fundraising AI workflows

What you will build

Turn one reusable nonprofit source pack plus one funder's rules into a review packet: budget draft, narrative draft, trace table, and open questions for human approval.

Why this workflow

Grant teams almost never write funding proposals from scratch. They already have everything they need, including the organization's background, project details, team bios, cost breakdowns, and the core story. What takes time is reshaping that familiar material to fit each funder's unique application form, spreadsheet layout, budget categories, narrative questions, and reporting guidelines, all while keeping track of every tweak along the way.

That's why a file-based, repeatable workflow is so powerful. You keep your unchanging facts in a master source pack, layer in the specifics of your current grant opportunity, then apply the funder's rules. From there, you ask Codex to assemble a draft review packet that your team can scan and polish before hitting submit.

This becomes more powerful the more it is used. Funders ask different questions, but much of the underlying substance stays the same, so every run sharpens the source pack, reveals another reusable answer, and makes the next funder-specific draft easier to assemble. The same compounding pattern shows up in donor reports, board updates, compliance documents, due diligence briefs, or any workflow where you need to know exactly where each piece of information came from and how it got there.

1.9M organization profiles

Many teams are reshaping similar facts for different funders.

3M annual grant transactions

Each grant can carry its own questions, spreadsheet format, and budget rules.

$180B annual grant dollars

Review needs traceability, clean assumptions, and open questions.

Source: Candid social-sector data.

Workflow pattern

Workflow pattern Reusable source files and funder rules flow into Codex, which compiles a review packet. INPUTS Known material Reusable source pack Project inputs Funder rules CODEX Compile against rules Reads source files Reshapes for the funder Leaves assumptions visible OUTPUT Review packet Budget draft Narrative draft Trace and questions

The reusable move is to separate what is already true from what changed for this grant. The source pack should stay stable across funders, the project inputs should describe this specific opportunity, and the funder rules should describe the shape the answer needs to take.

Codex sits in the middle as a compiler, not the source of truth. It reads the inputs, drafts the funder-shaped packet, and makes the review work easier by showing what came from where and what still needs human judgment.

Starter files

Runnable checklist

Watch a chapter, run the step, check the output.

Step 01

Watch 10 min

Review the deck

Deck reviewed

Download the V0 starter files, open Codex in the folder, and review the finished Jenga Fund deck in your browser. Make one tiny edit live to prove the slides are real HTML you own, not a binary.

Step 02

Watch 12 min

Research funders and draft the answers

Targets + answers

Find real, current funders that fit Jenga with sizes, deadlines, and sources, turn them into a targets workbook, capture the actual portal questions, then let the agent interview you and draft the high-signal answers straight into the workbook.

Step 03

Watch 6 min

Compile the budget packet and close

Review packet

Set up the file workspace under one rule (Codex writes only to outputs, never edits source), compile the funder-shaped narrative and budget with every claim traceable, reconcile the packet for a human to sign off, then run it again for a second funder and watch it get cheaper, not harder.

Comments

Loading…

Sign in with GitHub to ask a question or share what you built.