Start with work that happens often, follows the same steps every time, and costs you when it’s missed: confirming and reminding bookings, following up with new enquiries, chasing invoices, and copying the same details between tools. Fix the process before you automate it, keep a person in charge of anything that needs judgement, and check whether the tools you already pay for can do it before building anything new.
How to spot a good first candidate
A process is a strong candidate when most of these are true:
- It happens often. Daily or weekly, not twice a year.
- It follows the same steps. The same trigger leads to the same actions most of the time.
- Missing it costs you. A late follow-up loses a job; a missed reminder means a no-show.
- It involves retyping. The same details are copied from one place to another, where mistakes creep in.
- It has a clear starting point, such as a form submitted, a booking made or a job marked complete.
- A mistake would be easy to catch and fix.
The more of these a task ticks, the better it is as a first automation. The fewer it ticks, the more it needs a person.
Where service businesses often start
These are common first automations for small and mid-sized service businesses, because they tend to tick most of the boxes above:
- New enquiries. An immediate acknowledgement, the enquiry routed to the right person, and the details recorded in your customer system, so nobody waits and nothing gets lost.
- Bookings. Confirmations, reminders before the appointment, and an easy way to reschedule.
- Follow-ups. A reminder to follow up on a quote, or a check-in after a job, so it doesn’t depend on someone remembering.
- Invoices and payments. Invoices sent when a job is complete, and polite reminders when a payment is overdue.
- Moving information between tools. A form that fills in your customer system, which feeds your invoicing, instead of the same details typed three times.
- Review requests. A request sent after every completed job.
- Documents. Pulling the details you need out of forms, emails and PDFs, with a person checking anything that matters.
You don’t need all of them. One well-chosen automation that runs reliably is worth more than five that need constant attention.
What not to automate (yet)
- A process that isn’t settled. If the steps change every week, automate after they stop changing.
- Rare tasks. Something that happens a few times a year rarely repays the effort.
- Judgement calls. Complaints, pricing exceptions and sensitive conversations need a person.
- Anything where a wrong message would do real harm, such as messages about health, money owed or legal matters, without a person reviewing them.
- Anything that leaves customers unable to reach a person. Automation should make you easier to reach, not harder.
Fix the process first
Automating a messy process makes the mess faster. Before anything is built:
- write down the steps as they happen today
- remove the ones that don’t need to exist
- agree who is responsible when something goes wrong
Often this alone saves time, and it makes the automation simpler and more reliable.
Use what you have before building something new
Many booking, invoicing and customer-management tools already include reminders, follow-ups and basic automation. Turn on what you already pay for first.
Connecting your existing tools, so information moves between them on its own, is often the next step. Custom software makes sense when:
- your process is what sets you apart
- the tools you have force constant workarounds
- you need systems connected that weren’t designed to connect
Where AI helps, and where it needs a person
AI can do useful work in a small business:
- drafting replies
- sorting and routing enquiries
- answering common questions
- pulling details out of documents
It works best on tasks with a clear purpose and a person who reviews the results that matter. Don’t let it:
- make commitments on your behalf
- quote prices
- handle sensitive information without safeguards and a clear understanding of where that information goes
Rules, ownership and upkeep
- Automated texts have rules. Under FCC rules, texts sent to mobile phones with automated systems generally need the recipient’s prior consent, and marketing texts need written consent. People must be able to opt out, for example by replying STOP, and you must honour it (FCC: Stop Unwanted Robocalls and Texts).
- Review requests have rules too. The FTC’s rule on reviews bans fake reviews, rewards that depend on what a review says, and tactics to suppress negative reviews. Ask every customer, not only the happy ones (FTC final rule, August 2024).
- Your business should own it. The accounts your automations run on should be in your business’s name. The workflows should be written down, and someone should know what each one does.
- Plan for upkeep. Connected tools change and accounts expire. Make sure someone is notified when a step fails, and someone is responsible for fixing it.
This guide is general information, not legal advice.
How to choose your first one
- For one week, list the tasks your team repeats.
- Mark each against the checklist above.
- Pick the one that ticks the most boxes and would do the least harm if it went wrong.
- Start small, check that it works the way you expected, then choose the next.
How this works with Lux
Bookings, payments, follow-ups and records that move on their own, so nothing depends on someone remembering. We connect the tools you already use where they do the job, and build where they don’t, scoped in writing before work begins. The code we write for your project transfers to you under your agreement. Site OS can keep it running afterwards, with support requests answered within one business day.