Start with the right problem.
A process crosses too many tools, but the right place to begin is unclear.
Where the process is too inconsistent, the source data is unavailable, or nobody can own its decisions, the next step may be to simplify the work first.
Bring the context.
- A walkthrough of the current process
- The tools, people, and decisions involved
- Representative, non-sensitive examples
Keep credentials and confidential records out of the initial brief. Any access is agreed separately through business-owned accounts.
Something you can inspect.
- 01Map the trigger, data, and handoffs
- 02Identify repeat work and exception paths
- 03Compare effort, constraints, and ongoing ownership
- Current-state process map
- Prioritized automation opportunities
- A clear build-or-don’t-build recommendation
Agree what done means.
A prioritized opportunity map with a clear recommendation, including when to leave a process manual.
A recommendation, not a promise of savings. Scope, schedule, fees, and any ongoing service are agreed before work starts.