Funded innovation in practice: structuring ambitious projects so the numbers work

"Let's apply for funding" has killed more good technology projects than any competitor ever did.

Not because public funding is bad — it is one of the most underused levers in European business — but because of what that sentence usually triggers: months of forms, a project bent out of shape to fit a call for proposals, a decision timeline nobody controls, and a team that stopped building while it waited. By the time the answer arrives, the market moved, the champion left, and the "innovation project" is a folder of PDFs.

The instrument was never the problem. The sequencing was.

The two ways companies get funding wrong

After enough funding conversations, you notice that companies cluster into two failure modes — opposite in style, identical in outcome.

The grant-chasers start from the call. A programme opens, a consultant appears, and suddenly the company discovers it always wanted to build exactly what the call describes. Money is sometimes won. What gets built is shelfware — a project designed to satisfy evaluators instead of customers. The subsidy arrives, the value never does. Worse: the organisation learns internally that "innovation" means paperwork theatre, which poisons the next, genuine attempt.

The grant-ignorers are usually the more technical crowd. They dismiss the whole apparatus — too slow, too bureaucratic, not worth the distraction — and pay full price, at full risk, for R&D their competitor is executing at 45 to 75 percent co-financing. That is not purity. That is a self-imposed cost disadvantage on the most uncertain work the company does, adopted out of impatience with forms.

Both camps share the same root error: they treat funding as an event — a prize to win or a distraction to refuse — instead of what it actually is.

Funding is not the goal. It is a term sheet from the state for risk you were already planning to take.

Start from the project, not from the call

Read the sentence on every ambitious project that died in a spreadsheet: the numbers did not work. The idea was right, the market was there — but the cost was too high and the risk too concentrated to survive an honest board discussion. This is precisely the gap public innovation instruments exist to close. Europe has decided, as policy, to co-invest in exactly this class of risk — a decision we examine in the EU will fund your AI.

Used correctly, the sequence has a strict order:

1. Define the project that should exist — on commercial merit alone. If it would not deserve to be built with your own money, no subsidy fixes that.
2. Map it to the instruments — national and European. In Portugal that includes programmes such as STEP R&D&I and STEP Productive Innovation, alongside the broader Portugal 2030 and EU-level toolkit. Different instruments reward different risk profiles: research intensity, productive investment, digitalisation, internationalisation.
3. Structure the work so funding lowers the risk without touching the ambition — the workplan, milestones and budget shaped to qualify, while the product roadmap stays pointed at customers, not evaluators.

The order matters more than any individual step. Projects that start at step 2 end up as shelfware. Projects that skip step 2 pay retail for risk the state was offering to share.

There is also a portfolio dimension that single-project thinking misses. Instruments differ in cadence and depth: some reward long-horizon research intensity, others reward fast productive investment with measurable payback. A company with a real technology roadmap can usually decompose it into more than one fundable unit — the R&D-heavy core under one instrument, the industrialisation under another, the internationalisation under a third. That is not gaming the system; it is what the system was designed for. Public co-investment wants your project pipeline, not your project theatre.

The unpopular truth: a fundable project is usually a better project

Here is the part the anti-bureaucracy camp gets wrong. Look at what a serious funding application actually forces you to produce:

• A workplan with phases, dependencies and deliverables
• Milestones that can be verified by someone outside the project
• A budget that maps spend to outcomes
• A statement of what is genuinely new versus what is integration
• Measurable results you are willing to be held to

That is not paperwork. That is engineering discipline — the exact artifacts a well-run technology project needs anyway, and the exact artifacts most internal projects never write down. We have watched the funding-structuring pass expose fantasy timelines and unbudgeted risks before they burned real money. The evaluator was never the real audience. The team was.

We have yet to meet a project that was made worse by being forced to state, in writing, what "done" means and who will verify it.

The bureaucratic cost is real — reporting, audits, timing constraints. But the companies that complain loudest about the paperwork are frequently the ones whose internal projects have no workplan at all. The discipline was not the tax. The discipline was the point.

Momentum beats optimum: the parallel track

The most legitimate objection to funded innovation is time. Decisions take months. Ambitious teams cannot — and should not — freeze while a committee deliberates.

The answer is structural, not patient: run two tracks.

• Track one, self-funded, starts now. Build the thin slice — the risk-reducing prototype, the first workflow in production, the piece that generates learning and early value. Sized to survive on your own balance sheet: a focused, production-hardened workflow typically runs 4–8 weeks and €18k–45k — a number a board can approve without a committee.
• Track two, the instrument, carries the scale-up. The full platform, the productive investment, the R&D depth — structured so approval accelerates a moving project rather than resurrecting a paused one.

If the funding lands, the slope of the same line steepens. If it does not, you still own a working system and re-apply from evidence instead of promises — and applications backed by a running prototype read very differently to evaluators than applications backed by adjectives.

Funding should change the slope of your roadmap, never its direction. Any structure where a rejection letter can kill the project was a bet, not a plan.

What this looks like in practice

An honest composite, because real client numbers are confidential and invented ones are poison: picture a 120-person industrial manufacturer. The project that should exist is clear — automated quotation from technical drawings, feeding production planning. Commercially justified, but heavy: engineering, integration with a stubborn ERP, real R&D uncertainty in the extraction step.

Structured naively, it is a big ask against one budget in one fiscal year — so it dies. Structured properly, it splits: a self-funded first slice (quotation workflow on the two highest-volume product families, in production within a quarter, already returning hours) and an instrument-mapped second phase (the R&D-heavy generalisation and the productive-investment scale-out), with a workplan that doubles as the engineering plan. Put illustrative euros on the second phase: a €60k build co-financed at 60% nets to ≈€24k. The board approves it because the risk finally has a shape. That is what "the numbers work" means in practice — and shaping projects this way is exactly what our funding practice does, end to end: assessment, instrument mapping, structuring, and then actually building the thing.

That last clause is the differentiator we care about. Funding advice that ends at the approved application produces PDFs. We take the same projects through execution — which keeps us honest, because we have to live inside the workplans we write. Our own platform — the multi-tenant engine that renders complete websites from brand data, the retrieval-grounded assistant answering questions on this page, the publishing hub behind this article — was built under the same philosophy we sell: structure the ambition so it survives contact with a budget. It is also why we insist clients buy outcomes, not effort.

Independence first

Our philosophy, stated plainly: the objective is never to depend on funding — it is to make sure the right technological projects get built under the best possible conditions. Dependence inverts the logic; suddenly the calendar of calls is your product roadmap, and you have outsourced strategy to a funding agency. Independence keeps the causality straight: the project justifies itself, and the instrument improves its economics. One reason we operate from Portugal is that this toolkit is unusually rich here — part of a larger argument we make in why we build ambitious technology in Portugal.

Ambitious technology, built where — and structured so — the numbers add up.

If there is a project on your shelf that died in a spreadsheet, talk to us — an hour of structuring usually reveals whether it deserves a second life.