Guides
How to choose workflow automation tools without building a second job
Workflow automation tools for small business need questions that disqualify vendors early, not demos. Here is what to ask and what the contract must say.
What to take away
- Write down the three jobs you will never automate, so no vendor sells you a platform you do not need.
- Ask every vendor the same questions in writing, and keep the replies.
- Four answers end the conversation on the spot, whatever the trial looked like.
- Put the export format, the notice period and the billing trigger in the agreement before you pay.
A workflow tool earns its place when it removes a step you do by hand, not when it adds a dashboard you open each morning.
Scopes that are actually different jobs
Vendors sell one product against three separate problems. Trigger work starts when something happens: a form is submitted, an invoice arrives, a lead reaches the inbox. Record work keeps two systems agreeing, such as a customer in the CRM and in billing.
Three automation scopes
Trigger work
- Starts when
- Event happens
- Example
- Form submitted
- Weakness
- Thin approvals
Record work
- Starts when
- Systems disagree
- Example
- CRM vs billing
- Weakness
- Sync drift
Approval work
- Starts when
- Person waits
- Example
- Tax filing sign-off
- Weakness
- Deadline slips
Approval work waits on a person and a deadline. The selection criteria for business process automation differ across those three. A tool strong at triggers is often thin at approvals.
Scope sets the shortlist, and a team needing a form to create a row is buying a different product. A team routing a state sales tax approval to two people before a filing deadline needs approval logic.
If the trigger lives in the mailbox, read Choosing business email software first, since the disqualifiers there apply before any automation does.
Questions to ask
Send these in writing. A vendor who answers on a call but never in an email is telling you something. The reference article on workflow automation primes the vocabulary, which helps you read a reply for what it avoids.
Vendor questions to send
- Which events start a workflow without paid seat?
- What happens to mid-flight runs on failure?
- Can I export definitions, history and credentials?
- Who is alerted when a workflow stalls?
- Does the bill move with runs or seats?
Ask for one of your workflows to be rebuilt live with your sample data, and for the vendor to name the step they cannot do.
Evidence to request
Documentation is not evidence. Ask for the artifacts below, dated.
Claims vs evidence
Claim
- Works with stack
- Exact triggers list
- No code required
- Recorded rebuild
- Reliable
- Year of uptime
- Secure
- Audit log samples
Evidence
- Works with stack
- Integration logos
- No code required
- Vendor sample demo
- Reliable
- Percentage no period
- Secure
- Generic security page
Weak reply
- Works with stack
- No code required
- Reliable
- Secure
Evidence to request
- Works with your stack
- A written list of exact triggers and actions, with field names
- No code required
- A recorded rebuild of one of your processes
- Reliable
- Uptime history and incident notes covering a full year
- Secure
- Access controls, audit log samples and retention settings
What a weak reply looks like
- Works with your stack
- A wall of integration logos
- No code required
- A demo run on the vendor's sample data
- Reliable
- A percentage with no period attached
- Secure
- A generic security page
Access control is the part small teams skip. If the automation can read your billing records or your customer list, ask how roles are separated and how a departing employee loses access. The NIST Cybersecurity Framework is a workable checklist for those questions.
Calendar scheduling software sets out the pricing models you will be quoted, which differ between tools that schedule work and tools that route it.
Answers that should end the conversation
Four replies should stop the process, whatever the trial showed.
- "Export is available on request." Your process definitions and your run history are the asset. If leaving needs a support ticket, you are not leaving.
- "Pricing is per workflow, and we reconcile at renewal." The bill then scales with your success rather than your headcount.
- "We can build that step for you." Vendor-built custom work turns a subscription into a dependency no competitor can quote against.
- "Support replies within two business days." For an approval holding up a customer order, that is not a service level.
What the agreement must say
The contract carries the parts you will need in year two. It must state, in these terms:
- Ownership of every workflow definition, with the export format named and a frequency stated.
- The billing trigger in measurable unitsseats, runs, records or tasks, and which one counts.
- Notice before a price change, and the notice period for cancellation.
- An uptime commitment with a remedy attached, not a target.
- What happens to your data after termination, including a deletion date.
Seat pricing has its own traps, and the notes on hidden seat costs work through free tiers that shrink as a team grows.
If an automation moves customer records between two systems, your business stays the party answerable for how those records are handled. The FTC guide on protecting personal information covers the baseline, and it applies whether the processing runs in your office or in a vendor's cloud.
Example: one question asked early
Ask a vendor to define, in writing, what counts as one billable run. Some count a workflow triggered, some count each step, some count each record touched. The same process can look cheap under one definition and expensive under another. You learn which definition you bought before you sign, not at renewal.
Who can add users and change that trigger is an account question before it is a software question, and Account administration decisions covers the choices that are cheap now and costly later.
