Plenty of people will sell you a review of your business. Fewer will tell you what you should have in your hands when it ends. The word covers everything from a two-hour brainstorm with a slide deck to a real look at your work, your systems and who can reach what. This article sets out what a paid Workflow Review owes you, so you can judge mine or anyone else’s. (Until October 2026 this engagement was called the AI Opportunity Assessment; the work is the same.)
What is a Workflow Review?
It is a short, paid engagement that looks at how a few jobs in your business actually run, works out which one is worth taking off your plate first, and writes down what that would take and save. It comes after a 20-minute fit call and before anything is built. It can end with a recommendation to build nothing yet.
It is not a product demonstration, a strategy retreat, or a discovery call that turns into unpaid consulting. The short call decides whether there is a fit. The Review is the paid work of looking closely at your jobs, and it ends in decisions you can defend after the consultant has left.
What does the Review need from you?
It needs the people who do the work, someone accountable for the result, an honest picture of the systems involved, the rules that apply to the information, and a safe way to look. It does not need a tool preference, production passwords, or a long list of ideas. It starts from your work.
- The people who do the work. The person who retypes the order or answers the same question every week knows where the time goes.
- An owner for the result. A job without an owner cannot be improved, because nobody can say what better looks like.
- The systems as they are. Where the information lives, who can already reach it, and the workarounds nobody wrote down.
- The rules. Approval limits, retention, and anything a regulator or a contract says about the data.
- A safe way to look. Fictional records, past work, or read-only access. The Review never requires production access to begin.
How does it decide what to build first?
Each candidate job is written down as the steps people take today, then weighed on three things: what it is worth, what it would take to build and keep running, and what could go wrong. The job with the best balance of value and risk, and an owner ready to use it, goes first.
Value. Time returned, mistakes avoided, customers served faster. Where a number exists, it is stated with its source. Where it does not, the Review says so instead of inventing one.
Effort. How many systems the job touches, how tidy the information is, and how much looking after the result will need. A job that is easy to demonstrate and hard to maintain ranks as hard.
Risk. How sensitive the information is, what the setup would be allowed to change, and how easy a mistake would be to spot and undo.
A job that cannot meet the security conditions is reshaped until it can, or marked as not ready. It does not get a pass because a demonstration looked good.
What may an assistant actually do?
The Review draws that line in writing for each job before anything is connected: what the assistant may read, what it may draft, what it may change, and what a person must approve. Reading and drafting are usually fine. Sending, booking, paying, deleting and changing records need a person first.
The boundary should be written plainly enough that the job’s owner can tell when it has been crossed. It should name who can pause the setup, what record is kept of each action, and how a questionable result gets reviewed. Access follows the job: an assistant that sorts an inbox does not need the billing system.
A useful habit to test for is traceability. When an assistant prepares a draft, the person reviewing it should see which records it used, so they check sources instead of trusting a summary. When a setup says a task is done, someone should be able to check the record it changed.
What should you walk away with?
Five things, in writing, that you can hand to someone who missed every meeting: the ranked list of jobs, one recommended first job with success criteria, a roadmap, the findings and unknowns, and a recommendation on whether to proceed. If a colleague can explain the plan from the documents alone, the Review did its job.
- A ranked list of jobs. Every candidate, with the value, effort and risk reasoning attached, so a leader can explain why the first item beats the third.
- One recommended first job. One, with success criteria that can be seen in normal work, agreed before anything is built.
- A written roadmap. The order of work, the dependencies, and the approvals each step needs.
- Findings and unknowns. What was examined, what was assumed, and what could not be confirmed. The unknowns are where the next surprise would come from.
- A recommendation on whether to proceed. Build the first job, fix a prerequisite first, narrow the scope, or stop. All four are legitimate outcomes.
How can you tell a real plan from a slide deck?
A slide deck lists ideas, ranks them by excitement, quotes industry savings, and assumes access will be sorted out later. A real plan describes jobs as they run today, ranks them with the reasoning shown, states what was measured, and names which systems, which permissions and who approves.
| A slide deck | A real plan |
|---|---|
| Lists ideas | Describes jobs as they run today |
| Ranks by excitement | Ranks by value, effort and risk, with the reasoning shown |
| Quotes industry savings figures | States what was measured, and what was not |
| Assumes access will be sorted out | Names the systems, the permissions, and who approves |
| Ends with “next steps: implementation” | Ends with one job, success criteria, and an option to stop |
What happens after the Review?
Nothing happens automatically. You receive the written output and decide. If you go ahead, the recommended job is built and measured in a fixed-scope Automation Pilot against the criteria the Review set. If you don’t, the findings still record what would have to change for the work to make sense later.
You can see the kind of job a first Pilot usually builds in the examples, such as a shared office inbox sorted with the urgent email on top or after-hours voicemails turned into job tickets.
That is the standard I hold my own Workflow Review to, for businesses in Jonesboro and across Northeast Arkansas. If you are evaluating one from anyone, ask for the five deliverables by name before it starts.