Find the repeated job.
Map the trigger, inputs, people, decisions, systems, hand-offs and exceptions. The aim is to understand the work before choosing technology.
How we work · A practical method
The method is deliberately simple: understand one workflow, agree what it looks like today, design the right assistance and review, then measure the difference without exaggerating it.
Map the trigger, inputs, people, decisions, systems, hand-offs and exceptions. The aim is to understand the work before choosing technology.
Choose a small number of relevant measures: time to first draft, review burden, rework, turnaround, quality checks or capacity that can be used well.
Specify the context, source material, output boundaries, approval point and escalation route. A workflow should be able to explain how it reached a useful output.
Introduce the workflow in a bounded way, with owners, review and a way to surface what breaks or needs adjustment.
Compare the work with the baseline. Separate useful capacity from dollars that have actually been realised, and decide what is worth improving next.
Document ownership, current assumptions and the next review rhythm. The goal is a capability the business can understand and run, not a mystery system.
The boundary
A fast demo can be useful for testing an idea. It does not answer the questions that matter once client work is involved: what context is current, who approves the output, how exceptions are handled, what happens when a vendor changes, and how the team knows whether the workflow is improving.
Hundredfold is interested in those questions because they determine whether a change survives after the initial excitement.
Questions
No. The right outcome may be a controlled pilot, a clear decision not to proceed, or a smaller improvement that makes the next step safer.
It depends on the workflow. It may include turnaround, rework, senior-review time, source-tracing effort, capacity or a client experience measure.
The design names the decisions that remain human, the information a reviewer needs, the checks to perform and the path for an exception.
Next step · The assessment
The assessment takes about five minutes. It helps identify where repeated work, context and review are getting in the way before deciding what should change.