Issue link: https://construction.trimble.com/en/resources/i/1520113
7 Make Sure It's Intuitive Many construction companies hesitate to adopt specialized software for estimating out of fear that the learning curve will be steep and that estimators invested in existing processes will resist the change. The concern is fueled by the fact that some applications available today derived from accounting or project management platforms, don't follow estimating logic and are built around older technologies. The premise is that estimators need to become software experts and change the way they work to match the way the software works. This is a recipe for failure, especially in a construction environment. The better option is an application purpose-built from the outset to be intuitive and easy to use from the perspective of an estimator – not the perspective of a software developer or accountant. These applications should follow the fundamental logic familiar to estimators. Modern, Windows-based functionality and user interfaces will also make them easy to use, ensuring enthusiastic buy-in even for employees with limited computer experience. Companies that step up to this kind of estimating application can be up and running in days – not weeks or months – producing better estimates and winning more work. Enterprise-class Performance The technology platform supporting an estimating application is vital. This is what guarantees that the program runs fast and reliably and doesn't crash, even when multiple users are working on large, complex estimates. A modern, enterprise-class architecture will also accommodate advanced functionality and features as they emerge and it will allow a growing company to scale up as its estimating needs evolve. "There was a little expected resistance among some employees comfortable with existing systems. That disappeared almost immediately, as they saw how easy the software was to use and how it made it much easier for them to be even more productive." WARNING SIGNS To get faster buy-in and ensure a successful deployment, avoid estimating applications that: • Derive from an accounting or ERP application • Don't follow estimating logic • Are built on an outdated, non-enterprise technology platform • Have difficult user interfaces that don't adhere to Microsoft Windows standards • Are not flexible to accommodate varying job types and detail requirements