Case Study
From Idea to MVP in 3 Weeks --
Norwegian Logistics Startup
A Norwegian founder needed a working logistics coordination tool before a key investor meeting. His previous agency quoted six months. We shipped in three weeks.
3
weeks to delivery
6
months quoted elsewhere
0
scope creep incidents
The Problem
Small logistics operators were coordinating vehicle assignments, route tracking, and driver communication across WhatsApp, phone calls, and spreadsheets -- with no single source of truth. Operations managers were spending 2-3 hours daily just chasing information. The founder needed a working demo before a seed funding meeting, with no time or budget for a six-month agency engagement.
The Solution
A focused two-day spec process locked scope before any code was written. We built a web dashboard for operations managers -- real-time map view, route assignment, driver mobile web app, and status updates -- using React, Node.js, PostgreSQL, and Google Maps API. AI-assisted development at every layer compressed what would normally be a 12-week project into three weeks. Explicit out-of-scope decisions (no native apps, no route optimisation in v1) protected the timeline.
The Outcome
The founder had a live, working product to demo at his investor meeting. He raised his seed round in April 2026. The MVP was piloted with three logistics operators in Norway during March and April -- the core coordination workflow performed as designed. Feedback from pilots fed directly into a prioritised v2 roadmap.
The Brief
A lightweight operations hub -- not a full TMS
The target user: operations managers at small logistics companies (5-30 vehicles). The workflow problem was real -- real-time coordination was happening across three different communication channels with no central source of truth. Assignments got lost. Status updates were missed.
The MVP needed a web dashboard showing vehicle locations on a map, route assignment to drivers, and a mobile-friendly interface for drivers to see their current assignment and update status.
In scope for v1
- Web dashboard for operations managers
- Real-time map view with vehicle locations (GPS from driver mobile)
- Route assignment interface
- Driver mobile web app (browser-based, no installation)
- Driver status updates (available, en route, delivered)
- Basic authentication (manager accounts, driver accounts)
Explicitly deferred to v2
- Native mobile apps
- Automated route optimisation
- Invoice generation
- Customer tracking portal
- Historical reporting
The Timeline
21 days, step by step
Week 1 -- Specification and Architecture
Days 1-2
Discovery
Three-hour call mapping user journeys in detail, followed by a written spec document shared by end of day two. User journey maps, data model, integration requirements, auth approach, infrastructure decisions.
Day 3
Architecture Review and Sign-off
Founder reviewed the spec. One revision: add free-text note to drivers alongside an assignment. Twenty minutes to update the spec, then sign-off. No delays.
Days 4-5
Project Scaffolding
Authentication system, database schema and migrations, project structure, core API endpoints stubbed, React app initialised with routing -- all done with AI-assisted tooling.
Week 2 -- Core Feature Development
Days 6-8
Backend API Development
Vehicle management, route management, assignment API, status update endpoints, driver location reporting. Each endpoint: generate from spec, review for correctness, test against database.
Days 9-11
Frontend Dashboard
React components: map view (Leaflet.js), vehicle list, route management UI, assignment workflow. AI generated substantial portions of the component code; the engineer reviewed for correctness and UI quality.
Days 11-12
Driver Mobile Interface
Mobile-optimised web app: current assignment display, status update buttons, location permission request. Designed to work on any modern smartphone browser without installation.
Week 3 -- Integration, Testing, and Deployment
Days 13-15
Integration Testing
End-to-end test scenarios covering all user journeys. AI-generated test cases covered the happy paths; engineers wrote edge case tests for the status logic and offline scenarios.
Days 16-19
Staging Review + Production Setup
Deployed to staging, shared with founder for review. Two rounds of feedback: minor UI adjustments and one logic change. Then Railway production environment, domain setup, database backups configured.
Days 20-21
Handoff and Go-Live
Code repository transferred to client. Deployment documentation provided. One-hour walkthrough call. Day 21: production deployment. The founder had a working product to demo at his investor meeting.
Tech Stack
Built to be production-ready from day one
Every technology choice was made to serve a three-week timeline without creating technical debt. The stack is straightforward, well-documented, and easy for any future developer to pick up.
React
Manager dashboard + driver web app
Node.js
REST API and real-time location backend
PostgreSQL
Vehicles, routes, assignments, events
Railway
Hosting, database, environment management
Maps API
Google Maps API + Leaflet.js for live tracking
"I had a previous agency tell me this product would take six months. Kodework shipped in three weeks and I had something I could put in front of real users. The spec process they run at the beginning made the speed possible -- because we knew exactly what we were building before any code was written."
Norwegian logistics startup founder -- February 2026
Client details generalised at client's request
Key Lessons
What made three-week delivery possible
None of these individually were transformative. Together they compressed a 12-week project into three.
Clear requirements before development started
The two-day spec process was not overhead -- it was what made three-week delivery possible. Every hour spent in spec saves three hours in rework. The written spec document was the foundation everything else was built on.
Explicit out-of-scope decisions
The founder's first instinct was to include native mobile apps in v1. He had good reasons. We pushed back because native mobile development would have doubled the timeline. Deferring it saved the whole project. The out-of-scope list was as important as the scope list.
Fast feedback loops
The founder was available to give feedback quickly. We ran staging demos at end-of-week, not end-of-project. Issues got caught early, before they cost rework time. Two rounds of UI feedback in staging -- not in production.
AI-assisted development at every layer
Scaffolding took days not weeks. Standard CRUD endpoints took hours not days. Test generation was automated. Documentation was produced alongside code. Each of these compounded: the project moved at a pace that is simply not possible with purely manual development.
Work With Us
Starting something similar?
If you're a founder with a clear problem and a tight deadline, tell us what you're building. We'll tell you honestly whether the timeline is achievable and what the project would involve.
We respond within one business day with a clear scope and fixed-price estimate.