Stood Flows · epics · ROI
From a row in the matrix to a line in the budget
A finding is worth nothing until it is owned, priced and removed. Stood Flows files findings into epics and prices them against the CRM budget, so the backlog reads as a business case before anyone opens Setup.
Epics: a backlog that files itself
Three levels, one anchor. A dashboard card is a category (backbone processes, backbone records, global flows, Apex classes, licences). An epic is a folder-level intent: fifteen shipped, renameable, archivable, extendable by the customer. An issue is one finding on one graph, with a state, a criticality, and an invisible anchor that survives every refresh.
Pricing the backlog: three ledgers, one formula
"So what?" is a fair objection as long as debt is described by volume. It stops holding once debt is described by cost. The carrying cost of surface is surface × how often it is touched × how often it fails, and it lands in three ledgers that different people own.
Euros leaving the IT budget
Licences first: seats contracted minus seats that wrote business data, at the contract unit rate, times what survives review. Storage next. Buffer is a negotiating position, priced as purchases avoided.
Admin and engineer time
Run budget: incidents traced to debt, regression per release on dead surface, admin and integration effort. Build budget: the 20% debt tax on new work. Express as time first, then money.
Business value, owned by the business
Erroring automation, integration outliers, non-acting licences. Needs a unit value from the business owner, so it sits outside the model and gets its own budget line.
■ Licences €1.45M ■ Run €268k ■ Build €200k · inputs: 4,720 seats contracted, 1,296 wrote business data (gap 73%), 40% dead surface, 40% survives review, 25% of incidents traced to debt.
Every number is yours to move: the model on stoodcrm.com is interactive, and Stood Flows supplies the inputs per org (seat gap from the licence cascade, dead surface from the matrix, erroring share from the Flows view). Rule for the order of work: delete when the cost of deleting is lower than one to two years of carrying cost.
In the app
Captured from the application itself, built from the current source tree and opened read-only on the Meridian demonstration workspace.
