New Product Launch Management When Your Sales Team Is Spread Across 8 Cities
Last March, a beverage client of ours rolled out a new energy drink across 11 cities in Saudi Arabia. Their plan was solid on paper. Their execution? A mess for the first 18 days.
Not because the product was bad. Or the pricing was off. The issue was simpler — and a lot more common than founders like to admit. Information didn't move fast enough between head office, distributors, and the 240-odd reps who were supposed to push the SKU into 9,400 outlets.
By day 19, they'd fixed it. But they'd burned through roughly $84,000 in launch budget on territories that hadn't even received POSM yet. Honestly, this is the part of FMCG nobody writes case studies about.
So let me share what I've learned watching dozens of these launches go right and wrong.
The launch problem nobody talks about
When brands talk about new product launch SFA, they usually mean dashboards. Coverage maps. A nice rollup of how many outlets stocked the new SKU in week one.
That's the output. Not the work.
The actual work is messy. A brand manager in Dubai approves artwork. A distributor in Sharjah gets sample stock 4 days later. A super in Ajman briefs his team on a WhatsApp group at 9pm. Two reps miss the message. One rep briefs the outlet owner wrong. The outlet owner places an order for the wrong pack size. And somewhere in head office, a dashboard says "launch on track."
This is how distributed sales networks actually behave. Not like a synchronized swimming team. More like 14 cousins trying to plan a wedding over voice notes.
Good product launch management isn't about pretty dashboards. It's about closing the gap between what HQ decided and what the rep standing inside a kiryana store in Lahore actually says and does.
What we built after watching too many launches fail
I got this wrong at first. Early versions of Zivni had a "launch module" that was basically a fancy task list. Reps would get a notification: "Push new SKU X to all A-class outlets." Done.
It didn't work. Reps ignored it. Or they marked it done without actually doing it. Or they did it, but the order didn't reach the distributor because the SKU code wasn't synced yet.
Here's the thing — launch management isn't a task. It's a coordinated sequence across at least five roles: brand manager, sales ops, distributor, supervisor, rep. If any one of them is out of sync, the whole launch wobbles.
So we rebuilt it. Now product launch tracking inside Zivni works backwards from the outlet. You define which outlet clusters get the launch (by class, by geography, by channel), and the system pushes target SKUs, target volumes, target merchandising standards, and target call frequency down to the rep's daily beat plan automatically.
The rep opens the app in the morning. The launch SKU shows up as a priority. Voice order entry already recognizes the new product. The shelf photo AI is already trained to detect it. POSM checklists include it. Distributor stock visibility flags whether the SKU is even available in that warehouse before the rep walks into the store.
That last bit matters more than people think. Roughly 31% of failed launch calls in our data come from reps trying to sell something the distributor can't deliver for 4 more days. Embarrassing for the rep. Worse for the brand.
Five things that actually move the needle
I'll keep this practical. If you're planning a launch across a distributed network, here's what I'd focus on:
1. Pre-launch readiness scoring per distributor. Before launch day, every distributor should be scored on stock received, rep training completed, POSM delivered, and route plans updated. Don't launch in a market scoring below 80%. We've seen brands launch anyway and regret it for a quarter.
2. Beat-level launch targets, not regional ones. Telling a regional manager in Karachi to hit 4,000 outlets in week one means nothing. Telling rep #47 he needs to push the SKU into 22 specific outlets on his Tuesday beat — that's measurable.
3. Real-time photo audits in the first 14 days. Shelf placement decides whether a launch survives month two. AI shelf analysis catches whether the SKU is at eye level, in the right planogram block, or hidden behind a competitor. Don't wait for a retail audit company to send a PDF three weeks later.
4. Gamify the first 30 days, not the whole quarter. Launch energy fades fast. Reps respond to short bursts. A 30-day leaderboard with a tangible reward (we've seen brands give iPhones, Umrah tickets, and once a motorbike) outperforms quarterly bonuses by a wide margin.
5. Daily voice debriefs from supervisors. Not reports. Voice. A 90-second voice note from each supervisor at end of day, captured in the app, tagged to the launch. You'll spot patterns in 48 hours that a written report would hide for two weeks.
What still goes wrong
Look, even with all of this, launches still hit problems. A distributor in Muscat goes on holiday. A rep in Birmingham quits week two. A competitor in Riyadh drops their price by 15% the day after you launch.
No software fixes that. But what good product launch management does is give you the visibility to react in hours instead of weeks. That's the whole game.
The brands that win launches in 2025 aren't the ones with the biggest TV budgets. They're the ones whose rep in a small outlet in Sialkot knew exactly which two SKUs to push this morning, had the stock to back it up, and got credited the moment the order was placed.
Is your next launch ready for that? Or is it still living inside a PowerPoint and a WhatsApp group?