Current-state baseline
How the work actually runs today: volume, handling time, roles, delays, correction load, exceptions — and where the evidence is thin.
Loading — one moment.
Skip to contentBuild n BloomApply for Fit Call 01 02 03 04 05 06 07 08 ROUTE / 01 ROUTE / 02 ROUTE / 03 ROUTE / 04 ROUTE / 05 ROUTE / 06 THE NEXT RESPONSIBLE STEP
Menu
System Blueprint · standalone decision product
Buy the decision before you buy the build.
For one bounded workflow, the Blueprint measures what the work costs now, what should change, what the controls must be, and what “working” will mean. Its job is a defensible decision — not a forced sale.
Modelled scenarioWORKFLOW / CONTROLLEDEvery transition keeps an owner.
- 01CaptureContext + owner
- 02RetrieveApproved sources
- 03PrepareLinked working material
- 04ReviewNamed authority
- 05RecordAccepted handoff
CONTROLLED CENTREAI prepares. A named person decides.
01 / Commercial baseline
A defined product with an independent outcome.
The current first-cohort structure is deliberately narrow. The clock starts only when the prerequisites are real.
Current first-cohort price
US$3,500One bounded workflow · paid decision product
- Target timing
- 10 business days after cleared payment, complete intake, lawful access and named reviewers.
- Scope unit
- One recurring workflow with a named trigger, owner, output and operating boundary.
- Outcome
- A written recommendation: install, narrow, automate, configure an incumbent, self-implement, defer or stop.
- Installation
- Not included and not pre-committed. Any installation receives a separate scope, price and acceptance plan.
- Credit
- Fifty percent of the Blueprint fee — US$1,750, shown transparently on the installation quote — may be credited against an installation of the same workflow contracted within 30 days. The credit is not combined with any other discount or credit.
02 / What you receive
Enough operational detail to make a real decision.
The output connects how the work actually runs, what it costs, what could go wrong and what is technically feasible. It is not a generic AI-opportunity report.
Workflow and exception map
The trigger, the permitted inputs, the steps rules can own, the steps AI can help with, the human decisions, and where the work must stop.
Economic decision
What the workflow costs now, what is realistically addressable, the assumptions, conservative scenarios, and what recovered capacity would honestly be worth.
Data and delivery boundary
Data sensitivity, permissions, providers, regions, integration feasibility, client dependencies, and the questions that need a specialist before anything is built.
Acceptance design
The representative test inputs, observable behaviours, tolerances, reviewers and evidence that will decide whether the installed system counts as working.
Claim and evidence inventory
The reusable claims and findings your client work depends on: their sources, owners, permitted uses, current state, and what would invalidate each one.
Custody recommendation
Who should keep those claims current between engagements, derived from how fast your sources change, how often the work recurs, and whether a real internal owner exists.
Written recommendation
Install, narrow the scope, use ordinary automation, configure a tool you already own, build it yourselves, defer — or do not proceed.
03 / Decision routes
“Do not build” is a valid result.
A responsible design phase protects you from paying for an elaborate answer when a smaller or existing one is better.
Install
The workflow, the economics, the access and the control boundary support a separate installation proposal.
Narrow
A smaller version reaches value sooner, or removes a dependency that would make the build fragile.
Use ordinary automation
The job is predictable enough that AI would add cost and uncertainty without adding judgment support.
Configure the incumbent
A platform you already pay for can solve the problem credibly, without a separate installed system.
Self-implement
Your team has the capability, and the Blueprint is enough to guide the internal build.
Defer or stop
The evidence, economics, access, ownership or risk do not support implementation now.
04 / What is not included
The Blueprint removes uncertainty. It does not smuggle in delivery.
The boundary keeps the decision honest and stops discovery from becoming an open-ended implementation engagement.
Included boundary
Decision-grade design
Representative workflow analysis, assumptions, dependencies, controls, evidence gaps and acceptance behaviours for the agreed job.
Separate decision
Production implementation
Integrations, migration, production configuration, new access, full security remediation and ongoing operation sit outside the Blueprint.
Find out whether the workflow deserves a Blueprint.
The no-fee Fit Call tests whether the job is important, bounded, owned and ready enough for a paid decision. It does not require confidential material.