Saturday, January 31, 2009

False Alarm Reduction Association ( FARA ) cancels conference

1. We have just been notified the annual FARA conference in Denver Colorado is canceled. Although the conference is heavily influenced and sponsored by a company with a competitive product (Crywolf), we have enjoyed attending and adding one or two new clients each year that recognized the value proposition in our false alarm and alarm registration tracking software. We like to distinguish ourselves by giving the client the ability to modify the existing product to match exactly the needs of our clients without affecting our base product, reports, and other functionality. Older false alarm products have to be used as is; if it doesn't fit, you have to make do.

The False Alarm Reduction Association has been a good source of new clients for us over the last five years. We have welcomed at least one client each year into the EnablePoint family from the conference. We have been very proud of our success at FARA and also that clients of EnablePoint have been in attendance at subsequent FARA events.We are disappointed in the turn of events, but this appears to be the trend nationwide as a result of budget cuts.

Conferences and conference attendance in general are down nationwide. The most notable conference that struck me recently was the news of Apple Computer no longer attending Macworld. The way we sell our products and services is changing quickly along with everything else in the world.

My "elite" frequent flyer status is going away this year, thanks to web-ex allowing remote software presentations and support, and of course less airplane rides. We have successfully added several new False Alarm Billing (FAB) clients using this remote presentation tool. We do travel to the client site for implementation and training, however all the up front work has been completed before we even meet our clients in person.

What will be our next marketing step? We are not sure. Interest in tracking false alarms is increasing, evidenced by the increase in phone calls from the Internet. Most of these calls are cities considering and weighing the option of outsource versus purchase of software.

Outsource or Purchase false alarm software?

The short answer is the decision is up to each jurisdiction. We are getting a lot of cost inquiries, as the outsourcing companies are selling the idea of no upfront costs, and then a split of the generated revenue. This is a very good short term idea, however in the long term we have difficulty understanding the concept. It is true most jurisdictions do not have the personpower to staff a false alarm administrator position. It is also true that false alarm software can become expensive if your alarm ordinance is not exactly the most logical. The main reason to purchase over outsource would be that ALL of the recurring revenue (or as some prefer, "cost recovery") will go to your jurisdiction after what we would consider a very good ROI ratio of 500+ percent.

For those of you crunching the numbers, our software sells at an average of $15,000. plus implementation costs.

For the larger jurisdictions, the implementation and/or coding changes might grow your implementation to $20 to $30K. If you have concerns about the scalability of our software, consider the fact that we had a client importing around 2,700 incidents per day ( false alarms, true alarms, and many other events). Testing of your specific software configuration is done at our location in the Detroit Michigan area, and implementation and training is done onsite with you in person. The larger implementations mentioned requires a Microsoft SQL database, and of course our smaller implementations in Microsoft Access can be priced as low as $4,995.

As you may be able to tell, I am new at blogging. This is my second post, so when we get to the blog being this long I feel like I am rambling. I can be personally reached by anyone who wants to talk more about outsourcing False Alarm Tracking, or any other software development issues. Please give me a ring at 734-634-1576.

Frank A. Farren

No comments:

Post a Comment