What to Automate First in a Small Business: 5 Questions

Automate the process that happens often, follows rules you can write on one page, costs little when it goes wrong, already lives in a system and has someone who sees the result every day. For most small businesses that means lead intake, quote follow-up or a weekly report. It is not the most exciting process, it is the most repeatable one. Below is a five-question test you can run on any candidate in ten minutes, a worked scoring example, and an honest list of what to leave alone at the start.

Give each candidate process one point for every yes. A process that scores four or five is a good first project.

1. Does it happen at least weekly? A task done twice a year is not worth the build. A task done every day, by hand, by the same person, is the usual starting point.
2. Can you write the rules on one page? If a new employee could follow a checklist, a workflow can follow it too. If the answer is “it depends, I just know”, you are describing judgment, not a rule set. Our post on AI agents versus automation explains when judgment calls for a different tool.
3. Is a mistake cheap to catch? Start where an error costs little: an internal notification, a spreadsheet row, a draft email. A flow that moves money or sends legal documents belongs in the second project, once you trust the setup.
4. Does the data already live in a system? Automation connects systems that hold data. If the information sits in someone's head or in paper folders, the first job is getting it into a CRM, a sheet or your accounting tool.
5. Will someone notice when it breaks? Every flow fails eventually. Pick a process where a person looks at the result daily, so a silent failure does not run for weeks.

This is an illustration with invented processes, not a client case. Four candidates from a small service business, scored with the five questions:

• A web form lead goes into the CRM and the owner is notified. Daily, simple rules, a wrong row is easy to fix, the data is in the form and the CRM, the owner reads every lead. Five out of five: build this first.
• The Monday sales summary. Weekly, a fixed list of numbers from two tools, a wrong number gets noticed fast, the data is in both tools, the manager reads it. Five out of five.
• The month-end package for the accountant. Monthly, so it fails question one, and a mistake is expensive. Two or three out of five: later.
• Replying to unhappy customers. The rules do not fit on one page and a bad reply is costly. One out of five: leave it to a person, and let automation prepare the context.

The first two are what you build in week one. The third is a candidate once the first two run quietly. The fourth stays human.

• Lead intake. A form or message arrives, a row is created in your CRM, the right person is notified and the customer gets an acknowledgment.
• Quote follow-up. A quote goes out, and three days later a reminder is drafted if nobody answered. The value is that follow-up stops depending on memory.
• Weekly reporting. Numbers from two or three tools collected into one summary.
• New customer or employee setup. The same ten steps every time, across several tools.

For a broader view of what tends to automate well, see the real cost of manual operations.

Invoicing is a good example of a rule-based process, and in Israel the rules have moved. Under the Tax Authority's invoice reform (חשבוניות ישראל), a tax invoice above a set amount needs an allocation number issued by the Tax Authority. Green Invoice's guide, published on 24 March 2026, lists the threshold before VAT: 25,000 shekels from May 2024, 20,000 from January 2025, 10,000 from January 2026 and 5,000 from June 2026. The same guide says its system can request the number automatically by connecting to the Tax Authority's systems, once you authorize the connection in your account settings.

Two practical points. First, that is a vendor's guide, not the Tax Authority's own page, so confirm the current threshold with your accountant before you automate anything that issues invoices. Second, decide in advance what the flow does when no number comes back: stop and alert a person, rather than send an invoice you may have to correct. This is exactly the kind of rule that fits on one page.

• Anything you cannot describe step by step. Write it down first. If the document is vague, the automation will be too.
• Rare, high-stakes decisions. Pricing exceptions, refunds above a limit, anything with legal weight. Automate the preparation, not the decision.
• Processes that are about to change. Automating a process you plan to redesign next month builds the wrong thing quickly.
• Work that is really a conversation. A customer asking an unusual question needs a person. A bot or an agent can take the routine part and hand over the rest.

Before you build, write down two numbers: how many minutes the process takes each week now, and how many errors or missed follow-ups happened last month. The yearly time is minutes per run, times runs per week, times 52. Value it by what the delay costs you, such as a late quote or a missed follow-up, not by a rate for the time. After a month, compare with the same two numbers. Use your own counts. We do not quote an industry average here, because the saving depends entirely on your process.

We build a first automation from ₪4,500, plus an optional ₪450 a month for monitoring and tuning, plus VAT as required by law. The price is fixed per scope and confirmed before work starts. The next decision is which platform to build it on, and what each platform really costs follows from the volume and the owner you named above. See the automation and integrations service, take the fit quiz, or book a free intro call and we will score your candidate processes with you.

• Israel Invoice model: allocation number guide, Green Invoice, published 24 March 2026. A vendor guide, not the Tax Authority; verify the threshold with your accountant.