# Demonstration Summary

GrantFlow demonstrates the proposal-operations model on a curated demo benchmark. There are no customer pilots yet, and no measured customer baselines.

What exists today is an end-to-end, governed pipeline plus an illustrative benchmark set (`docs/pilot_benchmark_assumptions.json`) whose baselines are explicitly marked `illustrative` / "Not measured customer baseline."

## What The Demo Shows

On illustrative donor cases, the pipeline produces:

- a governed path from intake to a reviewable first draft
- HITL checkpoints and reviewer routing
- grounding checks and a critic verdict before export
- grounded, export-ready draft artifacts (Word/Excel)

These are capabilities demonstrated on demo data, not throughput gains measured against a real customer baseline.

## Where The Pipeline Is Most Built Out

Donor strategies with the most complete schemas and seed corpus today:

- `EU` (intervention logic / logframe)
- `FCDO` (logframe, VfM 4Es, OECD DAC)
- `USAID` (ADS 201) — works, but conditional depending on use case and operating constraints

Other donors in the catalog run through `GenericDonorStrategy` with a shared results framework.

## What Would Turn This Into Proof

A single real pilot with a named owner:

- one measured customer baseline (current time-to-first-draft and review-loop count)
- the same cases run through GrantFlow
- a Go/No-Go on the deltas

Until that exists, every number in the benchmark set is illustrative and should be presented as such.

## What This Means Commercially

Large proposal teams do not buy text generation by itself. The thesis GrantFlow is built around — to be validated by a pilot, not asserted here — is that they buy:

- faster reviewable drafts
- lower review chaos
- clearer reviewer routing
- cleaner export handoff
- reusable workflow infrastructure

## What To Send With This

Default companion set:

- `docs/buyer-one-pager.md`
- `docs/five-minute-demo.md`
- `docs/production-boundaries.md`
