Solutions / Nonprofit Funding Pipeline Software

A pipeline that won’t let a stage get skipped, or a move go unrecorded.

A spreadsheet tab per funder tells you where things stood the last time someone remembered to update it. This pipeline is a governed twelve-stage state machine: every forward move is checked against a real condition, every backward move requires a written reason, only an owner or admin can actually submit, and every transition writes to a permanent history record — whether or not anyone was watching when it happened.

See your applications on a real pipeline See the stage graph

The actual Applications pipeline

Not a mockup — the live Applications page, filtered by lifecycle family with a live count per tab, each row showing the funder, the deadline, days spent in the current stage, and the latest success-probability score where one has been calculated.

The live Applications page, showing pipeline stage-family tabs with counts and a list of applications each tagged with funder, deadline, and days in stage

Twelve stages, five families, one shared rulebook

The board, the list view, and the stage-transition modal all read the same transition graph, so they can never disagree about what’s allowed next.

Discovery

Discovered → Eligibility Review → Qualified

Drafting

Drafting → Awaiting Documents → Ready for Review

Submitted

Submitted → Follow-up Due

Awarded

Awarded → Reporting Required → Renewal Opportunity

Denied

Denied (reapply only if the opportunity recurs)

What a condition actually checks

DATA-BACKED CONDITIONS

Moving to Qualified or Denied requires an eligibility score to already exist. Moving to Awaiting Documents requires draft content. Moving to Ready for Review requires every required document to actually be attached, with a live “3/5 attached” count, not a checkbox someone can tick early.

MANUAL CONFIRMATIONS

Two conditions — the compliance check before submitting, and confirming a report was submitted before a renewal cycle opens — have no stored field to check automatically, so the system asks for an explicit confirmation instead of inventing a result it can’t actually verify.

Stated limitations

The success-probability score shown on some rows comes from a separate scoring pass and isn’t recalculated by the pipeline itself — a row without one yet simply shows no score, rather than a placeholder number.

The two manual conditions (compliance check, report submitted) rely on a person confirming honestly. The pipeline enforces that the confirmation happened before the stage moves; it can’t independently verify that the compliance check or the report itself was done correctly.

FAQ

What actually stops an application from skipping a stage?

A forward-transition graph defined once and shared by every view of the pipeline. Each of the twelve stages lists exactly which stages it's allowed to move to next, and most of those edges carry a condition — for example, an application can't move from Eligibility Review to Qualified until an eligibility score exists, and can't move from Drafting to Awaiting Documents until the draft actually has content. A move that isn't in the graph is rejected outright, not just discouraged.

Can staff move an application backward, and is that logged differently?

Yes, moving an application to an earlier stage is always allowed, but unlike a forward move it requires a written note explaining why — there's no silent backward move. Every transition, forward or backward, writes a row to a pipeline history table with who changed it, the from and to stage, and any note, so the full stage history of an application is a real audit trail, not an inferred one.

Who's allowed to actually submit an application?

Only an owner or admin can move an application into the Submitted stage; every other forward and backward transition is open to any role that can edit. That single role check is enforced in the same shared transition logic every view uses, so it can't be bypassed from a different screen.

What happens after an application is awarded or denied?

Awarded applications move to Reporting Required and then, once a report is submitted, to Renewal Opportunity — which starts a brand-new application for the next funding cycle rather than overwriting the awarded record. A denied application can only be reapplied to if the underlying opportunity is actually recurring (annual, quarterly, or rolling); one-time opportunities have nowhere to go from Denied, on purpose.

Does moving a stage trigger anything else automatically?

Submitting notifies the funder-relationship tracking for that funder. Submitted, awarded, and denied all trigger a best-effort follow-up-sequence check, and submission separately feeds the pipeline's own win-rate tracking. All three are fire-and-forget calls — if one fails, the stage transition itself still completes; a flaky notification never blocks the record of what actually happened to the application.

WANT THE WHOLE CYCLE, NOT JUST THE PIPELINE VIEW?

See how discovery, drafting, and submission feed this pipeline

Nonprofit Funding Software covers the full cycle this pipeline tracks the stages of.

See Nonprofit Funding Software

Put your own applications on a governed pipeline

A live demo walks through a real stage transition, including what happens when a condition isn’t met yet.

Book a demo Create an account