Nonprofit / Public build

Grant Match AI: inspect the fit before the application

Grant research can consume time before a nonprofit knows whether an opportunity fits. Grant Match AI explores a more structured way to make that first assessment.

Work
Early Phase 1; public code
Context
Grant discovery for nonprofits
Updated

A structured first look

The public foundation combines mission, geography, budget, eligibility, population and prior relationship in a match score. The code keeps the factor breakdown alongside the total, so the result is more than a single unexplained number. [1][2]

Separate rules from interpretation

Eligibility, geography, budget and prior relationship use programmatic scoring. Mission and population alignment are evaluated together in a model call and returned with reasoning. The scoring module then composes the result. [2][3]

This makes the division visible: some comparisons follow explicit rules, while others interpret descriptions. A match score still needs a person to consider the funder’s actual requirements.

From organization profile to opportunities

The project’s described workflow starts with an organization profile, including mission, location and budget, and presents opportunities in score order. That makes the organization’s own circumstances central to the comparison rather than treating every grant as equally relevant.

The code separates checks that can be calculated from the language-model evaluation of mission and population. Keeping a factor-level breakdown makes it possible to discuss why a result ranked as it did. A reviewer can examine the relevant requirement instead of relying only on a single total.

Public code is not a live-service claim

The repository describes the project as a Phase 1 foundation. Its README lists application tracking, narrative drafting, a story bank, a document vault and billing in the later roadmap. [1]

Some later-feature code is also present in the repository. That does not establish a deployed or available service. This page does not offer those capabilities as released features or promise an operating timetable.

Read the source with the limits in view

The public code is useful evidence of implementation. It does not establish grant success, production uptime or nonprofit adoption. We publish it as an early build that readers can inspect.

The nonprofit study covers related needs in fundraising and partnerships. We do not claim that the study caused this product to be built.

A development team can use the factor breakdown to ask better questions about an opportunity. A high overall score is still a starting point: the organization needs to read the funder’s requirements and decide whether the program fits its work. The engine helps organize that investigation; it does not decide a funder’s eligibility or award outcome.

Questions & answers

A few useful distinctions

Who is Grant Match AI for?

Nonprofit teams assessing which grant opportunities deserve closer review against their organization’s mission and circumstances.

How is fit scored?

The implementation combines mission, geography, budget, eligibility, population and prior relationship, with a factor-level breakdown.

Where does a language model enter the score?

Mission and population descriptions receive a paired model evaluation. The implementation also uses programmatic checks for factors that can be calculated directly.

Does a high score mean a grant will be awarded?

No. The score helps prioritize an opportunity for review. The nonprofit still needs to assess the funder’s requirements and decide whether to apply.

Is this a verified live service?

This page establishes a public codebase, not a verified operating service. Its README describes a Phase 1 foundation; later-feature code does not by itself establish a release.

Are tracking, drafting and billing released features?

They are not offered here as released features. The README places them in a later roadmap, and code presence alone does not establish deployment.

Public sources

These links provide the public material and background identified below. Client engagements are described by type.

  1. Grant Match AI repository and roadmap

    Public project README and source; evidence of code, not deployment.

  2. Scoring composition

    Implementation of the six factors and score breakdown.

  3. Mission and population evaluation

    The paired model evaluation and its validated response shape.

Written from the perspective of Zen Aegis.

About this build