A priced starting decision
Ignite publishes its $5,000 CAD business-plan line, $2,500 CAD systems-blueprint line, deliverables, exclusions, and vendor-neutral position before a request is submitted.
Evidence and examples
Evidence before adjectives.
ClearForge separates what can be inspected now, what is illustrative, and what cannot responsibly be claimed until client work has been measured and approved for publication.
The current proof boundary
Method evidence is not outcome evidence.
The engagement model, scope, software workflow, and decision boundaries can be inspected today. No client outcomes are published yet. That absence is more useful than replacing evidence with anonymous praise, invented metrics, or claims borrowed from an industry.
What can be inspected now
Credibility starts with visible commitments.
Continuation is a separate choice
Furnace and Anvil state their entry conditions and commercial boundaries. Neither is included in Ignite or presented as an automatic next step.
The request path shows its states
The public assessment flow exposes validation, consent, pending, duplicate, timeout, retry, and failure states instead of hiding them behind a generic contact form.
Worked example / illustrative
From an emailed request to an owned workflow.
This is an operating pattern, not a client result. It demonstrates the reasoning an Ignite blueprint should make visible without inventing a company, metric, or outcome.
- 01
Observe the loop
A customer request arrives by email. One person copies it into a spreadsheet, messages the next owner, and answers status questions from memory.
- 02
Name the operating model
Ignite maps required intake fields, ownership, state changes, exceptions, source records, and the decisions each role needs to make.
- 03
Define the system pattern
The blueprint can specify capture once, explicit ownership, visible status, exception handling, and an audit trail—without naming a vendor.
- 04
Measure before claiming
Time, error, capacity, or service improvements would be measured against an agreed baseline after implementation. None is assumed in the example.
Future case evidence
A result will need more than a good story.
ClearForge will publish a client outcome only when the evidence has these four parts.
A defined baseline
What happened before the change, how it was measured, and where the source data came from.
A bounded intervention
What changed, what did not, who was involved, and which outside factors could affect the result.
A measurement window
The period observed after release, the calculation used, and any uncertainty or missing data.
Client permission and limits
Approval to publish, appropriate anonymization, and a clear statement that one result is not a universal promise.
Begin with Ignite
Start with a decision we can examine.
An Ignite request asks for the operating strain and the change you need to make possible—not a testimonial, a preferred product, or a promised result.