From spreadsheets to software: a migration story
Meridian was running their entire business on a 47-tab Excel file. We spent six months turning that into actual software. Here's the playbook we used.
Meridian had grown from a small regional distributor to a national player. But their operational core hadn't changed. Everything—from inventory tracking to billing to customer relations—ran on a single, massive 47-tab Excel spreadsheet shared across a local network.
As you can imagine, this didn't scale. Version control was a daily nightmare, formulas got corrupted, and loading the file took five minutes. Here's how we helped them transition to a robust SaaS application.
The audit phase: mapping the chaos
Our first step wasn't to write code. It was to understand the spreadsheet. We realized that the file wasn't just data; it was a physical representation of their business processes. The complex color-coding, cell references, and macros represented the actual rules of their operations.
If you build software that ignores how your clients already do their job, they won't use it. You have to map their existing workflow first.
The solution: database normalization
We mapped the spreadsheet's tabs into a normalized PostgreSQL schema, ensuring that data redundancy was eliminated and real-time updates were guaranteed. We built a beautiful React dashboard that retained the speedy keyboard shortcuts they loved, but with strict validation and access control.