01
Workflow discovery
Observe real executions; map triggers, inputs, systems, handoffs, decisions, exceptions and completion.
Delivery process
Turn an SOP into
an owned system.
The work begins with how the operation actually runs and ends with measurable production behaviour—not a canvas handoff.
02
Baseline
Measure volume, active time, loaded cost, waiting, errors and failure consequence.
03
Automation design
Classify every step and remove work that should not exist.
04
Prototype
Build one representative end-to-end execution with real-shaped safe data.
05
Failure design
Test unavailable APIs, malformed input, duplicate triggers, invalid AI output, rate limits and human timeout.
06
Production
Deploy with scoped credentials, observable runs, alerts, documentation and a named owner.
07
Measure
Compare hours, throughput, accuracy, cycle time and exception work against the baseline.
08
Expand
Add related processes only when observed economics and reliability justify the next build.
Failure design workshop
Break the workflow before customers do.
Representative failures are first-class acceptance criteria.
API unavailable
Retry or queue without duplicate writes.
Malformed input
Reject with an actionable reason.
Duplicate trigger
Return the existing business result.
Invalid AI output
Repair format once, then abstain/review.
Rate limit
Respect provider backoff and preserve state.
Human timeout
Expire or escalate; never imply approval.
Definition of done
The operator can run and recover it.
- Named business and technical owners
- Versioned workflow and configuration
- Test fixtures for normal and failed paths
- Scoped client-owned credentials
- Monitoring and actionable alerts
- Exception queue and replay runbook
- Baseline and post-launch measurement
Expansion rule
Do not add the next automation because the first one is exciting. Add it because the first one is stable, measured and creates a useful shared foundation.
A practical starting point
The opportunity audit produces the first two process maps.
The buyer owns the maps, ROI model and backlog whether or not Bahman implements them.