Small-business outsourcing research

What share of customer estimates go out without a follow-up date?

A protocol for measuring how many customer estimates leave a service business without an owner and a dated follow-up.

What share of customer estimates go out without a follow-up date?

Research question and scope

This protocol asks what share of customer estimates leave the business without a named follow-up owner and a dated next contact. The unit is one estimate version, not one customer and not one job. The study measures the share missing a follow-up date, the time to first contact, and the share that never receives a recorded answer. It does not judge whether the customer was likely to buy.

Set the scope to one business, one estimate template, and one sales process. Record the system that holds the estimate and the rule for who follows up. If the process changes during the window, keep the original rule for estimates already sent and analyze later estimates separately. A new customer-relationship tool can change the record without changing the selling behavior.

Define the population as every estimate version sent to a customer during the window, including revisions and estimates that were later withdrawn. State any exclusion, such as an internal cost sheet that was never sent, and apply it to every version. Test the definition on two weeks of estimates before collection begins. The reader should be able to rebuild the population from the estimate system.

Definitions that make the measure reproducible

Define a follow-up date as a calendar date recorded on the estimate or in the customer record before the estimate was sent. Define an owner as a named person or role, not a shared inbox. A note that says "call next week" is not a dated follow-up. Record the exact text when the record is ambiguous.

Define first contact as the first outbound message or call after the estimate was sent, excluding an automated delivery receipt. Record the date, the channel, and the person who made contact. If the customer replied first, record that separately rather than counting it as business follow-up. The distinction matters because a customer reply is not a follow-up process.

Use the same estimate export for every week and keep the export timestamp beside the file. Record any estimate sent outside the system, such as a PDF from a personal mailbox. If a revision replaced an earlier version, keep both with the same customer identifier. An estimate that is missing from the export cannot be counted as sent.

Evidence standard and data dictionary

For each estimate version, capture the estimate number, the customer identifier, the amount, the send date, the owner, the follow-up date, and the expiry date. Add the first contact date, the customer answer, and the final status. Record whether the version was a revision and which earlier version it replaced. Keep the sent document linked to the record.

Capture the reason for a missing follow-up date when it is documented: a rush job, a template gap, a new salesperson, or a customer who asked not to be contacted. Do not infer a reason from an empty field. If the reason is unknown, mark it unknown and report the count. A guessed reason hides the process step that actually needs repair.

Record the number of follow-up attempts and the channel used. One attempt by email is different from a call and a written summary. Note whether the business has a written follow-up rule and whether it was followed. A rule that exists but is never used is a different finding from no rule at all.

Sampling and collection

Collect every estimate in the window rather than a sample, because the follow-up rule applies to each one. If the business has several salespeople or locations, collect each separately and record the group. A combined rate can hide one group with a persistent problem. Report the number of estimates and the total value behind every percentage.

Draw dates from the estimate system and the customer record, not from a spreadsheet maintained after the fact. If the record is incomplete, say so and reduce the claim. Record the export date, the filters, and any estimate that could not be matched to a customer. A missing record is itself a finding about the process.

Ask the sales lead to identify weeks when a large job or a holiday shortened the follow-up window. Those weeks can produce missing dates that have nothing to do with the rule. Record the event and analyze those estimates separately. The reader should be able to tell whether the rate reflects the process or the calendar.

Analysis and reporting

Report the share of estimates sent without a follow-up date, the share without a named owner, and the share with no recorded contact. Show the median and range of days to first contact. Present the results by salesperson, customer type, and week. Use the same denominator for every rate.

Separate estimates that received no contact from estimates where the customer replied first. A missing business follow-up is a process gap, while a customer reply is an answer that still needs a next step. Report both because they lead to different fixes. A business may accept a customer-driven pause but should not accept silence without a decision.

Inspect the largest estimates with no follow-up and describe which stage failed without naming the customer. A template gap, a handoff error, and a busy week each point to a different repair. Compare the delay with the estimate value and the expiry date. Report versions with incomplete dates rather than dropping them from the denominator.

Limits of the evidence

The record can show whether a date was entered, but it cannot show whether the salesperson intended to follow up. A date entered by a template may not reflect a real plan. The protocol also cannot capture a conversation that was never logged. State that limitation before presenting the rate.

A small business may have too few estimates to support a stable trend. Describe the estimate count and the value instead of ranking salespeople. If one owner sends every estimate, the result may reflect that person's availability more than the process design. Do not use the rate as a performance score without the context of seasonality and staffing.

Do not compare a business that follows up on every estimate with one that waits for the customer to return. The two operate different processes even when the missing-date rate looks similar. Report the follow-up rule beside the rate. A target that can be met by sending automated messages nobody reads is not a good target.

What to change

Give the result to the owner and the sales lead and ask them to choose one observable change. The change might be a required follow-up date in the template, a named owner at send time, a weekly review, or a shorter estimate expiry. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions after the change.

If the missing-date rate falls but the no-contact rate stays high, the field may be filled without a real follow-up. If both fall but revisions rise, the team may be reworking estimates instead of answering the customer. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.

Ask the salesperson which estimate was hardest to follow up and why. A concrete answer often reveals an unclear scope, a missing decision maker, or a price question that nobody could answer. Use that answer to improve the template rather than to blame the salesperson. The next measurement should test whether the same gap shrank.

Sources

Frequently asked questions

Does a favorable sample prove the routine caused the result?

No. The design is observational and supports a bounded operating decision, not a universal causal claim.

What should an owner review first?

Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.

Related research