When it makes sense

Some illustrative examples: equipment hire priced by item and number of days, a training course priced by seats and format, a photography package priced by hours and the number of edited images. In each, the customer already knows the answers that set the price.

  • The price depends on a handful of answers the customer can give without help.
  • The rules are stable: they change a few times a year, not every week.
  • Most requests fall inside the rules, and the ones that do not are easy to spot.
  • An estimate that turns out slightly wrong can be corrected without real harm.

What has to be decided first

  1. The questionsOnly the answers that change the price, asked as choices rather than free text wherever possible. A question that does not change the price is cut.
  2. The rulesBase prices, what each answer adds or takes away, minimums, combinations you do not offer, and rounding. Written down and signed off by whoever owns pricing.
  3. What the customer seesAn exact price, a range or a starting price, what it includes and leaves out, and how long it holds.
  4. When a person looks firstAnswers outside your normal limits, or anything you want to check, send the request to you instead of showing a number.
  5. What happens when something goes wrongA missing or contradictory answer gets a clear message, not a wrong price. If the calculator fails, the visitor can still send their answers as a request.
  6. Where the quote goesEach quote is saved with its answers and the version of the rules that produced it, and reaches your CRM or inbox so someone can follow up.

What the build includes

  • The question form on your site, in plain words and easy to use on a phone.
  • The pricing rules kept in one place, separate from the page, so a price change does not mean a rebuild.
  • A record of every quote: the answers, the price shown and the rules version.
  • A notification to you, and the quote on the lead's record in your CRM.
  • A check before launch: the calculator is run against jobs you have already priced by hand, and any difference is settled before a customer sees it.

When not to build one

If most jobs need an inspection or a conversation before anyone can price them, a calculator will be wrong more often than it is right. The same goes for prices that move every week with material costs, and for pricing that is negotiated. And if price questions are rare, a published price list or a clear starting price on the page does much of the same job for far less.

Honest limits

  • The calculator is only as good as its rules. Rough rules give rough prices.
  • Some visitors will take the number to a competitor. That happens with a quote by phone too.
  • An estimate should look like an estimate. Say what the price depends on, and that it is confirmed before work starts unless you are happy to be held to it.
  • If an AI step reads a free-text description, its job is to fill in the answers, not to set the price. The number comes from your rules, so it can be explained and repeated.