Replacing spreadsheets across four distribution centers
Product Manager (contract, part-time) · Freelance, for a distribution company in Ecuador · Nov 2025 – Present
A freelance engagement where I analysed the operation, designed the product, owned the roadmap and wrote the first layer of the code. The platform now runs four distribution centers with about 200 users.
- ~200
- users across 4 distribution centers
- ~14 h
- of manual work removed per week
- ~3 months
- from kickoff to first module live
1The problem
Crew performance, attendance and incentives were tracked in a set of disconnected Excel files. Reconciling the attendance data took about an hour every day, seven days a week. Calculating crew indicators took another hour. Crew members had no way to see their own standing at all.
2What I did
I started with the process, before any code. I mapped how trips were planned, how attendance was recorded and how incentives were calculated, and defined the problem set with the client. Then I designed the solution and owned the roadmap: 52 tasks across 7 sprints, tracked in Notion. I ran every client meeting, from requirements to sign-off.
It was a two-person team: one developer and me, both part-time. I wrote the first layer of the codebase myself with Claude Code, covering the database schema and the core functions, and the developer built on top of it.
3What shipped
- Trip planning with drag-and-drop crew assignment and a trip state machine
- An attendance engine with late-to-absence logic, a penalty calculator and scheduled auto-approval
- Fleet records with mileage tracking and an audit trail
- A weekly warehouse planning grid
- An API integration with the client's existing attendance system, and a payroll integration through Supabase Edge Functions
4The way we built it
The developer and I set up a multi-agent development workflow, with separate agent roles for brainstorming, development, evaluation and QA. Each change passed through an evaluator and a QA agent before either of us reviewed it. It let two part-time people keep a steady release rhythm.
5Result
The attendance integration removed the daily reconciliation step completely, and the KPI calculation is now automatic. Together that is about two hours a day, or roughly 14 hours a week. Every crew member can now see their own daily indicators, which was not possible before. The first production module went live about three months after kickoff.
Stack: React · TypeScript · Tailwind · Supabase · PostgreSQL · Prisma · Vercel