SBIR for University Founders: Navigating Conflict of Interest, IP, and the Faculty-Startup Divide

Every year, thousands of university researchers develop technologies with clear commercial potential — sensors, therapeutics, software platforms, advanced materials — and decide the next step is a startup. The federal government has spent over $4 billion annually through the SBIR and STTR programs specifically to help small businesses commercialize innovations like these. But for faculty founders, the path from lab bench to SBIR award is riddled with institutional tripwires that have nothing to do with the quality of the science.

Conflict of interest policies. Intellectual property assignment agreements signed years ago. Primary employment rules that do not bend for tenure-track schedules. University tech transfer offices that move at their own pace. These are not edge cases. They are the default reality for any professor who founds a company and wants to pursue SBIR funding. Getting them wrong does not just weaken your proposal — it can get your application returned without review, trigger an institutional investigation, or create IP disputes that poison a startup's cap table for years.

This guide lays out the specific rules, the institutional obstacles, and the strategic choices that faculty founders face when pursuing SBIR and STTR awards.

The Primary Employment Problem

The single most disqualifying issue for faculty founders applying to SBIR is the principal investigator employment requirement. Under SBIR rules, the PI must be primarily employed by the small business at the time of award. "Primarily employed" means more than 50 percent of the PI's total professional effort is with the company — not the university, not a hospital, not a national lab.

For a tenure-track professor carrying a full teaching and research load, this is rarely true. A typical faculty appointment consumes 80 to 100 percent of professional effort. Even faculty with reduced loads — say, a 50 percent appointment after negotiating a partial leave — are at the threshold, not safely above it. Agencies take this requirement seriously. NIH, NSF, and DoD all verify PI employment status, and applications where the PI's effort split is ambiguous or implausible are returned without review.

Faculty founders have three practical options:

Take a leave of absence. Many universities offer unpaid leaves for entrepreneurial activity, typically one to two years. During the leave, the founder's primary employment shifts to the company, satisfying the SBIR requirement. The downside is real: tenure clock implications vary by institution, and a leave may affect access to lab space, graduate students, and university resources that the startup depends on.

Shift to a minority appointment. Some institutions allow faculty to reduce to a 49 percent or lower appointment while maintaining their position. This keeps the faculty member connected to the university while making the company the primary employer on paper and in practice. The negotiation is institution-specific and often requires approval from the department chair, dean, and provost.

Name a different PI. If the faculty founder cannot shift employment, the company can designate a different employee as PI — a postdoc who joined the startup, a co-founder with industry experience, or a senior scientist hired specifically for this role. This satisfies the letter of the rule but can weaken the application if reviewers see the company's strongest technical leader listed as a consultant rather than the PI.

The strategic calculus depends on the agency and the topic. At NIH, where investigator track record heavily influences review scores, the identity of the PI matters enormously. At DoD, where the emphasis is on technical approach and military relevance, a strong non-faculty PI can work. At NSF, reviewers look for a PI who can bridge the research-to-market transition, which may actually favor a non-academic lead.

STTR: The Alternative Built for University Partnerships

The STTR program exists precisely because Congress recognized that SBIR's employment rules create a structural barrier for university-originated technologies. Under STTR, the PI can be employed by either the small business or the partnering research institution. A tenured professor can serve as PI on an STTR award while maintaining a full-time faculty appointment.

The trade-off is that STTR requires a formal Cooperative Research and Development Agreement between the company and the university. The CRADA must address intellectual property allocation, publication rights, dispute resolution, and each party's scope of work. The small business must perform at least 40 percent of the work, and the research institution must perform at least 30 percent.

For many faculty startups in the first 12 to 24 months, STTR is the correct vehicle. The technology is still close to the lab, the founder has not yet transitioned employment, and the university's facilities and personnel are essential to the proposed research. STTR lets you keep your faculty position, keep your PI status, and keep access to the institutional resources that make the project feasible.

The limitation is scope. Not every agency topic is available under STTR. DoD publishes far more SBIR topics than STTR topics in any given cycle. NIH and NSF offer both programs broadly, but specific funding opportunity announcements may be designated SBIR-only. Check the solicitation before building your proposal strategy around either program.

A common and effective pattern: start with an STTR Phase I while the technology is lab-stage, then transition to SBIR for Phase II once the founder has shifted to primary employment at the company and the work has moved from university facilities to company operations. This is explicitly permitted under program rules, as long as each phase independently meets its respective program's work percentage and employment requirements.

Intellectual Property: What You Signed When You Joined the University

Every faculty member at a research university signed an intellectual property assignment agreement, usually as a condition of employment. The specifics vary by institution, but the general framework is consistent: inventions conceived or reduced to practice using university resources — labs, equipment, funding, graduate student labor, computing infrastructure — are assigned to the university. The university owns them. The inventor receives a share of licensing revenue, typically 25 to 40 percent after costs, but does not control the IP.

This creates a direct tension with SBIR. The program is designed to fund small businesses to develop and commercialize their own technology. If the core invention belongs to the university, the startup needs a license — and that license must be in place before the SBIR award is made. Agencies want to see that the company has the legal right to develop and commercialize the proposed technology. An application where the IP sits with the university and the company has no license or option agreement will raise immediate red flags.

The typical path runs through the university's technology transfer office. The process looks like this:

1. Invention disclosure. The faculty inventor files a disclosure with the TTO describing the invention, the circumstances of its creation, and any external funding that supported it.
2. Patent evaluation. The TTO decides whether to file a patent application. If yes, the university bears the cost and owns the patent. If no, the inventor may be able to request assignment back.
3. License negotiation. The startup negotiates an exclusive license to the university's patent rights in the relevant field of use. Terms typically include upfront fees ($5,000 to $50,000), annual maintenance fees, milestone payments, a running royalty on product sales (2 to 5 percent is common), and an equity stake in the company (1 to 10 percent, depending on the institution and the perceived value of the IP).
4. Execution. The license is signed, and the company can represent to funding agencies that it has rights to the underlying technology.

The timeline for this process is the part that catches founders off guard. At well-resourced TTOs — Stanford's Office of Technology Licensing, MIT's Technology Licensing Office, the University of Michigan's Innovation Partnerships — a straightforward license can take three to six months. At smaller institutions with fewer staff and less experience with startup licensing, it can take nine to twelve months or longer.

If you are planning an SBIR submission for a technology that originated in your university lab, the license negotiation should start at least six months before the proposal deadline. Waiting until the proposal is drafted to approach the TTO is a common and avoidable mistake.

Conflict of Interest: The Rules Your University Cares About Most

Federal regulations under 42 CFR Part 50, Subpart F (for PHS-funded research) and NSF's COI policy require institutions to identify, manage, and report financial conflicts of interest related to research funding. When a faculty member has a significant financial interest in a company — defined as equity exceeding $5,000 in value or more than 5 percent ownership, or income from the entity exceeding $5,000 in the past 12 months — the institution must determine whether that interest could directly and significantly affect the design, conduct, or reporting of the research.

For a faculty founder who owns 30, 50, or 80 percent of a startup applying for an SBIR award, the conflict of interest is not hypothetical. It is definitional. The question is not whether a conflict exists but how the institution manages it.

Management plans typically include some combination of:

• Disclosure. The faculty member files an annual financial disclosure and updates it when circumstances change. Most institutions use electronic disclosure systems that route automatically to the COI committee.
• Management committee review. A committee (often called the Conflict of Interest Committee or Conflict of Commitment Committee) reviews the disclosure and determines whether the relationship is permissible and what conditions apply.
• Restrictions on university resource use. The management plan may prohibit the faculty member from using university labs, equipment, or personnel for the company's work — even if the SBIR project is scientifically related to their university research. This can be operationally devastating for early-stage startups that depend on university infrastructure.
• Student protections. Most plans require firewalls between the faculty member's academic mentees and the company. Graduate students and postdocs working in the faculty member's university lab generally cannot also work on the startup's SBIR project, or if they do, their academic evaluation must be insulated from the company relationship.
• Public disclosure. Some institutions and all PHS-funded projects require public disclosure of significant financial interests related to the research, typically posted on the institution's website.

The critical tactical point: get your conflict of interest management plan approved before you submit the SBIR proposal. If your university's COI committee has not reviewed and approved your startup relationship, you cannot honestly certify compliance with federal COI requirements on the application. Filing without that approval is not a gray area — it is a false certification that can result in termination of the award, repayment obligations, and debarment from future federal funding.

Conflict of Commitment: The Other Half of the Equation

Conflict of interest gets the headlines, but conflict of commitment is what actually determines how much time a faculty founder can spend on a startup. Most universities limit outside professional activities — consulting, board service, entrepreneurial work — to one day per week during the academic year, often called the "one-fifth rule."

Running an SBIR-funded company does not exempt you from this limit. If your faculty appointment is full-time, the university expects full-time effort on university duties. The SBIR work is outside activity, and it counts against your one-day-per-week allowance.

The practical consequences are severe for faculty founders who try to run both at full speed. A 10-to-12 month SBIR Phase I typically requires substantial PI effort — writing progress reports, managing subcontractors, conducting the research, communicating with the program officer. Fitting that into one day per week while also teaching courses, advising students, writing R01s, and serving on committees is not realistic for most people.

This is another reason employment status matters. If you take a leave or reduce your appointment, the commitment constraint loosens proportionally. A faculty member on a 25 percent appointment has far more flexibility for startup work than one on a 100 percent appointment. But the leave or reduction must be formalized through university HR, not just informally agreed to with the department chair over email.

Navigating Federal Reporting and Overlap Risks

SBIR applications include several certifications that interact with the faculty-startup relationship. The company must certify that it meets all size, ownership, and place-of-business requirements; that the PI meets the employment requirement (SBIR) or is employed by either the company or the research institution (STTR); that no principal has been convicted of fraud or debarred from federal awards; and that the company has disclosed all foreign affiliations under the 2026 reauthorization's foreign risk screening provisions.

The certification that catches faculty founders most often is scientific overlap. If the professor has an active NIH R01 or NSF grant at the university on a closely related topic, the SBIR proposal must clearly distinguish the company's work from the university's work. Agencies actively check for scientific overlap between SBIR awards and the PI's (or founder's) other federal grants. Overlap findings can result in award reduction, suspension, or termination.

The defense is clear delineation. The SBIR project should address a distinct technical question, use different methods or datasets, and target a different application than the university grant. If the two projects are genuinely different, documenting those differences in the SBIR proposal preempts the overlap review. If the two projects are not genuinely different, you have a bigger problem than paperwork.

The Decision Framework: SBIR, STTR, or Wait

The right choice depends on where you are in the faculty-to-founder transition:

Full-time faculty, early-stage technology, no license yet. You are not ready for SBIR. Start the TTO conversation, file your COI disclosure, and consider an STTR Phase I with your university as the research partner. This lets you develop preliminary data, establish the company's track record, and negotiate the IP license in parallel.

Reduced appointment, license in hand, company has employees. You are likely eligible for SBIR if your appointment is below 50 percent and the company is your primary employer. File under SBIR for maximum flexibility and control over the project. Ensure your COI management plan is current and your commitment reporting is up to date.

On leave, full-time at the company. SBIR is the natural fit. You meet the PI employment requirement cleanly, your conflict of commitment issues are resolved by the leave, and your COI management plan should already account for the relationship.

Faculty founder who will not leave or reduce appointment. STTR for Phase I, with a plan to transition to SBIR for Phase II once you are ready to shift employment. Alternatively, hire a qualified PI for the company and apply to SBIR with the faculty founder in a consulting or advisory role.

None of these paths are simple. All of them require coordination between the startup, the university administration, the tech transfer office, and sometimes outside patent counsel. The faculty founders who secure SBIR and STTR funding successfully are the ones who start these conversations early — six to twelve months before they plan to submit — and treat institutional compliance as a project management problem, not an afterthought.

For researchers navigating these decisions, Granted can help you identify the right SBIR and STTR solicitations for your technology, understand agency-specific requirements, and build a proposal that addresses the eligibility and compliance questions before they become disqualifying problems.