Blog / AI & automation

Business process automation for growing companies: what to automate first (with examples)

Econy Editorial Team · · 5 min read

Illustration of a workflow diagram with a trigger, a condition and two branching actions

Key takeaways

  • Automate the hand-offs and reminders between people before automating the work itself.
  • Every automation needs a trigger, an optional condition and a small number of clear actions.
  • Start with rules you can explain in one sentence, and keep a run history.
  • Review automations every quarter; retire the ones nobody notices.

Most growing companies do not have a process problem. They have a hand-off problem. Work stalls between people: a request waits for someone to notice it, an approval sits in an inbox, a follow-up is forgotten. Asana's research on the Anatomy of Work puts a number on the cost of this coordination overhead: knowledge workers spend 60% of their time on "work about work" rather than the skilled work they were hired for.

Business process automation (BPA) is the practice of letting software handle the predictable parts of those hand-offs. This guide explains how to choose what to automate first, how to design reliable rules and how to avoid the traps that make automation more trouble than it is worth.

What business process automation is — and is not

BPA is the use of rules to move work forward without someone having to remember: assigning a new request, reminding an owner before a deadline, escalating when a clock runs out, notifying the right people when something changes.

It is not a replacement for thinking. Rules are perfect for predictable steps and terrible at judgement. When a step needs judgement — reading a free-text request, drafting a reply — use a human, or an AI suggestion a human reviews (see our guide to AI agents for business).

The anatomy of a good automation

Every reliable automation has three parts:

  1. A trigger — something that happens: a record is created, a status or field changes, a due date approaches, a form is submitted, an approval is decided, or a schedule fires.
  2. A condition (optional) — only continue if, say, priority is Urgent or the client is on a premium plan.
  3. Actions — a small number of clear steps: set a status or priority, assign someone, notify people, create a follow-up task, add a comment, escalate.

If you cannot describe the automation in one sentence — "When an urgent ticket is created, assign the on-call lead and notify them" — it is probably doing too much.

How to find what to automate first

Spend one week listing every time someone says "I didn't know that was waiting for me" or "I forgot to follow up". Then score each candidate:

  • Frequency — how many times a week does it happen?
  • Predictability — is the right next step always the same?
  • Cost of delay — what happens when it is late? A frustrated customer? A missed payroll cut-off?
  • Cost of a wrong action — if the rule fires incorrectly, is it easy to undo?

Automate the high-frequency, predictable, delay-sensitive and easy-to-undo items first.

Ten automations that work in most companies

Sales and customers

  • When a lead form is submitted, create the lead and assign it to the owner for that region.
  • When a deal moves to Won, create a hand-off task for the delivery lead.

Service and support

  • When an urgent ticket is created, assign the on-call lead and notify them.
  • When a ticket's SLA is about to breach, escalate to the queue manager.

Projects and delivery

  • When a task's due date is two days away and it is not started, remind the assignee.
  • When a milestone is marked complete, notify the client contact and the project lead.

People and HR

  • When a new hire's start date is set, create their onboarding checklist.
  • When a leave request is approved, notify the team lead and update the rota.

Finance and operations

  • When an approval is decided, add a comment with the decision and notify the requester.
  • Every Friday, create a task to review open approvals older than a week.

Common automation traps

  • Notification floods. If every rule notifies everyone, people mute everything. Notify the one person who must act.
  • Hidden chains. Rule A triggers rule B triggers rule C. Keep chains short and documented.
  • No owner. Every automation needs a named owner who reviews it.
  • No history. When something goes wrong, you need a run history to see what fired and why.
  • Automating a broken process. If the process is unclear, automation makes the confusion faster. Fix the process first.

Measuring the impact

Measure what the automation was meant to improve:

  • Response time for requests and tickets.
  • Overdue rate for tasks and approvals.
  • SLA breaches before and after.
  • Time saved, estimated from the number of runs multiplied by the minutes each manual step used to take.

Automation and integration

Automations are most useful when the data lives in one place. If sales, delivery and support each use a different tool, every automation becomes an integration project. A shared workspace lets one rule connect them — for example, a won deal that creates a project hand-off. Where you do need other systems, signed webhooks let them react to changes safely.

A worked example: from signed deal to kick-off

A common source of delay in service companies is the gap between "the client signed" and "the team started". Here is a simple, three-rule automation set that closes it:

  1. When a deal moves to Won → create a hand-off task for the delivery lead, assign it, and notify them.
  2. When the hand-off is accepted → create the project from the right template and add a kick-off milestone due in five working days.
  3. When the kick-off milestone is two days away and not complete → remind the project lead; if it becomes overdue, escalate to the head of delivery.

Each rule is one sentence. Together, they replace a chain of emails and reminders that previously depended on someone's memory. The run history shows exactly when each step fired, which makes it easy to spot where hand-offs still stall.

A one-page template for documenting an automation

Use this for every rule you create, and keep the pages together:

  • Name: Urgent ticket → on-call lead
  • Owner: Head of support
  • Purpose: Make sure urgent requests reach someone within minutes
  • Trigger: Ticket created
  • Condition: Priority is Urgent
  • Actions: Assign the on-call lead; notify them
  • What could go wrong: Wrong person if the on-call rota is out of date
  • How we know it works: Median time to first response for urgent tickets
  • Review date: End of next quarter

Documenting automations this way takes five minutes and saves hours of confusion when something unexpected happens — or when the person who built the rule leaves.

Where Econy fits

Econy automations run across modules — projects, CRM, service desk, HR and more. Triggers include new records, status and field changes, approaching due dates, form submissions, approval decisions and schedules; conditions filter on any field; actions set status or priority, assign, notify, create follow-up tasks, add comments or escalate. Every run is recorded in a history, and signed webhooks can tell your other systems when records change. Because sales, delivery, HR and support share one workspace, a single rule can connect them.

Conclusion

The best business process automation is unglamorous: it removes the waiting between people. Start with hand-offs and reminders, keep each rule simple enough to explain in a sentence, give it an owner and a history, and review it regularly. The hours you get back go to the work only people can do.

Frequently asked questions

What processes should a small business automate first?

High-frequency, predictable hand-offs where delay is costly and a wrong action is easy to undo — such as assigning new requests, reminding owners before deadlines and escalating SLA breaches.

What is the difference between automation and AI?

Automation follows fixed rules for predictable steps. AI handles fuzzy work such as reading free text or drafting, and should be reviewed by a person.

How many automations is too many?

There is no fixed number. If people cannot explain what fires and why, or notifications are being muted, you have too many. Review and retire rules quarterly.

See Econy automations