Elevator Service Business Software: Complete Guide to Maintenance, Compliance, and Contract Management

An elevator service business looks, on paper, like a field service business — technicians driving to job sites, doing scheduled work, and writing tickets. In practice it is closer to a hybrid: part route-based maintenance contractor, part heavy-equipment service, part construction subcontractor when modernization work comes through, and part regulated entity answering to a state Department of Labor or municipal Bureau of Boilers and Elevators. The software stack has to cover all of it.

This guide walks through what elevator service contractors actually need from software in 2026, the contract revenue mechanics that make this industry unique, the ASME A17.1 and DOL compliance touch points you cannot ignore, and how to evaluate platforms without overpaying.

Most well-run elevator service shops are 60 to 80 percent recurring contract revenue. The math is straightforward: every elevator in the country needs a service contract, those contracts run multi-year, and the renewal rate at most reputable shops is north of 90 percent. The bidding cycle is competitive — you are quoting against a handful of national and regional players for every building over a certain size — but once you win the contract, you have stable monthly revenue for the life of the agreement.

This is dramatically different from most other field trades. A plumbing shop bills mostly by the call. A roofing contractor bills mostly by the project. An elevator shop bills by the contract, and one missed renewal can cost six figures of annualized revenue. That is why your software stack has to do contract management at the level of detail mortgage software does loan management. Renewal dates, escalator clauses, scope inclusions, exclusions, response time SLAs, parts coverage, after-hours rates, ride quality guarantees — all of it has to be queryable in seconds, because a building manager is going to call and ask whether their next escalation is at 3 percent or CPI, and the answer cannot be 'let me get back to you.'

Elevator code in the United States is governed by ASME A17.1 / CSA B44, with state and local jurisdictions adopting and amending it. The most common touch points your software has to handle are: the maintenance control program (MCP) per unit, scheduled testing on prescribed intervals (cat-1 annual, cat-5 every five years for traction units, etc.), fire service testing, brake testing, smoke detector and recall testing, governor and safety testing, and on hydraulic units the in-line check valve and pressure relief verification.

In most states the elevator inspector is a credentialed third party (QEI-certified) who shows up, witnesses your tech performing the test, and signs a state form that gets filed with the AHJ. Your software needs to schedule the test, alert the inspection company in advance, store the signed test report, and renew the unit's certificate of operation. Miss a test and the AHJ can pull the certificate, which means the unit cannot legally run — and your customer will hold you responsible.

The Department of Labor angle matters too. Elevator mechanics in most states are licensed individually (mechanic, helper, apprentice tiers), and the work hours of an apprentice toward licensure must be tracked. Your software should track license numbers, expiration dates, and apprentice hour progress alongside basic HR data.

Most elevator shops earn the steady revenue from maintenance contracts and the windfall revenue from modernization projects. A modernization can be a $40,000 controller swap, a $200,000 cab interior refresh, or a $1.2 million full mod with new machine, controller, fixtures, and ADA upgrades. These are construction projects with elevator-specific quirks: long-lead-time equipment, hoistway shutdowns that have to be coordinated with the building, escalating retainage, and lien waiver requirements at every progress draw.

Your software stack has to handle this side as a true project module — schedule of values, AIA-style billing, change orders, RFIs, submittals, and a punch list at closeout — not just as a glorified service ticket. If your platform forces you to run modernization as a multi-day work order, you will lose track of money and the GC will eat you alive on closeout.

A typical elevator contract lifecycle starts with a survey. A salesperson walks the building, counts cars, captures equipment data, identifies the controller and drive, and notes any visible deferred maintenance. The proposal includes the maintenance contract (priced per unit per month with a defined scope), a list of recommended repairs to bring units to baseline, and an optional modernization line item if any unit is past useful life. The customer signs and the contract is created in the system with anniversary date, escalators, and SLAs.

From there: scheduled maintenance work orders generate on the route mechanic's calendar at the agreed frequency (monthly, bimonthly, or quarterly). Unscheduled callbacks come in via phone, customer portal, or building management system integration. Every visit logs to the unit's history. State inspections schedule themselves twelve months from the last one and trigger a workflow to coordinate with the QEI inspector. Annually, the contract escalates per the agreed clause and an updated invoice generates. Every five years a cat-5 load test schedules itself. And every three years (or whenever the contract term ends), a renewal proposal generates with updated pricing.

In parallel, modernization opportunities surface from the maintenance data — units with rising callback rates, recurring component failures, or end-of-life controllers get flagged for sales follow-up. That feedback loop between service and sales is what keeps a healthy elevator company growing.

The elevator industry has a small number of vertical software platforms (CompuPlus and a handful of competitors) priced at $80 to $200+ per user per month with significant implementation fees. They are deeply opinionated for the trade and integrate with elevator-specific equipment data sources — but they assume a certain operational maturity and the price premium reflects that.

Mid-market field service platforms (BuildOps, ServiceTrade, ServiceTitan) handle the maintenance and callback side well at $75 to $200 per user per month, but most do not natively model multi-year contracts with escalators or modernization projects with AIA billing. You will fill the gaps with QuickBooks, project software, and spreadsheets.

Generalist all-in-one platforms (Deelo at $19 to $69 per seat per month) handle CRM, recurring contracts, scheduling, mobile field service, project management, and document control in one system. You will spend setup time configuring contract templates and AIA billing schedules, but you avoid stitching three or four platforms together and you avoid enterprise pricing.

Deelo is an all-in-one AI-native platform at $19 to $69 per seat per month. For elevator service shops, the relevant pieces are recurring contract billing with custom escalator support, a CRM that tracks per-unit asset histories, scheduling and dispatch with mobile offline support, project management that handles modernization with phased billing, and document management for MCPs, certificates, and lien waivers. The AI assistant can summarize callback history per building, draft a renewal proposal, or pull a list of units due for cat-5 testing in the next 90 days.

For shops below 50 mechanics that want one operational system rather than a stack of vertical tools, Deelo replaces three to four platforms at a fraction of the combined cost.