When spreadsheets multiply and the same numbers get retyped from one program to another, one answer keeps coming up: replace everything with an ERP, an enterprise resource planning system. Sometimes that is the right call. But there is another route, keeping the tools that work and connecting them, and a middle route as well. This guide compares no products. It gives you a way to decide based on your own operations, with two fictional businesses that reach opposite conclusions.
Two ways to organize information
An ERP brings activities such as accounting, sales, inventory and operations together in one piece of software, around a shared database. A sale, an inventory movement and an accounting entry are three sides of the same event.
The other approach keeps specialized tools, each chosen for its job, and links them with connections that carry information from one to the next. Think of an apartment building where every unit shares the same plumbing, compared with a row of houses you plumb together yourself, pipe by pipe. The first is consistent from day one but hard to change; the second is flexible, but every joint is yours to look after.
Between the two, BDC describes a middle option: adding a specialized tool that integrates with your current accounting system, such as inventory software, until moving to an ERP makes sense.
The signals that tip the balance
No single signal decides on its own. Just note which way each one leans in your situation, and see where the weight falls.
| Situation | Leans toward an ERP | Leans toward connected tools |
|---|---|---|
| One event changes several records | Often, and they must match to the minute | Rarely, or a few hours’ delay is fine |
| Handoffs between teams | Many, and each one causes errors | Two or three, clearly identified |
| Locations or entities | Several, sharing stock or resources | One, or independent locations |
| Current tools | Overloaded, worked around, disliked | Suited to the trade and liked by the team |
| Team capacity | People available for a long project | Little time for a major change |
| Pace of change | Processes stable for years | Ways of working that change often |
BDC offers a size benchmark: an ERP typically becomes indispensable once revenue approaches or exceeds $10 million, while noting that this is not an exact threshold. It also lists warning signs such as manual workarounds, repeated data entry and paper-based processes. Those signs show there is a problem to solve; they don’t yet tell you which route solves it best.
Two businesses, two conclusions
A fictional 18-person business rents tools and light machinery from two branches. Every booking affects equipment availability at both branches, the maintenance schedule, invoicing and deposits. Today, a unit can be promised twice because the branches don’t see the same list. Here, several records must match at the same moment: the balance tips toward a single system, whether an ERP or a complete rental platform.
A fictional six-person firm uses accounting software, a timesheet tool and a client list. All three work well and the team likes them. The only frustration: hours are retyped into invoicing every month. An ERP would replace three tools people like in order to fix one handoff. A connection between timesheets and accounting targets that one handoff, for far less effort.
Count the full cost on both sides
People often compare the price of an ERP with the price of their current subscriptions. That comparison is incomplete in both directions. BDC recommends comparing the total cost of each proposal, including licensing, hardware, implementation and maintenance, and planning at least a year to select and implement an ERP properly.
| Single ERP | Connected tools |
|---|---|
| Licences or subscriptions | Each tool’s subscription, which grows with the team |
| Implementation and setup | Building each connection |
| Cleaning and moving the data | Cleaning the data at both ends of each connection |
| Training the whole team | Monitoring connections and fixing them when one fails |
| Lost productivity during the switch | Adjustments when a tool changes and breaks a link |
| Maintenance and upgrades | Reconciliation time that remains despite the connections |
Test against your real operations
Instead of comparing feature lists, write down the five operations that matter most in a typical week, then follow each one through both setups. Where is the information entered? How many times? How many links does it cross? Who sees a mistake, and when?
Test sheet (one per operation)
Operation (e.g. a booking that becomes an invoiced rental): Trigger: Records affected: With an ERP: steps, entries, person responsible: With connected tools: steps, entries, connections crossed: What happens if a step fails, in each case: Score from 1 to 5 for each option, with one sentence of reasoning:
Then use these sheets with vendors. BDC advises giving them a demo script built around your most important tasks, rating each system on a scorecard and checking their references, the same way you would before hiring someone. A demo that follows the vendor’s script instead of yours teaches you almost nothing.
The risks of each route
A poorly chosen ERP is expensive. BDC reports a study of 1,600 ERP implementations in which over two-thirds of users did not get the benefits they expected, and notes that many failures come from systems that don’t fit the needs of the business. Add to that dependence on a single vendor and custom changes that complicate every upgrade.
Connected tools carry their own risks: connections that multiply with nobody keeping a list, silent failures, and data that slowly drifts apart. The connected route only makes sense if every link has an owner and an alert.
Before you decide
- The signals were scored with the team, not just by management.
- The middle option was considered and either ruled out for a specific reason or kept.
- The three-year cost is estimated on both sides, internal time included.
- Test sheets are filled in for your five key operations.
- Every demo followed your script.
- References from at least two comparable businesses were called.
- The contract puts in writing the requirements the vendor committed to meet.
Limits and mistakes to avoid
- The signals and cost items are general benchmarks; they don’t replace an analysis of your contracts and your data.
- This guide compares no products: offers, features and prices change often.
- Both examples are fictional and simplified; one business can combine a central system with a few connected tools.
- This guide isn’t legal or accounting advice.
Sources consulted
- BDC, “What is enterprise resource planning (ERP) software? Benefits and how to choose” ↗The definition of an ERP, the $10 million revenue benchmark (not exact), the warning signs (manual workarounds, repeated data entry, paper), total cost (licensing, hardware, implementation, maintenance), the timeline of at least a year and the middle option of a tool integrated with accounting.checked on November 9, 2026
- BDC, “3 key steps for selecting an ERP system for your business” ↗The study of 1,600 implementations (over two-thirds without the expected benefits), failures tied to poor fit, the demo script, the scorecard, reference checks and a contract that reflects the promised requirements.checked on November 9, 2026
- Canadian Centre for Cyber Security, “Baseline cyber security controls for small and medium organizations” ↗Assessing outside providers: data handling and privacy policies, location of data centres, and the rules of the jurisdictions where sensitive information is stored.checked on November 9, 2026
Written with the help of AI tools, then checked and edited by Over U. Examples are fictional. This guide is not legal advice.