Custom Software Development
An internal tool that replaced a spreadsheet chain
An illustrative engagement, written from how we work. Client details are withheld and no outcome figures are claimed.
Context and constraints
The situation this example is drawn from: an order-tracking process that had outgrown a chain of shared spreadsheets and an email inbox used as a makeshift approval queue. Nothing was technically broken — orders still got fulfilled — but every handoff between departments required someone to manually copy data between files, and the one person who understood every exception case was also the one person the process couldn't run without.
Approach
Survey work focused on shadowing the actual process, not the documented one — the two didn't match. Key decisions:
- Model the workflow's real exceptions as first-class states in the system, not edge cases handled by a person remembering them.
- Build role-based views so each department saw only what it needed to act on, instead of one shared spreadsheet everyone scrolled through.
- Keep the specification tight enough to ship in one build phase rather than splitting into multiple systems that would need to stay in sync.
Architecture Decisions
Single system of record
one database replacing three spreadsheets and an inbox, removing the manual copy step entirely.
Role-based access, not a shared view
each department's screen matched what they were actually responsible for.
Exception states modelled explicitly
the workflow's real edge cases became system states, not tribal knowledge.
Deployed to the client's own infrastructure
per their IT policy, documented for their team to maintain.
What Shipped
ENTRY — RESULT
A single internal system replacing the spreadsheet-and-email process, with weekly demos throughout the build so the operations team could flag process gaps before launch, not after. The manual cross-checking step that previously took the team the better part of a day each week was replaced by the system's own reporting view.