Module: Quote
Quotes
A customer asking "what will this cost?" is a customer who's ready to move. The faster they get a real answer, the faster they can say yes. "We'll get back to you with a quote" is where a lot of that momentum quietly dies — the customer moves on, or calls someone who answered sooner.
The trouble is that quoting is rarely as simple as looking up a price. Every business calculates a quote its own way, and most don't have anything clean to calculate it from. Getting the number fast matters — but getting it right matters more, because a wrong quote is worse than a slow one.
We Can Build the Pricing System, Then Connect It
For a lot of businesses, the honest starting point is that there's nothing to connect to yet. No quoting API, no pricing engine, sometimes not even a spreadsheet — just the way pricing has always been worked out by hand.
That's a starting point, not a blocker. The managed-service team can help build the missing piece: taking the business's pricing rules, rates, and exceptions and turning them into an actual quoting system — an API or structured logic that can produce a number reliably. Where something already exists, we connect to it. Where it doesn't, we help create it.
Once that pricing logic exists, it connects to the conversation layer. The same quoting engine can then answer through the Phone Bot when someone calls, through the Chatbot on the website, or wherever else the business talks to customers — so the customer just asks what it costs and gets an answer, without knowing or caring that a pricing system was built to make that possible.
Most Businesses Don't Start With a Pricing System
The first surprise, for a lot of companies, is that there's nothing to plug into.
There's no quoting API. Often there isn't even a spreadsheet — the pricing lives in someone's head, in a few rules of thumb, and in the way the owner has always done it. Before anything can be automated, that logic has to be pulled out and written down somewhere a system can use.
This is where the managed-service side matters. Part of setting up quoting is helping a business turn its informal pricing into something structured and reliable — capturing the rules, the rates, and the exceptions that were never written down. The business doesn't have to arrive with a pricing engine already built; helping create that is part of the work.
Some Quotes Are Calculations, Some Are Lookups
Once the logic exists, it isn't all one shape.
- Calculated quotes are built from inputs and rules: square footage times a rate, a base fee plus add-ons, tiered pricing by quantity. The answer is computed from what the customer tells you.
- Dynamic lookups pull the answer from somewhere external at the moment it's needed — checking a property's price, a live rate, a value that changes and can't be hardcoded.
Many businesses need both, sometimes in the same quote: a calculation that also depends on a value looked up in real time. The module is meant to handle either, because pricing that only supports one leaves half the business's quotes unanswerable.
Pricing Logic Changes, So It Has to Be Editable
Prices are not set once and left alone. Rates go up, a new service gets added, a seasonal discount starts and ends, a rule turns out to be wrong.
The quote logic has to be something the business can update, not something frozen at setup. When pricing changes, the quotes the system gives have to change with it — otherwise it's quoting yesterday's prices with confidence, which is its own kind of wrong answer.
Pricing Is Critical — You Cannot Get It Wrong
A wrong hour or a wrong address is an inconvenience. A wrong price can ruin the business.
Quote too low and the business is bound to a number that loses money. Quote too high and the customer walks. Either way the number was in writing, the customer saw it, and it's hard to take back. That's why quoting is built around approved logic and approved inputs rather than a free-form guess at a plausible-sounding figure. The number a customer sees should be one the business would stand behind.
Some Quotes Have to Escalate
Not every job fits the formula, and the module is designed to know the difference.
- Custom work that falls outside the standard rules shouldn't be forced into a number that doesn't fit. When a request is genuinely custom, the right move is to capture the details and hand it to a person who can price it properly — not to guess.
- Review before the customer sees it. Some businesses want a back-office manager to approve a quote before it goes out. In that case the quote is prepared, routed for review, and only sent once it's been signed off — so speed doesn't come at the cost of control.
Both are the same principle: the system handles what it can price reliably and escalates what it can't, instead of treating every request as if it fits the standard mold.
The Tension: Fast, But Right
Everything about quoting pulls in two directions at once.
Speed wins business — the sooner a customer has a real number, the sooner they convert, and nobody enjoys waiting for a quote. But accuracy protects the business, and some quotes genuinely need a human before they go out. A quoting module earns its place by getting the fast answers out fast — the standard, calculable, lookup-able ones — while cleanly routing the rest to the people who should handle them. Most customers never needed to wait. The job is to make sure they don't, without letting the ones that do need review slip out unreviewed.
Why This Is Hard
Quoting looks like arithmetic and turns out to be judgment. The pricing logic often doesn't exist in usable form until someone builds it. The quotes themselves come in two shapes, the rules change over time, the cost of a wrong number is real, and a meaningful share of requests shouldn't be auto-answered at all. Doing this well means being fast where speed is safe and careful where it isn't — and knowing, every time, which situation you're in.