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.
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
- 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
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
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
Scope, stated plainly
What we don't do
We are a software company, not an alarm contractor. In Texas, planning, certifying, selling, installing, servicing, monitoring and maintaining fire detection and fire alarm systems all require an Alarm Certificate of Registration from the State Fire Marshal's Office, held by a firm with licensed technicians on staff. That is real work, it is licensed for good reasons, and it is not ours.
We don't touch your panel. We don't connect to it, program it, commission it, certify it, or advise on system design. Everything we build sits beside the fire alarm system, working from exports, schedules, reports and records — never from a live connection to life safety equipment.
Which means we are not competing with your alarm contractor. If you're a building owner, we'll 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.
We will
Build the record systems, documentation, migrations and integrations that surround your fire alarm work — and hand you every line of the source code.
We won't
Program, service, certify, install or monitor a fire alarm system, or write anything that makes an automated change to one. Those stay with your licensed technician.
Why say so out loud
Because the fastest way to lose a life safety client is to be vague about where your competence ends. We'd rather publish the boundary than negotiate it later.
Context we already have
Systems we work around
We don't program these. We read their exports, migrate their schedules, and build the software that surrounds them.
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. Never hourly. 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?
No, and we don't work as one. We're a software company. Everything requiring an Alarm Certificate of Registration stays with your licensed technicians — see the scope section above, which we wrote first for exactly this reason.
Do you connect to the panel?
No. We work from exports, device schedules, inspection records and monitoring reports. There is never a live connection between anything we build and life safety equipment.
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. No flag days, no big-bang launches.
Talk to the engineer who'd do the work.
No sales rep, no discovery deck. Fifteen minutes on how your records actually move, and a straight answer about whether we can help.