Track record
UnikFeet went from four tools to one system.
UnikFeet makes custom-made insoles, with a head office and partner clinics in Ho Chi Minh City. I delivered a complete system in 12 weeks, from June to September 2026. The staff use it every day.
Before and after
Before
- Client files and measurements lived in spreadsheets.
- 3D scan files stayed on the scanner’s computer, then got copied by hand to a shared drive.
- Insole production was tracked from memory and over messages.
- Appointments and invoicing were split between spreadsheets and WhatsApp groups.
After
- Each client has a file with contact details, measurements and history.
- Scan files land in the right client file on their own.
- The production board shows the step, the person responsible and the date for every pair.
- Appointments are booked by clinic and by employee.
- Invoicing and payment tracking are in the same place.
- Management has a dashboard.
Before, nobody could say how many pairs were in production or at which step. Files got lost between the computer and the drive, and each clinic had its own version of events. Today everyone looks at the same screen.
What the team says
“Before, we tracked our clients with Excel files, paper sheets and WhatsApp messages. Now everything is in one place and we save a lot of time. The system was easy to use from day one.”
“We wanted a system we own, one that follows exactly how we work, down to the dashboard and the manufacturing pages. We have big growth plans, and the cost stays the same no matter how many users we add. Our partners often compliment us on the platform.”
“Before, we built the production calendar by hand, in Excel or on paper, with a separate calendar app and messages on WhatsApp and Zalo. Every small change meant redoing everything. Now it’s all connected: if someone moves an appointment, the calendar updates on its own. We do everything in the platform, every day.”
What we keep improving
The staff have asked for changes every week since go-live. I take that as a good sign, because nobody asks for changes to a system they work around. A small change ships in a few hours, a big one in two or three days. It’s also why the Evolution plans include points for changes.
What I would do differently
I built several modules before the people who would use them had approved the screens. A good share of the requests after go-live were screen choices that a two-hour workshop would have settled beforehand. That’s why the Blueprint now exists as a separate step. We draw every screen with you before any code is written.
For the curious
- 35 pages in the portal, 71 tables in the database, 252 API routes.
- About 134,000 lines of code and 78,000 lines of tests.
- Access by role, nightly backups, updates tested before every delivery.
UnikFeet owns its system. That’s exactly the model I’m offering you.
Reference available on request: someone on the UnikFeet team you can call.
Your business doesn’t look like UnikFeet, but the starting point is often the same.
Book a meeting