Small-business outsourcing research
What share of customer referrals are rewarded within the stated window?
A protocol for measuring how many qualifying customer referrals receive their reward inside the window the business promised.

Research question and scope
This protocol asks what share of qualifying customer referrals receive the promised reward within the window the business states. The unit is one referral entry, not one customer and not one sale. The study measures the time from qualification to payment, the share of entries still open, and the entries that were denied after being counted. It does not judge whether the referral offer was a good marketing investment.
Set the scope to one business, one offer version, and one payment method. Record the offer document, the reward amount, and the date the terms took effect. If the terms change during the window, keep the original rule for referrals already received and analyze later referrals separately. A new reward amount can change both the volume and the approval behavior without changing the process.
Define the population as every referral entry created during the window, including entries that were later denied, duplicated, or expired. State any exclusion, such as an employee referral handled under a separate program, and apply it to every entry. Test the definition on ten closed referrals before collection begins. The reader should be able to rebuild the population from the register and the payment records.
Definitions that make the measure reproducible
Define a qualifying referral as an entry that met every condition in the offer version in force when it arrived. Record the condition that made it qualify, such as a first paid invoice or a completed service. Define the stated window as the number of calendar or business days the business promised, and record which one it used. A window that is not written down cannot be measured against.
Define payment as the date the reward was issued, applied as a credit, or marked as sent in the payment system. A promise to pay is not payment until the transaction appears in the record. If the reward is a discount, record the date the code was created and the date it was used. The difference between issue and use is useful but should be reported separately.
Record whether the referral was denied, duplicated, or expired before qualification. Keep those entries in the denominator and report them as separate outcomes. Do not remove a denied entry simply because it makes the completion rate look better. The measure should show what happened to every referral the business received.
Evidence standard and data dictionary
For each entry, capture the referral identifier, the referrer, the referred customer, the received date, the offer version, and the qualification date. Add the approval date, the approver, the payment date, the amount, and the payment method. Record the channel that brought the referral and the owner of the first contact. Keep the customer's written referral linked to the entry.
Capture the reason for a denial or delay when it is documented: an existing prospect, a missing name, an expired offer, an unapproved reward, or a dispute. 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 stage that actually needs repair.
Record whether the customer was told about the delay and what the business said. A referral that is paid late without a message is a different finding from one that is paid late after an explanation. Note the reminder dates and the person who sent them. These details matter because the customer experience is part of the promise.
Sampling and collection
Collect every referral in the window rather than a sample, because the reward promise applies to each qualifying entry. If the business runs several locations or partner programs, collect each separately and record the group. A combined rate can hide one group with a persistent approval problem. Report the number of entries behind every percentage.
Draw dates from the referral register and the payment system, not from a spreadsheet maintained after the fact. If the register is incomplete, say so and reduce the claim. Record the export date, the filters, and any entry that could not be matched to a payment. A missing payment record is itself a finding about the control.
Ask the owner to identify weeks when a promotion or a seasonal sale changed referral volume. Those weeks can produce delays that have nothing to do with the normal process. Record the event and analyze those entries separately. The reader should be able to tell whether the rate reflects the rule or the calendar.
Analysis and reporting
Report the share of qualifying referrals paid inside the window, the share paid late, and the share still open at the end of collection. Show the median and range of days from qualification to payment. Present the results by offer version, channel, and approver role. Use the same denominator for every rate.
Separate time spent waiting for the customer from time spent waiting for an internal approval or payment run. A customer who never confirms a name is a different finding from a reward that sat unsigned for two weeks. Report both because they lead to different fixes. A business may accept a customer delay but should not accept an internal delay without a documented decision.
Inspect the oldest open entries and describe which stage dominated without naming the customer. A missing qualification event, an unassigned approver, and a payment batch cutoff each point to a different repair. Compare the delay with the stated window and the reminder schedule. Report entries with incomplete dates rather than dropping them from the denominator.
Limits of the evidence
The register can show that a reward was paid, but it cannot show that the customer was satisfied with the offer. A paid referral may still have produced a poor experience for the referred customer. The protocol also cannot capture a verbal promise that was never written down. State that limitation before presenting the rate.
A small business may have too few referrals to support a stable trend. Describe the entry count and the offer amount instead of ranking staff. If one owner approves every reward, 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 volume and turnover.
Do not compare a business that pays after the first invoice with one that pays at the moment of referral. The two operate different triggers even when the completion rate looks similar. Report the qualification rule beside the rate. A target that can be met by denying difficult referrals 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 referral field at intake, a named approver, a weekly payment run, or a simpler reward rule. 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 paid-on-time rate rises but disputes also rise, the team may be approving entries that do not meet the offer. If both fall but denials increase, the business may be enforcing the rule more strictly without improving the customer experience. 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 owner which referral was hardest to qualify and why. A concrete answer often reveals a missing name, a prospect that was already in the pipeline, or a partner agreement that nobody could find. Use that answer to improve the intake rather than to blame the customer. The next measurement should test whether the same delay shrank.
Sources
- U.S. Small Business Administration, marketing and sales, U.S. Small Business Administration; checked 2026-11-17
- Federal Trade Commission, endorsement guides, Federal Trade Commission; checked 2026-11-17
- Federal Trade Commission, advertising and marketing guidance, Federal Trade Commission; checked 2026-11-17
- U.S. Government Accountability Office, internal control standards, U.S. Government Accountability Office; checked 2026-11-17
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
How often do failed subscription payments recover without manual contact?
A protocol for measuring how many failed subscription payments recover through the retry schedule before a person has to intervene.
What share of lost-package claims close inside the carrier claim window?
A protocol for measuring how many lost-package claims reach a final carrier decision before the claim window closes.
How long do job applicants wait for a first response from a small business?
A protocol for measuring the time between an application and the first substantive response from a small-business hiring process.