For service and AMC companies
Run the contract book
off records, not memory.
Elevator service software for companies running maintenance contracts at scale. SLA exposure you can see, technician time you can account for, AMC renewals that arrive before expiry, and service delivery you can prove. Built to your contract structure, including the billing layer most field service products leave out.
A normal Tuesday
Nothing went wrong.
The day still cost you money.
Service companies rarely lose money on dramatic failures. They lose it in the small gaps that nobody logs, five of which happen in almost every operating day.
A building manager calls about a lift that stopped last night
The fault happened eleven hours ago. The SLA clock has been running unmeasured, and the first thing your coordinator has to do is work out which unit and which contract this is.
Two technicians are dispatched to sites forty minutes apart
Neither knew the other was in that area. Route and load are decided by whoever is answering the phone, so travel time is the largest line item nobody measures.
A planned AMC visit is missed because the technician was pulled to a breakdown
Nothing records the miss. The visit count for that contract quietly falls short, and the client will notice it at renewal before you do.
A client disputes last month response times
The evidence is spread across a WhatsApp group, a paper job card, and one technician memory. The dispute is settled by credit note rather than by record.
A repair quote from three weeks ago is still unsent
The finding was real, the work is still needed, and the revenue is sitting in an inbox. Nobody owns the chase because nothing tracks quote age.
What it does
Contracts, tickets, technicians
and invoices in one place.
The system is built around the object a service company actually sells, which is a contract, and around the object it actually maintains, which is a specific lift with a specific controller and a specific history.
Illustrative SLA compliance across an example contract book.
Contracts modelled properly
AMC scope, visit frequency, response commitments, escalation rates, inclusions and exclusions, and renewal dates held per contract. The system knows what a given site is entitled to before anyone is dispatched.
Tickets with a real start time
Manual, phone, portal, and auto-raised tickets land in one queue with priority and category. Where lifts are connected, the fault opens the ticket itself with controller data attached, so the clock starts at the fault.
SLA tracking and escalation
Response and restoration targets per contract tier, live countdowns on open tickets, automatic escalation before a breach, and reportable performance per client at the end of it.
Dispatch that accounts for reality
Assignment by skill, location, current load, and contract priority rather than by whoever picks up. Technician day views show planned visits and breakdowns together.
Planned maintenance that survives the week
AMC visit schedules generated from contract terms, with misses flagged rather than absorbed. Blockers such as awaited parts, site access, and pending approvals are tracked as first-class states.
Service history you can hand to a client
Every visit, part, fault and fix logged against the unit, exportable per site or contract. The renewal meeting and the dispute both stop being arguments about memory.
Renewals with numbers attached
Renewal tasks surface ahead of expiry with the contract service load, breakdown count, parts spend, and margin visible. You know which contracts to defend and which to reprice.
AMC billing in the same system
Contract billing, chargeable repairs, parts consumption, and profitability per contract and per site. Operations and accounts read from one dataset instead of reconciling at month end.
Tell us your contract count, your SLA tiers, and what your team is running on today. We will map the first stage.
Book a scoping call →Getting off spreadsheets
Staged rollout.
No big bang cutover.
A service company cannot stop operating for a migration. The build is sequenced so each stage relieves real pain and connects to the next without a rewrite.
Map the contracts and the elevators
Sites, units, controller types, contract terms, technician structure, and the reports your clients already demand. This is what the build is shaped around.
Move ticketing and SLA first
The fastest relief for most service companies is getting complaints, priorities, and response times out of chat and into a queue with timestamps. This usually goes live before anything else.
Bring planned maintenance and history across
AMC schedules, asset records, and service history follow, including import of existing records so the timeline does not start from zero.
Connect the lifts that carry the most risk
IoT is added where downtime is most expensive: your tightest SLAs, your most disputed sites, your oldest units. Live fault data then drives ticketing rather than the phone.
Close the loop with proposals and billing
Findings become quotes, approvals become jobs, and AMC and repair billing run from the same records. At this point the leak between operations and accounts is closed.
Why RnD Square
Your contracts are specific.
So is the build.
No two service companies price, schedule, or escalate the same way. Fixed products force a common shape and the team ends up keeping a shadow spreadsheet for everything that did not fit. RnD Square builds the system around what you already do.
- Every AMC contract modelled with scope, tiers, and renewal dates
- Tickets with a real start time and a live SLA countdown
- Dispatch by skill, location, load, and contract priority
- Planned maintenance that flags misses instead of absorbing them
- Service history you can export per site or contract
- AMC billing, chargeable repairs, and margin in the same system
Billing is part of it
AMC invoicing, chargeable repairs, parts, and contract margin sit in the same system as the service data. Most competitors stop at the work order and leave the money to a separate tool nobody reconciles until month end.
Real controller data when you want it
The IoT hardware and firmware are engineered in house, so when you connect lifts the fault data is genuine and mixed-make portfolios of lifts are handled per controller rather than ignored.
One team behind the whole stack
Hardware, firmware, operations, ERP, CRM, and accounting are built by the same engineering group. There is no integration project between four vendors and no argument about whose layer broke.
FAQ
What service companies ask.
Prove the service.
Keep the contract.
Bring your contract terms, your SLA tiers, and the reports your clients ask for at renewal. We will come back with a staged build plan for your service operation.