Rule of thumb: You almost never apply alone. Either the district/SELPA applies and buys PulsePoint, or you apply (SBIR) as a company. For state/federal education grants, your job is usually to make the district’s application easy to write.
Universal steps (every path)
Do this once, then customize per funder.
Pick one path — don’t apply everywhere at once. Start with district pilot OR one site grant.
Name your applicant — write down who signs: you, your LLC, a school, OUSD, a SELPA, or a nonprofit partner.
Get a champion — SPED director, principal, or program manager who will co-sign or let you say “in partnership with…”
Prepare a 2-page packet: master pitch (from grants index), 1 screenshot of funding dashboard, 1 screenshot of Grafana demo, link to sandbox :13002 (not live FERPA data).
Draft success metrics — e.g. % teachers logging weekly, progress rows/month, hours saved on goal evidence (estimate conservatively).
Draft budget — software, implementation, PD, support (use Scenario A $35k–$120k as template on funding page).
FERPA paragraph — who accesses data, demo vs production, no family-facing AI without review.
Submit through the official portal only — never email PDFs to specedinfoshare@cde.ca.gov as an application.
IDEA Part B · District paid pilot (recommended first)
Applicant: OUSD or SELPA · You: vendor · Timeline: 4–12 weeks to MOU, then 1 semester pilot
What you should do
Send the director email below (goal: 30-min meeting, not funding commitment).
In the meeting, show funding page + Grafana first — student login demo second if time allows.
Propose Scenario A: one school, one semester, written success criteria (from grants index).
Ask which bucket pays: IDEA Part B, SPED local plan, or LCAP supplemental — their finance person decides.
Send a 1-page pilot SOW: scope, roster size, training days, support hours, data ownership, exit if metrics miss.
Offer sandbox demo for their IT review (:13002 + Funnel); keep production :3002 off public Funnel.
District runs procurement (may be sole-source under threshold, RFP, or piggyback — ask OUSD purchasing).
Sign MOU or contract; you deliver PD week 1, office hours weeks 2–16.
Monthly: export funding metrics PDF for their records; quarterly brief for director.
End of pilot: written report against success criteria → decision to scale or stop.
Email to SPED director (first outreach)
Send to the SPED director or program manager on their district email. Do not use CDE specedinfoshare@cde.ca.gov for this.
Do
Don’t
Ask for a 30-minute briefing only
Attach many files or live-student demo links in email #1
Name one school if you have a site champion
Ask them to “find a grant” for you in the first email
Offer sandbox demo after they agree to meet
Promise FERPA compliance without a written summary ready
CC principal or SPED lead only if they expect it
CC large distribution lists on a cold pitch
Subject line (pick one)
Request: 30-min briefing — SPED progress documentation pilot (one school)
PulsePoint pilot proposal — IDEA-aligned progress evidence (sandbox demo available)
[District] SPED: one-semester pilot — progress data for IEP teams
To: [Director name]
Cc: [Principal or SPED lead — optional]
Subject: Request: 30-min briefing — SPED progress documentation pilot (one school)
Dear [Director name],
I am [your name], [your role and relationship to the district — e.g. special education
teacher at [School] / working in partnership with the [School] SPED team]. I am writing
to request a brief meeting to discuss a controlled pilot of PulsePoint, a teacher-first
platform that helps SPED teams document IEP-aligned instruction, student progress, and
behavior supports in one place—so program leaders can see adoption and outcome evidence,
not only attendance.
Why now: We have leadership reporting that aggregates progress by student, subject, and
month (for IDEA/LCAP conversations), plus a district sandbox environment that does not
use live production student data for demonstrations.
What I am asking for: 30 minutes with you or your designee to walk through:
• Program metrics and director-level dashboard (funding view)
• Optional operations view (API/database health on the sandbox stack)
• A proposed one-school, one-semester pilot with written success criteria
Proposed pilot (starting point for discussion):
• Scope: one school, SPED case managers and selected general-education collaborators
• Duration: one semester
• Success metrics (examples): percent of case managers logging weekly progress;
progress records per month; teacher-reported time saved assembling goal evidence
• Budget framing: planning range approximately $35k–$120k depending on support level
(we can align to IDEA Part B, SPED local plan, or LCAP actions per your finance team)
I am not asking you to commit funding in this email—only to see whether a pilot fits your
priorities this year and who should be in the room (IT, compliance, principal).
If helpful, I can send a one-page summary before the meeting. Live student data would only
be used under district policy after any pilot is approved; demos use an isolated sandbox.
Would any of these times work for a Zoom or in-person briefing?
• [Option 1]
• [Option 2]
• Or a time you suggest
Thank you for your consideration.
Respectfully,
[Your name]
[Phone]
[Email]
Follow-up (5–7 school days, no reply)
Subject: Re: SPED progress documentation pilot — 30-min briefing
Dear [Name],
Following up on my note below. I can keep this to 20 minutes and bring a one-page pilot
summary only. If timing is not right this semester, could you point me to the right
contact for instructional technology or SPED pilots?
Thank you,
[Your name]
[Phone]
Send after they say yes (not in email #1)
One-page pilot summary (problem, scope, metrics, budget range, FERPA paragraph)
Funding dashboard walkthrough — screen-share or passcode on request (funding gate)
Letter-of-support template for principal (blank signature line)
Five bullets for the meeting
Problem: SPED evidence is scattered; leaders cannot see consistent program use.
Risk control: sandbox demo; pilot MOU; written success criteria before scale.
Ask: “Who owns procurement, and which bucket—IDEA, SPED, or LCAP?”
Next step: draft pilot SOW + one call with IT/compliance.
Documents to prepare
Pilot statement of work (1–2 pages)
Budget by line item (software, implementation, PD)
FERPA / data privacy summary (1 page)
Letter of support from principal + SPED lead (templates they sign)
Optional: W-9, insurance cert if district requires vendor onboarding
District does Procurement, IDEA/LCAP coding, board approval if needed, roster access policy
You doDemo, training, support, metrics reports, product fixes during pilot
LCAP · Supplemental & concentration
Applicant: District only · You: named in LCAP action · Timeline: LCAP cycle (often spring adoption for July 1)
What you should do
Ask when LCAP draft is written (usually winter–spring).
Meet LCAP coordinator + SPED director together — LCAP must show increased/improved services for high-needs students.
Provide 2–3 measurable actions they can paste: e.g. “Implement progress-documentation platform for SWD in inclusive settings; target 80% case managers logging weekly by month 6.”
Attach funding dashboard chart exports as exhibit (anonymized).
Do not ask for a separate “LCAP grant” — it's a budget line inside the district plan.
After board approval, follow district contracting same as IDEA pilot.
Documents to prepare
LCAP action language (bullet + metric + dollar amount)
Service description aligned to high-needs students / SWD
Annual cost estimate for district-wide vs pilot scale
Oakland Public Education Fund
Applicant: School, nonprofit, or fiscal sponsor · Timeline: varies by program year
What you should do
Go to oaklandedfund.org — find open RFPs (don’t cold-email without a listed opportunity).
Partner with a school site (principal signs) or fiscal sponsor if you’re not a 501(c)(3).
Frame as student outcome + teacher capacity, not “buy our software.”
Ask amount realistic for site pilot: often $5k–$25k range for innovation grants (verify current programs).