A growing business has outgrown spreadsheets when important work can no longer be followed reliably from request to completion. Common signs include conflicting versions, stock or project costs rebuilt by hand, approvals hidden in messages, and routine questions that depend on one person. The next step is to identify the connected workflows that need one shared operational record, not simply to replace every spreadsheet.
Spreadsheets are flexible, familiar, and often the fastest way to begin. The problem is not that a business still uses them. The problem begins when a file has quietly become the operating system for work that several people must coordinate.
There is no universal employee-count threshold. A focused team can have complex purchasing, inventory, projects, production, or multi-company reporting. A larger team can still run a straightforward operation. Look at the work, the handoffs, and the cost of uncertainty.
The real threshold is operational friction
A shared system becomes worth considering when normal questions require manual reconstruction. Can the team see what has been ordered but not received? Can it explain why a project cost changed? Can sales see what stock is already committed? Can finance follow a bill or payment back to the operational event behind it?
If the answer depends on opening several files, asking one particular colleague, and deciding which version is current, the business has an information problem rather than a spreadsheet problem.
Six warning signs to examine
- Several versions claim to be current. People spend time reconciling files before they can discuss the work itself.
- Approvals live in email or chat. The decision is separated from the requisition, order, or payment it controls.
- Stock availability is uncertain. A balance may exist, but reservations, expected receipts, and planned use sit elsewhere.
- Project costs arrive late. Commitments and actual costs are combined after the opportunity to respond has passed.
- Handoffs require re-entry. Sales, purchasing, warehouse, project, and finance teams repeat the same details in different formats.
- Knowledge is concentrated. One person's memory explains status, exceptions, and the meaning of important columns.
These signs are useful because each points to a workflow that can be tested. They are stronger evidence than a generic claim that the business has reached a certain size.
What spreadsheets can still do well
Moving core operations into a shared platform does not require abandoning spreadsheets. They remain useful for temporary analysis, scenario planning, and ad hoc presentation. The boundary is responsibility: a spreadsheet should not be the only trusted record of an approval, stock movement, project commitment, customer order, or accounting event.
Keep the operational record in the system that controls the workflow. Export or analyse it when needed, while preserving the history and context behind the result.
Choose the first connected workflow
Start with a flow that crosses roles and already creates visible friction. Purchasing is often a useful example:
Use a real recent transaction. Identify who owns each record, where approval occurs, what changes are allowed, and which questions should be answerable without rebuilding the history. Repeat the exercise for customer orders, inventory, projects, or production as needed.
Compare the next step fairly
| Option | Useful when | Check carefully |
|---|---|---|
| Improve the current files | The workflow is stable and owned by very few people | Version control, access, and continuity |
| Add a focused application | One bounded workflow needs stronger control | Record ownership and links to adjacent work |
| Adopt a connected operations platform | Several teams need the same operational context | Implementation scope, standard workflows, and accounting choice |
Compare the full operating change, not only licence prices. Include data preparation, implementation, training, ongoing support, and the effort of maintaining connections between separate products.
How Datum approaches the transition
Datum is an operations-first, AI-native ERP for growing businesses. Its editions connect standard modules for sales, purchasing, inventory, projects and manufacturing, accounting, and cash and reporting. The edition is selected around the work; its standard modules are included together.
Guided imports help bring agreed records into the workspace. The implementation proposal defines the edition, data scope, accounting path, support, Dot usage, and any company-specific custom modules. The aim is a controlled transition from fragmented operational files to one connected record, while retaining spreadsheets where they remain useful.
Related questions
Does using many spreadsheets mean we need an ERP?
Not by itself. Some spreadsheets are useful analysis tools. The stronger signal is repeated operational risk: conflicting records, missed approvals, uncertain stock, late cost visibility, or work that depends on private files.
Should every spreadsheet be migrated?
No. Move the operational records and history that people need to run or explain the work. Retain other files according to your reporting, audit, and retention needs.
Is employee count a reliable threshold?
No. Workflow complexity, transaction volume, traceability, and the cost of errors matter more than a headcount range.
What should we improve first?
Choose one connected workflow with a clear business cost, such as purchasing through receipt or quotation through payment. Define record ownership, approvals, and the questions the new setup must answer.