Elevator Estimating and Quotation Software (2026 Guide)

By Sumeet Katariya, ElevatorPlus · Published 16 September 2026 · Last updated 16 September 2026 · ~11 min read

In short: Elevator estimating software builds a quotation from a rate list and a past job rather than from a blank page, so the number that goes out matches the number the business can deliver. Most estimating tools fail for one reason, which is that the sales team keeps using the spreadsheet they trust. The tool that wins is faster to a sendable document in the company's own format, carries a price book somebody owns, and hands the accepted scope to operations without a retype.

Key takeaways

• The brief is narrower than buyers expect. A rate list that is current, a past job you can carry forward, margin applied line by line, and a document in your own format. Everything beyond those four things is decoration.
• Adoption is decided by speed, not accuracy. A tool that is more accurate but slower than the spreadsheet loses on a busy afternoon, and the loss stays invisible for months because nobody announces a reversion.
• A price book without an owner decays. Supplier and labour costs move, the rate list does not, and the first symptom is a job that came in on price and out on margin.
• The retype between quotation and contract is where scope goes missing. In year one nobody notices. In year two it is the argument, because two documents that were meant to say the same thing do not.
• Three measures tell you whether it is working. Days from enquiry to quotation sent, acceptance rate split by product type, and margin at quotation against margin at completion.

What this guide covers: what estimating software actually has to do · why the quotation module gets abandoned · what a price book is and why it decays · where estimating errors come from · how a quotation becomes a contract without a retype · what the document should look like · revisions, approvals and acceptance · how to measure adoption · FAQs.

What does elevator estimating software have to do?

The job is narrower than most buyers expect. It has to hold a rate list that reflects what your parts and labour actually cost this quarter. It has to carry a past job forward, because almost every new enquiry is a variation on something you have already priced.

It has to apply the right margin to the right lines, since a hydraulic goods lift and a passenger machine room less unit do not carry the same commercial logic. Then it has to produce a document in your own format, with your terms and your assembly names, ready to send without anyone opening a word processor afterwards.

That is the whole brief. Everything else an estimating tool offers is decoration until those four things work.

It also helps to be clear about where estimating sits. It is the hinge between the sales conversation and the delivery commitment, which is why it belongs in the same system that runs projects and installation work. A quotation is the first version of the job, and treating it as a standalone document is what produces two versions of the truth later.

Why does the estimating tool get abandoned?

This is the part nobody puts in the business case. Most estimating tools are built for the finance team's view of a quotation, which is a cost sheet with a margin on top. The estimator's view is different. The estimator is trying to reproduce a document a customer already recognises, quickly, while the site visit is still fresh.

When those two views collide, the estimator wins, because the estimator is the one under deadline. If the tool cannot output the layout the customer expects, someone rebuilds the layout by hand. If the tool takes eleven clicks where the spreadsheet took three, the spreadsheet comes back out for the urgent one, and then for the next urgent one.

Nobody announces this. The estimator quietly reverts, the tool keeps its licence, and the reports coming out of it slowly stop matching what is actually going to customers. A year later someone runs a margin review and finds half the year's quotations were never in the system at all.

So the test is not whether the tool impresses in a demo. The test is whether it beats the spreadsheet on a Tuesday afternoon with three enquiries pending and a customer waiting. Speed to a sendable document is the only measure that decides adoption. A tool that is more accurate but slower will lose, every time, and the loss will be invisible for months.

Two practical consequences follow. First, whoever chooses the tool should watch an estimator build a real quotation in it, start to finish, timed. Not a demo quotation with tidy inputs, but a real one. Second, the company's actual quotation format has to be set up before rollout, not promised for phase two. Phase two is where estimating tools go to die.

What is a price book and why does it decay?

A price book is the rate list sitting underneath every quotation. Parts, labour rates, and standard scopes such as a routine modernisation package or a standard maintenance visit, each with a defined content so that pricing them is a lookup rather than a judgement call.

It decays for an ordinary reason. Supplier prices move, labour costs move, and nobody owns the update. The price book is everybody's responsibility, which means it is nobody's, and it drifts further from reality every quarter it is left alone.

A price book last reviewed eighteen months ago is quietly quoting at a loss on some lines and quoting yourself out of the market on others. The first sign is rarely a complaint. It is usually a job that came in on price and out on margin, and by the time you notice, you have won several more of the same kind.

Give the price book an owner and a review date. It does not need to be a committee. It needs one person whose name is against it and a fixed month when the rates get checked against what procurement actually paid.

There is a practical link here to the parts side of the business. A rate list kept by hand, separately from the bill of materials you order against, is always a second copy of something, and second copies go stale. When the assemblies a quotation is built from are the assemblies procurement recognises, the review becomes a check rather than a rebuild.

Where do estimating errors actually come from?

The fourth row is the commonest, and the least discussed. Every retype is a chance for a detail to fall out. The customer remembers the conversation on site. The quotation records something slightly narrower, and the difference only surfaces when someone asks why a job is not covered.

The fifth row is the easiest to remove, because it is purely a filing problem. If revisions live as versions of one record rather than as separate files, there is nothing to attach by mistake.

How does a quotation become a contract without retyping?

The retype is where the gap between what was sold and what is serviced first opens. Sales agrees a scope, the quotation is accepted, and then somebody in operations builds the service contract by reading the quotation and typing it again into a different form. Small things go missing. Which door operators are covered, whether the controller is included, what the visit frequency actually is.

In year one nobody notices, because the equipment is new and nothing needs arguing about. In year two that gap is the argument. The customer says a component was covered, your engineer says it was not, and both of them are working from different documents that were supposed to say the same thing.

When the contract is created directly from the accepted quotation, that gap closes. The equipment list carries forward as it was priced. The scope carries forward as it was written. If the quotation named eight lifts with specific controllers and a defined visit frequency, the contract says the same, because it was not retyped by anyone.

That carried-forward scope is also what your maintenance and inspection reminders should be built from. A visit frequency that was typed twice will eventually be scheduled against the wrong one of the two.

👉 Wondering whether your own quotation format can survive the move into software?

See how branded quotations are built →

What should the document itself look like?

Like something your customer already expects. Your letterhead, your terms, your ordering of sections, and the assemblies named line by line rather than hidden behind a single word.

"Comprehensive" is the most expensive word in this industry. It means one thing to the person selling it and another to the person paying for a rope replacement in month twenty. A quotation that lists the assemblies, ropes, controller, door operator, machine, safety gear, and states plainly what sits inside the price and what does not, prevents that argument before it starts.

The formatting matters more than it should, because a document that does not look like your other documents gets rebuilt by hand, and the rebuild is where the tool loses. This is why document generation from your own templates is a practical question rather than a cosmetic one.

What happens between the first draft and the signature?

A quotation is rarely sent once. It gets revised, discussed, approved internally, sent again, and eventually accepted. The tool has to survive that whole sequence, and most of the pain sits in the middle of it rather than at the start.

Revisions come first. Can two versions of the same quotation exist as versions of one record, with the earlier one visible but clearly superseded? If revisions are separate files, someone will send the wrong one.

Approvals come next. When a quotation needs sign-off above the estimator, does the tool route it, or does it rely on a message that may or may not get answered? Approval routing that is part of the record means the authorisation sits with the quotation rather than in somebody's inbox. The same applies once work is under way, where a change order is only worth anything if it was approved before the labour was spent.

Then acceptance. How does the customer say yes, and where does that yes get stored? A signature captured against the quotation record removes the most common gap in the whole chain, which is an acceptance that exists only as an email nobody can find two years later.

If you quote across borders, add one more. A quotation raised in one currency and reported in another needs currency handling inside the system rather than a conversion done in a spreadsheet, which is correct exactly once, on the day it was done.

How do you know it is working?

Three measures, and you can start tracking all of them this month.

Days from enquiry to quotation sent. This is the adoption measure. If it is not falling after rollout, the estimators are working around the tool and you should ask them why rather than assume.

Quotation to acceptance rate, split by product type. Aggregate win rate hides everything useful. Split by product and you can see whether you are losing passenger jobs on price while winning goods lifts, which tells you something specific about where your rates sit.

Margin at quotation against margin at completion. This is the one that exposes a stale price book. When the two numbers agree, the price book is close to reality. When quoted margin is consistently higher than delivered margin across unrelated jobs, the problem is not the sites and it is not the engineers. It is the rate list, and it needs an owner and a date.

Add a fourth once those three are stable. The share of quotations raised inside the system. If that is not close to all of them, every other measure is read off a sample that excludes the awkward jobs, and the awkward jobs are usually the ones that lose money.

Frequently asked questions

1. What is elevator estimating software?

It is software that builds a lift or elevator quotation from a maintained rate list and from previous jobs, applies margin line by line, and produces a sendable document in the company's own format. It sits between the enquiry and the contract, and its output is the scope that delivery will later be held to.

2. What is a price book in elevator quoting?

The rate list underneath every quotation. Parts, labour rates, and standard scopes such as a modernisation package or a defined maintenance visit, each with agreed content so that pricing a line is a lookup rather than a judgement call.

3. Why do quotation modules go unused?

Because they are slower to a sendable document than the spreadsheet the estimator already trusts, or because they cannot produce the layout the customer expects. The estimator is under deadline, so the estimator reverts, and the reversion is never announced.

4. How often should an elevator price book be reviewed?

Give it a named owner and a fixed review month rather than a general intention. The trigger for reviewing sooner is a widening gap between margin at quotation and margin at completion across unrelated jobs.

5. Can a quotation become a service contract without retyping it?

Yes, and it should. When the contract is generated from the accepted quotation, the equipment list, the named assemblies and the visit frequency carry forward exactly as they were priced, which removes the most common source of scope disputes in year two.

6. What causes most elevator estimating errors?

Stale rates, a scope copied forward from a building with different conditions, blanket margin applied to lines that carry different commercial logic, a quotation retyped from a site note, and an older revision sent by mistake.

7. How do you measure whether estimating software is working?

Days from enquiry to quotation sent, acceptance rate split by product type, and margin at quotation against margin at completion. Add the share of quotations raised inside the system, because a low share makes the other three unreliable.

8. Does estimating software replace the estimator's judgement?

No. It removes the lookup, the retype and the reformatting. Deciding what a difficult shaft is going to take, and what a particular customer relationship is worth, stays with the person who visited the site.

📲 Join our WhatsApp channel for compliance tips, updates: ElevatorPlus - Business Automation Tool

The estimating problem in this industry is almost never a calculation problem. Companies that have been quoting lifts for decades know what a job takes. What they do not have is one place where that knowledge is written down, kept current, and reused without being retyped.

So the buying question is not which tool prices most accurately. It is which tool an estimator will still be using in month six. That is a question about speed, about format, and about whether the rate list has an owner. A tool can be right about every number and still lose to a spreadsheet that opens faster.

The second question is what happens after acceptance. A quotation rekeyed into a contract has already lost part of its value, because the two documents will diverge and the divergence surfaces at the worst moment. The accepted scope should become the contracted scope without anyone reading one screen and typing into another.

Get those two things right and the reporting fixes itself, because the quotations are all in one place and the rates behind them are current. Get them wrong and you will have a licence, a dashboard, and a folder of spreadsheets that nobody admits to.

👉 See how quotations, contracts and delivery scope stay on one record. Book a demo →

Related reading

• Quick Quotation: build branded quotations from your own format
• BOM Management: keep quoted assemblies and ordered parts on the same list
• Change Order Management: price and approve variations before the labour is spent
• Approval Workflows: route sign-off as part of the quotation record
• Project Management: carry the accepted scope into installation and delivery

About the author. Sumeet Katariya is the founder of ElevatorPlus, the Elevator Business Operating System used by 200+ elevator companies across 20+ countries.

Book a Demo with ElevatorPlus

 👉 Follow ElevatorPlus on,
Instagram LinkedIn Facebook YouTube Qoura Substack Twitter