"We build custom workflow automation for professional services, so read this as a statement against interest: automation is the right answer far less often than it is sold. An automated version of a pointless process is just a pointless process with an ongoing API bill."
In mid-market professional services firms—whether legal practice, wealth management, accounting, or family offices—inefficiency is a constant source of friction. The natural instinct of management is to seek software to automate the pain away. Yet, starting with the software is a structural mistake. The first question is never "can a system do this?" It is "should this exist at all?"
During our workflow diagnostics, we analyze candidate processes and place them into three honest columns: **Build**, **Kill**, or **Ignore**. In most firms, the Build column is rarely the longest.
1. The Process is Unclear or Inconsistent
If two partners in your firm run the same client onboarding flow differently, and neither can agree on which exception is correct, you do not have an automation candidate. You have an operational alignment problem.
Automating a confused, unstructured process freezes the confusion into software code. The system will fail because it cannot reconcile the differing expectations. Before you write a single script, you must align the team on a unified, logical process path. Often, that clarification is the entire solution, and no software development is needed.
2. The Volume Does Not Repay the Build
A task that takes an associate two hours a month is annoying, but it does not justify an automation project. Every line item in an automation register should have an effort estimate next to it, alongside a volume-based return on investment (ROI) calculation.
If a custom integration costs €25,000 to deploy and saves €100 of associate capacity per month, it will take decades to reach payback. Tedium is not a business case. High-impact document automation requires high volume, high frequency, or critical error reduction to be economically justified.
3. The System Lack Internal Ownership
Document processing pipelines degrade over time as upstream formatting, formats, and software environments change. If no one inside your company has the technical ownership or the mandate to manage the system day-to-day, the automation is a liability being installed, not a capability.
A system without an operational owner will fail silently the first time an external system updates its interface. Do not automate a workflow unless you have designated an internal owner who understands what normal behavior looks like.
4. Professional Judgment is the Product
Some steps in professional services look like structured processes but are actually judgment calls: the partner's read of a litigation risk, the underwriter's exception reasoning, or the wealth manager's allocation discretion.
You should automate the administrative paperwork *around* these decisions—gathering files, extracting key clauses, formatting letters—but never the judgment itself. The moment you automate the core professional decision, you dilute the value of the advice your clients are paying for.
The Elimination Rule
Before you invest in workflow automation, run the process through the elimination test. Can you delete the step entirely? Can you reduce the reporting requirements? Elimination is always cheaper than a build, and it has zero maintenance costs.