Starting small: how to test university collaboration without big risk

Working with a university doesn't have to mean a multi-year research programme, a six-figure budget, or a legal team on standby. Some of the most successful business-university relationships start with something much smaller: a short, low-commitment pilot that answers one question: is this worth doing properly?

If the idea of university collaboration has always sounded like a big step, here's how to shrink it down to something you can test in weeks, not years.

What's stopping businesses from getting started?

Many businesses assume that university collaboration requires significant budgets, lengthy contracts, a fully developed R&D strategy, or a long-term commitment.

In reality, many successful collaborations begin with a single technical question, a short pilot, or a targeted piece of exploratory work. The challenge is often not the collaboration itself, but knowing where to find the right expertise and having the confidence to take the first step.

Starting small reduces both cost and uncertainty. It gives businesses a practical way to gather evidence, assess potential partners, and decide whether further investment is justified.

Start with a question, not a project

The businesses that get the most out of a first collaboration usually aren't trying to solve everything at once. They're trying to answer one practical question: Does this technology actually work for us? Is this material fit for purpose? Would this process change save the time we think it would?

A narrowly defined challenge is easier to resource, easier to explain to a university partner, and easier to walk away from if the answer turns out to be no. That last part matters more than most businesses expect. A good pilot is designed to provide a clear answer either way, not simply to keep momentum going.

Carbonyze is a good example. The climate tech start-up originally used konfer to explore industrial pilot opportunities for its CO₂-to-methanol technology. But the conversations that followed helped sharpen the next step: before approaching pilot sites, the company needed stronger laboratory evidence. That led to a more targeted collaboration call seeking university and research partners for bench-scale proof-of-concept work, including catalyst testing, reactor development and process validation.

Low-risk ways to get a first collaboration off the ground

You don't need a formal R&D programme to get started. Some of the lowest-risk, most common entry points include:

• A short feasibility study. A few weeks of academic time to sense-check an idea before you commit real budget to it.

• A student project or placement. Low cost, fixed-term, and a genuinely useful way to get fresh eyes on a problem without a long-term commitment on either side.

• A single piece of expert advice. Sometimes what you need isn't a project at all, just an hour with someone who has deep knowledge in a particular area.

• Access to equipment for a one-off test. If you need to run a trial or assess a material and don't have the facilities in-house, a single booked session at a university lab can answer your question without requiring an ongoing relationship.

Lightricity took the student project route when it used konfer to connect with an MSc student from University College London (UCL). Rather than launching a major research programme, the company posed a clearly defined technical challenge: evaluating the energy efficiency of an emerging Bluetooth channel sounding protocol.

As a specialist in photovoltaic energy harvesting and IoT, Lightricity wanted to understand the technology's power consumption and potential applications before investing further time and resources. Working with academic supervisors and the student, the company was able to explore the protocol in detail and gather evidence that informed its next steps.

As Dr Julien Campos of Lightricity explained, "The student's work provided exactly the insights we needed to consider a proof of concept powered by our photovoltaic technology."

The project helped Lightricity assess a potentially important technology at relatively low cost and risk, demonstrating how a contained collaboration can provide valuable evidence before a business commits to something larger.

Each of these approaches can be scoped, delivered and closed out in a matter of weeks, and none requires the kind of formal, long-term agreement that puts many businesses off collaborating in the first place.

Set a small, honest budget and stick to it

Treat your first collaboration like an experiment, not an investment. Decide upfront what you're willing to spend to get an answer, and be upfront about that constraint with any university partner you talk to.

Universities are used to working within defined scopes and budgets, and being clear about limits early tends to lead to a better-matched, more realistic proposal, not a smaller one.

Agree what "done" looks like before you start

One of the most common reasons small pilots drift is that nobody agreed what finishing actually meant.

Before any work begins, agree on:

• What question you're trying to answer

• What a successful outcome looks like, and what a "no" looks like too

• A rough timeframe and a natural end point

None of this needs a lengthy contract. A short, plain-English summary of what's been agreed, even in an email, is usually enough to keep a small pilot on track.

Let the pilot make the case for what comes next

The value of a pilot extends beyond answering the original question. It also gives you a stronger basis for deciding whether further work is worthwhile.

If it works, you'll have evidence, an established relationship and a partner who already understands your business, creating a much stronger foundation for a larger piece of work. If it doesn't, you'll have spent a modest amount to avoid a much larger, costlier mistake.

Both Lightricity and Carbonyze started small. In each case, the initial collaboration wasn't about solving everything at once. It was about reducing uncertainty and deciding what to do next.

A well-scoped pilot can help you test an assumption, explore a new technology, access specialist expertise or build confidence in your next step. If the results are promising, you have the foundations for a deeper partnership. If they are not, you've learned something valuable before making a larger investment.

University collaboration doesn't have to start with a major commitment. Often, the most effective way to begin is simply by testing one idea and seeing where it leads.

How konfer helps

Finding a university partner for a small, clearly defined piece of work can feel disproportionately hard. Most outreach routes are designed for large, formal partnerships rather than quick exploratory projects.

konfer is built for this. You can post a collaboration call describing exactly the challenge you want help with, and it's shared with teams across more than 150 UK universities. Relevant researchers and departments can respond directly to you.

Post your challenge on konfer and see who responds. Or explore live collaborations to see how other businesses are already testing the water with universities before committing to more.