Inventory modernization
A twelve-store retailer ran stock on three disconnected spreadsheets. We built a thin layer on top of their existing system: same backend, much better front. They did not migrate.
- 3 mo
- 12
jadid.work
Index: 04 engagements
A small portfolio because we are a small studio. Every project here was a real engagement, anonymized where the client asked.

A twelve-store retailer ran stock on three disconnected spreadsheets. We built a thin layer on top of their existing system: same backend, much better front. They did not migrate.
An agent that reads their wiki and ticket history and drafts first-response replies for the human support team. Operator-facing, not customer-facing.
A field-ops app for technicians, replacing a chronically broken spreadsheet-over-WhatsApp workflow. Offline-first, syncs when online, signed off with one button.
A six-year-old internal admin tool everyone hated. We kept the backend and replaced the frontend. Same data, same routes, very different mood.
We do not produce 80-page strategic slide packages. We audit the raw schema, clarify the actual bottleneck, and write working prototypes by day four.
Rewriting operational software from scratch is usually hubris. Where legacy APIs function reliably, we reinforce the edges and wrap cleanly.
We deploy, document and train. When the build is done, your people operate the system day to day, and your data stays exportable at any time.
Bring your problem, we’ll tell you honestly whether we’re the right studio to build it.
Start a conversationAll systems normal