GrantDiscovery
The current public slice is intentionally narrow: qualify whether a buyer is credible for the BMWK ZIM lane, explain the missing evidence, and tell the operator what to do next. The earlier Python implementation remains preserved under legacy-python/ as the source-grounded migration bridge.
Guided intake flow
This is the correct GD order: entity first, innovation second, evidence third. Proposal guidance comes only after eligibility, lane fit, and evidence gaps are visible.
1. Entity first
Capture who is applying and from which country.
2. Innovation second
Describe the actual innovation and give it TRL/BRL and pilot context.
3. Evidence third
Only then decide the best lane, missing proof, and proposal next move.
Innovator intake
This public beta now preserves the intake as real URL-backed product state, while applicant country, company size, maturity stage, pilot-proof, and TRL still decide whether the live lane stays actionable or drops back to block/reshape-first.
Use the shareable link to preserve this exact intake state across reloads and operator handoffs.
No saved workspace loaded
No saved workspace is currently loaded. Saving now will create a fresh local or server snapshot while the shareable URL remains the portable operator handoff path.
0 saved workspaces · server-file-seam · adapter:file · owner:default
The interim server seam is reachable, but it does not hold any named workspace snapshots yet. Durability: interim file-backed seam.
Save named local snapshots for this browser even before the Postgres-backed workspace stack lands.
Local saves stay in this browser; the share link remains the portable cross-device/operator path.
No local saved workspaces yet. Save the current intake here to reload it later without depending only on the URL.
This is the first server persistence seam for GD-1. It is still a bounded interim layer, not the final Postgres/Auth.js cutover.
This adds an interim server-side save/load seam beyond the URL, but it is still a temporary file-backed layer rather than the final durable workspace stack.
No server-backed workspaces yet. Save the current intake to the server seam to make the first canonical persistence bridge visible in the UI.
No fallback blocker signal is active, so the canonical sample brief still explains the lane reasoning.
Lane reasoning is still coming from the checked-in canonical sample qualification brief because the current intake does not yet trigger a harder country, beneficiary, budget, or readiness blocker.
AgroFlow GmbH
Sensor-guided irrigation optimisation pilot · sme_company in Germany · AgriTech
Public beta promise
Keep the product promise honest while live-actionable coverage is still concentrated in one family.
Qualify whether BMWK ZIM is credible for this buyer now, explain why it fits, show the missing evidence, and tell the operator what to do next.
It does not pretend the buyer has broad live grant choice today. Non-live families stay visible only as explained fallback/watchlist lanes.
Innovator intake snapshot
The editable intake on the left updates this summary immediately. Intake state is live in the URL, while lane reasoning still comes from the proven checked-in qualification briefs.
Canonical qualification flow
Show the real GD progression directly from the active brief: eligibility first, proposal guidance last, with no hidden leap from discovery to drafting.
1. Eligibility
Applicant country fits the programme geography scope.
2. Best lane
The current live-actionable coverage depends on one source family (BMWK ZIM), so source diversification remains an active priority.
3. Application posture
Application posture stays intake-first: The source is live, but the operator should collect the missing buyer inputs first so packet drafting does not run ahead of the evidence needed for a credible ZIM submission lane.
4. Evidence gaps
Still missing: technical concept note, work package outline.
5. Fit improvement
Improve fit by doing Reframe the buyer narrative around applied r and d, digitalization so the lane reads closer to the programme's stated theme language., Request a technical concept note from the buyer covering novelty, technical approach, and pilot scope..
6. Proposal guidance
Request the missing technical concept note and work package outline for ZIM Einzelprojekt before starting the application-readiness drafting pass.
Source portfolio checkpoint
Make single-family dependency visible instead of hiding it in notes.
The current live-actionable coverage depends on one source family (BMWK ZIM), so source diversification remains an active priority.
Fallback lane checkpoint
Preserve the canonical GD behavior: keep fallback lanes visible without implying they are ready now.
Top-lane workspace
Decision recommendation: pursue ZIM Einzelprojekt now, but keep the lane intake-first until the buyer provides the missing technical concept note and work package outline. Keep EIC Accelerator as the fallback lane. Avoid spending proposal effort on rejected lanes until the project shape materially changes.
Priority actions
- Reframe the buyer narrative around applied r and d, digitalization so the lane reads closer to the programme's stated theme language.
- Request a technical concept note from the buyer covering novelty, technical approach, and pilot scope.
- Request a work package outline from the buyer with milestones, owners, timing, and expected proof points.
Evidence to collect
- technical concept note
- work package outline
Operator handoff
The source is live, but the operator should collect the missing buyer inputs first so packet drafting does not run ahead of the evidence needed for a credible ZIM submission lane.
Operator handoff · request now
- technical concept note
- work package outline
Operator handoff · draft now
None.
Operator handoff · blocked items
None.
Operator sequence · request now
- Ask the buyer for a short concept note covering novelty, technical approach, and pilot scope.
- Ask the buyer for a milestone-level work package outline with owners, timing, and expected proof points.
Operator sequence · start now
None.
Blocked until
- technical concept note
- work package outline
Top-lane source checkpoint
Current source indicates the lane can be treated as open because ZIM Einzelprojekte accept direct digital applications via the Förderzentrale Deutschland portal.
Source was checked 1 day ago, so recency risk is currently low.
Gefördert werden einzelbetriebliche Forschungs- und Entwicklungsaktivitäten zur Entwicklung innovativer Produkte, Verfahren oder technischer Dienstleistungen ohne Einschränkung auf bestimmte Technologien und Branchen. Antragsberechtigt für ZIM -Einzelprojekte sind: kleine und mittlere Unternehmen weitere mittelständische Unternehmen Definition antragsberechtigter Unternehmen kleine Unternehmen mittlere Unternehmen weitere mittelständische Unternehmen Beschäftigte unter 50 unter 250 unter 500 Jahresumsatz oder bis 10 Mio. Die zuwendungsfähigen Kosten betragen maximal 690.000 Euro; die Förderung erfolgt als nicht rückzahlbarer Zuschuss in Form einer Anteilsfinanzierung. Die Antragstellung im ZIM erfolgt volldigitalisiert über das Online-Portal der Förderzentrale Deutschland.
Open official sourceReview gate
Collect the buyer inputs first, then move into packet drafting once the missing evidence is confirmed and operator review keeps the lane credible.