Not everything is a project
Automation conversations tend towards five-figure builds. Meanwhile there is a layer of small, cheap automation that most businesses have not done and that needs no supplier at all.
Each of the following is an afternoon of configuration in tools you probably already pay for.
Twelve worth doing
- Email filing rules so routine mail never reaches the inbox
- Templated replies for the five questions you answer weekly
- Calendar links instead of arranging meetings by email
- Form routing so enquiries reach the right person automatically
- Automatic acknowledgements to anyone who contacts you
- Scheduled reports sent rather than pulled
- Document templates that pre-fill from a record
- Reminders for recurring obligations — renewals, filings, certificates
- Automatic folder creation for new clients or projects
- Payment reminders from your accounting package, switched on
- Out-of-hours auto-response that sets expectations honestly
- Backup verification alerts, so you learn about failures
Why these are worth doing first
Each saves perhaps twenty minutes a week. Twelve of them is four hours, every week, for a few afternoons of setup and no ongoing cost. That is a better return than most software projects.
They also teach the business what automation feels like, which makes the case for larger projects considerably easier to make.
Check what your existing tools already do
Most businesses use a fraction of the automation available in software they already pay for: email rules, accounting reminders, CRM workflows, calendar scheduling, document templates.
Before buying anything, spend an hour in the settings of the three tools you use most. The results are frequently surprising.
Do them one at a time
Pick one, do it, use it for a week, then do the next. Attempting all twelve in a day produces twelve half-configured things and no habit.
Assign each one an owner, even in a small business, so somebody notices when it stops working.
When to graduate to a project
When the automation needs to span systems, handle exceptions, or carry real business consequence. That is where configuration stops and building starts.
Doing the small ones first means you arrive at that point knowing exactly what you need, which makes the project cheaper and better specified.