Product-Based Funding
What is Product-Based Funding?
Product-based funding is a budgeting model that funds long-lived product or value-stream teams with a stable budget, reviewed regularly against outcomes, instead of funding individual projects with fixed scope.
Updated November 2026 · 2 min read
Project funding vs product funding
Traditional budgeting funds projects: a defined scope, a start date, an end date and a team assembled for the duration. Product-based funding turns this around. It funds a persistent team, or group of teams, responsible for a product or value stream, and lets that team decide what to build within agreed goals.
| Project-based funding | Product-based funding | |
| Unit funded | A project with fixed scope | A product or value stream |
| Team | Assembled for the project, then disbanded | Stable and long-lived |
| Approval | Business case per project, often annually | Budget per product, reviewed quarterly or semi-annually |
| Changing priorities | Requires change requests and re-approval | Team re-prioritizes its backlog within its guardrails |
| Measure of success | On time, on budget, on scope | Outcomes: adoption, revenue, cost, customer value |
Why organisations move to it
Software and digital products are never really finished, so funding them as projects creates artificial endings and restarts. Each new project means a new business case, a new team and lost knowledge. Product-based funding keeps teams together, which builds expertise and speed. It also makes it easier to shift money toward what is working, because funding decisions are made against outcomes every quarter rather than locked in once a year. The shift is a core part of the project to product movement and of Lean Portfolio Management (LPM).
An example
An insurer used to approve around 200 IT projects a year, each with its own business case. It reorganises into 14 product areas, such as claims, quoting and customer portal, each with a stable team and an annual budget envelope. Every quarter, a portfolio forum reviews each area's outcome measures and adjusts the next quarter's funding. When digital claims adoption beats its target, the forum moves budget there from a product area that has stalled, without starting a single new project.
What it takes
- A clear map of products or value streams, each with an accountable product leader
- Outcome measures for each product, agreed with finance and the business
- A regular funding review, often called a participatory budgeting or portfolio forum
- Guardrails for large investments, which may still need a lean business case
- Finance support for new reporting, including how to treat capital allocation and capitalization
Common pitfalls
Some organisations rename projects as products without changing how money moves, so nothing really changes. Others fund products but keep annual, line-by-line approval, which removes the flexibility the model is meant to create. A third trap is losing financial control: without outcome measures and regular review, stable funding can become a blank cheque. Finance needs to be a partner in the design from the start, not informed afterwards. Related models include lean budgeting and Beyond Budgeting, along with agile portfolio management.
Frequently asked questions
What is the difference between project funding and product funding?
Project funding approves money for a defined piece of work with fixed scope and end date, then disbands the team. Product funding gives a stable budget to a persistent team responsible for a product or value stream, reviewed regularly against outcomes. Product teams decide what to build within that budget; project teams deliver a predefined scope.
Does product-based funding mean losing financial control?
It should not. Control moves from approving individual projects to setting budgets for products and reviewing their outcomes regularly, often quarterly. Finance still sets guardrails, tracks spending and can move money between products. Done well, it gives leaders more frequent chances to redirect funds than an annual project cycle does.
How do you start moving to product-based funding?
Most organisations start small. They pick one or two product areas with stable demand, give them a dedicated team and budget, agree outcome measures, and review results each quarter. Lessons from the pilot shape how products are defined, how finance reports spending and how funding decisions are made before scaling to the wider portfolio.
Related terms
Project to Product
Shifting funding from temporary projects to long-lived product teams.
Lean Portfolio Management (LPM)
Funding value streams, not projects, and adjusting investment often.
Participatory Budgeting
Stakeholders decide together how a shared budget is split.
Lean Business Case
A short, hypothesis-driven case with an MVP to test the idea first.