Sales force automation explained

The day without SFA

A salesperson for an FMCG stockist leaves home at 9:30 with a diary. Visits 18 shops. Writes orders on paper, phones the big ones to the office, collects ₹38,000 in cash and cheques. In the evening, the office types the orders, sometimes the next morning. The owner asks how many shops were covered and gets a number from memory. Two orders are entered wrong because the handwriting was unclear.

Nothing here is unusual. The cost shows up as late deliveries, wrong items, missing collections and no way to judge which salesperson is actually productive.

What SFA puts on the phone

• Today's plan: the beat or route for the day, with shops in a sensible order.
• Check-in with location: proof that the visit happened at the shop.
• Customer context: what the shop bought last time, what it owes, any pending order.
• Order booking: items with the right price for that shop, quantities, scheme or discount.
• Collections: cash, cheque or UPI collected, recorded against the customer.
• Notes and photos: display, competitor activity, complaints.
• Leave and attendance for the field team.

What the manager or owner gets

The guide on measuring salesperson performance explains which of these to use for incentives.

Making it work with your team

Field teams often resist tracking. A rollout that works:

1. Start with what helps them. Show the salesperson they can see a shop's outstanding and last order before walking in. That saves them embarrassment.
2. Keep the app simple. If booking an order takes longer than writing it, they will go back to paper.
3. Be clear about location. Tell the team location is captured at check-in for visit proof. Being open about it avoids distrust.
4. Pilot with two willing salespeople for a month, fix the problems they find, then roll out.
5. Stop accepting paper orders after a fixed date.

Choosing the right measures

SFA produces a lot of numbers, and the wrong ones drive the wrong behaviour. If you pay incentives on visits alone, salespeople make quick, useless visits. If you pay only on order value, they push stock that dealers cannot sell and collections suffer. A balanced weekly view uses four measures together: planned visits completed, productive calls (visits that led to an order), order value, and collections against that salesperson's dealers' overdue bills.

Compare each salesperson with their own last month first, and with each other second. Territories differ; a salesperson covering a rural area with long distances will always make fewer visits than one in a dense market.

Collections in the field

Collections are where SFA often pays for itself. When a salesperson records ₹12,000 collected in cash at a shop, the office knows to expect it the same evening, and the dealer gets confidence that the payment is acknowledged. Make it a rule that cash handed to the office is matched daily against collections recorded in the app; differences are followed up the next morning, not at month end.

Common pitfalls

• Orders that do not reach the books. If an SFA order must be retyped into accounts, you have only moved the typing.
• Wrong prices. If the app shows a single price list, salespeople override it and margins leak.
• Too many mandatory fields. Every extra field at check-in is a reason to skip the check-in.
• Using it only to police. If the app is seen only as surveillance, data quality drops.

SFA connected to Tally

Cashflow OS includes a staff app with a "Today" screen for salespeople: customers to attend, visits, orders and collections. Field force tools add dealer locations, areas and route plans, recommended visits, check-in with location, visit notes and photos, leave and a performance view for the owner. A salesperson sees items and their own customers, not the company's accounts. Orders can require approval and are then posted as sales orders into Tally. See field force tracking and the staff app.