Collecting data is easy. Getting it back out in a form that answers a real question is the hard part, and it is where a lot of tools fall down.
Edventory has a report builder that lets you pull the data that matters to you without needing me to build a custom report every time someone asks. You pick what you want to see and it assembles it. The point is to put the answers in the hands of the person who has the question, instead of making every report a support request that takes a week.
On the other side of the system there is invoicing. For operators running Edventory, there is branded invoicing built in, so billing looks like it came from you and not from some generic third party. If you provide technology services and you need to bill for them, the tool that tracks the work can also bill for the work. That keeps the whole loop in one place, from the device, to the ticket, to the cost, to the invoice.
This is the same theme again, and I am not going to pretend otherwise, because it really is the organizing idea of the whole product. Keep the loop closed. The system that holds your data should let you report on it. The system that tracks your work should let you bill for it. Every time you have to export to another tool to finish a job, you have created a seam where things get lost. I try to remove those seams wherever I find them.