The problem
A clothing brand ran its whole production flow from spreadsheets: fabric stock, cutting, sewing by internal and outside tailors, and quality checks. The spreadsheets could not show cost of goods reliably. Warehouse and production staff also needed something they could use from a phone.
My role
Freelance project, August 2026 to present. I own the architecture, data model, scope decisions and review. Implementation is done by an AI executor working from my plans. I review every change before it ships.
What it does
- Fabric inventory on an append-only stock ledger, with soft delete and approval flows
- Cutting and bundling, then sewing orders for internal staff and outside vendors
- QC, finishing and packing
- Cost of goods and production reports
- Mobile-first screens and an installable PWA
Proof of use
- Four of five planned stages have been handed over, with training.
- The client runs production on it daily, on a separate production database since September 2026.
Technical highlights
- Caught a data bug that passed every check. An audit found fabric widths of 24, 30 and 32 inches all stored as the same value. It compiled and tested clean, and only showed up against real data.
- Replaced free-text fields with master data. 14 free-text columns that should have been foreign keys were identified and fixed.
- Matched the software to the floor's language. Menu names and terms follow what the production staff actually say, which removed a class of "wrong menu" bug reports.