Insights / Perspective / Enterprise software implementation
PerspectiveChoosing software for the business you will become
A system chosen only for today can limit growth. A system chosen for an imagined future can overcomplicate today. The answer lies in a realistic two-to-three-year view.
Software selection usually begins with today’s pain. The accounting package cannot handle a second company. Stock is tracked in spreadsheets. Sales orders are re-keyed from email. The requirements list writes itself, and the temptation is to buy whatever solves those problems fastest.
That approach has a known failure mode. Two years later, the business opens a subsidiary abroad, launches an online channel or acquires a competitor, and the new system cannot follow. A second selection begins, often while the first implementation is barely settled.
The opposite failure is less discussed but just as common. A business buys a platform sized for a future it imagines, with modules, entities and complexity it will not use for years, if ever. Implementation takes longer, users struggle with screens built for a larger organisation and licence costs run ahead of value. A system selected only for today can limit growth. A system selected for an imagined future can overcomplicate today.
Plan for two to three years
The useful horizon for most mid-sized organisations is two to three years. It is long enough to cover the growth that is already being discussed and short enough to rest on real plans rather than aspiration. Consider new entities, currencies and channels that are likely, not just possible.
The distinction between likely and possible matters. A board that has approved a new distribution centre next year has given you a likely requirement. A strategy deck that mentions international expansion someday has given you a possibility. Design for the first; make sure the second is not ruled out.
- Legal entities: will you add companies, branches or subsidiaries, and in which countries?
- Currencies and tax regimes: will you trade or report in new ones?
- Channels: online sales, marketplaces, B2B portals, field sales?
- Volumes: transactions, products, warehouses, users, by a realistic factor rather than a hopeful one.
- Business model: subscriptions, services, rentals or manufacturing alongside distribution?
Ask the leadership team to agree these assumptions explicitly. Writing them down turns vague ambition into criteria that vendors can be tested against.
It also surfaces disagreements early. A finance director who expects one new entity and a sales director who expects five new markets are describing very different systems. Better to settle that in a workshop than to discover it halfway through implementation, when the chart of accounts and company structure have already been built for one view of the future.
Prefer modular growth
The best protection against both failure modes is a platform that lets you add capability when you need it. Many modern ERP and business platforms, from Odoo to Microsoft Dynamics 365 to SAP Business One and beyond, are built around modules or applications that can be switched on over time. Start with finance, inventory and sales; add manufacturing, field service or e-commerce when the business is ready.
Modularity is only useful if the modules share one data model. A platform that bolts separate products together through integrations behaves very differently from one where a new module simply uses the same customers, products and ledgers. During selection, ask vendors to demonstrate adding a module or an entity to a working system, and watch how much configuration and data work it really takes.
Check the ecosystem
Licence fees are only part of what a platform costs over its life. Skills, partners and integrations affect long-term cost, and they are easy to overlook when comparing feature lists.
- Skills: can you hire or train people who know the platform in your region, at reasonable cost?
- Partners: are there several capable implementation and support partners, so you are not dependent on one?
- Integrations: does the platform connect readily to the banks, carriers, marketplaces and tools you use or plan to use?
- Roadmap: is the vendor investing in the product, and in the parts that matter to you?
- Community and extensions: is there a healthy market of add-ons for needs the core does not cover?
A platform with excellent features but a thin ecosystem in your market can become expensive and risky to run. One with good-enough features and a deep pool of skills and partners is often the safer long-term choice.
Test growth scenarios in demonstrations
Include at least one growth scenario in vendor demonstrations, such as adding a new company with a different currency, or onboarding a new sales channel. How a vendor handles it tells you more than any brochure.
Avoid buying the future too early
Planning for growth does not mean implementing for it now. Licence only what you need for the first phase, configure for current operations and keep the design clean enough to extend. Many organisations overspend by licensing every module on day one, paying for capability that sits idle while the core is bedded in.
A phased roadmap helps. Phase one stabilises the core processes. Phase two adds the next most valuable capability once users are confident. Later phases follow the business’s real growth, not the projection made at selection time. Each phase begins with a short check: are the original assumptions still true?
A practical next step
Before your next selection, hold a two-hour session with the leadership team to list the likely changes over the next two to three years, and separate them from the merely possible. Turn the likely ones into demonstration scenarios and ecosystem questions for every vendor. The result is a selection that serves the business you are becoming without burdening the one you are today.
Source: Intelliversal analysis.
