Comparison
Best Elevator Software:
The Four Options You Actually Have
Every elevator company shopping for software is choosing between four categories, whatever the brand names on the shortlist. This page explains what each category is good at, where each one runs out of road, and how to tell which one your operation actually needs.
Start Here
The Feature List Is the
Wrong Comparison
Most software comparisons in this industry are checkbox tables, and checkbox tables hide the decision. Two products can both claim maintenance scheduling. One means a calendar reminder. The other means a schedule that shifts when the controller reports a door cycle count above threshold. The word is identical. The capability is not.
A more useful comparison starts with categories, because categories share a shape. A generic field service tool will always be a horizontal product with lifts bolted on. Elevator-specific SaaS will always be a fixed product with a vendor roadmap. An in-house build will always cost you a permanent team. A built-to-spec system will always start with a scoping phase. Those constraints are structural, and they matter more than any individual feature.
We build the fourth category, and we will say plainly where the other three are the better buy. If you are running twelve lifts in one city with one contract type, engaging an engineering partner to build you an ERP is the wrong use of your money. Read the fit criteria honestly before you read our pitch.
The Four Categories
What Each Option Is,
and When It Fits
Generic field service and CMMS tools
Horizontal job management software sold to plumbers, HVAC contractors, facilities teams and lift companies alike. Work orders, scheduling, a technician app, basic invoicing.
When it fits
Small to mid service operations whose immediate problem is that jobs live in a WhatsApp group and a spreadsheet. It is quick to start, cheap per seat, and it will genuinely improve dispatch discipline within weeks.
Where it runs out
It has no concept of a lift. There is no controller connection, no floor position, no door cycle, no fault code. AMC contract structures, per-unit warranty windows and multi-year service agreements get forced into fields that were designed for something else. Accounting sits in a separate system and gets reconciled by hand.
Elevator-specific SaaS products
Subscription software written for the lift industry. Unit registries, maintenance schedules that understand AMC visits, elevator fault categories, and in some cases a monitoring device.
When it fits
Companies that want lift-aware software without running an engineering project. The domain model is already right, onboarding is measured in weeks, and the vendor carries the roadmap. For a company whose process is close to the industry norm, this is often the sensible answer.
Where it runs out
You are buying a vendor opinion of how an elevator company should run. Where your approval chain, pricing structure, regional hierarchy or billing rules differ from the assumptions built into the product, you adapt. Controller coverage is whatever the vendor already supports, and ERP and accounting usually stay outside the product.
Building it in house
Hiring hardware, firmware, backend and frontend engineers and building the connected product yourself, either as a standalone team or inside an existing IT function.
When it fits
Companies with a real strategic reason to own the technology, the capital to fund a multi-year team, and the management capacity to run engineering as a second business. If the connected product is the product you intend to sell, owning it outright makes sense.
Where it runs out
The hard part is not the first prototype. It is controller coverage across a mixed portfolio of lifts, OTA update infrastructure, field failure diagnosis, and keeping four disciplines staffed for years. Attrition in a two-person firmware team is an existential risk. Most in-house elevator IoT efforts stall between working prototype and reliable deployment across every elevator.
A built-to-spec system
An engineering partner designs the interface hardware, writes the controller-specific firmware, and builds the operations, CRM, ERP and accounting layers to your written specification. You own the result.
When it fits
Companies whose workflows are genuinely their own, who run a mixed or older set of controllers, who want operations and money in one database, or who intend to sell the connected product under their own brand.
Where it runs out
It starts with a scoping and discovery phase, so the first live data is weeks away rather than days. It costs more upfront than a subscription. If your process is standard and you run few elevators, you may be paying for flexibility you will never use.
Side by Side
Structural Differences,
Not Feature Checkboxes
These rows describe what each category can do by construction. Individual products vary inside a category, so treat this as a starting frame and verify against the specific vendor in front of you.
| Criteria | Built to spec | Generic field service | Elevator SaaS | In-house build |
|---|---|---|---|---|
| Reads live controller data | Yes | No | Partial | Yes |
| Elevator domain model | Yes | No | Yes | Yes |
| Custom approval and workflow logic | Yes | Limited | Partial | Yes |
| CRM in the same system | Yes | No | Partial | Partial |
| ERP and accounting in the same system | Yes | No | No | Partial |
| Fast time to first live data | Partial | Yes | Yes | No |
| You own the roadmap | Yes | No | No | Yes |
| Criteria | Generic field service | Elevator SaaS | In-house build | Built to spec |
|---|---|---|---|---|
| Reads live controller data | No connection to the lift | Depends on supported devices | Yes, once engineered | Engineered per controller type |
| Elevator domain model | Generic assets and work orders | Built for lifts | Whatever you build | Built for lifts, to your definition |
| Custom approval and workflow logic | Limited configuration | Within product limits | Full control | Written to your spec |
| CRM in the same system | Usually separate | Varies by product | If you build it | Included in scope |
| ERP and accounting in the same system | Separate, reconciled manually | Commonly out of scope | A second large project | Included in scope |
| Time to first live data | Days, but no lift data | Weeks | Many months | Weeks after controller mapping |
| Cost shape | Low recurring per seat | Recurring per seat or per lift | Salaries, indefinitely | Project engineering, then support |
| Who owns the roadmap | The vendor | The vendor | You | You |
Reads live controller data
Generic field service: No connection to the lift
Elevator SaaS: Depends on supported devices
In-house build: Yes, once engineered
Built to spec: Engineered per controller type
Elevator domain model
Generic field service: Generic assets and work orders
Elevator SaaS: Built for lifts
In-house build: Whatever you build
Built to spec: Built for lifts, to your definition
Custom approval and workflow logic
Generic field service: Limited configuration
Elevator SaaS: Within product limits
In-house build: Full control
Built to spec: Written to your spec
CRM in the same system
Generic field service: Usually separate
Elevator SaaS: Varies by product
In-house build: If you build it
Built to spec: Included in scope
ERP and accounting in the same system
Generic field service: Separate, reconciled manually
Elevator SaaS: Commonly out of scope
In-house build: A second large project
Built to spec: Included in scope
Time to first live data
Generic field service: Days, but no lift data
Elevator SaaS: Weeks
In-house build: Many months
Built to spec: Weeks after controller mapping
Cost shape
Generic field service: Low recurring per seat
Elevator SaaS: Recurring per seat or per lift
In-house build: Salaries, indefinitely
Built to spec: Project engineering, then support
Who owns the roadmap
Generic field service: The vendor
Elevator SaaS: The vendor
In-house build: You
Built to spec: You
Send us your shortlist and your controller types. We will tell you which category actually fits, even when it is not ours.
Book a Straight Answer →Our Category
Where Built to Spec
Earns Its Cost
Three situations make the engineering cost worth paying. If none of them describe you, buy the subscription and spend the money elsewhere.
- You run a mixed or older set of controllers
- Your approval chains and contract types are genuinely your own
- You want operations, CRM, ERP and accounting on one database
- You intend to sell the connected product under your own brand
- You have the capital and patience for a scoping phase
- Off-the-shelf pricing scales badly at your projected number of elevators
Your workflows are genuinely yours
Regional approval chains, contract types the industry does not have a standard name for, pricing that varies by client tier and service line, inspection formats mandated by a specific authority. Fixed products handle these with free-text fields and a manual process on top. Built to spec means the approval chain is modelled as it exists, and the report comes out of the system rather than out of a spreadsheet.
Operations and money in one database
AMC renewals, spare parts consumption, proposal approvals, invoicing and SLA credits are all downstream of service data. When they live in a separate accounting package, month end becomes a reconciliation project and margin per contract is a guess. Building CRM, ERP and accounting against the same schema as the ticket and the asset removes the handoff.
Controller-level data on mixed elevators
Most real portfolios of lifts are a mix of VVVF drives, relay panels and proprietary OEM boards across decades of installs. Coverage is an engineering question, not a licensing one. When the interface hardware and firmware are written for your panels, the awkward legacy units become readable instead of staying invisible.
And where it does not. A single-city operation with under about fifty lifts, one contract template, modern controllers from one manufacturer, and no plan to sell a connected product will get more value faster from a subscription. Buy the tool, run it for two years, and revisit the question when the constraints start to bite.
Evaluation Checklist
Six Questions for
Every Vendor
Ask these of us too. The answers separate categories faster than a demo does, and they surface the assumptions a feature list is designed to hide.
How does this read our controllers?
A demo dashboard proves nothing about your panels. Ask which controller families are already supported, what the interface looks like electrically, and what happens with a proprietary or legacy drive nobody has connected before.
What happens when the site loses connectivity?
Lift machine rooms are basements and rooftops. If the device does not buffer locally and resync, you will have gaps in exactly the records you need during a dispute.
Do service data and billing data share a database?
If AMC billing lives in a different system, somebody reconciles by hand every month. That is where renewals lapse and invoices go unsent.
Can our approval chain be modelled exactly?
Most quoting delays are approval delays. If the product supports one level of sign-off and you need three with regional conditions, the workaround becomes email again.
What is the export path if we leave?
Ask for the raw schema and a full export, not a PDF report. Data you cannot extract is data you do not own.
What does year three cost?
Per-seat and per-lift pricing scales with your growth. Model the fee at your projected number of elevators, not the one you have today.
Frequently Asked Questions
Questions Buyers Ask
While Comparing
The honest answer is that the four categories solve different problems, so the best choice depends on the number of elevators you run, controller mix, and how unusual your process really is. If jobs are chaotic and the lifts are offline, a generic field service tool fixes the immediate pain fastest. If you want lift-aware software without an engineering project, elevator-specific SaaS is a reasonable buy. If your workflows, contract structures and accounting rules are genuinely yours, a built-to-spec system is the only category that will match them without compromise.
Keep Reading
Related Pages
Tell Us What You Are
Comparing.
Bring your controller list, the number of elevators, and the two or three workflows that are currently costing you the most. We will map them against the four categories and give you a direct recommendation, including when the answer is to buy something off the shelf.