Smart Elevator / Custom Workflows
Software that follows
your process.
Off-the-shelf elevator software makes you change how you work. RnD Square maps how you already work, writes the specification, builds the screens and workflows to match, integrates with what you already run, and ships changes as your process evolves. Custom elevator software development, end to end.
The hidden cost of buying
Every off-the-shelf tool
asks you to work its way.
Your process is not accidental. It came from years of learning which technician handles which tower, which client needs a call before the visit, and which approval cannot be skipped. Software that cannot express it does not remove the process, it pushes it back into WhatsApp and paper where nobody can see it.
The product has one approval path
Yours has three, because a modernization quote goes through a technical reviewer and an AMC renewal does not. The product cannot express that, so your team approves everything on WhatsApp and marks it done in the system afterwards.
The job card fields are fixed
Your technicians record things the product has no field for, so those things go into a free text note nobody can report on, or onto paper that never reaches the office.
Branches do not exist in the model
The product assumes one company, one stock, one team. You run five branches with their own purchasing authority, and the workaround is five separate logins and a consolidation spreadsheet.
The report is not the report you need
A client, an auditor or a group standard asks for a specific format. The product exports its own format, so someone rebuilds it by hand every month.
How a build runs
Discovery, spec, build,
deploy, iterate.
This is the whole method. It is unglamorous on purpose. Most custom software fails at the first two steps, because the process was assumed rather than documented, and the specification was a sales deck rather than something anyone could build from.
We map how the work actually happens.
A signed specification you review and correct.
Short cycles with screens in front of real users.
Phased rollout on your data and your process.
Scoped changes ship as the business moves.
Discovery
We sit with the people who do the work. The dispatcher who decides which technician goes where, the branch manager who approves an indent, the accounts clerk who raises the AMC invoice, the technician filling the job card in a lift lobby. We follow a ticket end to end and a contract end to end, and we write down what actually happens, including the parts that happen on paper and in phone calls.
OutputA written process map of the business as it runs today, with the failure points marked.
Specification
The process map becomes a specification: entities and how they relate, screens and who uses them, states and transitions, approval rules and their thresholds, integration points, report formats, roles and permissions. You review it and mark what is wrong. Disagreements surface here, on paper, where they cost an hour instead of in a build where they cost a month.
OutputA signed specification with scope, phases and what is deliberately out of scope.
Build
Engineering runs in short cycles against the spec. Screens go up early and get put in front of the people who will use them, because a dispatcher looking at a real dispatch screen finds problems that no amount of document review would surface. Where the engagement includes hardware, firmware development runs in parallel against your controller types.
OutputWorking software reviewed at each cycle, not a demo at the end.
Integration
We connect to what stays. Your accounting package for the statutory books, payroll, an existing dealer portal, a customer app, a BMS, or the controller itself through our interface hardware. Data mapping and migration happen here, including the historic contracts and open tickets you cannot afford to lose.
OutputA system that fits into the estate you already run rather than sitting beside it.
Deploy
Rollout is phased. The area causing the most pain goes live first, usually ticketing and maintenance or the billing run, and the rest follows once the team is confident. Training is done on your data with your process, so it is a walkthrough rather than a course. Nothing here requires a big-bang cutover.
OutputA live system, a trained team, and the old workaround retired.
Iterate
Businesses change. A new branch opens, a large client demands a different report, a regulator adds a requirement, you win a portfolio of lifts with a controller type you have never serviced. Each of those becomes a scoped change and ships. This is the difference between an engineering partner and a licence renewal.
OutputA system that keeps matching the business as the business moves.
What gets built to spec
The specifics are
the whole point.
These are the places where a product either fits your business or fights it. In a built-to-spec system each one is a decision made with you, written into the specification, and implemented as described.
| Criteria | Built to spec | Off the shelf |
|---|---|---|
| Fit to your process | Built from your process map | You adapt to the product |
| Scope of the system | Operations, CRM, ERP and accounting in one | Field service and maintenance only |
| When the process changes | Scoped change, built and shipped | Wait for a roadmap or add a workaround |
| Integration | Built for the systems you run | Whatever connectors exist |
| Ownership | You own the system | Per-seat licence on vendor infrastructure |
Approval rules that match your delegation
Value bands, category exceptions, branch authority, and the one senior who has to sign anything touching a hospital contract.
Job cards with your fields
The checks your technicians actually perform, in the order they perform them, including the ones a generic product has no field for.
Contract types you actually sell
Comprehensive, semi-comprehensive, oil and grease, unit rate, and whatever hybrid a large client negotiated. Each with its own billing and coverage behaviour.
Dispatch logic you already use
Skill, zone, current load, contract priority, or the informal rule that a specific technician always handles a specific tower.
Reports in the format they are asked for
Client review packs, audit records, regulator submissions and internal management reporting, built to the layout your market expects.
Roles that match your org chart
Branch manager, dispatcher, storekeeper, accounts, technician, dealer, client. Each seeing what they should and nothing else.
Describe the one workflow no software has ever handled properly for you. That is where we start.
Start with discovery →Off the shelf versus built to spec
Two different
kinds of decision.
Most products in this market are field service and maintenance tools. If field service is all you need and your process matches how one of them already works, buy it. If your process is specific and you need the commercial layers too, the arithmetic changes.
| Criteria | Off-the-shelf elevator software | RnD Square, built to spec |
|---|---|---|
| Fit to your process | You adapt to the product. Gaps become workarounds. | The product is built from your process map. |
| Scope of the system | Field service and maintenance. Commercial layers excluded. | Operations, CRM, ERP, accounting and custom workflows in one system. |
| When the process changes | Wait for a roadmap, or add another workaround. | Scoped change, built and shipped. |
| Integration with what you run | Whatever connectors exist. | Built for the systems you actually use. |
| Hardware and controller data | Generic device support if any. | Interface hardware and firmware written per controller type. |
| Ownership and hosting | Per-seat licence on the vendor infrastructure. | You own the system. Cloud hosted or on your own infrastructure. |
Fit to your process
Off the shelf: You adapt to the product. Gaps become workarounds.
Built to spec: The product is built from your process map.
Scope of the system
Off the shelf: Field service and maintenance. Commercial layers excluded.
Built to spec: Operations, CRM, ERP, accounting and custom workflows in one system.
When the process changes
Off the shelf: Wait for a roadmap, or add another workaround.
Built to spec: Scoped change, built and shipped.
Integration with what you run
Off the shelf: Whatever connectors exist.
Built to spec: Built for the systems you actually use.
Hardware and controller data
Off the shelf: Generic device support if any.
Built to spec: Interface hardware and firmware written per controller type.
Ownership and hosting
Off the shelf: Per-seat licence on the vendor infrastructure.
Built to spec: You own the system. Cloud hosted or on your own infrastructure.
Your extended R&D team
A team that builds your software
and keeps building it.
Off-the-shelf software is built for a market and asks every company to work the same way. RnD Square builds the software your company needs and stays to keep building it, across hardware and software, from the interface board inside the lift panel to the AMC invoice that leaves your office. You run the elevator business. We run the engineering behind it.
That matters most where the layers meet. Live controller data driving a maintenance schedule, that schedule driving material planning, and consumption on that plan landing in the invoice, are only possible when one team owns the whole path. Split that path across three vendors and the joins become your problem.
You own what gets built. It can run on your own infrastructure and carry your branding when your clients use it. When your process changes, you call the team that wrote the code rather than filing a feature request.
FAQ
Questions about building to spec
Related
What we build to spec.
Bring us the process.
We will build to it.
Discovery is where every engagement starts and it produces something useful on its own: a written map of how your business actually runs. Book a call and we will scope it.