Putting AI to work across a national charity
We helped a national charity adopt AI across the team, with a shared AI workspace and the training and guardrails that make it stick.
The tool that was right at 200 devices doesn’t feel right at 2,000. Nothing broke. No outage, no support ticket, no red banner telling you to act. It just quietly started costing more than the number on the invoice.
That’s the trap with asset inventory tools. They’re priced and pitched as infrastructure, so they get bought once and left alone. Nobody puts “review the inventory tool” on a roadmap. It sits there working, technically, until one day someone asks “how many devices do we actually have” and the honest answer is “we’re not sure.”
Here’s what outgrowing one of these tools actually costs, on the invoice and off it.
The bill you can see
Most inventory tools, Lansweeper included, price by asset count in tiers. Free up to a point, then a paid tier with a minimum, then the next tier up once you cross another threshold. It’s a sensible model for a vendor. It’s a bad one for you, because the trigger for your next bill isn’t “we need a new feature.” It’s “we hired people” or “we opened a site” or “the estate grew the way estates do.”
You can end up paying for headroom you don’t use, because the tier jumps in blocks rather than tracking your actual count. Or you cross a threshold you didn’t plan for and the renewal quote is a surprise. Either way, the tool’s pricing model is reacting to your growth, not your usage.
That’s a real cost, and it’s the easy one to spot. It’s also not the one that costs the most.
The costs that don’t show up on an invoice
The expensive part of outgrowing an inventory tool is what it stops telling you.
Manual reconciliation creeps back in. At 200 devices, a spreadsheet gap here and there is a five-minute fix. At 2,000, someone is spending real hours every month chasing down what the tool missed, and that time never gets costed against the tool itself.
Blind spots grow with the estate. Remote workers, IoT, anything that doesn’t sit neatly on the office network, these were always the edge cases. At scale, the edge cases are a meaningful share of what you own, and most inventory tools were built to scan a network, not to see a device that’s never on one.
Audits get slower, not faster. The whole point of an inventory is to answer “what do we have” quickly. When that answer takes a project instead of a query, the tool has stopped doing its one job, even if it’s still technically running.
Nobody wants to touch it. By this point the tool is embedded, the exports feed other systems, and replacing it looks like a bigger job than living with it. So the gaps get worked around instead of fixed, and the workaround becomes the process.
None of that shows up as a line item. All of it is a cost.
How to tell you’ve actually outgrown it
A few honest signals, in order of how much they should worry you:
- You’re moving up a pricing tier this year because of headcount or device count, not because you need anything the new tier adds.
- Nobody in the business can say, with confidence, how many devices you actually have right now.
- “Where is this device and is it a risk” takes longer to answer than it should.
- Remote and IoT devices are effectively invisible until something goes wrong with one of them.
- The tool tells you what exists. It doesn’t tell you which of those things is actually dangerous.
If none of that applies, the tool is fine. Growth isn’t the same as outgrowing something, and a bigger invoice on its own isn’t proof you need to switch.
Buy a bigger tool, or diagnose the actual gap
The instinct, once a tool feels tight, is to shop for a replacement. That’s usually the wrong first move. “We’ve outgrown this” and “we bought the wrong thing to begin with” look identical from the outside, and they call for different fixes.
Before any of that gets a budget line, it’s worth working out what the tool is actually meant to be doing for you now. Pure inventory? Security posture? Compliance evidence for an audit that’s coming? Those are different problems with different answers, and a lot of switches happen without anyone doing that work first, which is exactly how you end up outgrowing the replacement too. That diagnosis, done properly, is cheaper than a wrong migration.
If the tool in question is specifically IT asset inventory
If this is landing because Lansweeper or something like it is the tool you’re weighing up, Obsonis’s Lansweeper comparison is a useful next stop. It puts eight tools side by side, Lansweeper included, on pricing model and what each one actually covers beyond a device count, which is the exact question this post has been circling.
The real cost
The sticker price of outgrowing an inventory tool is the smallest part of it. The real cost is the blind spots, the manual work nobody budgeted for, and the false confidence that comes from a tool that still runs but no longer sees everything it should. That’s worth diagnosing properly before it’s worth buying anything new.
— and we’ll tell you honestly whether the problem is the tool, the process, or something else entirely.
