Your annual planning cycle consumes four months. 200 teams write business cases. Every business case inflates estimates to survive the cut. Every approved project receives a fixed budget tied to a scope that will change before the first sprint ends. And 40% of your technology staff's time goes not to building software but to estimating, justifying, re-baselining, and defending budgets for work they haven't started yet.
The annual planning cycle is where organizational dysfunction crystallizes into financial concrete. In September, every team writes a business case. The business case requires a scope definition for work that hasn't been designed, an estimate for work that hasn't been started, and a timeline for work that hasn't been planned. The estimate is wrong before the ink dries. Everyone knows it is wrong. And the entire organization spends four months pretending it is right — because the alternative, admitting that complex software development cannot be accurately estimated 12 months in advance, would require a fundamentally different funding model. This service builds that different model.
Product funding replaces the annual project-based budgeting cycle with persistent capacity allocation to product teams. Teams are funded based on strategic priority, not estimated project costs. Success is measured by outcomes delivered (revenue impact, customer satisfaction, cost reduction), not outputs produced (features built, milestones hit, budget consumed). And the 40% of time currently spent on estimation, business case writing, re-baselining, and budget defense is redirected to the work that the business actually values: building software that customers use.
The annual planning cycle at a typical Fortune 500 technology organization, broken into the activities that consume time without producing value.
Product funding is not just a change in how money flows. It is a change in what the organization values, how it measures success, and who makes decisions about investment.
From portfolio structure design through CFO alignment — every deliverable designed to make the transition from project to product funding successful, sustainable, and financially transparent.
The first step in product funding is defining what the products are. Most organizations have a portfolio of 80-200 active projects that do not map cleanly to business capabilities or customer outcomes. Multiple projects may serve the same customer journey, the same business process, or the same technology platform — without anyone recognizing the duplication. We map the organization's technology investments to value streams: end-to-end flows of business value that serve a specific customer segment or business capability. Each value stream becomes a candidate for persistent product team funding. The typical enterprise consolidates 120 active projects into 22 persistent product teams — each with a clear domain, a clear owner, and a clear set of outcomes to deliver.
Quarterly capacity allocation replaces the annual budgeting cycle with a 90-day investment rhythm. Each quarter, the portfolio governance body reviews three inputs: outcome data from the prior quarter (did each product team produce measurable business value?), strategic signals (has anything changed in the market, the competitive landscape, or the business strategy that should shift investment?), and capacity requests from product owners (does any team need more or fewer people to pursue its current objectives?). Based on these inputs, the governance body confirms, increases, decreases, or redirects capacity across the portfolio. Teams that are producing value keep their capacity. Teams that are not producing value are redirected or wound down. The decision is made with evidence, not estimates — and the feedback loop is 90 days, not 365.
Product funding only works if the organization can measure the outcomes it is funding. Most organizations measure outputs (features delivered, story points completed) because outcomes (revenue impact, customer retention, cost reduction) are harder to measure and slower to materialize. We design outcome metrics for each product team that are specific enough to be actionable, measurable within a quarter, and attributable to the team's work. We also build the measurement infrastructure — dashboards, data pipelines, and reporting cadences — that make outcome data available to the portfolio governance body at every quarterly review. The governance question becomes "is this investment producing the business impact we expected?" rather than "is this project on schedule and on budget?"
The full business case is a relic of capital budgeting that was designed for building factories, not funding software development. It requires detailed scope, precise cost estimates, multi-year ROI projections, and risk assessments — all based on information that doesn't exist yet. The lean business case acknowledges this uncertainty honestly: it states the strategic hypothesis (we believe that investing in X will produce outcome Y because of evidence Z), the investment required (team size and quarterly cost), the success metrics (we will measure A, B, and C to determine if the hypothesis is correct), and the decision point (we will evaluate at the end of Q2 and decide whether to continue, pivot, or stop). The lean business case fits on one page, takes 2 hours to produce, and is designed to be updated as the team learns — not defended against change requests.
Portfolio governance in a product-funded model operates on a quarterly rhythm with three key forums: the quarterly portfolio review (where the governance body reviews outcome data, adjusts capacity allocations, and makes strategic investment decisions), the monthly portfolio sync (where product owners share progress, surface dependencies, and flag risks that may require governance attention), and the continuous escalation path (where product owners can request mid-quarter reallocation when unexpected opportunities or threats emerge). Each forum has clear decision criteria, pre-read discipline, and a commitment to decide in the meeting — not defer to the next one. The governance body's job is not to approve individual features or design decisions. It is to ensure that the portfolio's investment mix aligns with the organization's strategic priorities and is producing measurable value.
The most common objection to product funding comes from the CFO: "How does this work with our financial planning, our CapEx/OpEx classifications, and our chart of accounts?" The answer is: product funding operates within existing financial governance, not outside it. We design the mapping between persistent team costs and enterprise financial structures: team capacity costs map to cost centers (the team is a cost center, replacing the project as the financial unit), CapEx/OpEx classification uses activity-based tracking (the same team produces both capitalizable development work and operational maintenance), and quarterly capacity allocations feed into the enterprise's rolling forecast model. The CFO sees the same financial data in the same formats through the same systems — the only difference is that the underlying cost unit is a team, not a project. This alignment is essential: product funding that operates outside the CFO's governance framework will be killed in the next budget cycle.
Most executives cannot answer a simple question: "What is your technology organization working on right now?" The answer is scattered across project management tools, Excel trackers, status reports, and individual heads. Portfolio Kanban provides a single visual representation of the entire technology investment portfolio: what products are actively funded, what outcomes they are pursuing, what stage of value delivery each is in, where work is blocked or at risk, and how investment is distributed across strategic themes. The board becomes the primary artifact for portfolio governance meetings — replacing slide decks with a live, continuously updated view of the organization's technology investments. When leadership asks "should we fund this new initiative?" the answer is visible on the board: here is everything we are currently funding, here is how it is performing, and here is what we would have to deprioritize to fund the new initiative.
Product funding without strategic alignment produces fast teams working on the wrong things. OKR integration creates a clear line of sight from organizational strategy to product team objectives: the organization's annual OKRs define strategic priorities, portfolio governance allocates capacity to product teams aligned to those priorities, and each product team's quarterly objectives connect directly to one or more organizational OKRs. This creates bidirectional visibility: leadership can see which teams are pursuing each strategic objective and how much capacity is allocated to it, and product teams can see how their work connects to the broader strategy. When the strategy shifts — as it inevitably does — the OKR framework provides the mechanism for realigning capacity at the next quarterly review.
Switching from project to product funding overnight is neither possible nor advisable. The transition follows a phased approach: pilot with 3-5 product teams that have clear domain boundaries and measurable outcomes, demonstrate value within two quarterly cycles, expand to 10-15 teams with governance body evolution, and complete the transition with full portfolio migration. Each phase includes stakeholder alignment (particularly CFO and business unit leaders who must endorse the new model), communication strategy (explaining to teams how their work changes and how their success will be measured), and governance body evolution (transitioning the project portfolio management office into a product portfolio governance function). The transition takes 18 months from pilot to full portfolio — and at no point does delivery stop or slow down, because the teams keep building while the funding model evolves around them.
A Fortune 200 retailer managed 120 active technology projects through an annual budgeting process that consumed four months of leadership attention and 40% of team time. Meridian consolidated the portfolio into 22 persistent product teams aligned to value streams, replaced annual budgets with quarterly capacity allocations governed by OKRs, and implemented lean business cases that replaced 30-page documents. The annual planning cycle was eliminated entirely. Time-to-value dropped from 9 months (the time between funding approval and first customer impact) to 6 weeks. Budget defense time — estimation, business case writing, change requests, and re-baselining — dropped 87%. The CFO signed off because the financial model mapped team costs to cost centers and CapEx/OpEx classifications within the existing chart of accounts. No financial systems changed. Only the unit of investment changed — from project to team.
A global bank with a $340 million annual technology budget had never reallocated investment mid-year — because the annual budgeting model locked allocations for 12 months regardless of performance. Meridian implemented quarterly capacity allocation with outcome metrics for every product team. In the first year, the quarterly governance body reallocated $28 million — 8% of the total budget — from products that were not producing measurable value to products that were producing outsized returns. Three product teams were wound down (their domains were absorbed by adjacent teams). Two new product teams were created to pursue market opportunities that emerged after the annual plan was set. The bank's CTO described the impact: "For the first time, we could respond to what we learned instead of defending what we planned."
A PE-backed platform company that had acquired three businesses in 18 months faced three separate annual planning processes, three separate portfolio governance bodies, and three separate definitions of "project success." Meridian unified all three into a single product portfolio with quarterly capacity allocation, shared outcome metrics, and a single governance body. The unified model eliminated 14 weeks of annual planning time across the three organizations, created portfolio-level visibility that the PE sponsors had been requesting since the first acquisition, and enabled cross-company reallocation that would have been impossible under three separate annual budgets. Engineering velocity across all three businesses increased 2.4x — not because engineers worked faster but because they spent 87% less time on estimation, business cases, and budget defense.
We spent four months every year planning and four months every year replanning. Our teams wrote business cases for work they hadn't designed, estimated costs for work they hadn't started, and defended budgets for work that had changed by the time anyone reviewed it. Meridian showed us the math: 40% of our technology organization's time went to budgeting activities, not building activities. We eliminated the annual cycle, moved to quarterly allocation with outcome metrics, and gave product owners authority to prioritize within their capacity. Our teams now spend 90% of their time on delivery. The other 10% is governance, not theater. My CFO approved the change because we designed it within our existing financial model. She didn't have to change anything in her systems. She just started seeing "product team" where she used to see "project."
In twenty years of running technology at banks, I have never been able to reallocate investment mid-year. The budget was locked in December. If a market opportunity emerged in March, the answer was always "put it in next year's plan." With quarterly allocation, I reallocated $28 million in the first year — away from products that weren't producing value, toward products that were producing outsized returns. And I created two entirely new product teams to pursue opportunities that didn't exist when the year started. For the first time in my career, my investment portfolio responds to what we learn rather than defending what we planned. That is what product funding actually means.
Our PE sponsors acquired three companies and asked for a simple thing: a single view of what the combined technology organization was working on and whether it was producing value. After 18 months and three separate annual planning cycles, they still didn't have it. The unified product portfolio gave them the visibility they needed in one quarterly review. They could see every product team, every outcome metric, every capacity allocation — across all three businesses, on one board. And they could make cross-company investment decisions for the first time. The velocity increase was a bonus. The real value was that the PE sponsors finally trusted that the technology organization was investing in the right things — because they could see the evidence, not just the business cases.
Request a Portfolio Funding Assessment — a 3-4 week diagnostic that quantifies how much time your organization spends on budget theater and designs the transition to product funding.