Keep the spreadsheet, add discipline
Choose it when
Two or three people use it, the rules are simple, and an error is cheap.
What it costs
Someone becomes the spreadsheet’s keeper. It works until they leave or the volume grows.
Replace the spreadsheets that run the business.
Every record gets an owner, a history, and permissions, and the Friday report builds itself. We build the tool the shared spreadsheet has been standing in for, load its data, and run both until the numbers match.
You know this is you when
- More than three people edit the same spreadsheet, and someone has overwritten someone else this month.
- There is a “master” copy, and it is not the one people are using.
- A weekly report is built by copying cells into another spreadsheet.
- Nobody can say who changed a value, or when.
- A new hire spends their first weeks learning the spreadsheet’s workarounds.
Why it is happening now
Spreadsheets are excellent until they are shared. The moment several people depend on one to run an operation, it needs the things a spreadsheet does not have: one record per thing, an owner, a history, permissions, and reports that build themselves. Growth usually brings this to a head: a new site, contract, or hire arrives, and the spreadsheet breaks in a way a customer notices.
Illustration of an internal tool built by Baybloom to replace a shared spreadsheet: purchase requests as records with owners and budget lines, approvals recorded, and the weekly report built from the records.
What we would do first
The first steps, in order.
- 01
Read the spreadsheet with the people who use it
Every column is a decision someone made. We find out which ones matter, which are workarounds, and which systems the values really belong to.
- 02
Define the first release
It covers the main workflow the spreadsheet runs, as records with owners and stages, plus the roles, the report it fed, and the integration that removes the most re-typing.
- 03
Build it on the real data
The spreadsheet’s history is loaded, cleaned, and reconciled, so the first day in the new tool starts with the records people know.
- 04
Run both until the reports match
Then the spreadsheet goes read-only. Nothing is deleted without sign-off.
What it looks like after
Each thing the spreadsheet tracked is a record with an owner and a history. People see what they are allowed to see. The Friday report builds itself. When a value is wrong, you can see who changed it and put it right once.
Property management company
Coordinators, vendors, and the leasing office can all see where each unit turnover stands.
At a property management company, a move-out usually starts a spreadsheet row that coordinators, outside vendors, and the leasing office all edit at once, and nobody can tell who changed a status. A turnover tool makes each one a record with the unit, a checklist, vendor tasks, due dates, and photos, and the leasing office sees which units are ready to show. The vacancy report builds from those records. The spreadsheet stays available, read-only, until the reports match, and a next phase often connects work orders to accounting.
The path from here
What we would build, and for whom.
The service
Custom software developmentApplications built around the way your business runs.
ReadWhat we build
Internal tools and business softwareReplace the shared spreadsheet, the approval email thread, and the admin console nobody was given.
ReadBy industry
Logistics and distribution businessesOrders, stock, and shipment status that agree across the ERP, the warehouse, and the carriers, so customers see where their order is without calling.
ReadA guide
Should you buy software, connect your tools, or build something custom?Written for the decision, not the sale.
ReadQuestions
Before you decide.
What companies in this situation ask us first.
Is a spreadsheet ever the right answer?
Often. When a few people use it, the rules are simple, and mistakes are cheap, it is the best tool there is. The problem starts when it becomes shared infrastructure.
Will we lose the history?
No. The spreadsheet’s data is loaded, cleaned, and reconciled into the new records, and the original is kept read-only.
How do you keep the new tool from becoming the next spreadsheet?
We replace cells with records, a shared file with named owners, trust with permissions, and copied reports with reports built from the records. The structure enforces the discipline.
Can the team keep exporting to a spreadsheet for analysis?
Yes. The new tool can export to a spreadsheet; the spreadsheet just stops being the system of record.
Describe the spreadsheet.
Tell us the situation and the systems around it.We’ll come back with what we would do first, and what it would take.