The Tool That Needs a Person
Some tools run themselves and some require somebody. The second kind is not worse — it is more expensive than its price, and the difference is invisible on any comparison. For a related reference point, Monitask has a guide to the 7-minute payroll rule, which is useful when comparing whether a dedicated tool is warranted.
No affiliate links on this site, and nothing here is ranked.
What the person does
Adds and removes users. Small, recurring, and forgotten — which is how seats outlive the people who held them.
Configures. Fields, templates, permissions, automations. Anything configurable requires reconfiguring as the work changes.
Answers questions. "How do I..." arrives at whoever set it up, permanently.
Fixes what breaks. Integrations that stop, imports that fail, a report that no longer runs.
And holds the knowledge. Why it is set up this way, what the fields mean, which of the six similar-looking views is the real one.
Spotting it before buying
Five signals, visible during a trial.
A settings section you cannot understand without help. If configuration needs a call, maintenance will too.
A vendor offering onboarding as a paid service. Honest, and it tells you the setup is not self-evident.
Automations, rules, or workflow builders. Powerful and they encode decisions — decisions somebody has to revisit when the process changes.
Integrations. Every connection is a thing that can break, and the breakage arrives without notice.
And a permissions model with more than two levels, which means somebody is deciding who sees what, forever.
What it costs
Not hours per week — hours per month, unpredictably distributed.
The cost is not the total. It is that the hours arrive when something breaks, which is not when the person has time.
And it concentrates. In a small firm it is one person, and everybody else's use of the tool depends on their availability and their remaining with the business.
The single-person risk
A tool only one person can work is a tool with a departure date.
Not a reason to avoid it, and a reason to do two things.
Write down how it is set up. One page, plain words: what the fields mean, what the automations do, who has access and why. Twenty minutes, and it converts a personal arrangement into something the firm owns.
And have a second person who can do the basics — add a user, run the export, reset a password. Not full competence; enough to keep going for a fortnight.
Choosing the self-running version instead
Where a task can be done by a tool that needs nothing, that is worth a premium.
No configuration, no permissions, no integrations, no automations. It does one thing and it keeps doing it.
This is the argument for the smallest adequate tool restated in a different form: a simpler tool is not only cheaper to buy, it is cheaper to keep, and the second cost is the one that recurs.
Where you already have one
Do the one-page write-up first. It is the cheapest risk reduction available and it takes less time than the next support question will.
Then ask whether the configuration is still earning its place. Automations built in year one are frequently wrong by year three and nobody unpicks them, so the tool is being maintained against a process that no longer exists.
And note the maintenance hours for a month. Where they are substantial, that number belongs in any comparison with an alternative, and it is usually absent.
The person who wants it to need them
Uncommon and worth naming.
Somebody who set a tool up, understands it alone, and prefers it that way has made themselves necessary, usually without deciding to.
The remedy is the same write-up, requested as a routine matter rather than as a challenge — "can you put down how it works, in case you are on holiday when something breaks" is a reasonable request that nobody can object to.
Where it is resisted, that is information about a risk rather than about a person.
Configuration as accumulated decisions
Every setting is a decision somebody made, and most were made once and never revisited.
A tool configured three years ago encodes how the work was done three years ago. Processes move and configurations do not, and the gap grows silently.
An annual look at the settings — half an hour — finds automations firing into nothing, fields nobody fills, and permissions for people who left.
It is the same practice as reading the bill applied to configuration rather than to spend, and it is skipped for the same reason: nothing prompts it.
Where the person is the vendor
A category worth separating: tools sold with implementation.
Somebody configures it for you, and the arrangement works while the relationship lasts.
The question to ask is what happens afterwards — whether you can change it yourself, whether the configuration is documented, and what a change costs once the implementation period ends.
Where every alteration requires a paid request, the tool has an ongoing cost that is not on the pricing page and does not appear until you need something changed.
Ask during the sale: "What does it cost to change a field in a year's time?" The answer is informative and it is rarely volunteered.
The honest exception
Some tools are worth a person because the job is worth it.
Accounting, payroll, anything regulated — these require attention regardless of the software, and the maintenance is part of doing the thing properly rather than an overhead of the tool.
The objection on this page is to unplanned maintenance, absorbed by whoever happens to be able, on tools bought without anybody costing it. A separate outside reference is MakeUseOf.
The short version
- Some tools require somebody to keep them working, which is a cost invisible on any comparison
- The person adds and removes users, configures, answers questions, fixes breakages, and holds the knowledge
- Five signals during a trial: incomprehensible settings, paid onboarding, automations, integrations, and a layered permissions model
- The cost is not the total hours but that they arrive when something breaks rather than when there is time
- A tool one person can work has a departure date: write one page on how it is set up, and train a second person in the basics
- A tool that needs nothing is worth a premium, because the keeping cost recurs and the purchase cost does not