When a research-built tool stops moving, the explanation on paper is almost always the same: the grant ended. That’s true. But it isn’t really the reason — it’s the symptom. The reason is what the grant was designed to pay for in the first place.
A research grant funds a question. It buys the people, the equipment, and the time to find out whether something works. It is finite, it is tightly scoped, and — the part that quietly catches projects out — it is often use-it-or-lose-it. Every dollar is assigned before the work begins.
What that budget almost never contains is a line for what happens after the question is answered: the unglamorous work of turning a validated prototype into something a stranger can pick up and use.
The money funds the science, not the product
Most of the researchers I talk to don’t have a funding problem, exactly. For the research itself — the next study, the next question — grants are competitive but they exist. The gap is specific and narrow. It’s the money to take a thing that has been proven to work and make it into a product.
One clinician-researcher described this precisely. The science had funding. The tool did not — and a tool, unlike a paper, is not finished when the study ends:
“It needs money coming in. It doesn’t have money coming in.”
— a clinician-researcher, on a software tool after the grant
Software is not a deliverable you complete and shelve. The operating systems beneath it update. Dependencies break. Devices change. A tool that works perfectly the day the grant closes will, without anyone touching it, slowly stop working. As the same researcher put it, a project like that doesn’t stay current — it “becomes stale, potentially quickly.” A grant has an end date. The software’s need for upkeep does not.
The chicken and the egg
There’s a second trap, and it’s structural. To win the kind of grant that funds commercialization, you generally need a promising, well-scoped prototype to point at — evidence that the thing is worth scaling. But building that prototype takes money. The funding follows the promising prototype; the promising prototype needs the funding.
Researchers feel this clearly. More than one has told me, in effect: if the early version looked genuinely promising, that would be the thing worth writing the next grant around. Which is correct — and also the catch. The early, promising version is exactly the part no one has funded yet.
When the budget is already spoken for
Even inside a funded project, the structure works against continuity. Real testing surfaces real needs — a refinement, a fix, a feature the prototype clearly should have. Necessary work. But if it wasn’t in the original scope, there is no budget mechanism to absorb it. It gets deferred to “a future phase, if more funding comes through.”
So scope ends up reverse-engineered from whatever money is left, rather than from what the project actually needs. I’ve had researchers describe their side of a promising collaboration as, candidly, “pretty much zero” — not because the work lacked value, but because every dollar was already committed.
What actually changes this
The fix is not simply more money. It’s treating commercialization as its own piece of work — scoped, budgeted, and planned deliberately, instead of improvised once the grant runs dry.
In practice that means a few things. Build the first prototype so the next phase is an extension of it, not a rebuild — that single decision is the difference between a cheap next phase and an expensive one. Tie each phase to a milestone that unlocks the next round of funding: a publication, a working demo, the pilot data that makes the next application credible. And budget honestly for the fact that software needs maintenance — that “done” is not a state a digital tool ever actually reaches.
A grant is built to end. That’s not a flaw; it’s the design. The flaw is expecting a finite, question-shaped instrument to carry a product across a finish line it was never measuring. Plan for that gap on purpose, early, and the grant ending becomes a milestone instead of an obituary.
Peppermint Labs is a Toronto-based research commercialization consultancy. We work with university labs, clinician-researchers, and institutional teams across Canada to close the gap between a validated prototype and a product the world can actually use.