Smart Elevator / Proposals
Every finding becomes a quote.
Every quote gets chased.
Elevator proposal software that starts where the work is found. A technician records a condition on site, the system builds the proposal around that unit, routes it through your approval chain, and turns the signature into scheduled work. Built to your rate cards, your thresholds, and your document format.
The problem
Repair revenue does not get lost.
It gets delayed to death.
Most elevator companies have no shortage of quotable work. Technicians find it every week. The failure is in the distance between the finding and the signature, and that distance is measured in days of typing, forwarding, and remembering. Four places where it breaks.
The finding never becomes a document
A technician sees a worn door operator on a Tuesday. He mentions it to the supervisor on Thursday. By the following week the job card is filed and nobody has written a quote. The work is still needed. The revenue is gone.
The quote takes three days to leave the office
Someone has to find the part number, check the rate card, ask what the contract covers, and rebuild the same document that was built for the last five sites. Every quote is retyped from scratch, so every quote is slow.
Approval happens in an inbox
Internal sign-off is an email to a manager who is on site. Customer sign-off is an email to a facility team that forwards it to accounts. Nobody owns the chase, so the follow-up depends on whoever remembers.
Nobody can see the pipeline
Ask how much repair and modernization work is sitting in open quotes and the honest answer is a guess. Without a pipeline state per proposal, the business cannot forecast, and stalled quotes are invisible until they are dead.
The same repair, two outcomes. On the left is how a finding travels today. On the right is the same finding once every step is a tracked state.
How a proposal moves
From site observation to
scheduled work.
The proposal is a state machine, not a document. Each transition is owned, timestamped, and visible, so the question is never who is sitting on it.
Recorded against the unit on site with photos and fault data.
Drafted from your rate card with contract terms prefilled.
Routed through your chain with value thresholds.
Captured with a timestamp and an identity.
Approval reserves parts and assigns the visit.
Finding recorded against the unit
The technician logs the observation during the visit: component, condition, photos, and the fault data that supports it. It attaches to the elevator record, not to a notebook.
Draft proposal generated
The finding lands in the quoting queue as a draft with the unit, site, client, contract terms, warranty position, and service history already populated. The estimator prices it, they do not rebuild it.
Internal review and commercial approval
The draft routes through your approval chain. Value thresholds decide who has to sign. Margin, discount bands, and exception rules are applied before the document is allowed to leave.
Sent for customer sign-off
The client receives a clean, branded document with the evidence attached. Sign-off is captured in the system with a timestamp and an identity, so approval is a record rather than a forwarded email.
Approved work becomes scheduled work
Approval creates the job. Parts are reserved, the technician is assigned, the visit is scheduled, and the elevator record shows the quoted scope alongside the eventual completion.
Value lands in accounts
The approved document carries into billing and revenue reporting. The invoice references the proposal, and the parts consumed reference the same job, so month end reconciles itself.
Show us your current quote-to-approval path. We will map where it stalls and what the built version looks like.
Book a scoping call →Inside the module
What the estimator
actually works with.
The point of building the module to spec is that the person pricing a job spends their time on judgement, not on retyping context the business already holds.
What the proposal workflow covers, at a glance.
- A finding on site becomes a draft quote without retyping
- Pricing driven by your rate card, parts catalogue and discount bands
- Contract-aware pricing separates chargeable from warranty work
- Multi-stage approval routing with value thresholds and escalation timers
- Pipeline states timestamped, so stalled quotes surface by age
- Customer sign-off captured as a record, then written into scheduled work
Rate cards and parts catalogue
Your labour rates, your part numbers, your supplier costs, your discount bands. Pricing is driven by data the business already maintains rather than typed per quote.
Contract-aware pricing
The system knows whether the unit sits under AMC, under warranty, or out of contract, and prices the finding accordingly. Chargeable and non-chargeable work stop getting confused.
Evidence attached by default
Photos, fault codes, service history extracts, and condition notes travel with the document. Customers approve faster when the reason is visible.
Multi-stage approval routing
Configurable chains with value thresholds, role-based approvers, delegation for absence, and escalation timers when a stage goes quiet.
Pipeline states with age
Drafted, sent, viewed, approved, rejected, expired. Each state is timestamped, so the sales view shows what is moving and what has been sitting for eleven days.
Revision history
Every version of a quote is retained with who changed what. When a client argues about a number, you open the version they were sent.
Templates in your format
Document layout, terms, tax treatment, and language are configured to match what your clients already receive from you.
Full audit trail
Who found it, who priced it, who approved it, who signed it, and when. The trail sits against the unit permanently.
Why RnD Square
Built to your
commercial rules.
Quoting is where a company expresses how it makes money. Discount authority, contract carve-outs, regional pricing, and the difference between a repair quote and a modernization proposal are specific to the business. A fixed product asks you to flatten those rules. RnD Square encodes them.
Your approval chain, not a fixed one
Most quoting products ship with one or two approval patterns and expect you to adapt. If your commercial rules involve regional managers, contract-specific limits, or a separate track for modernization work, that logic is built in rather than worked around.
Connected to the layers that matter
Proposals only work when they sit next to service history, asset records, ticketing, and the accounting layer. Because RnD Square builds those layers too, the proposal is a live object across the business rather than a document exported to a spreadsheet.
Built on real service data
The IoT hardware and firmware are engineered in house, so the fault evidence behind a quote is genuine controller data. A proposal supported by recorded fault history is a different conversation from a proposal supported by an opinion.
FAQ
Questions we get about quoting.
Related
Where proposals connect.
Stop retyping quotes.
Start closing them.
Bring your rate cards, your approval limits, and your current quote format. We will come back with a build plan for the proposal layer and how it connects to the rest of your operation.