Fixed scope: process map, data boundaries and candidate backlog.
Discuss scope →Do not add AI.
Change one process.
Start with recurring work, output quality and risk. Choose a workflow that can be tested, handed to an owner and improved.
Three ways to start.
Per 60-minute session; minimum 4 sessions, total from $1,560, maximum 5 people.
Discuss scope →One bounded workflow; scope cap 35 hours.
Discuss scope →One workflow. A testable operating model.
Map
Document the current process, inputs/outputs, owner, frequency, human checks and cost of failure.
Select
Choose one workflow with clear value and limited blast radius instead of pretending to automate the company in a week.
Prototype & test
Build a working version and test edge cases, quality, data boundaries, fallback and human checkpoints.
Handoff
Document ownership, operating rules, limitations, verification criteria and the next improvement backlog.
Scope the process before the demo.
Four deterministic local scenarios: AI role, human checkpoint, success signal, stop condition and handoff. No data is sent.
Internal knowledge triage
01Candidate scopeRepeatable search across an approved knowledge base where every useful answer must map back to concrete sources.
02AI roleFinds candidate evidence, compares passages, drafts an answer and surfaces uncertainty.
03Human checkpointChecks the primary source, data access and approves the answer before operational use.
04Success signalA pre-agreed reviewer-acceptance and response-time threshold for source-backed answers.
05Stop conditionSources do not cover the question, access rights are unclear or review takes as long as the current process.
06Pilot artifactWorkflow spec + source rules + test set + fallback.
Sensitivity, not a savings promise.
Formula: people × routine hours/week × 52/12 × selected recoverable share × hourly value.
This is a sensitivity scenario, not a forecast or savings guarantee. It excludes implementation, model/API, integration, QA, error, tax costs and whether recovered time can actually be monetized.
Brief text — copy manually
Good candidate
- repeatable knowledge work with a clear input and output
- documents, research, classification, drafting or decision preparation with human review
- an accountable process owner and a describable definition of good output
- a bounded pilot that does not require autonomous access to critical actions
Stop signals
- no process owner or nobody willing to review the output
- a fully autonomous safety-critical decision is required
- required data cannot be used or privacy boundaries are unclear
- the expectation is to replace people with one button without redesigning the process or controls
Artifacts, not AI theatre.
Current-state map · candidate backlog · prototype · test cases · human checkpoints · privacy/data boundaries · owner & fallback · operating notes.
Ship · Revise · Stop.
Agree output quality, human review, failure modes, data boundaries, fallback and the process owner before building. Decide against those criteria, not demo appeal.
Ship
Criteria pass; the owner accepts the workflow and ongoing review.
Revise
Value exists, but bounded quality, data or operating-rule issues need correction.
Stop
STOP when risk, missing ownership or data constraints make adoption worse than the current process.
Support with explicit limits.
4 hours per month
8 hours per month
Scope, schedule, payment, rescheduling, cancellation and refund terms are confirmed in writing before payment.
Six points are enough.
Process, people and owner, frequency, inputs, good output, and what happens if AI is wrong.
Prepare the brief →