To track client meals, set a monthly cap, log every meal with the headcount and the client's name, and at month end divide the total by the number of people fed. Cost per head and a simple note on what each meal led to turn a vague hospitality figure into something you can judge.
What goes into each entry?
- Date, restaurant and total amount including any cash tip.
- Number of people, counting yourself.
- The client or prospect and the purpose, in a few words.
- The outcome if you know it: order confirmed, follow-up needed, nothing yet.
Entering the headcount at the time costs five seconds. Reconstructing it a month later is guesswork.
How often do client meals happen?
Irregularly, and in clusters. A product launch, a quarter-end push or the weeks before Diwali can bring five meals in ten days, followed by a quiet fortnight. Because of that, set the cap for the month and keep an eye on the running total each week, rather than expecting an even spread.
A sample month
Say you set a cap of ₹7,000 and these five meals happened. The numbers are invented.
| Meal | People | Bill | Per head |
|---|---|---|---|
| Coffee with a prospect | 2 | ₹850 | ₹425 |
| Lunch, two buyers | 3 | ₹2,100 | ₹700 |
| Dinner to close an order | 3 | ₹3,100 | about ₹1,033 |
| Lunch with a regular client | 2 | ₹1,500 | ₹750 |
| Quick tea after a site visit | 2 | ₹600 | ₹300 |
The bills add up to ₹8,150, which is ₹1,150 over the ₹7,000 cap. Headcount is 12 people across the five meals, so the average is about ₹679 a head. The dinner was the largest single item, so ask whether it was worth it: did the order close? If yes, you may simply raise next month's cap for similar occasions.
A cap is a guide, not a wall. If a meal pushes you over, the point is to notice and decide, not to feel guilty. Some months a single dinner is the reason a large order came through. What you want to avoid is drifting over the cap month after month without ever choosing to.
How do you spot a change?
Compare three numbers with the previous month: the total, the number of meals and the cost per head. A higher total with the same number of meals means each meal got more expensive. A higher total with more meals means you are simply meeting more people, which may be good news. Both can look the same in a single total.
What should the review decide?
- Was the cap realistic, or did you set it without checking last month?
- Which meals produced a result, and which were purely social?
- Is there a cheaper venue that would suit regular meetings?
- Should a call or a short office visit replace some lunches?
In SpendixAI you can enter the headcount in the note, keep the bill photo against the transaction and see the month's Client meals total in the reports, which makes the cap check a matter of seconds.
What about gifts and festival hampers?
Sweets and hampers sent to clients around Diwali or the new year are not meals, and putting them in the same group distorts your per-head figure. Keep a separate Client gifts line and track it yearly, since it clusters in one or two months. If a client sends you something, you do not record that as an expense, though a note can help if you want to return the gesture later.
Weekly and monthly routine
- After each meal, log amount, headcount and purpose that day.
- Every Sunday, compare the running total with the cap.
- At month end, work out cost per head and note the outcomes.
- Adjust next month's cap, and write the reason beside it.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


