Grant Fund stores company-level funding state and updates route viability, no-fit reasons, readiness gaps, missing evidence, source changes, and decision history.
It is built for founder-led deeptech startups in Europe that need to know which routes are viable now, which are dead, which are blocked but recoverable, what evidence is missing, what changed at source level, and what the company should do next.
What Grant Fund does
Stores company grant state
A structured company-level applicant record, not a loose text profile.
Checks route viability
Records whether a funding path is eligible now, not eligible, not yet ready, conditionally viable, or escalation-only.
Records no-fit logic
Stores why a route fails and what must change before re-check.
Maps readiness gaps
Tracks missing preparation across entity, evidence, documents, and route-specific conditions.
Tracks source-level changes
Links program changes back to affected routes and company state.
Preserves decision history
Keeps a reusable audit trail of what was rejected, deferred, escalated, or pursued.
A system of record for grant viability and readiness
Most teams handle grants with a mix of public calls, notes, spreadsheets, generic AI output, and fragmented advisory input. That creates repeated confusion because the company’s funding state is never stored properly.
Grant Fund replaces that with persistent company-level grant records. It does not just tell a founder that a route may fit. It records whether the route is viable now, why it is blocked, what evidence is missing, what changed in the source, what decision was made, and when the case should be reviewed again.
The product is not built around search. It is built around state.
The six persistent records
1. Company Grant State
A structured record of the company as a funding applicant. It stores jurisdiction, entity profile, stage, technology maturity, funding constraints, operating context, evidence inventory, and escalation flags.
2. Route Viability Record
A route-level record showing the current status of a funding path: eligible now, not eligible, not yet ready, conditionally viable, or escalate.
3. No-Fit / Not-Yet-Fit Record
A structured explanation of why a route should not be pursued now, including blocker type, blocker severity, whether the blocker is structural or temporary, and what must change before re-check.
4. Readiness Gap Record
A record of what is missing before a viable route can be acted on, including entity readiness, document readiness, evidence readiness, route-specific preparation, and escalation requirements.
5. Evidence Status Record
A structured view of what proof already exists and what proof is missing. It makes visible reusable materials, weak or stale evidence, route-specific evidence needs, and dossier gaps.
6. Decision Audit Trail
A record of what was considered, rejected, deferred, escalated, or approved. It preserves decision date, decision rationale, source linkage, affected route, and next review trigger.
Example route record
Route: EIC Accelerator Status: Not yet ready Reason: TRL below threshold; missing evidence package; no EU operating entity Evidence status: 3 required items missing Source status: rule change detected 6 days ago Next action: complete evidence set; re-check after entity setup Decision log: deferred, not rejected
This is the level at which Grant Fund operates. Not as a chat answer. As a persistent record.
What gets updated on each review
Every review updates company state. Grant Fund does not start from zero when a founder returns. Each review can update route status, blocker logic, missing evidence, readiness gaps, source-linked change exposure, decision history, and next review timing.
That means later route checks become narrower, faster, and more defensible. The product compounds with use because the company becomes more legible over time.
Why generic AI is not enough
A general model can summarize a funding call, draft text, or suggest possibilities. That is not the same as maintaining persistent company-level grant records across time.
Generic AI does not automatically preserve a reusable company grant state, route-level status history, formal no-fit logic, evidence dependencies, source-linked change impact, or decision audit history. Grant Fund is built to preserve those records and update them consistently.
The durable value is not “AI for grants.” The durable value is persistent funding state.
Why this is not a database
A database tells you that programs exist. Grant Fund tells you whether a specific route is viable for a specific company now, why it is not viable if it fails, what must change before re-check, what evidence is missing, what changed in the source, and what should happen next.
The hard problem is not access to public calls. The hard problem is preserving a verified model of company-level route viability.
Why this is not a chatbot
A chatbot answers questions. Grant Fund maintains records. A chatbot can generate a plausible reply once. Grant Fund preserves a company’s funding state across repeated reviews and repeated routes.
That difference matters because funding work is not a single question. It is a sequence of route decisions made over time.
Core outputs
Which routes are viable now?
Identifies routes that are currently actionable.
Which routes are dead?
Removes routes that should not consume founder time.
Which routes are blocked but recoverable?
Separates temporary blockers from structural blockers.
What evidence is missing?
Shows what proof must exist before serious route execution.
What changed at source level?
Tracks changes in programs, rules, deadlines, and route relevance.
What should the company do next?
Converts status into concrete next actions and re-check triggers.
Operating workflow
Store company state
The company is represented as a structured funding applicant, not as a loose text description.
Evaluate routes
Relevant funding paths are checked against the company’s current state.
Record no-fit and not-yet-fit logic
Bad routes are not just hidden. They are explicitly classified and explained.
Map readiness gaps
The system records what must be prepared before action.
Track source-level changes
Changes in programs are linked back to affected routes and company state.
Preserve decisions
The system records why a route was rejected, deferred, escalated, or pursued.
Re-check without starting over
Later reviews reuse stored state instead of rebuilding context from scratch.
What persists after each session
Grant Fund preserves company applicant state, route history, no-fit logic, readiness gaps, evidence status, source-change exposure, decision rationale, and re-check conditions.
That is the core product asset. The interface is not the moat. The persistent records are.
Persistent company state
Each company becomes a structured funding object, not just a set of chat prompts.
Formal no-fit logic
Rejected routes become reusable decision assets, not forgotten conversations.
Evidence compounding
A company does not rebuild its dossier logic from zero every time.
Source-linked change tracking
Program changes are mapped to live company records, not just surfaced as news.
Decision memory
Past route decisions remain usable in future route evaluations.
Controlled escalation
The system identifies where software is sufficient and where expert escalation is required.
Software-safe layer
Grant Fund handles the repeatable layer in product:
- company state storage;
- route viability checks;
- no-fit classification;
- readiness mapping;
- evidence status tracking;
- source change tracking;
- decision logging.
Escalation boundary
Grant Fund does not pretend software should finish every case. Some cases require escalation, including:
- legal structuring;
- tax-sensitive interpretation;
- consortium complexity;
- specialized submission work;
- high-stakes local judgment.
Built for founder-led deeptech in Europe
Grant Fund is built for teams that face high ambiguity and high decision cost in European non-dilutive funding.
- founder-led startups;
- deeptech and R&D-heavy companies;
- early-stage teams building toward European funding routes;
- companies with real evidence and readiness complexity;
- teams that need route control, not generic advice.
Infrastructure direction
Grant Fund starts with the founder workflow. Over time, the same record system can support founder-level funding operations, portfolio-level visibility, partner workflows, API delivery, and agent-native surfaces later.
The durable layer is not a landing page and not a chat surface. It is the record system underneath them.
Frequently asked questions
Is Grant Fund a grant search engine?
No. It stores company-level grant state and evaluates route viability, readiness, evidence, and decision history.
Is this just another AI tool?
No. It may use AI internally, but the product is a persistent record system, not a generic answer layer.
What happens when a route is not viable?
Grant Fund records the reason, classifies the blocker, and defines whether the route should be killed, delayed, or re-checked later.
What happens when new program information appears?
Grant Fund tracks source-level change and maps it back to affected routes and company state.
What happens when the company changes?
The company record is updated and route viability can be re-evaluated without rebuilding context from zero.
Does it replace all external experts?
No. It reduces waste in the repeatable layer and identifies when escalation is genuinely required.