Snabbit Network Design: From Remote Plan to Ground-Level Execution
Rebuilt supply network design by creating accountability structures and feedback loops that made a remote plan actually land on the ground.
Abhiram Nair
Senior Product Analyst at Snabbit
From their time as
Program Manager
Snabbit • 2025 - 2026
Overview
Three weeks into his role at Snabbit, Abhiram was handed a vague brief: fix the supply network. He approached it the way he approaches most problems, analytically. He spent several days mapping demand grain by grain, redesigning hotspot locations, sizing supply at each zone and hour, and building a detailed plan of roughly 20 daily actions for the ground teams to execute.
The Story
Three weeks into his role at Snabbit, Abhiram was handed a vague brief: fix the supply network. He approached it the way he approaches most problems, analytically. He spent several days mapping demand grain by grain, redesigning hotspot locations, sizing supply at each zone and hour, and building a detailed plan of roughly 20 daily actions for the ground teams to execute.
The plan was solid. The execution was not happening. The ground teams were in Gurugram; Abhiram was in Bangalore. He had no visibility into what was actually being implemented, and after the first week of monitoring metrics, he got nothing back. The analytical work had produced a good design that was not landing.
He recognized that the challenge was never the analytical bit. It was execution, and execution required accountability and visibility that did not yet exist. He started by working with the GM in Gurugram to designate one person whose sole responsibility was network design implementation. That person's performance was directly linked to the outcome, giving the work a clear owner on the ground.
He then built manual feedback loops. Ground teams were asked to send photographs of hotspot locations at different times of day, confirming that experts were actually sitting where the design required. Updates came through WhatsApp groups. It was a manual process, but at that stage of the company, it was the right one. A product solution replaced the WhatsApp process roughly six months later, once the team had the bandwidth to build it.
The combination of local accountability and real-time feedback loops turned the design into something that actually ran.