The short answer
Track estimates by the next real action: sent, awaiting response, owner conversation, appointment requested, accepted, declined, deferred, or no response. Keep contact permission and opt-outs separate from sales stages. A reply or appointment request must not automatically become an accepted job.
Write down what each stage requires
“Interested” is subjective. “Appointment requested” is observable but still not a confirmed visit. Use labels that another person can interpret without guessing what the owner meant.
The tracker is a working record, not a legal definition of contract acceptance. Your business should define how the correct quote version is approved and what documentation is needed before a job becomes accepted.
- Sent: current estimate delivered through the chosen process.
- Owner conversation: a reply needs human attention.
- Appointment requested: preferred times are collected, not confirmed.
- Accepted: the owner has verified acceptance of the correct scope.
Do not make permission a sales stage
A homeowner can be interested in a fence and still opt out of texts. Maintain channel permission and suppression separately so a stage update cannot accidentally reactivate outreach.
Likewise, a manual pause should remain in force until the owner resolves it. Moving a record from deferred to active must not silently override a previous request to stop.
Pair each active stage with an owner and next action
A stage without a next action can hide a forgotten conversation. Record who will answer, what they need to review, and when they agreed to reconnect. If there is no next action, decide whether the record should remain active.
Review inactive records by reason. No response, explicit decline, and deferred timing point to different improvements; combining them into one “lost” bucket makes the follow-up process harder to diagnose.
A practical example
Four distinct events
A homeowner replies, asks for a visit, receives an owner-confirmed appointment, and later accepts a revised quote. Record those events separately rather than counting the first reply as a booked installation.
Suggested operating model. These stages describe a process and are not a claim that every stage is currently automated in Fencepost.