Strike Rate and Productive Calls: The Field Sales Numbers That Matter

Ask a sales manager how a salesperson is doing and the first answer is often "he visits a lot". But visits do not pay the bills, orders do. The number that connects the two is the strike rate: the share of visits that end in an order. This guide explains the strike rate in field sales, how productive calls are counted, and how to use the figure to coach your team in a fair way.

Definitions in plain words

• Visit (call): a recorded visit to a shop.
• Productive call: a visit that ends with an order. You may also decide to count a payment collection, but write the rule down.
• Strike rate: productive calls divided by total visits, as a percentage.

Formula:

Strike rate = productive calls / total visits x 100

Example, with invented numbers: 40 visits, 26 with an order. 26 / 40 = 65 percent.

Why strike rate beats raw visit counts

Two salespeople can both do 40 visits. One books 26 orders, the other 8. A report of "visits" shows them as equal. Strike rate separates them, and it points at the right question: what happens at the door?

It also protects people on hard routes. Someone covering a difficult area may have a lower strike rate but still be doing a good job. Read it against their own history first.

Read strike rate with four companion numbers

1. Visits per day: the effort.
2. Order value per productive call: the quality. A high strike rate with tiny orders is not a win.
3. Outlets reached versus the route plan: the coverage. See retail outlet visit planning.
4. No-order reasons: the explanation.

The no-order reasons are the real gold

A strike rate tells you how many shops said no. The reasons tell you why. A good field app forces the salesperson to choose a reason when there is no order, for example stock still full, owner not present, price issue, buys from competitor or payment pending. After a month, count them:

Reason	What it usually means	What to do
Stock still full	The visit is too early	Lengthen the visit cycle for that shop
Owner not present	Bad visit timing	Visit when the owner is in
Price issue	Your price or scheme is weak	Review price list or scheme
Buys from competitor	Competitive pressure	Share with the manager, try a trial pack
Payment pending	Credit problem	Collect first. See collecting payments on time

Many low strike rates are not a salesperson problem. They are a price, timing or credit problem that the reasons reveal.

An illustrative example

Invented numbers again. Two officers in one valley branch:

• Officer A: 40 visits a day, 14 orders, strike rate 35 percent. Most no-order reasons: "stock still full".
• Officer B: 28 visits a day, 20 orders, strike rate 71 percent. Few no-order visits.

The simple reading is "B is better". A closer look shows A's visit cycle is too short, so he returns before shops need stock. Moving A to a longer cycle on those shops and adding new outlets raises his strike rate and his coverage without any extra effort. B, meanwhile, may be skipping hard shops. Check his coverage against the route plan.

How to raise strike rate fairly

1. Fix the visit frequency. Match the visit cycle to the shop's buying cycle.
2. Plan the order of stops. Visit when the owner is usually present.
3. Suggest the order. Review each shop's past orders so the salesperson can propose a quantity. Read forecasting demand from order history.
4. Clear credit blocks. A shop that cannot buy because of overdue payment needs a collection first.
5. Coach on the visit. Ride along with a weaker officer once a month.
6. Use schemes carefully. See dealer schemes that pay for themselves.

Mistakes to avoid

• Setting a single strike rate target for everyone. Routes differ.
• Rewarding strike rate alone. People will skip hard shops. Combine it with value and coverage.
• Punishing the number. Use it to start a coaching talk.
• Ignoring data quality. If visits are recorded without a real check-in, the number is not real. See stopping fake visits.

Put it in the weekly rhythm

Strike rate is most useful in the weekly meeting. Show each person's last four weeks, the no-order reasons and one action. Running a weekly sales meeting with data shows the format, and monthly sales reports per agent explains the monthly view.

A second example: raising strike rate by changing the visit cycle

A different illustrative case. A masala distributor's officer visits 30 small shops every Monday and Thursday. Over a month he makes 240 visits and books 72 orders, a strike rate of 30 percent. The no-order reasons: 95 "stock still full", 40 "owner not present", 20 "price issue", 13 "buys from competitor".

The manager notices that more than half of the failures are "stock still full", which means the officer is back before the shop needs anything. She changes the plan: the 18 fastest shops stay on a twice-weekly cycle, and the 12 slow shops move to once a week. The freed time goes to 10 new shops that have never been visited.

In the next month the officer makes 216 visits, books 86 orders and the strike rate is 40 percent, while coverage grows from 30 to 40 shops. The change cost no extra effort. It came from reading the reasons.

	Before	After
Shops covered	30	40
Visits	240	216
Orders	72	86
Strike rate	30%	40%

Common questions

Does a very high strike rate mean the officer is excellent?

Not by itself. It may mean he only visits friendly shops. Look at coverage, order value and the share of the route actually visited.

Should a visit that collects a payment count as productive?

It depends on your business. Many distributors count it separately, because a collection visit does not create sales. Whatever you decide, apply the same rule to everyone.

How many visits are enough to read a strike rate?

A single day is too noisy. Look at four weeks of data per person, and look for the trend rather than one result.

How do I compare a hill officer with a valley officer?

Do not compare them directly. Compare each with their own previous months and with similar routes. A walking route with few shops will have fewer visits and often a different strike rate.

What should a salesperson do before walking into a shop?

Check the last order, what was sold, any balance due and any scheme. A suggested order based on history is more likely to turn a visit into an order. See forecasting demand from order history.

A simple monthly strike-rate review

1. Pull each officer's visits, orders and strike rate for the last four weeks.
2. Group the no-order reasons and find the largest.
3. Pick one action per officer: change the cycle, fix timing, review price, clear credit, or coach.
4. Agree the action in the weekly meeting and check it next month.
5. Share the lessons, such as the cycle change above, with the whole team.

How GamiTrack shows it

In GamiTrack, each visit ends with an outcome (Order taken, Payment collected, No order or Shop closed), and a No order outcome needs a reason. The profile of each field person shows their strike rate, defined as how many visits end in an order, along with a breakdown called "Why shops did not order". The Performers page ranks officers for the month with calls and productive calls next to secondary sales and target. Because visits are checked in against the shop's location, the calls behind the number are real visits. See visits, flags and the day view and check in at a shop. You can see this on your own team with a free trial.

Key takeaways

• Strike rate is productive calls divided by visits.
• Read it with visits, order value, coverage and no-order reasons.
• Compare people with their own history and similar routes.
• Use it to coach, not to punish.