Start with one repeatable task

This is sample content for the blog. The scenario below is illustrative and does not describe a completed client engagement.

The first automation does not need to connect every tool in a business. A better starting point is often a single task that happens frequently and follows a recognisable pattern.

Write down the manual version

Before choosing software, describe what someone actually does today. For a simple enquiry log, that might mean copying a name, a question, and a preferred appointment time into a spreadsheet.

Keep the description concrete. “Improve operations” is an ambition; “record each new enquiry in one place” is a task you can inspect.

Define the boundaries

Three questions help make a first version understandable:

1. What starts it? A new enquiry arrives.
2. What should happen? The essential details are recorded once.
3. What happens if it fails? Someone is notified and can finish the task manually.

A small workflow is easier to trust when its limits are visible.

Keep the record simple

A starting record might use the fields name, received_at, question, and status. Add more only when they support a real decision.

{
  "name": "Example client",
  "question": "Do you have availability on Friday?",
  "status": "needs-reply"
}

Review before expanding

Try a duplicate enquiry, an incomplete message, and an unavailable destination. These cases show whether the workflow needs a clearer fallback before it takes on more responsibility.

In a finished article, this section could show what you tested, what failed, and what you changed. Replace these placeholders with your own observations.

Read the companion sample on designing a better human handoff.