The NSF I-Corps program (National Science Foundation Innovation Corps) is a federally funded entrepreneurial training program that teaches researchers a structured customer-discovery method for evaluating whether a laboratory technology has a viable path to commercial or societal impact. It is not a product-development grant and it is not R&D funding — it funds a team’s time and travel to interview at least 100 potential customers, partners, and stakeholders over a set curriculum, so the team can make an evidence-based decision about whether to pursue a startup, a license through a university technology transfer office, an SBIR/STTR proposal, or none of the above.
For research administrators and technology transfer staff, I-Corps sits at a specific, recurring pinch point: it is usually the first time a lab-based research team receives federal funding whose explicit purpose is commercialization rather than discovery, which means the sponsored programs office (SPO) and technology transfer office (TTO) both have a role in setting it up and handling what comes out of it. This guide covers the program’s structure, team roles, funding mechanics, and — the part generic explainer content usually skips — what a research administrator actually needs to do around it.
What NSF I-Corps is and where it came from
NSF began developing the program in 2011, working with Silicon Valley entrepreneur and educator Steve Blank to adapt his “Lean LaunchPad” customer-discovery course for federally funded researchers; the first cohorts ran in 2012. The American Innovation and Competitiveness Act of 2017 gave the program a statutory basis and led NSF to reorganize its regional delivery structure into what is now called the National Innovation Network (NIN).
NSF’s own framing of the rationale is direct: many NSF-funded innovations were not failing because the underlying science didn’t work, but because the research team had no structured way to find out whether anyone outside the lab actually needed it. I-Corps teaches customer discovery — systematically testing that assumption through direct interviews — rather than assuming product-market fit and building toward it.
How the program is structured: Hubs and National Teams
I-Corps operates at two tiers, and mixing them up is the most common source of confusion for administrators encountering the program for the first time.
- I-Corps Hubs (regional training). The National Innovation Network is currently delivered through 13 regional I-Corps Hubs — university-led consortia covering the continental U.S. — that run shorter, regional-level customer-discovery courses (often called “I-Corps Sites” training in program history, now delivered under the Hub structure). Regional training is open to a broader pool, including researchers who don’t yet have NSF funding, and often serves as the on-ramp to the national program.
- I-Corps National Teams (the flagship program). A competitive, cohort-based, seven-week program run centrally by NSF, delivered fully online. National Teams cohorts run in groups of roughly two dozen teams at a time, working through a kickoff entrepreneurial-immersion session, weekly training meetings, and a closing “Lessons Learned” presentation.
A separate, related solicitation — I-Corps Hubs as a funding mechanism in its own right — funds the consortia that deliver the regional training; that is a distinct award to an institution, not something an individual research team applies for directly.
Team composition and eligibility
Every I-Corps National Teams application requires three defined roles, and NSF is specific about what each one is for:
- Technical Lead (TL). Usually the Principal Investigator — a faculty member, senior research scientist, or postdoctoral scholar with deep, direct technical expertise in the underlying discovery.
- Entrepreneurial Lead (EL). A postdoc, graduate student, staff member, or other researcher who drives the commercial investigation — in practice, this is the person doing most of the customer interviews.
- Industry Mentor (IM). An experienced entrepreneur or business leader with a track record of moving technology out of an academic lab and into the market.
Teams are capped at four members including co-leads. Eligibility to apply to National Teams runs through one of two pathways: (1) the team has a current or prior NSF research award in a relevant field, active within the past five years, or (2) the team has completed a regional I-Corps Hub training program and received a recommendation letter from Hub staff. NSF also requires an explicit connection to an institution of higher education beyond just personnel — the underlying technology has to trace back to a discovery made in the context of fundamental science or engineering research at that institution.
Curriculum and required deliverables
The National Teams curriculum is built on the same customer-discovery / Lean Startup framework Steve Blank originated: teams form and test hypotheses about their business model (traditionally mapped onto a Business Model Canvas), then go out and systematically disprove or confirm each hypothesis through direct conversation rather than survey data or internal assumption. The concrete, non-negotiable deliverable is a minimum of 100 interviews with potential customers, partners, and other stakeholders in the team’s proposed target market, completed over the seven-week training window, with the award’s period of performance extending up to 12 months to give teams scheduling flexibility around the interview requirement.
The expected end-state is not a business plan — it’s a team that can state, with interview evidence behind it, whether their initial assumptions about who would pay for this technology and why were correct, and what pivot (if any) the evidence points toward.
Funding: award amount, participation fee, and stipend structure
A National Teams award is worth up to $50,000 per team per 12-month period of performance. That figure is gross, not what the team receives in stipends — a mandatory participation fee, currently $10,000, is paid out of award funds directly to the third-party organization NSF contracts with to run National Teams training and logistics. Under the current solicitation, allowable stipend maximums are capped at up to $10,000 for the Technical Lead, up to $15,000 for the Entrepreneurial Lead, and up to $3,000 for the Industry Mentor, with indirect costs capped at $5,000 and a cost-sharing requirement attached. (These specific dollar caps are drawn from NSF’s National I-Corps Teams solicitation current as of this writing and are revised periodically — an SPO setting up an award should always confirm the caps against the live solicitation rather than this or any other secondary source.)
Because the award funds stipends, travel, and a pass-through fee rather than a traditional research budget, SPOs setting these awards up should expect a simpler-than-usual budget structure — but one where the participation-fee line item and the stipend caps are fixed by NSF rather than negotiable, which is a common source of budget-justification questions from first-time PIs.
What happens after I-Corps: the technology-transfer decision point
This is the part of the I-Corps lifecycle a generic “how to apply” explainer usually skips, and it’s the part that actually involves research administration and tech transfer staff most directly. A team that completes I-Corps has, in principle, validated (or invalidated) its core commercial hypotheses, and typically faces one or more of the following next steps:
- SBIR/STTR proposal. Graduates commonly move toward America’s Seed Fund — NSF’s branding for its Small Business Innovation Research and Small Business Technology Transfer programs — to fund the actual product/prototype development the customer-discovery evidence supports. I-Corps completion is not a formal SBIR/STTR eligibility requirement, but the customer-validation narrative it produces materially strengthens a subsequent Phase I proposal.
- Licensing through the university’s technology transfer office. If the underlying IP is owned by the institution under Bayh-Dole, a decision to commercialize typically routes through an invention disclosure (if one hasn’t already been filed) and a licensing conversation with the TTO — I-Corps interview evidence about market demand is directly useful input to that negotiation, on both the university’s and any prospective licensee’s side.
- Startup formation. Some teams spin out a company, at which point the university’s standard startup-equity, conflict-of-interest, and IP-licensing-to-founder-startup processes apply — the same processes that would apply to any faculty spinout, just triggered earlier and with better market evidence than usual.
- Return to research. A genuinely valid outcome: the interviews show no viable market, and the team returns to bench research having spent $50,000 and seven weeks establishing that, rather than spending years and a much larger grant finding out the same thing later.
For the SPO, the practical implication is that an I-Corps award on a PI’s record is a reasonably reliable early signal that an invention disclosure, a licensing negotiation, or an SBIR/STTR submission may be coming within the following year — worth flagging to the TTO proactively rather than waiting for the disclosure to arrive cold.
I-Corps vs. SBIR/STTR: not the same kind of award
These two are frequently confused because they’re sequential steps on the same commercialization pathway, but they fund fundamentally different activities. I-Corps funds customer discovery — talking to the market to test whether a commercial hypothesis holds up — and explicitly does not fund product development. SBIR/STTR (Small Business Innovation Research / Small Business Technology Transfer) funds the applied research and development needed to build and de-risk an actual product or prototype, awarded to a small business (STTR additionally requires a formal partnership with a nonprofit research institution). A team typically does I-Corps first to validate the opportunity, then applies for SBIR/STTR to build against it — though neither program formally requires the other as a prerequisite.
Frequently asked questions
Is NSF I-Corps only open to researchers with NSF funding?
No. Researchers with a current or recent (within five years) NSF award have a direct pathway into National Teams, but researchers without NSF funding can still enter through regional I-Corps Hub training and a subsequent recommendation letter into the national program.
Does the university keep ownership of any IP that comes out of I-Corps?
I-Corps itself doesn’t change IP ownership — it’s a training and market-validation award, not a research grant that generates new inventions in the way a standard R&D award might. Underlying IP ownership continues to be governed by the institution’s existing Bayh-Dole-based invention-assignment policy and any prior sponsor agreements on the original research.
How competitive is I-Corps National Teams?
NSF doesn’t publish a single standing acceptance rate, since eligibility and review are cohort-based and the applicant pool varies by solicitation cycle. Institutions with an active I-Corps Hub relationship typically report better odds for teams that complete regional training first, since Hub staff can help strengthen the application before national submission.
Is I-Corps limited to STEM fields NSF traditionally funds?
The underlying technology has to trace back to a discovery in fundamental science or engineering at an institution of higher education, which in practice keeps National Teams concentrated in NSF’s traditional disciplinary scope, though the customer-discovery methodology itself is discipline-agnostic and several regional Hubs run adapted tracks for a broader range of research areas.
Does completing I-Corps guarantee SBIR/STTR funding or a license?
No. I-Corps produces evidence — interview data on customer need and market fit — that can strengthen a subsequent SBIR/STTR proposal or licensing negotiation, but it is a separate, independently reviewed application in either case. A genuinely valid I-Corps outcome is also a team concluding, from the interview evidence, that the commercialization path isn’t there yet.
Related CASRAI resources
For the proposal-development side of federal awards more broadly, see CASRAI’s guide to NIH modular budgets and writing a budget justification narrative. For how sponsored-programs functions are typically organized relative to a technology transfer office, see departmental vs. central sponsored programs office. For the broader research-administration role that usually handles I-Corps award setup, see what a research administrator does.
