8 August 2026 · 6 min read
By Gokul Kumar
Pay them when the money arrives, not when the order is booked
A delivery rider finishes a drop and the money appears. Not at month end, not on a statement he cannot reconcile — now. Then a bar tells him three more unlocks a bonus. Everything is visible, immediate, and his.
A distribution salesman has the exact opposite. He works a beat all month, has no idea what he has earned, and finds out in a payslip with a single line on it. Same effort, none of the feedback.
The gap between doing the work and seeing the reward is the whole product. Everything else is decoration.
The alternative, and why it fails: pay at “order booked” and the incentive is earned before the money exists. The month looks like a record while receivables quietly grow, and nobody notices for a quarter.
What it looks like on a beat
He closes a shop. The app shows what that order earned him and how far he is from the day's target. He collects an overdue payment and that credits too. At four in the afternoon he can see that two more calls gets him over the line — which is exactly the decision you want him making, and exactly the one he cannot make today.
The mistake almost everybody makes
Pay for orders and you will get orders. You will also get orders that were never wanted, high-incentive products pushed onto shopkeepers who did not ask for them, easy shops visited three times while the difficult ones go untouched, and — eventually — orders that were never real.
In Indian distribution the specific version of this is brutal. An order is not money until it is collected. Incentivise the booking and you will grow your receivables while celebrating a record month, and nobody will notice for a quarter.
The thing that will kill it
Not the design. The arithmetic.
If the app says he has earned four thousand two hundred and payroll pays three thousand eight hundred, you have not built a motivation tool. You have built a grievance, and it is worse than never having built anything, because now he actively distrusts every number you show him.
So the wallet has to be computed from the same records payroll pays from — not a parallel calculation that drifts. Every deduction has to appear as a line he can read, not a silent adjustment. And when a number changes, it changes in front of him with a reason attached.
That is unglamorous work and it is the whole build. The screen is a week. Making the screen true for two years is the project.
Keep it a display, not a bank
There is a strong pull toward letting people withdraw. Resist it, at least at first.
A wallet that shows accrued earnings against existing payroll is a reporting feature. A wallet that moves money is a regulated product, with the compliance surface that implies. The motivation comes almost entirely from seeing the number — the withdrawal button adds a great deal of risk for a small amount of additional effect.
Why this matters beyond field sales
Most businesses have someone whose effort is invisible to them until payday. Service engineers, collection staff, delivery teams, installers. They are told they are valued and shown nothing, and then everyone is puzzled that they behave like people paid to be present rather than people paid to perform.
The technology here is not difficult. What is difficult is deciding what genuinely deserves reward, and then being honest enough to compute it in front of the person earning it.
Get that wrong and you have built a scoreboard nobody trusts. Get it right and you have built the only management tool that works when you are not in the room.