Turning the spreadsheets your business depends on into software
Turn a spreadsheet into software when several people need it together, when an error in it is costly, or when no one can trace a change. Brihat reads the file's formulas as the specification, then builds roles, approvals and records around them.
Last reviewed:
Three tests
A spreadsheet has outgrown its role if it fails any of these tests:
- Shared use. Two people cannot edit it at once, so work queues behind whoever holds the file.
- Cost of a mistake. A bad figure shifts money or breaks a promise to a customer, and no check catches it.
- Change history. The only record of edits is a version number in the file name.
Other signs: the macro's author has left the company, and emailed copies drift apart.
How the replacement runs
- Pick the file that matters. Start with the one whose failure for a day would hurt, rather than the one that looks most complex.
- Read the formulas as the specification. They hold decisions nobody remembers making. Writing them out often shows the business its own pricing and approval rules in plain words for the first time.
- Model the workflow. Add roles, states, validation and approvals. A grid rebuilt as a web grid adds none of these.
- Connect what stays. Link the platform to the systems that remain, so figures are not typed twice.
- Run alongside the old file until the platform matches it over a full cycle. The file stays the reference until then.
No-code tools or custom software
A no-code tool suits a simple form-and-list process within one team. Check three things before choosing it: how complex the rules are, how many systems it must connect to, and whether per-user fees will spread across the whole company as use grows. Where those point upward, custom software on your own repository is the better base.
When to keep the spreadsheet
- One person uses it now and then, and the analysis changes each time.
- The process still changes every week. Encoding it now makes each change dearer.
- A packaged tool already does the same job.
See it in practice
A pan-India logistics operator moved trip tracking from phone calls to one control tower. Figures are on the case page.
Related: Tally to a custom ERP, build or buy.
Questions buyers ask
Test each formula against the business rule before carrying it over. A spreadsheet collects exceptions that were right once. The rewrite is the chance to drop them.
The number of rules and connections, not the number of columns. A paid discovery scopes it first; the engagement guide explains the steps.
Tell us what you want to build.
The first call is 45 minutes with an architect, usually the founder. It is free, and we will sign an NDA first if you ask.