Most companies do not wake up with an automation problem. They have a follow-up problem, a retyping problem, an approval problem, or a month-end problem.
The same customer details get typed into three systems. Someone rebuilds the same report every Friday. One person sorts every message in a shared inbox. A new hire waits for access because the checklist lives in someone’s head.
Automation can remove work like this. But repeated work is not always ready to automate, and company size does not make it ready either.
The short answer
One loop. Four safety checks.
- Pick one repeated loop that wastes time, causes delays, or leads to mistakes.
- Automate it only when the result is clear, one person owns it, mistakes can be found, and the team has a backup plan.
- If those things are not true, fix the process first. Keep important decisions with a person.
Recognize the work
Ten loops worth looking at
Start with the work you can see, not a tool you want to buy. Pick one pain point to study, not one automation to build.
Turn documents into draft records
- What repeats
- A person opens a PDF, form, photo, or email and types details into another system.
- Smallest useful change
- Create a draft record, mark missing details, and stop when information does not match.
- Human checkpoint
- Check the record. Approve money, special terms, and unusual cases.
Copy approved details between systems
- What repeats
- Someone copies a customer, job, order, payment, or status from one system to another.
- Smallest useful change
- Move only approved fields from the trusted system. Send conflicts to a review list.
- Human checkpoint
- Resolve price changes, partial payments, credit terms, and real data conflicts.
Gather a complete packet
- What repeats
- Someone searches email, chat, folders, and software for the items needed to close, hire, bid, or audit.
- Smallest useful change
- Gather the named items, show what is missing, and prepare a draft packet.
- Human checkpoint
- Waive a requirement, change an entry, set a price, sign, or submit.
Sort incoming requests
- What repeats
- One person reads every message and decides who should get it.
- Smallest useful change
- Use written rules to route routine requests and confirm they were received.
- Human checkpoint
- Handle complaints, promises, price changes, sensitive cases, and anything outside the rules.
Use software you already own
- What repeats
- The company pays for software, but the work still runs through email or a spreadsheet.
- Smallest useful change
- Turn on the forms, reminders, approvals, templates, or links already in the product.
- Human checkpoint
- Decide how the team should use the product and whether training or a vendor change is needed.
Clean up old automations
- What repeats
- No one knows which automations still run, whose login they use, or what happens when they fail.
- Smallest useful change
- List every automation, its owner, login, failure plan, and whether it should be removed.
- Human checkpoint
- Approve shutdowns and take ownership of the work that remains.
Send reminders, then stop
- What repeats
- Someone remembers to chase a document, invoice, review, or estimate—or forgets.
- Smallest useful change
- Follow a set reminder plan, stop when the item arrives or is disputed, then alert an owner once.
- Human checkpoint
- Offer a payment plan, give a discount, write off a balance, waive a rule, or withdraw an offer.
Route an approval
- What repeats
- A purchase, discount, change order, or sign-off gets lost in an email thread.
- Smallest useful change
- Send the request to the right approver, remind them, and record the answer.
- Human checkpoint
- Make the decision. The system carries the request and answer; it does not supply the yes.
Start the next checklist
- What repeats
- A signature, sale, hire, finished job, or departure makes several people start work by hand.
- Smallest useful change
- Let one confirmed event create the right folders, tasks, notices, and draft records.
- Human checkpoint
- Change scope, pick a start date, approve access, waive missing items, or make an employment decision.
Build the same report on a schedule
- What repeats
- Every Monday or month-end, someone rebuilds the same report or missing-items list.
- Smallest useful change
- Gather approved data on a schedule and leave gaps visible.
- Human checkpoint
- Explain the numbers, set priorities, make a forecast, and decide what happens next.
These are ideas, not approval to build. Sensitive messages, prices, payments, hiring, legal promises, access approval, and unusual cases need an accountable person.
Before you build
Is the workflow ready?
A useful idea can still be the wrong first project. Play a route, then answer the seven questions.
Your answers stay on this page. Nothing is saved or sent.
Does the work happen enough to matter?
Count the time spent doing, waiting, fixing, and chasing. Frustration is a clue, not yet a business case.
Can two people agree on the finished result?
If the team still disagrees about the policy, fields, or goal, automation will repeat that disagreement faster.
Does one named person own the result?
That person approves changes and decides when the workflow should stop. “The office” is not a named owner.
Can you explain the usual path and unusual cases?
The usual work needs a stable path and everything missing, disputed, or outside the rule needs a clear handoff.
Do you know which system to trust?
Choose the trusted system for each important detail and decide what happens when that detail is missing or old.
Can you find a wrong result?
“It ran” does not mean it was right. Decide how you will spot missing records, wrong labels, and rejected updates.
Can the team keep working if it stops?
Name the responder, write down the manual path, and know how to undo a bad change.
- Stop doing work no one uses.
- Make the steps and ownership clear.
- Turn on a feature you already pay for.
- Connect two systems with fixed rules.
- Let AI prepare a draft that a person checks.
- Let software take a narrow action only after the safety checks pass.
Set the boundary
Carry the work. Keep the decision human.
Automation can carry work to a decision. It should not quietly take over a decision that a person must answer for.
- Payments
- Hiring and firing
- Legal promises
- Access approval
- Safety choices
- Major price changes
- Policy exceptions
- Sensitive customer messages
AI changes the limit, not the need for one
Level 1
Rules repeat
Send a complete form to the right office based on location.
Boundary: Use fixed rules and send anything outside them to a person.
Level 2
AI suggests
Pull details from a document or draft a reply for review.
Boundary: A person checks the output before it becomes official.
Level 3
Software acts
Send a message, change a record, change access, or start a payment step.
Boundary: Require approval for important actions and keep a record of what happened.
Headcount is a clue
Growth changes where to look—not whether you are ready
Use the range closest to your company as a place to look. It is not a grade, deadline, service band, or buying rule. The workflow still has to pass the readiness check.
Fewer than 10 people
Look for: Work held in memory: follow-ups, renewals, invoices, and tasks that stop when one person is away.
Start with: Choose one trusted place for each record, a named owner, simple alerts, and a written backup plan.
10–49 people
Look for: Handoffs between people and tools: shared inboxes, repeated entry, manual checklists, and document chasing.
Start with: Agree on trusted systems, allowed fields, an exception owner, and the result you will measure.
50–99 people
Look for: Teams doing intake, approval, billing, reporting, or access work in different ways.
Start with: Set clear roles, test safely, approve changes, check records, and name business and technical owners.
100–199 people
Look for: A group of automations using personal accounts, old logins, hidden passwords, or copied building blocks.
Start with: Keep one inventory, use company-owned accounts, review access, watch failures, and retire old work safely.
200 or more
Look for: Shared rules and tools across departments that also build their own workflows.
Start with: Use this only as context. This range is outside Zoevin’s core focus; seek help built for larger companies.
A one-loop worksheet
What can you do this week?
Choose one loop that ate part of last week. Do not choose a whole department or job. Watch the real work while you answer; the written procedure may miss the side email or judgment call.
Your answers stay on this page. Nothing is saved or sent.
Not answered.
Not answered.
Not answered.
Not answered.
Not answered.
Not answered.
Not answered.
Not answered.
Not answered.
Not answered.
Better automation means less avoidable work
The goal is not a bigger bot count. It is reliable work with less retyping, chasing, sorting, and waiting.
Start with one loop. Name the result and the owner. Keep important decisions human. Make sure you can spot a mistake and keep working if the system stops.
Use your own numbers to estimate the cost of one repeated loop before you decide to build anything.
See what the loop is costingEvidence
Sources
The practical examples are editorial guidance. These primary sources support the risk boundaries.
primary source
NIST — Artificial Intelligence Risk Management Framework 1.0Primary framework behind the article’s advice to define human roles, test AI, document limits, and manage risk throughout use.
primary source
Federal Trade Commission — Protecting Personal Information: A Guide for BusinessPrimary business guidance behind the questions about what data is needed, where it goes, who can access it, and when it is deleted.