What a Category Is
Software categories look like natural divisions and are mostly commercial ones. Knowing where they came from explains why every shortlist contains products that do not resemble each other.
Reviewed August 9, 2026.
Where categories come from
Analyst firms and review platforms define them, because a directory needs sections and a report needs a market to size. For a related operational perspective, Monitask also publishes a reference on how to identify mouse jigglers among a remote team.
Vendors position into them, choosing which category page to appear on based on where the buyers are.
And buyers inherit them, searching for "project management software" because that is the phrase that exists.
For broader context, see ClickUp.
None of that makes a category wrong. It makes it a description of how products are sold rather than of what they do.
Why the boundaries do not hold
Every successful tool grows into its neighbours, and a CRM is where that accumulates most expensively while scheduling is where it spreads most quietly.
A time tracker adds invoicing. An invoicing tool adds projects. A project tool adds time tracking. After five years all three appear in all three categories, each strong in its origin and adequate elsewhere.
Which produces the recurring shortlist problem: three products in one category, one of which is a time tracker with project features, one a project tool with time features, and one built for the category from the start.
They will win on different things and a feature comparison will not reveal which is which.
The question that cuts through it
"What was this product originally for?"
Find the founding story, the first version, the earliest documentation. The origin predicts what is deep and what is shallow, and it predicts it better than any current feature list.
A tool is usually excellent at its origin and adequate at everything added since. That is not a criticism — an adequate second function you already own frequently beats an excellent one you have to buy, integrate and administer.
But knowing which is which tells you where the product will disappoint, and that is the useful part.
Sizing the question before shortlisting
Write down the one thing this tool must do well. One sentence. If it takes three, you may be looking at two tools.
Then the things it must do adequately. (In accounting that list is partly set by law.)
Then the things you are hoping for. (In HR and payroll several of those are set by jurisdiction rather than by preference.)
Shortlist on the first list only. The second and third are tiebreakers, and letting them into the primary criteria is how organisations buy a suite that is mediocre at the thing they actually needed. Size the list to the team you have.
The alternative to a category
Sometimes the answer is not in one.
A spreadsheet, for a process with five participants and no compliance requirement.
A feature of something you already pay for, which is the most commonly missed option — several categories on any shortlist are already partly covered by an existing subscription nobody audited.
Or nothing, where the process is not yet stable enough to encode in software.
The short version
- Categories are defined by analyst firms and review platforms because directories need sections, and vendors position into them
- They describe how products are sold rather than what products do
- Every successful tool grows into its neighbours, so after five years the same three products appear in three categories
- Ask what a product was originally for — the origin predicts what is deep and what is shallow better than any feature list
- Write one sentence for what the tool must do well, and shortlist on that alone
- Check whether the need is already covered by an existing subscription, a spreadsheet, or nothing at all