For an elevator company, cost mostly comes down to how much of the operation you're automating. Dispatching callbacks alone (reading an incoming request, checking which technician is free and nearby, assigning and confirming) is a contained piece of work. Add scheduling for maintenance contracts, generating and filing inspection paperwork, and drafting proposals for new contracts or modernization jobs, and you're asking for a system with several moving parts talking to each other: your field service software, your calendar, whatever you use for e-signatures and record keeping. More parts and more integrations mean more build time, and that's the first thing that sets the cost.
The other factor is whether we build it and hand it over, or build it and keep running it. A one-time build costs less up front, but someone on your team still has to watch it, fix it when a vendor's login page changes, and handle whatever it can't resolve on its own. When we operate a system, we're the ones checking it works every day, updating it when something breaks, and stepping in only when a decision genuinely needs a person, so the ongoing cost reflects real, continuous work rather than software left to run unattended.
Some of this work should stay with a person. Whether an inspection finding is serious enough to pull an elevator out of service, how to talk down an angry building manager after a callback, and final pricing on a large modernization job are calls a system should flag, not make on its own. To judge if automating is worth it, look at how much staff time currently goes into scheduling, chasing paperwork, dispatching technicians, and writing proposals, and whether that volume is steady enough to keep a system busy. Because the price depends entirely on your specific mix of workflows and whether you want it built or built-and-operated, the honest next step is a short conversation about what your team actually does each week.