Sales Process Optimization: Measure a Bottleneck Before a Pilot

Define the problem narrowly

Fictional team records ten completed proposal requests. Each request has working days spent waiting for missing buyer scope information and working days of active preparation. Five complete requests wait 1 day each; five incomplete requests wait 5 days each. Active preparation takes 1 day for every request. These categories do not overlap.

Salesforce discusses process optimization as a way to examine sales workflow efficiency. For this fixture, the question is whether incomplete handoffs account for a measurable share of delay, not whether staff should simply prepare proposals faster.

Calculate the current delay

Design the proposed pilot

Pilot idea: before submitting a request, the coordinator checks that final scope, required date and buyer review contact are present, or explicitly marks an unresolved item. The proposal lead returns unclear requests through the agreed process instead of silently guessing. The process owner approves the trial; this is a written exercise only.

Record request date, completeness status at submission, waiting time, active time and whether the proposal needed correction. Keep the starting and ending events the same as the baseline. Count a request still unfinished at cutoff separately instead of pretending its waiting time is zero.

Read the pilot result without overclaiming

Suppose ten later completed requests have total waiting of 18 days and active preparation of 10 days. Mean elapsed time is(18+10)÷10=2.8 days, compared with 4 in the supplied baseline: a 1.2-day reduction, or 30%.

That before-and-after result is encouraging evidence for this small fixture, not proof that the check caused the change. Request complexity or staffing may differ. Check the supplied quality record too: if corrections increased, a shorter elapsed time may hide rework elsewhere. No correction counts have been provided here, so quality remains unresolved.

Write a decision record rather than declaring success

Completed note: “Waiting time was the main observed component. A later ten-request group had lower mean elapsed time, but request comparability and correction counts require review. The process owner should assess those gaps before deciding whether to extend the trial.”

Practice task: identify one reason not to compare calendar days in the pilot with working days in the baseline. Answer: the units differ, so the reported change could reflect the measurement choice rather than workflow performance.