After written acceptance and 30 calendar days of in-scope stabilization, you decide who operates the installed capability. Each model names responsibilities and price; none starts automatically.
Human-reviewed workflowAn installed workflow touches approved sources, rules and claims when a service case uses them. Between cases, permissions, facts or providers can change without an active review. After launch, name who notices those changes, who decides what to do and how far that responsibility extends.
The installation includes checks and an exception path for the agreed work. During the included 30-day stabilisation, Build n Bloom corrects in-scope defects. After handover, the named operator handles routine issues unless a separate support scope assigns them to us.
For firms whose approved sources, claims or operating rules change faster than active service work uses them. A recurring review reaches what active cases do not touch.
For firms with no internal owner, high source volatility or a material exception load, where the custody role is performed rather than handed over.
How the answer is reached: the Blueprint measures how fast the firm's sources actually change, how often service cases run, and whether a named internal owner has real capacity. Where active use catches changes before they matter, scheduled or carried custody is not warranted.
Handover is complete without a recurring fee. Scheduled assurance or managed operation is optional and quoted only when its named responsibility is warranted. The written scope identifies covered workflows, activity, response boundary, hours and dependencies; software and provider usage remain separate client costs. No recurring service starts automatically.
A broad promise to keep the system working hides both risk and labour. The operating agreement names the activity, response boundary and retained human authority.
Who notices failed runs, degraded retrieval, provider changes and abnormal exception volume?
Who owns provider accounts, permissions, user administration and credential rotation?
Who investigates an operating exception, and where does professional authority remain?
What is correction, what is optimisation and what requires a new scope or risk review?
The initial system stays governable when operating defects, routine assurance, optimisation and new scope are treated as distinct changes.
An accepted behaviour does not perform as agreed. During stabilisation, Build n Bloom corrects and retests the in-scope defect.
The accepted workflow needs a named inspection of controls, versions, providers, exceptions or performance.
The same bounded workflow can be improved within an agreed responsibility and capacity envelope.
A new workflow, source, permission, integration, decision or risk boundary requires explicit assessment and agreement.
The relevant measures are selected during the Blueprint. They allow the owner to see whether the workflow remains useful without inventing a universal ROI guarantee.
Monitoring creates evidence for a decision. It does not grant the system authority to change itself.
Execute the accepted workflow version
Retain inputs, steps, latency and exceptions
Compare behaviour with written tests
A person classifies defect, drift or new need
Change the bounded logic or control
Retest and approve a new version
Usage, retrieval, exceptions and reviewer behaviour remain visible to the named owner.
Defect, provider drift, new source or expanded scope follows its own authority and acceptance route.
Time to find the applicable source, precedent or prior decision.
Human handling time from accepted intake to review-ready material.
Correction loops, unresolved questions and senior reviewer handling time.
Source coverage, required-field completeness and unsupported-claim stops.
Unowned commitments, missing decisions and time to an accepted operating record.
Exception-routing performance, defects, rollback tests and version integrity.
Share of material claims currently approved for their intended use, and share past their review condition.
Elapsed time from an invalidation event to a recorded owner decision.
Claims re-approved, replaced or retired rather than left in an unresolved state.
Accepted claims carried into a later pursuit instead of reconstructed—the direct measure of whether the inventory compounds.
The correct operating model depends on the workflow, internal owner, provider risk and recurring responsibility—not a preference for recurring revenue.
