From Pitch Deck to Paying Customers in 11 Weeks: A Logistics SaaS MVP
A $48K, 11-week logistics SaaS MVP that reached 14 paying customers and unlocked a $2.1M Series A.
The founder — a 15-year freight logistics veteran — had spotted a gap. Mid-size freight brokers handling 50–500 shipments a month were running operations on 2000s-era TMS software, Excel, email chains, and phone calls. The alternatives were enterprise platforms with 6-figure annual contracts and 6-month implementations, or basic tools that couldn't handle multi-modal freight coordination.
He had $180K in pre-seed funding, LOIs from three pilot customers, and a Series A investor whose commitment was contingent on a working product with live traction within 4 months. The constraints were hard: $50K maximum for MVP development, 12 weeks to a deployable product, and pilot customers committed to a 60-day evaluation starting no later than week 14.
The feature wishlist was 47 items long. It had to be cut to the 12 features that would make a broker switch off their spreadsheet. Three US development shops had quoted $120K–$220K with 16–24 week timelines — numbers that would have consumed the entire raise.
Sprint Zero locked scope and architecture in one week for $4,500. The build ran as four 2-week sprints: foundation (auth, tenant management, roles, CI/CD), core workflow (shipment creation, multi-stop routing with Mapbox, carrier assignment, document upload), intelligence (real-time tracking on a map, automated notifications, KPI dashboard), then monetization and polish (Stripe per-shipment billing, customer portal, reporting, CSV import).
The cadence was strict: Monday sprint planning with the founder on video, daily async standups across the Dhaka–US time gap, and a Friday demo on staging where the founder and a pilot customer tested live. Feedback fed directly into the next sprint.
Weeks 10–11 were testing and launch. A QA engineer ran 180 test cases covering multi-tenant isolation, payment failure handling, and concurrent editing with optimistic locking. Load testing validated 50 concurrent users with 500 active shipments at under 200ms response times, with headroom for 200+ concurrent users. Production deployment used a zero-downtime ECS rolling update — the founder onboarded his first pilot customer the same afternoon.
The platform shipped in 11 weeks — one week ahead of the 12-week target — for $48,000, under the $50K budget. All 12 committed MVP features delivered, zero critical bugs at launch, 78% automated test coverage, and $180/month infrastructure costs at launch.
Traction compounded: 3 pilot customers in month 1 grew to 7 by month 3 and 14 by month 6. MRR went from $1,700 to $19,000 over the same period, with NPS holding between +58 and +64 and uptime at 99.97%+.
Four months after launch the founder closed a $2.1M Series A at a $6.2M pre-money valuation. The lead investor cited product quality, development speed, and capital efficiency — and audited the codebase. After the raise, the founder retained 3 Gigabit engineers as his dedicated development team at $14,500/month.
I talked to three US dev shops and the cheapest quote was $120K for 16 weeks. Gigabit delivered a better product for $48K in 11 weeks. And they didn't just write code — they challenged my assumptions, cut the scope to what actually mattered, and built an architecture I could grow into. My Series A investors audited the codebase. They said it was cleaner than most Series B companies they'd seen.
