Scaling Logistics-as-a-Service from MVP to 30K Monthly Orders
How I took an engineer-built MVP, rebuilt it around real user feedback, and scaled it to full national coverage in seven months.
Inheriting an MVP in Motion
Joining Tazz at a pivotal moment, I inherited a Logistics-as-a-Service (LaaS) product that had been built purely from an engineering perspective. While technically functional, the MVP lacked the user-centric polish and operational scalability required for a commercial rollout.
The initial build focused on the "how" of delivery without fully solving for the "who," the restaurant managers and dispatchers who needed a frictionless interface to manage growing delivery demands without technical overhead.
Laying the Groundwork Before Launch
Before hitting the "scale" button, we needed a roadmap that accounted for geographic diversity. My first priority was mapping potential cities across the country, evaluating market density, and existing logistics infrastructure.
I spearheaded the creation of a comprehensive guidelines document, a "Standard Operating Procedure," that defined everything from partner onboarding to technical integration. This wasn't just documentation; it was the blueprint for national expansion, ensuring that the experience in a secondary city was as robust as in the capital.
The Iteration Loop
First Launch
Early feedback highlighted a complex UI. Partners felt the dashboard was overwhelmed with data points they didn't need for daily operations.
Rebuild
We stripped the interface back and redesigned it around the actual restaurant workflow. Speed of order entry became our North Star metric.
Scale Unlocked
The breakthrough: Order batching for a major partner. This allowed us to handle high-volume spikes without linear increases in courier costs.
Retention Through the Right Features
SMS Order Tracking
Real-time transparency for the end customer, significantly reducing inbound support calls from restaurant partners.
Invoice Management
Automated financial reconciliation that turned a multi-day manual process into a single-click export.
Automated Payment Controls
Granular control over payment flows, ensuring partner payouts were fast, accurate, and predictable.
The Result
By the end of month seven, the transformation was absolute. What began as a localized experiment had scaled to full national coverage across Romania.
We successfully onboarded over 2,500 restaurant partners, ranging from local independent kitchens to massive international chains, all running on the same optimized infrastructure.
Monthly Orders
in 7 Months
What I Learned
Rebuild with reason, not ego
It's tempting to scrap everything immediately, but the MVP had valuable technical lessons. The rebuild was surgical, keeping the robust core while completely replacing the user-facing experience based on behavioral data.
The best features come from partners
Our most successful features, like order batching, weren't dreamed up in a boardroom. They were solutions to specific pain points expressed by the partners who were actually using the tool in high-stress environments.
"The fastest way to know what to build next is to launch what you have and actually listen to what comes back."