DanielOnPurpose Grant Pipeline
A repeatable loop for turning a funding opportunity into a submitted, rubric-aligned application. Follow it end to end.
Step 1 — Notice intake
From the PDF/URL, extract a structured brief:
- Eligibility (and which entity is the right applicant)
- Scoring rubric — every point category and weight; the application is written to the rubric
- Match requirement and deadline (compute days remaining)
- Prerequisites: required resolutions, registrations (e.g. SAM.gov), estimates, letters
- Required attachments checklist
Step 2 — Clarifying questions
Ask a NUMBERED list of only the questions that block drafting. Rules:
- "I don't know" is a valid answer → draft anyway with a clearly flagged
[PLACEHOLDER: …], never block on it. - Pull known facts from existing files/notes before asking.
Step 3 — Draft the application
- Write to the scoring rubric, section by section.
- Save as .docx (most teams work in Word/Google Docs, not markdown) in the project folder.
- Flag every unknown as
[PLACEHOLDER: what's needed + who likely has it].
Step 4 — Letters of support
Keep a standing signatory bench (partner orgs, institutions, local officials). Tone rules:
- Civic / community pride for elected officials
- Operational / fiscal for administrators
- Programmatic partnership for institutions
Each letter: one page, .docx, ready for letterhead.
Step 5 — Team briefing
Draft the internal briefing (use the team-memo style): warm and collaborative, acronyms spelled out, ending with a clear ask list. Deliver as copy-paste text.
Step 6 — Record it
- Add/update the opportunity in your grants tracker (keep a JSON/markdown source of truth, not just app state).
- Archive the brief + application + letters in your knowledge base (Active / Library / Templates).
- Close out with the
wrap-sessionskill: a handoff note + open items (placeholders awaiting answers).