
For student founders working on technical ideas, one of the most confusing questions can be surprisingly basic: Who actually owns what you’re building?
That question can get complicated quickly when a startup grows out of work done at a university. Maybe you first encountered the technology in a class. Maybe you worked in a faculty lab, received university funding, used university resources, or developed the idea while working as a research assistant. For a student trying to turn an idea into a company, it can be difficult to know when something is truly yours and when the university may have rights to the underlying intellectual property.
To better understand how student founders should approach those questions, I spoke with Matt Rannals about university intellectual property, technology transfer, commercialization, and the transition from academic research to a startup. Matt is a Principal with the University of Virginia Licensing & Ventures Group (LVG), where he works with UVA researchers and founders to identify and develop new venture opportunities and supports the UVA LVG Seed Fund. He also helps lead UVA’s NSF I-Corps programming, working with researchers and entrepreneurs on customer discovery and commercialization. Before moving into venture development, Matt earned his Ph.D. in Neuroscience from UVA and completed research fellowships at Johns Hopkins, Penn State, and the University of Pittsburgh.
One of the clearest themes from his answers was that founders do not need to have everything figured out before reaching out for help. In fact, getting clarity earlier can make the process much easier later.
Reach Out to Tech Transfer Earlier Than You Think
A student founder might assume that a technology transfer office only becomes relevant once there is a patent to file or a company ready to license university technology. Matt’s view is broader. He explained that reaching out early can be useful because technology transfer professionals work with intellectual property and commercialization every day and can often connect founders with relevant business, regulatory, legal, and university resources.
That means the first conversation does not necessarily need to be about negotiating ownership or signing a license. It can simply be a way to understand what resources exist, whether an ownership question needs to be resolved, and what the appropriate next steps might be. For student founders especially, that can be valuable because it is much easier to clarify those questions early than to discover an IP issue after a company has already been formed or investors have started asking about ownership.
University Ownership Is More Nuanced Than Most Students Think
One of the biggest misconceptions around university IP is that there is a single trigger that determines whether the school owns something. Matt explained that the reality is more nuanced. Universities have obligations to manage intellectual property developed using certain grants and resources, particularly when taxpayer-supported research funding is involved, but factors like university funding, lab resources, faculty involvement, and employment status should be thought of as a checklist rather than automatic triggers.
He gave two useful examples that show the difference. If a student learns about a technology in class and later builds something independently with friends, that technology generally would not be owned by the university. On the other hand, if a student is working as a research assistant with a faculty advisor and develops an invention as part of the objectives of a funded research grant, the university would be involved in filing the patent with the inventors. There are, of course, many situations that fall somewhere between those two extremes.
That is probably the most important takeaway for student founders worried about university ownership: do not assume either that the university owns everything or that it owns nothing. The details of how the invention was developed matter, and a technology transfer office can help evaluate the circumstances of a particular project.
A Good Research Project Is Not Automatically a Good Startup
Ownership is only one part of commercialization. Even when the intellectual property situation is clear, there is still a much bigger question: should the technology actually become a company?
Matt drew an interesting distinction between academic research and commercial opportunity based on the kinds of questions being asked. Academic work may begin with a technical hypothesis, while commercialization requires founders to start asking who is actually ready to buy the product or service. Researchers already have experience forming hypotheses, designing ways to test them, and interpreting evidence. Matt’s point was that those same skills can be redirected toward understanding markets and customers.
For a technical student founder, that is an important shift. Building something scientifically or technically impressive is not the same thing as proving that there is a market for it. Commercialization begins when the founder starts applying the same discipline used in research to questions about customers: Who has this problem? How important is it? How do they currently solve it? Who makes the buying decision? What evidence would convince them to change?
What Makes a Founder Look Ready to Build a Company?
When I asked Matt what signals make him believe that a founder is actually ready to build a company around a technology, his answer was not about patents, pitch decks, or even how advanced the technology was. He pointed instead to a committed team that understands its customer.
That does not mean the team needs to know exactly what the company will look like five years from now. Matt acknowledged that successful companies can change direction and pivot as they learn. What matters is whether the team has done enough work to understand how its customers make decisions. A team that develops that capability is also much better positioned to recognize new opportunities and change course when its original assumptions turn out to be wrong.
That is especially relevant for university startups, where it can be easy for founders to become focused almost entirely on the technology. The technology may be what makes the company possible, but understanding the customer is what determines whether it can become a business.
Licensing Matters Before Serious Fundraising
If a company is built around university-owned intellectual property, the founders also need to think about the rights the startup has to commercialize that technology. Matt explained that when a startup is commercializing university research, investors will typically want to see a license agreement in place before funding the company. If the technology is still early and the founders are continuing to evaluate it, a simpler option agreement may sometimes make more sense.
The university’s goal, as Matt described it, is to help put the technology with a commercial partner capable of moving it forward rather than allowing it to sit undeveloped. Licensing agreements can therefore include due-diligence milestones that the startup agrees to achieve as commercialization progresses.
For student founders thinking about raising capital, the practical implication is straightforward. You do not want to reach serious investor conversations and only then begin trying to understand whether your company actually has the rights to its core technology. If university IP is involved, understanding the licensing path early can remove a major source of uncertainty later.
The Hard Part Is Often Knowing Which Resource You Need
Universities can offer an enormous number of resources for founders: advisors, funding programs, industry connections, entrepreneurship centers, translational programs, competitions, and more. Interestingly, Matt did not think the biggest problem was necessarily that students were overlooking one specific resource. Instead, he pointed to how difficult it can be to know which resource is useful at which point in the company’s development.
His broader advice was that founders need to learn how to take in a lot of different advice and then decide what action to take. No single advisor will always know exactly what a founder should do next. Building a broad network, however, increases the odds that when a particular problem comes up, the founder knows someone who can provide the right expertise, introduction, funding opportunity, or perspective.
That is a useful way to think about university entrepreneurship resources generally. The goal is not necessarily to participate in every program available. It is to understand what you need at the current stage of the company and build enough relationships that you know where to turn when a new problem appears.
Start by Talking to People
When I asked Matt what he would tell a student sitting on a promising technical idea but unsure whether to turn it into a company, his answer was simple: talk to people.
That does not have to begin with a formal customer-discovery program or a declaration that you are launching a startup. It can start with conversations with people who understand the industry, have seen similar technologies, or can introduce you to others who know the space. Those early conversations can give founders a much better perspective on where their technology fits and whether there may be a real commercial opportunity around it.
That may be the broader lesson behind the entire conversation. A student founder does not need to understand IP ownership, licensing, customer discovery, fundraising, and commercialization all at once. But they do need to start asking the right questions early enough to learn.
And if your startup involves university research, faculty work, grant funding, lab resources, or other university support, “Who actually owns this?” is probably one of those questions worth asking sooner rather than later.