Adoption and strategy
Where to start with AI: pick the smallest painful workflow first
Do not start with a strategy. Start with the smallest painful workflow you can name. Here is how to find the one first use case that pays for itself, teaches your team, and gives the regulator nothing to flinch at.
By Seb Lawson · 6 July 2026 · 4 min read
Start with the smallest painful workflow you can name. Not the biggest opportunity, not the flashiest demo, not the thing a vendor put in front of you. The narrow, repetitive, annoying task that a specific person does every week and quietly resents. That is where AI earns its keep, and it is where you learn what your firm can actually absorb.
Most firms get this backwards. They open with a strategy workshop, a long list of possibilities, and a plan to transform three departments at once. Six months later there is a deck and no working system. The firms that get value do the opposite. They ship one small thing, measure it, and use what they learn to pick the next one. Momentum beats ambition every time.
Why smallest and most painful wins
Small means you can finish it. A workflow you can describe in two sentences is a workflow you can build, test, and put a human check around in weeks rather than quarters. Painful means someone will actually use it, because they already feel the cost of doing it by hand. Pick something nobody minds doing and adoption dies on contact. Pick something that ruins a Tuesday afternoon every week and people will pull it into their work without being asked.
There is a risk argument too. A small, well-chosen first workflow keeps you in the low and medium stakes buckets, where a wrong output is an inconvenience or gets caught by a human before it matters. You get to learn the discipline, the audit trail, the sign-off, the prompt versioning, on something that cannot hurt a client, a payment, or a regulatory return. We wrote about that risk tiering in our AI governance framework.
How to find it
Do not run a survey. Sit with the two or three people who do the most repetitive work and ask one question: what do you do every week that feels like it should not need a person. Then look for the four markers of a good first candidate.
- High frequency. It happens daily or weekly, not twice a year. Frequency is what turns small time savings into real numbers.
- Rules you can write down. The task follows a pattern a competent new joiner could learn in a morning. If the logic lives only in one person’s head and changes every time, it is not your first case.
- Structured or semi-structured inputs. Documents, emails, spreadsheets, forms. Messy is fine. Genuinely unpredictable is not.
- A tolerable failure mode. If the system gets one in twenty wrong, a human catches it and the cost is small. That is a starting point. If one wrong output reaches a client unchecked, that is a later case, not a first one.
In regulated firms the same handful of workflows come up again and again. Client take-on and KYC document gathering. Extracting figures from statements and reports. First-draft file notes and letters. Investor and NAV reporting packs. Triaging a shared inbox. None of these are exotic. All of them are painful, frequent, and rule-bound, which is exactly the point.
Put a number on it before you build
A workflow is only worth automating if you can say what it is worth. Before any build, write the number down. Take the hours the task consumes each week, multiply by the loaded cost of the person doing it, and annualise. A task that eats six hours a week of a person on a fifty pound loaded hourly rate is costing you the better part of sixteen thousand pounds a year, and that is before you count the errors and the delay. If you cannot put a number on the outcome, it is not the right first workflow. There is a fuller method in how to measure AI ROI.
One workflow, not ten
The discipline is to resist the second idea until the first one is live and measured. Ship one workflow. Watch it run for a fortnight. Confirm the hours it saved and the errors it removed. Only then pick the next, and let the pattern you proved carry over: the same audit trail, the same human checkpoint, the same way of versioning prompts. This is how a firm builds capability instead of a graveyard of pilots. It is also why so many pilots never reach production, which we covered in why AI pilots fail.
What good looks like in six weeks
A first workflow scoped, built, and running in production inside four to six weeks, with a named owner, a human sign-off where it counts, and a changelog from day one. That is the shape of how we work, built precisely so the first thing you ship is the smallest painful workflow rather than the biggest slide.
If you want a candid read on which workflow to start with, book a review. We will look at your week, find the task that hurts most and risks least, and tell you what it is worth to fix. No deck, no hype. Just the first move worth making.