What a Plow Horse is — and why repricing is different
Plot every dish on popularity × contribution margin. Plow Horses sit in the top-left quadrant: ordered constantly, profitable only on paper. Common Indian-restaurant culprits: dal makhani, butter chicken (when paneer/butter spike), veg thali, chicken biryani at aggressive aggregator prices. The full menu engineering matrix guide covers classification; this post covers what to do once you've identified them.
When to raise — and when to wait
| Signal | Action |
|---|---|
| Food cost on the dish rose >8% in 30 days (commodity spike) | Raise within 2 weeks — customers expect it |
| Dish is a Plow Horse for 2+ consecutive monthly audits | Raise or re-engineer — margin won't fix itself |
| You're in a launch ramp (weeks 1-8) | Wait — build rating and repeat first |
| Aggregator rating dropped below 4.2 in last 30 days | Fix ops before repricing — price won't save a bad kitchen |
| Competitor within 500m dropped price on same dish | Bundle or re-engineer recipe — don't match on price alone |
| Month-over-month covers on the dish are flat or growing | Green light for a ₹15-25 increment |
How much to raise
Indian restaurant data across 40+ outlets: ₹15-25 per dish is the safe band for dine-in Plow Horses. Above ₹30, order volume drops 8-15% on items under ₹350 list price. Below ₹15, the margin lift doesn't justify the customer communication effort.
On aggregator listings, round to ₹10 increments (₹285 → ₹295, not ₹292). Aggregator grids make odd endings invisible; ₹10 steps feel intentional, not arbitrary.
Play 1: Price raise with a quality signal
The raise sticks better when paired with a visible upgrade — even a small one. Examples that worked in pilot outlets: 'hand-churned butter' callout on dal makhani (+₹20, no recipe change), extra 30g chicken on butter chicken (+₹25), switch from pouch paneer to block paneer (+₹15, actual cost +₹6). The quality narrative gives customers a reason; the margin lift is real either way.
Play 2: Bundle instead of bare repricing
If volume sensitivity is high, don't raise the standalone price — raise the bundle anchor. Butter chicken at ₹385 holds; 'Butter chicken + garlic naan + raita' moves from ₹520 to ₹545. Bundle attach rate on Plow Horses runs 28-40% in casual dining; you're repricing the majority of orders without touching the headline SKU price.
| Bundle | Before | After | Attach rate |
|---|---|---|---|
| Dal makhani + jeera rice | ₹340 | ₹360 | 34% |
| Butter chicken + naan + raita | ₹520 | ₹545 | 38% |
| Veg thali (full) | ₹280 | ₹295 | 41% |
Play 3: Recipe re-engineering before price
Sometimes the Plow Horse doesn't need a price raise — it needs a cost cut that doesn't show. Three high-ROI moves: reduce butter portion by 15g (saves ₹8-12/plate on dal makhani), switch cream grade (saves ₹6-10 without taste shift), tighten protein portion with a scale at the pass (saves ₹14-22 on butter chicken). Run recipe costing before any price change; a 12% food-cost reduction on a Plow Horse often beats a ₹20 price raise for margin and keeps volume intact.
Aggregator-specific rules
- Separate aggregator menu — 8-12% markup vs dine-in is standard; customers don't cross-check.
- Raise during low-visibility windows — Tuesday-Wednesday price changes sync faster and attract less review backlash.
- Watch refund rate for 7 days post-raise — a spike above 2.5% means the portion or quality signal wasn't credible.
- Don't raise and run a discount in the same week — effective price stays flat but rating drops because customers feel manipulated.
What to measure after a repricing move
| Metric | Target (14 days post-raise) |
|---|---|
| Unit volume change | < −5% |
| Contribution margin per dish | +₹12 minimum |
| Aggregator rating | Hold ≥ 4.2 |
| Refund rate on the SKU | < 2.5% |
| Bundle attach rate (if bundled) | Hold or grow |
If volume drops more than 8% in 14 days, revert the standalone price and try Play 2 (bundle) or Play 3 (recipe) instead. Plow Horses exist because customers love them — the goal is margin, not martyrdom.