How to scale UniAsset as you grow
The thing that does not change
Assets are unlimited on every plan, including the free one.
You will never be prompted to upgrade because you have too many assets. Asset count is a health indicator, not a revenue lever — so growth in your estate never forces a commercial decision.
What does change as you grow is operational depth: what you need the system to do, not how many rows it holds.
What growth actually demands
| As you grow | What you need | Plan |
|---|---|---|
| More people using it | More seats | Orbit, then Odyssey |
| Maintenance becomes a process | PM rules, work orders, checklists | Orbit |
| Finance starts asking questions | Depreciation, TCO, Fixed Asset Register | Orbit |
| Equipment moves between people | Asset Check-Out | Orbit |
| Leadership wants a portfolio view | Executive Dashboard | Odyssey |
| Response times become commitments | SLA engine and escalation | Odyssey |
| Other systems need the data | REST API and webhooks | Odyssey |
| Directory becomes the source of truth | Entra sync | Cosmos |
The upgrade moment is operationally motivated. A team that has started scheduling maintenance needs the maintenance tier; a team requesting an API key has already declared its intent to integrate.
Structure is what scales, not effort
The structural decisions that hold up at scale:
Put PM rules on categories, not assets. A category rule governs every asset in it, including assets added later. This is the difference between a schedule that maintains itself and one that needs manual work with every purchase.
Keep the location hierarchy shallow and consistent. Two to four levels. Filtering includes descendants, so you rarely need more.
Use Asset Stock for interchangeable units. Twenty identical spares are one record with a quantity, not twenty assets to maintain.
Agree naming before a bulk import. Renaming a thousand assets afterwards is a job nobody does.
Get these right early and growth costs you very little. Get them wrong and every new asset adds friction.
Distribute the work
A single administrator does not scale.
Site or department leads as Managers — they create and update assets, assign them, and manage maintenance in their own area.
Technicians as Employees — they update assets, complete maintenance, and check items in and out.
Finance and leadership as Viewers, unless they need to see work orders, in which case they need at least Employee.
See Team workflows.
Watch data quality, not volume
At scale, the risk is not the number of records — it is the proportion that are thin.
Use asset intelligence regularly to find assets missing purchase data, missing maintenance history, missing documents, or with no recorded activity. A thousand well-recorded assets are worth more than five thousand half-recorded ones.
Stale asset detection surfaces the inventory that has quietly stopped being managed — which is the failure mode of a growing estate.
Automate the input
Once records are arriving faster than people can type them, move to the REST API (Odyssey and above) for anything recurring, and webhooks to push events into your own systems.
A monthly spreadsheet round-trip is a process waiting to go wrong.
Where UniAsset stops
Be clear about the edges so you pair it with the right things:
- Not an ERP — no procurement, purchase orders, or general ledger
- Not a full CMMS — no technician dispatch optimisation, workforce routing, or shift scheduling
- Not a warehouse management system — no bin locations, pick and pack, or shipping
- Not an IT service desk — no ticket queues or change management
- Not a real-time IoT automation platform — signals are stored and displayed, nothing reacts automatically
Where one of those is genuinely required, UniAsset feeds it rather than replacing it.
Related articles
Need Help?
If you have questions not covered in this article, our support team is here to help.
Contact Support