Operation and switching
Small-business automation: decide this before the product name
Build a shortlist from volume, exceptions, ownership, existing systems and API or desktop requirements — not from which vendor appeared most often in your feed.
The job comes first. The tool is allowed into the room once the job has made its case.
THE SHORT ANSWER
Automate stable, repeated work with enough volume to justify ownership. Keep judgement-heavy or infrequent work manual until the process becomes clearer.
OPERATING CONDITIONS
Test the awkward path, not the demo
Volume
Is there more work than people can sensibly process?
Exceptions
How often does a person still need to decide?
Owner
Who repairs it?
Cost
What grows with usage?
COST AND CONSTRAINTS
Price is one operating condition
Compare total monthly saving with subscription, setup, exception handling and maintenance time.
EVIDENCE
What to test before committing
Pilot one bounded process for a week and record manual touches.
Small firms with a named problem, measurable baseline and someone responsible for operation.
A ‘digital transformation’ with no process owner, volume estimate or definition of success.
SIMPLER ALTERNATIVE
Before changing the operating model
Simplify the process, use a spreadsheet or create a clear manual checklist first.
If all four answers are vague, the shortlist is early. The sales calls will remain available.