Tool Documents

The Team You Have

Software is frequently bought for the organisation somebody expects to have: larger, more disciplined, with roles that are currently one person doing four things.

The tool then arrives for the organisation that exists, and the mismatch is not a training problem. For a separate operational reference from Monitask, see this overview.

Four ways it goes wrong

Capability nobody uses. A product with governance, approvals and reporting built for a hundred people, bought by twelve. The features are not the cost — the configuration burden and the administrative overhead are, and they fall on somebody who also does three other jobs.

Roles that do not exist. Products assume an administrator, a process owner, a data steward. In a small organisation these are the same person, and a permission model built around separation of duties becomes friction with no benefit.

For broader context, see ZDNET.

Process the team has not agreed on. Buying a tool to settle that is the failure named elsewhere on this site.

And a price built for a size you are not. The tier with the features you were sold on is frequently priced for the headcount you were imagining.

The opposite error

Being fair, because under-buying is real too.

A tool that fits perfectly now and breaks at forty people is a migration in two years, and migrations are not cheap.

The relevant question is not current fit but the shape of the wall: does the product stop being adequate gradually, giving you time, or abruptly?

Gradual is fine. Abrupt — a hard user limit, a missing capability that becomes mandatory, a tier boundary at a critical feature — deserves planning.

What to actually buy for

The team you have, plus the growth you can evidence.

Evidence means a hiring plan, a signed contract, a funded project. Not an ambition.

And check the two-year figure rather than the current one, at the headcount the evidence supports.

The question that separates the two errors

"What breaks first as we grow, and how much notice does it give?"

A vendor can answer this and rarely gets asked. The answer tells you whether the ceiling is a wall or a slope.

And it converts the decision from a guess about the future into a comparison of failure modes, which is a much easier thing to decide between.

The under-noticed cost

Administrative time.

Every tool needs somebody to add users, remove leavers, adjust permissions, respond to changes, read renewal notices and answer questions. Six tools is a part-time job, and it is never in the business case.

For a small organisation this is frequently the binding constraint — not licence cost, not features. A simpler tool that needs no administration can beat a better one that does, and that comparison is made almost nowhere.

The short version