Automate first a workflow that runs every day, costs money when it is slow or wrong, passes through systems a machine can read, and has one person who owns the result. Score your candidates on those five tests. Leave for later anything rare, judgment-heavy, about to change or without an owner.
Ask what business processes can be automated and the honest answer is most of the ones that repeat. That answer does not help you spend the first dollar. This topic is part of the field guide to the AI readiness assessment, and it covers one decision inside it: which process goes first, and which ones wait.
What business processes can be automated?
Most of the work that repeats in a mid-market company can be carried by a system today: reading an emailed order and entering it, matching a vendor invoice to its purchase order, answering an inquiry that arrives after hours, drafting a quote from the price book, assembling the Monday numbers. What these have in common is a clear input, a clear output and a system of record where the result lands.
Processes that usually score well in traditional companies.
- Quoting. Quotes, proposals and RFP responses built from the price book and past wins. The play is P08 Instant quotes, proposals, RFPs, and contracts.
- Customer inquiries. Calls, forms and emails that wait for someone to answer. The play is P07 Answer every lead in 60 seconds.
- Order entry and vendor invoices. Emailed purchase orders keyed into the ERP, and vendor invoice processing. Both run on P06 Never touch a PO or invoice again.
- Dispatch coordination. Scheduling crews and routes around calls that change by the hour. For dispatch, nothing in our library fits, so it goes down the custom path.
- The weekly numbers. The report someone builds by hand before every Monday meeting. The play is P02 Your growth machine, on a weekly rhythm.
Processes that usually score well in B2B software companies.
Lead follow-up, onboarding handoffs, support triage, CRM updates and billing checks. Each one repeats daily, runs through systems with good records, and has an obvious owner.
The guide to quoting and inquiries goes deeper on the revenue side, and the back-office automation guide covers orders, invoices and reports.
Five tests for a first workflow.
The first process you automate sets the budget, the team's trust in the system and the number your CFO remembers. So pick it on evidence. Score each candidate from 1 to 5 on these five tests.
- Volume.How often does it happen? A process that runs hundreds of times a week pays back faster than one that runs four times.
- Cost of delay.What does waiting cost in revenue or customer patience? A quote that goes out the same day wins jobs a Thursday quote loses.
- Cost of errors.What does a mistake cost to find and fix? Errors that reach customers, invoices or cash score high.
- System access.Does the work pass through email, documents and systems that can be read? Paper and memory score low.
- A named owner.Is there one person who will say whether it works, and who can approve changes to the process?
Score your candidates.
Add up the five scores for each candidate and tag it with the number it moves: revenue (REV), cost (COST) or time (TIME). The highest total goes first. When two candidates tie, pick the one with the clearest baseline, because you can prove the result sooner.
| Test | Score 1 when | Score 5 when |
|---|---|---|
| Volume | It happens a few times a month. | It happens many times a day. |
| Cost of delay | Nobody notices a wait. | A slow answer loses the job, the discount or the customer. |
| Cost of errors | Mistakes are caught before anyone sees them. | Mistakes reach customers, invoices or cash. |
| System access | The input lives on paper or in someone's head. | The input arrives by email or lives in the ERP, the CRM or shared files. |
| A named owner | A committee owns it, or nobody does. | One person owns it and can change the process. |
Here is how a regional distributor might score three candidates.
| Candidate | Lever | Vol | Delay | Errors | Access | Owner | Total |
|---|---|---|---|---|---|---|---|
| Emailed purchase orders into the ERP | TIME | 5 | 4 | 4 | 5 | 5 | 23 |
| Quotes for non-stock items | REV | 4 | 5 | 3 | 4 | 4 | 20 |
| The monthly board report | TIME | 1 | 2 | 3 | 4 | 5 | 15 |
Order entry goes first. Quotes go second, once order entry is running. The board report waits: it matters, but it happens once a month.
For a distributor, the office work worth checking first is laid out in AI use cases in distribution.
What accounting processes can be automated.
Accounting is where many companies find their first workflow, because the volume is steady and every step already leaves a record.
- Invoice entry and matching. Vendor invoices read, coded and matched to purchase orders and receipts.
- Payment reminders. Collections follow-up drafted on schedule, with a person sending it.
- Reconciliations. Bank and card activity matched to the ledger, with the differences flagged.
- Month-end reports. The standard pack assembled from the books before the close meeting.
A person still approves anything that moves money.
What to leave alone for now.
The processes you set aside matter as much as the one you pick. Write these down as a do-not-build list.
- Rare tasks. If it happens a few times a quarter, the setup costs more than the work.
- Work with no data trail. If the inputs live in conversations and memory, a system has nothing to read.
- Decisions that need a license or a signature. A system can prepare them. A qualified person makes them.
- Processes about to change. If the ERP is being replaced next quarter, automate after the move.
- Work with no owner. Without an owner, nobody judges the result and nobody updates the process when the business changes.
A written do-not-build list protects the budget, and it keeps the same ideas from coming back every quarter.
Common mistakes when picking a first project.
- Choosing the flashiest option. The project that demos best is rarely the one that moves a number.
- Starting with a chatbot that has no workflow behind it. A chat window on its own rarely changes a number the owner tracks.
- Picking a process owned by a committee. Every change waits for a meeting, and nobody calls the result.
- Ignoring how the systems connect. The work is only automated if the result lands in the system of record.
- Skipping the baseline. Measure the hours, errors and response times before you start, or you cannot show what changed.
Put a number on your top two.
For your top two candidates, estimate the yearly value in the three places a workflow pays: revenue answered sooner, cost taken out and hours given back. Use your own inputs, then subtract what it costs to run.
Budgeting the work comes next, and what AI consulting costs shows how the options are priced.
The play for this.
Three of the workflows above map directly to plays in the StrikeArc PowerPlays Library. Each one is a pre-built AI system we install and run for you, with a named person approving the steps that need judgment.
- P06Never touch a PO or invoice againTIME
- P07Answer every lead in 60 secondsREV
- P08Instant quotes, proposals, RFPs, and contractsREV
Never touch a PO or invoice again
Orders and invoices arrive by email and process themselves: read, extracted, checked against your data and posted. Only the exceptions wait for a person.
- Runs on
- Your inbox and your accounting or ERP system
- The rule
- Documents move on their own only where your rules allow. Where money moves, a named approver signs off.
- Reports in Helm
- Share of documents processed without a touch.
P06 Never touch a PO or invoice again takes the emailed orders and invoices from the example off your team's desk. In StrikeArc Helm, it reports the share of documents processed without a touch, next to every other play in the value ledger.
Have StrikeArc Scout do the scoring.
You do not have to run this sheet by hand. StrikeArc Scout scores every play in the StrikeArc PowerPlays Library against your business, and a person walks you through the readout: the value at stake, the top plays and the do-not-build list. When nothing in our library fits, Custom Discovery at $10,000 scopes the play you need. See how find, install and run work.
Questions owners ask.
What business processes can be automated?
Any repeatable process with a clear input, a clear output and a system of record. Quoting, order entry, invoices, inquiries and reports are common starting points.
What should a small or mid-sized business automate first?
The workflow with the highest score on volume, cost of delay, cost of errors, system access and ownership.
How do I know if a process is a good fit for AI?
It happens often, it follows a pattern, its inputs can be read by a system, and one person owns the result.
Should we start with a chatbot?
Only if it sits on top of a real workflow and real answers. On its own, a chatbot rarely changes a number the owner tracks.
How many workflows should we automate at once?
One, measured against a baseline. Then the next.
What accounting processes can be automated?
Invoice entry and matching, payment reminders, reconciliations and month-end reports. A person still approves anything that moves money.