NSF 26-507: Fostering Interdisciplinary Networks to Develop Emergent and Responsive Solutions Foundry (FINDERS FOUNDRY)

NSF 26-507: Fostering Interdisciplinary Networks to Develop Emergent and Responsive Solutions Foundry (FINDERS FOUNDRY)

NSF 26-507: FINDERS FOUNDRY is the open NSF program that connects school-side and innovation-side teams around one objective: create practical solutions that respond to real learning and workforce problems, with AI as a recurring focus area, and then scale what works.

The solicitation is active and was posted in March 2026. It is not a single-purse scholarship. It is a structured program with two distinct stages of support (Planning and Development), two different submission tracks, and clear rules on eligibility, leadership composition, and sequencing. Because the page includes separate due dates, this is useful for applicants who can already start planning and are ready to submit a planning concept in the current cycle.

Key details at a glance

What this opportunity is, in practical terms

This is one of the few NSF programs that explicitly requires mixed stakeholder participation from the start, not as a compliance formality.

If your project idea assumes education, technology, and policy must move together, this program is designed for you. The solicitation explicitly describes collaboration among K-12 educators, technologists, researchers, parents or guardians, and K-12 students and families as a core design principle. In review language, this means you are expected to have a pipeline of co-design and practical feedback rather than a polished prototype built in isolation.

The program also emphasizes “emergent and responsive” solutions. That phrasing matters. It is not asking for only broad pilots; it rewards teams that can respond to signals from real users, adjust quickly, and then move from concept to implementation over two phases.

Why this is currently strong for 2026–2027 planning

The posting has explicit 2026 activity with structured due dates and a built-in progression rule. That makes it strategically useful in two ways:

1. You can apply for Planning this cycle and only continue to Development if funding and validation justify it.
2. You are not forced into a one-shot proposal gamble.

That path is valuable because you can use Planning grants to test evidence, prototype responsibly, and build enough user signal to justify scaling. For teams with a credible education-tech concept that still needs user validation, this is materially better than a single large proposal where all expectations are immediate.

Because the page is marked as an active funding opportunity and posted in 2026, this is aligned with the target window for 2026 and potentially 2027 implementation. The planning deadline being in late 2026 means Development phase candidates can still emerge for later stages without requiring a full implementation budget upfront.

What is funded and what is not

The most common misunderstanding is treating this as a single full-size grant with immediate scaling requirements. In practice, it is a staged funnel.

Funding offered

• Planning: up to 50 awards, each up to $50,000, generally for about 2 months.
• Development: up to 20 awards, each up to $300,000 for one year.
• Total anticipated program funding: around $8.5 million.

What is expected in planning

The solicitation frames planning as more than a concept note. It is a stage where teams can explore and test ideas against real K-12 conditions.

To increase odds of continuation into Development, planning work should usually produce:

• a real user-anchored problem statement
• evidence of cross-role participation and ownership
• clear user path from prototype to measurable outcomes
• a practical prototype or wireframe path that can be tested

What Development expects

Development funding is not an automatic extension. It is only for teams that have already proven progress and received a Planning award. Expect stronger scrutiny on feasibility, milestone reporting, and rollout planning.

Who can apply, by eligibility logic

The solicitation requires a leadership team with one representative from each of four groups:

• K-12 educators
• Technologists
• Researchers
• Parents or guardians

Unaffiliated individuals are explicitly not eligible. The team is not a “solo PI plus friends” model; it is an ecosystem model.

Additional constraints from the official page:

• One Planning proposal per organization.
• One Planning and, if awarded, one Development proposal per PI/co-PI.
• A PI does not need a required terminal degree.
• Unclear organizational eligibility specifics and compliance language are specified in the full solicitation and should be followed exactly.

If your team currently has a school partner, an implementation designer, and a research lead, this may already be on the right track. If your team does not yet include parents or guardians in formal project roles, you should fix that before submission.

Application process: what to do and why order matters

The solicitation provides two relevant deadlines and a strict sequencing model:

• Full Proposal deadline: May 27, 2026.
• Planning proposals deadline: November 18, 2026.

The official channel references submission through Research.gov or Grants.gov depending on your setup. The solicitation explicitly says Preliminary proposals and letters of intent are not required.

Phase 1: Planning (first pass)

Use Planning to establish validity quickly:

1. Define the specific pain-point in K-12 learning or workforce preparation, ideally one that can be shown through direct inputs from students, educators, and families.
2. Build the leadership team to include all required stakeholder roles.
3. Keep scope small enough for a 2-month deliverable timeline.
4. Provide a practical roadmap from issue to prototype.
5. Define measurable outcomes tied to learner impact and readiness for future workforce participation.

Phase 2: Development (second pass)

The Development application is only meaningful if Planning succeeds. The solicitation points to three major progression milestones:

• wireframe validation,
• prototype testing,
• MVP deployment,

and then broader public demonstration. This is a real sequencing expectation, not soft language.

Submission architecture

The solicitation and program pages point to NSF and grants systems support channels:

• Research.gov questions and support.
• Grants.gov support for grant submission support.
• NSF FINDERS FOUNDRY contact inbox ([email protected]; phone listed in the program page).

You should set your AOR and account access early because many NSF submissions fail from technical bottlenecks rather than weak ideas.

Application package and evidence checklist

Below is a practical checklist based on what the program states and what NSF grants generally require in this segment:

Minimum team design evidence

• Proof of team composition and role ownership with the four stakeholder groups.
• Documentation showing who is leading design, technical development, school implementation, and user research.
• Explicit confirmation that unaffiliated individuals are not leading as independent submissions.

Core narrative evidence

• Problem definition grounded in K-12 needs, not abstract technology capability.
• Why the selected approach is scalable and responsive, not fixed.
• How AI literacy or workforce readiness is central, not decorative.

Proposal mechanics

• Follow official due date and time requirement (5 p.m. submitting organization’s local time).
• Use NSF formatting requirements from the current PAPPG.
• Include budget assumptions consistent with phase: Planning for short-cycle work, Development for implementation.

Budget guardrails

The program specifically states voluntary committed cost sharing is prohibited. If a draft budget assumes matching funds as mandatory, remove that language.

Best-fit applicant profile (and weak-fit profile)

This program works best for:

• K-12 schools or school networks that can contribute real use cases and access.
• University-affiliated innovation labs partnering with schools on practical prototypes.
• Civic-tech teams where parents and guardians can genuinely participate in iteration.
• Teams that can run short design sprints and show measurable progress.

This program is weak fit for:

• Teams without a concrete K-12 implementation pathway.
• Teams built mainly around a single technical founder without school-side representation.
• Applications designed around speculative R&D disconnected from learner impact.
• Teams trying to apply to bypass user partnership requirements.

What reviewers likely score well

Given the language in the solicitation and the program’s priorities, a strong submission should make these things explicit:

• Co-design is real, not rhetorical.
• K-12 participants contribute in problem framing, testing, and iteration.
• The idea is responsive, not rigid.
• The technical design reduces friction for educators and families.
• The team knows what “minimum viable product” means in this domain.

Reviewers also penalize vague user outcomes, unrealistic timelines, and leadership structures that look postured rather than operational.

Common mistakes and how to avoid them

1) Submitting a lone-PI concept

Not all grants require strict PhD-level leadership, but this one does require an authentic cross-sector team. A technically strong individual cannot substitute for team role coverage.

2) Ignoring the Planning-to-Development sequence

If you overcommit to full-scale implementation at the planning stage, you reduce credibility. Planning should be about validated, bounded early progress.

3) Confusing local pilots with K-12 co-design

The program centers the user group in identification, design, testing, and refining. It is not enough to present a school as a future site.

4) Budget assumptions based on cost-sharing

Cost sharing is prohibited if committed voluntarily. Keep the budget clean and realistic.

5) Missing technical submission basics

Even an excellent concept can fail on compliance if Research.gov/Grants.gov setup is delayed. Contact details are not optional checkboxes in a late submission.

6) Duplicating proposal language across phases

A Planning proposal should not read like a full implementation bid. Keep the Development intent separate and conditional on Planning progression.

Timeline planning for teams that want to start now

If you are targeting late 2026 Planning submissions, create a reverse schedule:

1. Week 1–2: lock stakeholder roles and written responsibilities.
2. Week 3–4: draft planning workplan tied to measurable student and educator outcomes.
3. Week 5: complete budget and compliance checklist.
4. Week 6: internal dry-run with full proposal instructions (format + system path).
5. Week 7: internal review for role coverage and user co-design evidence.
6. Week 8: submit with buffer for internal signature and technical queue.

If your team is already at Development readiness from prior pilots, keep planning lean but rigorous and leave room to demonstrate what you can test quickly.

Required official links

• Solicitations page (full text and requirements): https://www.nsf.gov/funding/opportunities/nsf-finders-foundry-national-science-foundation-fostering-interdisciplinary/nsf26-507/solicitation
• Program page (guidelines, events, contacts, official dates): https://www.nsf.gov/funding/opportunities/nsf-finders-foundry-national-science-foundation-fostering-interdisciplinary
• NSF Proposal systems and support: Research.gov and Grants.gov from the NSF solicitation page
• NSF contact point: [email protected] and (703) 292-4228

FAQ for rapid decision-making

Is this only for U.S.-based applicants?

The solicitation is a U.S. NSF program and aligns with NSF administration and U.S. systems. If your team includes international collaborators, coordinate eligibility through an eligible U.S. submitting organization and the official proposal rules.

Can students apply?

The solicitation is not written as a student-only program. It is an institutional/team grant program where eligible organizations submit proposals. Team structure matters far more than individual status.

Is one project enough for both full proposal and Development?

No. Development comes after Planning award in sequence, and not all planning winners can assume Development funding.

Are there degree requirements?

The solicitation explicitly states no PI degree requirement is listed. That does not eliminate other role and compliance checks.

Is this a good program for a technical startup with no school partner?

Only if you can assemble the required stakeholder model and show real school-level implementation. Without an educator-led route, readiness is weak.

What to do next before application

Before writing begins, confirm each of these items as true:

• Team includes all required sectors at leadership level.
• Organization eligibility is confirmed for submission.
• You know which proposal system your institution uses and who the AOR is.
• You have a clear 2-month plan with outputs that can be evidenced.
• You can articulate a Development escalation path without claiming guaranteed continuation.
• Contacts and phone/email support are bookmarked.

If the answers are all “yes,” this is likely a high-fit program. If some are “not yet,” do that pre-work first. The idea is strong; NSF’s process discipline is stronger.