How to Explain Aspire Software

This is how I’d explain Aspire Software from a high level to new users…

1. First and foremost; Aspire is a “Work Ticket Based” system. Every ticket has revenue we earn and direct costs that we incur ascribed to it. This is called job costing and allows us to see on a single service occurrence whether or not that occurrence was profitable. This is the entire point of the system and the reason it was built. Full stop. If you’re not going to strive to job cost accurately and as close to the dollar as you can, Aspire is not for you.

2. Aspire is a “Property Centric” system. You’ve probably heard this if you’ve sat in on a logic demo from Aspire. Everything centers around, gets connected to, or built on top of a “Property” in the system. This is very intentional and easily allows us to view profitability, schedule, send bids, etc. by property. This would be opposed to a “Customer Centric” system. Some may prefer the latter, but for our industry, I’d make the case that the Aspire methodology is more beneficial. You can still report by customer, it just takes a little bit of thoughtfulness when building your reports.

That’s how I start my "Logic Demo" of the system with clients. I have found that understanding the basic framework before showing the actual system significantly improves how they receive the "demo" portion of the presentation and therefore allows them to learn Aspire faster.