Inventory counts wrong by the time anyone reads them. Purchase orders managed across three tabs. Product data taking a third of the week. The signs your business has outgrown its spreadsheets, and how I would build the system that replaces them.
37+
BX1X production modules, multi-tenant, no drift
15+
Years building production software
14+
Years on Node.js, PostgreSQL, React
4
Continents served
They built it over months or years. They know which cells to never touch. If they leave, the business has a serious problem.
Sales has their copy. Operations has a different copy. Finance downloaded one last week. "Which is the latest?" is asked weekly.
A simple question ("how many orders did we do last month?") needs a pivot table, cleaned data, and a half-day of building.
Spreadsheets show you what someone last entered. They do not show live inventory, overdue orders, or queues waiting for someone out today.
When stock counts are wrong, cash is tied up in slow stock, and product data eats a third of the week. The decision tree, the off-the-shelf options, and the custom-build path.
Read the article›When POs are tracked across three tabs and reconciliation against invoices is a monthly fire.
When the customer list is in Excel, follow-ups are missed, and nobody can see whose conversation is whose.
When monthly reporting is a half-week of pivot tables. Dashboards that match how the business actually thinks about performance.
The solution to a spreadsheet that is too complex is never another spreadsheet. The cross-references multiply, VLOOKUP across folders becomes load-bearing, and breaking one breaks several.
When the SaaS fits, use it. When it does not, you spend more time working around the tool than working in it. The "almost fit" SaaS is the most expensive option in disguise.
You have moved the data-entry problem to a person. The error rate stays. The reporting still takes hours. The single-point-of-failure now has a different name.
Spreadsheet-to-system engagements start with a discovery call to map the actual workflow (not the spreadsheet, the workflow the spreadsheet is trying to model). The build is scoped after discovery.
Anton handles the discovery and the design directly. For larger multi-module builds, the engagement runs through VVW (Villiers Vision Works), the company that operates BX1X — a 37 plus module production platform, multi-tenant, multi-year, no drift.
Each article walks the workflow, the decision tree, and the build path I would propose for that named spreadsheet replacement.
The discovery answers this honestly. If your processes are standard, off-the-shelf is the right answer and we will say so. If your processes are specific or your integrations are deep, custom pays back.
Four to twelve weeks for a first usable version, depending on the scope. The discovery scopes it.
Yes. The code, the database, the documentation. You own everything.
Yes. Most builds include at least two integrations. The discovery confirms which.
It stays in use. We migrate one workflow at a time. The spreadsheet is retired only when the new system has proven out for that workflow.
Yes. The discovery includes a handover review and a continuation plan.
You can keep adding tabs, formulas, and macros. You cannot add row-level user permissions, audit trails, automation, real-time integration with your other tools, or the ability for ten people to edit the same row at once without overwriting each other. Replacing the spreadsheet is not about modernising. It is about getting the business out from under the failure mode of "one workbook, one person who understands it."
One form field. Two short sentences. Phone and email visible if you would rather call.
