Custom Quote vs Catalog Price Decision Tree

Why this matters

Every catalog eventually meets a job that does not fit it, and the moment a tech or a dispatcher has to decide "do I quote this off the catalog or write a custom number" is a moment where inconsistent judgment costs the shop money, either by under-pricing scope the catalog never accounted for, or by scaring off a customer with a custom quote for something that should have been a routine catalog price. This tree gives the call a repeatable order instead of a gut call that differs by whoever answers the phone.

Start here: does a catalog entry exist for this scope

Before anything else, confirm whether the job in front of you actually matches an existing catalog line, not just a similar one.

• If the scope matches a catalog entry's description exactly (same access, same complexity, same included parts and labor), use the catalog price. Do not "eyeball a discount" or "round up for hassle" on a matching entry. Consistency is the entire value of having a catalog.
• If the scope is close but not exact, move to the next question rather than forcing the catalog price.
• If nothing in the catalog resembles this job, skip to "build a custom quote" below.

If the scope is close but not exact

This is the most common gray zone and the one most likely to be handled inconsistently across a crew. Ask, in order:

1. Is the difference in access or condition, not scope? A harder-to-reach unit or a corroded fastener is added difficulty, not added scope. Most catalogs should carry a documented "difficult access" or "additional time" modifier for exactly this. Use it if the catalog has one; if it does not, that is a catalog gap to flag, not a reason to freelance a number on the spot.
2. Is the difference an added component or step the catalog entry does not include? If the base catalog entry does not cover it, price the additional piece separately, either from another catalog line (if one exists) or as a genuine custom add. Do not silently absorb it into the base price and do not silently pad the base price to cover it either; both hide real information from future estimates.
3. Is the difference smaller in scope than the catalog entry (a partial version of a full job)? Resist the urge to quote the full catalog price for less work. A customer who feels overcharged for a smaller job on a first visit is a customer who negotiates hard on every visit after.

If, after these three questions, the job still cannot be cleanly assembled from catalog entries plus a documented modifier, treat it as custom.

If nothing in the catalog resembles this job: build a custom quote

1. Scope it in writing before pricing it. What exactly is included, what is excluded, what assumptions are you making about access and condition. A custom quote without a written scope is the single biggest source of change-order disputes later.
2. Price from your real cost basis (labor hours at your loaded rate, materials, a margin consistent with your other work), not from a gut feel of "what sounds fair." A custom quote priced on instinct tends to drift low, because the instinct is calibrated against catalog jobs that already have overhead baked in.
3. Flag it for catalog review. A custom quote that comes up more than once or twice is telling you the catalog has a gap. Log it (a running list, a tag in the estimate, whatever your shop uses) so the person who owns the catalog sees the pattern instead of relearning it job by job.
4. Get a second set of eyes on anything unusually large or unusual in scope, before it goes to the customer. A custom quote skips the guardrails a catalog price already has built in, so it needs a different guardrail: another person's judgment.

Recap

Match first, modify second, custom last. A catalog entry that fits exactly always wins. A near match gets a documented modifier, not an eyeballed number. Only a genuine gap earns a from-scratch custom quote, and every custom quote is a candidate for becoming tomorrow's catalog entry if it keeps recurring.

References

• Trade-standard practice for scope-based estimating in field service
• See related: Simplifying an Overgrown Catalog
• See related: The Catalog Entry for a Service You Rarely Do