Small-business outsourcing research

What does a new-customer onboarding handoff lose between sales and delivery?

A protocol for comparing what sales promised with what delivery received, including scope, dates, access, and the first success measure.

Research question and scope

This protocol asks what information is lost when a new customer moves from sales to delivery. The unit is one new-customer handoff inside the observation window. The study compares the sales record, the contract, and the delivery record for scope, dates, price, access, and the first success measure. It does not evaluate whether the salesperson was honest or whether the customer's expectations were reasonable.

Set the scope to one small business, one sales team, and one delivery team. Record the customer record, the contract template, and the onboarding checklist in force at the start. If the process changes during the window, keep the earlier definition for the full sample or analyze the change separately. A new checklist can look like a better handoff when it is only a new form.

Population and unit of analysis

Define the population as all new customers who signed an agreement during the window and started delivery within the observation period. The unit is the customer handoff, identified by the customer and the agreement date. A customer who buys a second service later is a new unit if the handoff is separate. A handoff that is paused and resumed remains one unit with a timeline.

Record the service type, the deal size, the salesperson, and whether the delivery team was involved before the signature. These strata matter because a large custom deal and a small standard service carry different handoff needs. Include customers who cancelled before the first delivery, because the reason is part of the evidence. Test the unit definition on two ordinary handoffs before collection begins.

Definitions that make the measure reproducible

Define the sales record as the written summary of scope, price, dates, exclusions, and promises that existed before the signature. Define the delivery record as the information the delivery team had on the first working day. Define a lost detail as a field present in the sales record but missing, contradicted, or unusable in the delivery record. Define a first success measure as an observable outcome agreed with the customer for the first thirty days.

Do not count a detail as transferred when it exists only in a call recording that the delivery team never listened to. Do not count a verbal introduction as access. A detail that was transferred but later contradicted by the contract is a conflict rather than a loss, and should be coded separately. Each definition should include one positive example and one boundary example.

Evidence standard and data dictionary

For each handoff, capture the customer, the service, the deal size, the salesperson, the signature date, and the first delivery date. Add the scope, price, start date, exclusions, access requirements, and the first success measure from both records. Record whether the delivery team was introduced before the signature and whether the customer confirmed the summary. Code each field as present, missing, contradicted, or not applicable.

Also record whether the customer had to repeat information and whether the first delivery slipped. These fields help explain a loss that was not visible in the documents. If a field was transferred in a meeting, record the meeting date and the attendees. A second coder should be able to classify the handoff from the packet without asking the salesperson what happened.

Sampling and collection

Draw the sample from the agreement log and the delivery board rather than from a list of recent complaints. Record the export date, the filters, the row count, and the selection rule. Include deals of different sizes and service types so the result is not dominated by one large customer. If the population is ordered by signature date, a fixed interval spreads the sample across the window.

Collect the sales record and the delivery record as they existed on the first delivery day. Do not reconstruct a missing detail from a later conversation. If the sales record was edited after the handoff, record the edit time and analyze the original separately. Note the collection date separately from the signature date so the reader can see how much of the record has aged.

Analysis and reporting

Report the share of handoffs with each field transferred, the share with a contradiction, and the share where the customer had to repeat information. Show the counts by deal size and service type. Present the share with an agreed first success measure and the share with a delivery slip. Use the same denominator for every rate and show the number of handoffs with incomplete evidence.

Inspect the handoffs with the most lost details and describe the pattern without naming the salesperson. A cluster in custom deals may point to a scoping template, while a cluster in standard services may point to an assumption that the service is simple. Compare the loss with the first delivery result, because a lost detail may or may not have caused the slip. Report the cancellations separately.

Limitations and sources of error

The record cannot show whether the customer would have stayed or whether the delivery team could have recovered with better communication. It can show only what was written and what the delivery team had. A complete handoff is not proof of a happy customer, and an incomplete one is not proof of a lost account. The protocol also cannot capture the informal conversations that happen between sales and delivery.

Customer records can omit verbal promises, side agreements, and details that were shared in a meeting. A promise that was never written down may not appear in the sample. Record those cases and their treatment instead of dropping them silently. If the same person sold and delivered the service, note the independence limitation and analyze that subgroup separately.

Review cadence and next action

Give the result to the sales lead and the delivery lead and ask them to choose one observable change. The change might be a required handoff field, a pre-signature introduction, or a customer-confirmed summary. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the contract template and the checklist at the same time.

Repeat the protocol with the same definitions after the change and compare the same fields. If scope transfer improved but delivery slips did not, the issue may be capacity rather than information. If customer confirmation improved but repeats did not, the summary may be arriving too late. Close the review when the owner accepts the finding and the next sample is scheduled.

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