The business runs on a file called final_v3
Stock, approvals, pricing and the month end all live in workbooks that one or two people understand.
What it looks like from the inside
Spreadsheets get a business a long way, which is why they are still there. The trouble starts when the company outgrows them: two people edit the same file, an approval is an email nobody can find, and there is no record of who changed a number or why.
The fix is rarely a large platform. It is the boring internal tool nobody demos: the approval screen, the review queue, the admin panel that everybody actually uses.
- Approvals happen over email and chat, with no record afterwards
- Two people edit the same file and one version quietly wins
- Month end takes a week, and most of it is reconciliation
- Only one person can produce the report, and they know it
What we do about it
Follow the process as it is really run
We map what people do, which is rarely what the org chart or the documentation says, and that map becomes the specification.
Put roles and limits into the workflow
Who can do what, and what amount turns an action into an approval, with the reason visible rather than hidden in a menu.
Record every action
An audit trail with the before and the after, including refusals, so nobody has to reconstruct a Tuesday from memory.
Integrate rather than replace
It talks to the systems you already pay for. Migration off the spreadsheets is part of the build, not homework afterwards.
What you end up with: internal tools with role-based access, connected workflows, audit trails and the dashboards operations run on
The services this draws on
Other weeks that are not working
Does this sound like you?
Send a paragraph about how it shows up in your week. We reply within two working days with questions, a rough shape, and an honest answer on whether we are the right people for it.
Start a project