Sales & estimates
Define a consistent HVAC quote-conversion cohort before reporting
Prepare an AI-assisted metric definition and exception list so sent quotes, decisions and revisions are counted consistently.
Approved divided by sent and approved divided by decided answer different questions; label the denominator and observation date.
Editorial workflow guide · AI-assisted preparation · Not a hands-on product test. How we work
Write the metric definition before reading the percentage
Choose the sales question first. For a sent-quote cohort, define the sending period, unique commercial unit being counted, included quote types, revision treatment, approval evidence and observation cutoff. Ask AI to organize a definition card and identify records that do not fit. Let the reporting owner decide those rules rather than silently accepting a model’s interpretation of conversion.
This is different from assigning opportunity stages. It is a reproducible counting method for a specific report. Record whether the unit is a quote version, an opportunity or another approved entity. A revised PDF should not automatically become another potential sale simply because it has a later sent date.
Sponsors
SPONSORED
AI FOR YOURSales team.Less busywork.More selling.
Put AI to work in your HVAC sales process.
Get AI help from KnowSPONSOREDYOUR NEXT CHAPTERBuild with us.HVAC expertise.Business support.
You know HVAC.
Let’s build a business together.
Compare two fictional denominators
A fictional cohort contains 20 unique opportunities first quoted in a defined week. At the stated observation cutoff, eight have verified approvals, six have verified declines and six remain open. Approved divided by sent is eight divided by 20, or 40%. Approved divided by decided is eight divided by 14, approximately 57.1%. Neither figure can be substituted for the other without changing the question.
Keep the six open cases visible. Do not label them lost just to close the denominator, and do not remove them from a sent-cohort metric because their eventual outcome is unknown. Where two quote revisions belong to one opportunity, apply the approved counting rule and retain the revision links for audit.
Check comparability before describing a change
Give each row a stable identifier, cohort inclusion reason, source dates, observed outcome and unresolved issue. Recalculate totals outside the assistant. Show exclusions and missing outcomes alongside the percentage, including how you treated withdrawn or superseded quotes. Preserve the observation cutoff so a later approval does not appear to have been known earlier.
When comparing periods, use the same definition and comparable observation windows. A younger cohort has had less time to reach a decision. Changes in customer mix, scope or pricing also limit interpretation. Do not attribute a conversion change to AI messaging from this table alone. The assistant may draft a qualified explanation but must not update pipeline outcomes or invent approval evidence.
Review checklist
- Define the counted entity and revision rule.
- State sending period and observation cutoff.
- Show pending cases, exclusions and missing evidence.
- Use matching definitions and observation windows for comparisons.
Source context and limits
Jobber documents quotes and their workflow states. Our fictional cohort definitions and arithmetic are an independent reporting method, not a claim about the default calculation in any Jobber report.
A prompt to adapt
Prepare a quote-conversion definition card and cohort table from these approved records. Apply the supplied unique-entity, period, revision and outcome rules. Show sent, approved, declined, pending, exclusions, cutoff and separately labeled denominators. Do not infer decisions, hide open cases or claim causal improvement.
Use fictional or anonymized examples while testing. Add your approved business rules before using a draft.Source documents
Primary sources support the factual references above. The proposed workflows are editorial guidance. Confirm current product availability, pricing, and integration details directly.
Questions or corrections?
See our editorial policy for how we distinguish workflow suggestions, vendor statements, and tested results.