The program lives in one head
Control-by-event logic, device schedules, custom labels, voice messages — held in one technician's laptop and one technician's memory. When they retire, the building's configuration retires with them.
Services · Houston, TX
The software behind fire alarm work.
Panel programs documented instead of memorized. Inspection records you can produce on demand instead of reconstruct. Deficiencies that turn into invoices instead of disappearing. For fire alarm contractors and building owners across Greater Houston.
The problem
The system works. The paperwork around it doesn't.
Three things we hear from almost every life safety shop in Houston.
Records can't be produced on demand
NFPA 72 wants documented inspection, testing and maintenance history. When the AHJ, the insurer, or a buyer's diligence team asks for three years of it, someone spends two days in a filing cabinet and a spreadsheet. The fix, built for a warehouse: audits that will not close until the required photos and notes are attached.
Deficiencies never become revenue
A tech finds eight deficiencies on a Tuesday inspection. Four get quoted. Two get invoiced. Nobody can tell you which four fell through, or what that pattern costs across a year of inspections.
What we build
Four pieces of work, each one shippable on its own
Inspection, testing & maintenance records
Every inspection captured once, in the field, and retrievable in seconds for the next ten years.
- Device-level inspection capture on a phone or tablet, offline-tolerant — see field service app development
- Frequency scheduling so nothing quietly goes past due
- Deficiency logging with photos, severity and a follow-up state
- AHJ-ready reports generated instead of assembled
- Full history per building, per device, per technician
- Records that survive the technician who wrote them
Case study inspection records that lock failing equipment out of use
Panel program documentation & recovery
Get the configuration out of one laptop and into something version-controlled, searchable and inheritable.
- Device and point schedules extracted into a structured, queryable form
- Control-by-event logic documented in plain language, side by side with the program
- Version history, so you can see what changed on which service visit
- Backups of program files with an actual restore procedure
- Cross-building search: every device of a given type, everywhere you service
- Onboarding material a new technician can read on day one
Device schedule migration
Panel replacements shouldn't mean re-typing two thousand device labels.
- Point and device schedules converted between vendor formats
- Label and zone naming normalized and de-duplicated first
- Discrepancies between as-built drawings and the live schedule surfaced before cutover
- Import files prepared for your technician to review and load
- A reconciliation report proving old count matched new count
- Rollback copy of the original retained and documented
- The same reconcile-and-roll-back method we use on any system migration — the records here just happen to be devices
Integration & reporting
Close the loop between what the tech finds, what gets quoted, and what gets paid.
- Inspection findings flowing into work orders and quotes automatically
- Deficiency-to-invoice tracking, with the leakage rate on one screen
- Monitoring and receiver event data summarized for reporting
- Recurring inspection contracts and renewals tracked against actual visits
- Clean, reconciled numbers flowing to QuickBooks
- One dashboard: past-due inspections, open deficiencies, unbilled work
Where we fit
Built to work beside your licensed technicians
We're the software side of fire alarm work. In Texas, planning, certifying, selling, installing, servicing, monitoring and maintaining fire detection and fire alarm systems is licensed work: it takes an Alarm Certificate of Registration from the State Fire Marshal's Office, held by a firm with licensed technicians on staff. That work belongs to your licensed technicians, and everything we build is designed to make it easier to document, prove and bill.
Our software works from exports, schedules, reports and records, so it sits safely beside the fire alarm system while the panel itself — its programming, commissioning, certification and design — stays in your technicians' hands.
That makes us a natural partner for your alarm contractor. If you're a building owner, we work alongside whoever services your systems. If you are the alarm contractor, we're the software shop you've been looking for — the one that already understands why a device schedule matters.
What we build
The record systems, documentation, migrations and integrations that surround your fire alarm work — with every line of the source code handed to you.
What your technicians keep
Programming, servicing, certifying, installing and monitoring the system itself. Our software reads the records that work produces, and every change to a panel is made by a licensed technician.
Why it's set up this way
Life safety clients deserve a clear line between the software and the system it documents. Spelling it out up front means the owner, the contractor and the AHJ all know exactly who does what.
Context we already have
Systems we work around
We read their exports, migrate their schedules, and build the software that surrounds them, while the programming stays with your technicians.
Panels & manufacturers
- Notifier
- Simplex
- Edwards / EST
- Fire-Lite
- Silent Knight
- Gamewell-FCI
- Potter
- Mircom
The office side
- Inspection reporting apps
- Field service & dispatch software
- Work order & CMMS platforms
- Central station monitoring reports
- Building management systems
- QuickBooks & accounting
- The spreadsheets nobody admits to
- The filing cabinet, honestly
How it works
Assess, build, support
Three stages. You know what the next one costs before you agree to it, and you can stop after any of them.
Assess
We map what you run, where the records actually live, and which gaps are costing you real money across a year — in writing, with numbers, and with our own conservatism haircut applied before you see them.
Fixed fee, agreed up front. Credited back against a build.
Build
Quoted against a written specification, so the number is the number. Delivered incrementally — you'll be using a working piece of it long before the last piece lands. You own every line of the source code from inception.
Fixed price, quoted up front. Changes go through a change order.
Support
Monitoring, break-fix and ongoing improvement after launch, so the system doesn't quietly rot the way the last one did. The first sixty days are included in the build.
Month to month. Cancel with thirty days' notice.
Questions we get
Before you call
Are you a licensed fire alarm contractor?
We're a software company that works alongside licensed fire alarm contractors. Everything requiring an Alarm Certificate of Registration stays with your licensed technicians, and the section above sets out exactly who does what.
How does your software get its data from the panel?
From what the panel and your technicians already produce: exports, device schedules, inspection records and monitoring reports. That keeps everything we build safely separate from the life safety equipment itself.
We already use an inspection app. Is this still relevant?
Usually, and usually the answer is integration rather than replacement. Inspection apps are good at capturing the inspection and weak at what happens after it — turning deficiencies into quotes, quotes into invoices, and proving the whole chain three years later. That gap is where we work.
How long before we see anything?
The assessment is ten business days. Builds ship incrementally — you'll be using a working piece of it long before the last piece lands.
Get in touch
Talk to the engineer who'd do the work.
Fifteen minutes with an engineer on how your records actually move, and a straight answer on what would help most.
Prefer to talk?
Call 832-598-8234 or email msco@stoneagesoftware.com. Houston, Texas — serving Houston, The Woodlands, Conroe, Sugar Land, Katy, Pearland, and the Greater Houston metro.
What happens next
We read your message, an engineer replies with questions or a straight answer, and if a call would help, we book one. From the first reply on, you're talking to the people who'd do the work.