Operating foundation
The approved data, workflow, access, and integration foundations needed for the first useful release—not a speculative platform build.
Furnace / Build the foundation
Turn an accepted blueprint into working infrastructure.
A separately scoped implementation that turns an accepted blueprint into working business infrastructure through ordered, testable releases.
The decision
Build the smallest foundation that changes the work.
Furnace is where an accepted operating model becomes working infrastructure. Scope comes from the blueprint, and each release must improve a real workflow while preserving an understandable path back.
- Entry condition
- Accepted blueprint
- Commercial model
- Separate statement of work
- Pricing
- Scoped from requirements
- Delivery
- Ordered releases
What the engagement produces
Artifacts the next decision can rely on.
Each output has a job to do. It should make the operation clearer, reduce ambiguity, and remain useful after the engagement ends.
Priority workflows
The highest-value manual loops translated into tested workflows with clear owners, exceptions, and decision points.
Useful reporting
Operational views tied to decisions people actually make, with definitions and source data that can be inspected.
Documented handoff
Release notes, operating instructions, decision records, and team preparation so knowledge does not remain with the builder.
A strong fit when
The conditions support useful work.
- The target operation and priority sequence have been accepted.
- A business sponsor and the relevant process owners can make decisions.
- Budget, constraints, data access, and ownership are named before work begins.
- The change can be delivered and verified in useful increments.
The boundary
What Furnace is not.
- Furnace is not included in the Ignite fee and is never an automatic next step.
- It does not begin while core requirements, sponsorship, or decision rights remain unresolved.
- It is not an all-at-once transformation with no release sequence.
- It does not hide a product sale inside a neutral planning engagement.
Begin with Ignite
A build should begin with an accepted blueprint.
New relationships still start with Ignite. If you already have equivalent discovery artifacts, the assessment request can identify what needs review before any build is proposed.