The ItFtI seal: the letters I, t, F, t, I form the walls of a maze, with an entrance at the bottom and an exit at the top.

Find the way from impact to funding.

Many projects get lost before they reach support. ItFtI has a project for each end of the maze. One exists today; the other is still an idea.

Impact to Funding builders · experimental

An open-source skill for your AI agent: find where your skills help, build with others, and explain what would help the work continue.

Funding to Impact funders · proposal

An idea, not a service yet: funders publish what they support in a simple file people and agents can read.

Install ItFfree and open source

The maze

Useful work often stalls on the way to support. Builders lose time reading scattered, outdated or vague funding pages. Funders read applications that were never a fit.

ItFtI starts from both sides. From the builder's side, it helps people describe their work and what would help it continue. From the funder's side, it proposes a plain way to say what they support, before anyone spends time applying.

Impact to Funding

For builders. Available now as an experimental skill.

ItF is a skill for the AI agent you already use. It helps you:

  • explore where your skills could be useful,
  • develop shared work with others,
  • learn what difference the work makes,
  • explain what would help it continue.

Start with your situation. You don't need a theory of change, a project, evidence or a fundraising goal. It's for developers, maintainers and independent builders who already use AI agents; community organisers, small teams and facilitators may find it useful too.

Install

Claude Code

Run this in your terminal, from the project where you'll use ItF. You need Git.

target='.claude/skills/impact-to-funding'
revision='4566892ad990131fb36f760e14c73e5f275600cc'
if [ -e "$target" ] || [ -L "$target" ]; then
  echo "Destination already exists; stop and inspect: $target"
else
  git clone https://github.com/zhiganov/impact-to-funding.git "$target" &&
    git -C "$target" checkout --detach "$revision" &&
    git -C "$target" rev-parse HEAD
fi

Open Claude Code in the same project and type /impact-to-funding. If the session was already open, run /reload-skills first.

Codex CLI

Run this in your terminal, from the project where you'll use ItF. You need Git.

target='.agents/skills/impact-to-funding'
revision='4566892ad990131fb36f760e14c73e5f275600cc'
if [ -e "$target" ] || [ -L "$target" ]; then
  echo "Destination already exists; stop and inspect: $target"
else
  git clone https://github.com/zhiganov/impact-to-funding.git "$target" &&
    git -C "$target" checkout --detach "$revision" &&
    git -C "$target" rev-parse HEAD
fi

Open Codex in the same project and type $impact-to-funding. You can also pick it from /skills.

OpenCode

Run this in your terminal, from the project where you'll use ItF. You need Git.

git clone https://github.com/zhiganov/impact-to-funding.git .opencode/skills/impact-to-funding
git -C .opencode/skills/impact-to-funding checkout --detach fbb8993060254ef63f5157d3b9ddcbb8bb4cf19b

In OpenCode, in the same project, type @impact-to-funding. This is an older snapshot, the one tested in OpenCode. It lacks some newer guidance. Use an empty destination.

Installs into this project only and changes no global settings. If something already exists at the destination, it stops instead of overwriting. Full guide, personal installs and updates: installation guide.

How it works

How the two meet

  1. Impact → funding

    A builder works out what their contribution is, what difference it makes so far, and what support would help it continue.

  2. Funding → impact

    A funder states what it supports, who can apply, how much, by when and with what evidence, in a form people and agents can read.

When both sides speak plainly, fewer people get lost in the maze. ItF is meant to be one reader of what funders publish, not the only one and not a gatekeeper. The two parts can be used separately.

Funding to Impact

For funders. A proposal: nothing to install yet.

Before I apply, can I tell whether this funder supports work like mine, whether I'm eligible, and how to approach them?

FtI proposes a simple file a funder publishes on its own website, inspired by llms.txt and meant to reuse existing grant-data work such as CommonGrants rather than add a new competing schema. A funder would explain:

Priorities
the problems, communities and kinds of work it wants to support, and what it excludes.
Eligibility
whether individuals, informal groups, organisations or fiscally sponsored projects can apply, and where.
Support
the type, typical amount, duration and eligible costs.
Availability
whether an opportunity is open, rolling, invitation-only, forecasted, closed or withdrawn.
Process
the official route, required materials, deadlines with time zones and reporting expectations.
Evidence
what applicants should show, including whether exploratory work without prior results can be supported.
Freshness
who published it, authoritative links, and when it was last reviewed.

Funding interests are not open calls. Past awards don't mean applications are open now. Missing eligibility is unknown, not permission to apply.

Read the idea

What exists today

  • Impact to Funding is published and open source. It offers conversation, optional templates and reference material. It doesn't find collaborators, provide funding or certify impact. Trials so far were small; we haven't tested how useful it is to people or whether it helps them raise money.
  • Funding to Impact is a proposal, documentation only. There is no published standard, schema, server or importer yet, and no funder has adopted it.

ItF on GitHub