Approval workflow software solves a big-company problem: a purchase request needs three signatures, the signatures live in email, and nobody knows where it is stuck. Route it, remind people, record the decision. Useful, and not the approval problem a small business has.
The approval problem in a five-person office is different. There is one approver, you, and the question is not how requests reach you but what software may do without reaching you. As soon as a tool writes to your calendar, your sheet or your customers' inboxes, that is the approval that matters.
Two kinds of approval
Approval between people. A staff member asks, a manager decides, the system records it. This is what approval workflow software does. If you have more than one layer of sign-off, you may need it.
Approval of software's own changes. An agent reads an inquiry and wants to book a showing, log a lead, send a reply. Should it? This is the approval an owner-run business lives with every day, and almost no approval software covers it, because it was built for the first kind.
Tensor Autonomous is built around the second kind.
How Tensor asks
Every responsibility in Tensor follows one rule: it asks before it writes or sends. When a task reaches a change, you see exactly what will change and where: the calendar event with its time and unit, the sheet row with every cell, the email with its recipient and text. You approve, edit or decline. Tensor shows you each change before it makes it, drafts included; nothing it drafts is sent until you send it.
That is approval at the only point it protects anything: before the write, with the real change in front of you, not a description of it.
How you stop approving every one
Approving everything forever is how people learn to click without reading. So once a routine has run right a few times, you set limits for it instead: 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. Tensor may book without asking on weekday mornings, up to three a day, say. Within the limits Tensor works without asking; outside them it stops and asks. Sending email, payments and refunds, and moving or cancelling a calendar event always ask; limits can't cover them.
Limits turn approval from a chore into a setting. The routine runs; the exceptions reach you.
The record
Approval software keeps a log of who approved what. So does Tensor, for its own changes: every run leaves a receipt with what was asked, what it read, what it proposed, who approved it and when, what it wrote, and the read-back from the record confirming the write matched. Next to each write, Undo removes what Tensor created after you confirm what will be removed; a responsibility can be rolled back to an earlier version. Sent email cannot be unsent, which is the reason every send waits for your OK; limits can't cover sending.
When you still want approval workflow software
- Several people must sign off in order, and the system needs to enforce the order.
- Requests originate as forms that need routing, not as work that needs doing.
- You need a central dashboard of pending human approvals across departments.
Tensor does not do those. It does the office work and asks you before changing anything. If you have both needs, they do not overlap.
A buyer's checklist for the second kind of approval
- Does it show me the exact change in my own account before it happens?
- Can I set limits for routine changes, and does it stop at the edge rather than guess?
- Does it show me each draft before it makes it, and leave the sending to me?
- Does it read the result back and keep a receipt I can open later?
- Can I undo a wrong write, and pause the job while I look?
If a tool answers all five, it has solved the approval problem a small business actually has.
Where to start
- Product: responsibilities, approvals, limits and receipts.
- Try it live: approve one real change on sample data.
- Plans from $149 a month.
Related reading
- Automated approval: what should run by itself, and what should wait for you
- Approval process automation: the two minutes that matter
- The receipt: what Tensor records about every run
See it in a demo
Watch a change wait for your OK, then land, then show up in the receipt.