SpunkArt
Small business and writing

How to plan a simple business automation

An automation is a set of steps a computer runs for you when something happens, such as copying a new form entry into a spreadsheet and sending a reply. Many no-code tools can do this. The planning is the same whichever tool you choose.

Trigger, actions, conditions

Almost every automation is made of three parts:

  • Trigger: the event that starts it. A form is submitted, an order is paid, a time of day arrives, a file lands in a folder.
  • Actions: what happens next. Add a row, send an email, create a task, post a message.
  • Conditions: rules that decide which actions run. “Only if the order is over a certain amount”, “only on weekdays”.

Time-based triggers work like a scheduled job; the cron guide explains schedule syntax. Event triggers often use webhooks, which the webhook guide covers.

Step 1: Write down the manual process first

Do the task by hand one more time and list every step, including the small judgements. For a fictional house-cleaning business handling a new quote request:

  1. Read the request in the inbox.
  2. Copy name, address, number of rooms and preferred day into the bookings sheet.
  3. Reply with the standard “thanks, here is what happens next” message.
  4. If the address is outside the service area, reply with a polite decline instead.
  5. Add a reminder to call back within one working day.

Steps 2, 3 and 5 are mechanical and good candidates. Step 4 needs a rule you can state exactly (a list of postcodes, for example). If you cannot state the rule, keep that step manual.

Step 2: Estimate whether it is worth it

hours saved per year = minutes per task × tasks per week × working weeks ÷ 60

Worked example (made-up numbers). The quote handling takes 12 minutes and happens 25 times a week.

  • Per week: 12 × 25 = 300 minutes, which is 5 hours
  • Over 48 working weeks: 5 × 48 = 240 hours a year
  • If setting it up takes 6 hours, it pays back in 6 ÷ 5 = 1.2 weeks

A task that takes 3 minutes once a week saves about 2.4 hours a year; it may not justify the setup and the upkeep.

Step 3: Build it to fail safely

  • Test with fake data before switching it on for real customers.
  • Notify a person on failure. Most tools can email you when a run errors. Make sure someone reads it.
  • Keep a log: a sheet or folder where every run leaves a line, so you can check what happened.
  • Avoid loops, such as an automation that adds a row which triggers itself again.
  • Limit access. Connect the tool with the narrowest permissions it needs, and remove access when you stop using it.

Step 4: Review it

Put a date in your calendar a month after launch. Check the log, ask whoever relies on it whether anything was missed, and note the steps that still need a human. Write a short description of what the automation does and where it lives, so someone else can fix it if you are away.

Common mistakes

  • Automating a messy process instead of simplifying it first.
  • Sending automatic replies that sound robotic or promise things a person must then do.
  • Storing customer data in more places than needed.
  • Nobody knowing the automation exists until it breaks.

Questions people ask

Do I need to code?

Not for simple automations. No-code tools connect common apps with menus. Code helps when you need unusual logic or want to avoid per-task fees.

What should never be fully automated?

Decisions with real consequences for a person, such as refusing a refund or a complaint, deserve a human look. Automate the gathering of information, not the judgement.