Problem
A growing business ran its core operation from shared spreadsheets. Orders, approvals, staff assignments and reporting all lived in one file that everyone had to edit in fear of breaking.
Business Context
The business had outgrown the spreadsheet stage. Multiple people needed to work on the same records at the same time, and management needed to see the state of the operation without asking for a copy of the file.
Constraints
- The workflow itself worked — people understood their process. Only the tool was wrong.
- Users were non-technical and needed a simple, guided interface.
- Approval rules had to be enforced, not just written down.
Analysis
The spreadsheet was a symptom. Underneath it were real business objects — orders, assignments, approvals — that had never been modelled as data. Every column was a field; every color highlight was a status waiting to be a state.
Architecture
The workflow was modelled as Frappe DocTypes with defined states, roles and permissions. The spreadsheet's single file became a set of connected records with one master entry point per workflow step.
Solution
A structured business system replaced the spreadsheet: guided data entry, enforced approval chains, role-based visibility, and dashboards that report from live records.
Technology
- Frappe framework
- Custom DocTypes and workflows
- Role-based permissions
- Approval engine
- Dashboard views
Implementation
We mapped the spreadsheet columns into the data model first, imported the live records, then rolled out one workflow at a time so the team could adapt gradually.
Challenges
The hardest part was unpicking spreadsheet habits — color codes, merged cells and informal notes that had meaning to the team but no structure in the data.
Outcome
The operation now runs on a system where data is entered once, approvals follow the rules, and reporting reflects reality. The spreadsheet no longer sits between the business and its own information.
Lessons
A spreadsheet is a symptom of an unmade model. When the workflow is understood, the data model almost builds itself.
Future Improvements
Automating recurring reporting, adding role-based dashboards per department, and connecting customer communication to order states.