Back to blog
ArticleBlog / Workflow Automation
Jun 22, 20264 min readWorkflow Automation

Workflow automation software for a small business: what to look for, in five questions

How to choose workflow automation software when the work is in your inbox, calendar and sheets: five questions on reading, asking, limits, receipts, price.

Written by Tensor AutonomousThe Tensor Autonomous team builds approved AI Action and workflow automation systems for service businesses.

Search for workflow automation software and you get two kinds of product: enterprise suites with flowchart designers, and connector tools that move data between apps. Both assume the work is already tidy. In a small business the work is an inbox, a calendar and three spreadsheets, and the person doing it is you.

Here are the five questions that sort the tools that will help from the ones that will become another thing to maintain, and how Tensor Autonomous answers each.

1. Can it read a message, or only a form?

Most of your work arrives as prose: a tenant describing a leak, a prospect asking about a date, a customer asking for a quote. Software that needs a form with fields cannot start until someone has typed the prose into the form, which is the job you were trying to automate.

Tensor reads the message. The Library's Log maintenance requests starter logs each tenant's maintenance request with its urgency and drafts a reply that says what was logged, from the tenant's email as you paste it in. No form.

2. Does it ask before it changes anything?

Automation that runs silently is fine for moving data between apps. It is not fine for writing to your calendar or your customers. Ask to see the exact change before it happens, in your own account.

Tensor asks before it writes or sends: tensor shows you each change before it makes it, drafts included; nothing it drafts is sent until you send it.

3. Can you set limits, so you are not approving forever?

Approving everything trains you to click without reading. Ask whether routine changes can be allowed within limits, and what happens at the edge.

In Tensor you set, per responsibility, which kinds of change may run without asking (adding a row, creating a draft, adding an event), a daily cap, a days-and-hours window, and for each write an amount ceiling and a limit on recipients. Within the limits it runs; at the edge it stops and asks. Sending email, payments and refunds, and moving or cancelling a calendar event always ask; limits can't cover them.

4. Does it keep a receipt you would actually read?

Not a log for developers. A page per run that says what was asked, what was read, what was proposed, who approved it, what was written, and whether the result, read back from the record, matched.

That is Tensor's receipt. Next to each write, Undo removes what Tensor created after you confirm what will be removed, and a responsibility can be rolled back to an earlier version. Sent email is the one thing no tool can take back, which is why every send waits for your OK; limits can't cover sending.

5. What does it cost, and what does it need?

Enterprise suites price per seat and need a project to set up. Connector tools price per task and add up quietly. Ask for a flat monthly price and for what is required on your side.

Tensor is $149, $399 or $999 a month (Starter, Operator and Operations Team; Enterprise on request), with nothing to install. It needs the Google account the work lives in: Gmail, Google Sheets and Google Calendar today, Microsoft 365 later.

What the software should not try to be

It should not replace the system that owns your records. Your property-management, field-service or invoicing software keeps its job; Tensor does the admin around it: the inquiry answered, the request logged, the quote followed up, the showing booked. If a vendor claims to replace all of those, ask which one it does badly.

A short test before you buy

Pick one job that repeats and ends in a small change: a maintenance request logged, a quote followed up. Run it through the tool for a week with approval on every change. Count three things: how often it did the right thing, how often it asked when it should have, and how long the receipt took to read. If the answers are "almost always", "always" and "a minute", widen the limits. If not, do not buy a bigger plan.

Where to start

See it in a demo

Watch the five answers in one run: read, propose, your approval, the write, the receipt.

Try it live

Tagged in#workflow automation#software#approvals