features

With today’s global reality, we wanted to take the opportunity to share some of our favorite resources to help security installers acclimate to a remote working model.
From the very beginning, we built FieldHub around distributed teams. We have key team members in the US, Canada, and Europe. Even before launching FieldHub, I ran my security integration business, Urban Alarm, with distributed teams. From accounting and HR to provisioning video servers and IP cameras, our team members were dispersed across the globe. We shared one of our configurations for remotely provisioning IP gear in a previous post here.
In this post, we have collected the tools we’ve used over the years that have made this model a success.
We’re skipping file sharing and document creation since most organizations are using Microsoft 365 or Google which are both going to provide flexibility and functionality for a distributed team.
Photo Credit: Photo by Andrew Neel on Unsplash

FieldHub, the all-in-one cloud platform for security, fire, and low-voltage integrators, is pleased to announce a new integration with fireNspec, the inspection management platform built for fire and life safety companies. The integration links inspection work to the rest of the business, so a customer or site entered in one system no longer has to be entered again in the other.
Most integrators run inspections and the business itself on different tools. The account lives in one place, the inspection lives in another, and staff spend time keying the same details into both and checking two systems to answer one question.

FieldHub has introduced Billing Rules, a new configuration engine that automates how labor, materials, and miscellaneous charges are priced and added to work order scope. Instead of a technician’s hours sitting as a gap to be filled in manually after every visit, Billing Rules writes the correct line — at the correct rate — into the work order the moment a work log is ready for invoicing.
Most platforms handle service pricing with static price books or a “service level” tag sitting off to the side of operations—a label that must still be manually translated into scope, line by line, by someone in the office.

You’d never sign a 3-year lease on a building you’ve never walked through. Why do that with your software?
Most software companies want to close the deal. We want to make sure the deal should close.
A failed implementation costs everyone—your team loses time and trust, and we lose a customer who should never have been one. The pilot exists to prevent that. Before either side commits, we work together to confirm that FieldHub aligns with your needs, your expectations, and your operational reality. If the fit is right, the project is set up for success before it even begins. If it’s not, we’d rather you know now.