No one scales a business entirely without software. It’s one of those things that are kind of possible, but too much of a risky experiment today. And yet, this means you have to scale the software in question alongside the business itself.
At the time when all decisions start to feel riskier.
Most SMEs at this stage we’ve worked with share a common anxiety: what if we lock ourselves in a system, and later find out it wasn’t even designed for someone like us? But then what if we fail to address the challenges we’re facing right now?
That’s where businesses start investing in software based on immediate needs – and making nervous moves. Then, after several years, it’s about redevelopment again. In general, as far as ERPs and similar toolkits go, only about ⅓ of implementations are fully successful.
But there’s good news, too. Here is what we found out based on our experience about how to scale business and software in a healthy way: without sacrificing efficiency or spending years waiting for ROI.
Software arsenals for scaling SMEs
Let’s take an example of a SME in eCommerce that’s growing past the spreadsheet phase. By this point, something already clearly needs optimizing, some processes need automation – and the company happily implements tools to facilitate it. The available toolkit can include:
- eCommerce platforms – are often there since the start and just multiply in amount – meaning there’s risk of parallel systems that compete with each other
- WMS (warehouse management system) – improves accuracy and provides for better warehouse visibility. Over time, it also needs tight integrations with other tools because duplicate data is common (and if you juggle several eCommerce platforms at once, getting things right here is a must)
- PIM (product information management) – because product data is not always the same across platforms, especially in some industries. At a certain point, many companies just need a single source of truth for data governance, even if this means more coordination overhead.
- Accounting and finance tools – typically evolve on their own alongside everything else (and that’s the problem when it comes to manually reconciling data)
- Logistics – some 3PL portals as a rule – cover outsourced order fulfillment, tracking, returns. Very convenient when building an entire logistics infrastructure is out of the question – but also depend on external system logic.
- Middleware and integrations
- At the same time, many of these functions can be found in a big, enterprise-grade ERP: you get orders, inventory, purchasing, sometimes finance, all under the same hood. This is an option for those who are ready to take a plunge.
Accordingly, some companies go for separate tools at first, then, if the integration effort between them becomes scary, consider a big ERP system or build custom software.
And the common mistake at this point is to get distracted by the software complexities to forget the business complexities that this software is meant to solve.
Common challenges when scaling business systems
By now, there exists something of a “recognized list” of the most common “growing pains” in businesses. Software developers with industry expertise, especially those above the middle/senior level, can event recite it by heart, because that’s what the users demand to solve first:
- too much manual work;
- lack of visibility across processes (“where is this order right now?”, “what is actually in stock?” and so on);
- coordination between teams eats up paid working hours;
- workarounds and exceptions (and teaching new employees to handle these takes months);
- data inconsistency across functions or systems (“why are the statuses different depending on who you ask?”).
Most software primarily solves this. Within its own operational context. And that’s where the less obvious challenges start to matter.
Hidden challenges in ERP and system implementation
When companies come for custom development, we often hear this interesting formulation:
– Everything was working fine until we hired new employees. Then we found out things were functioning because the older employees knew what to do in tricky situations.
Which means the actual “working system” was not the one they codified in procedures, but the one quietly existing under radars in the employees’ heads. And that, in turn, points at the hidden challenges to solve with ERP or other software when scaling:
- Processes exist, but are not fully consistent. E.g. the same type of order or request is handled slightly differently depending on context, urgency, or whose shift it is.
- Decisions are made, but not always in the same way. In other words, similar cases but unpredictable outcomes.
- Workflows function but depend on who is involved – the “people who know” vs. “how do we scale” dilemma.
At a small scale, this is manageable. As complexity grows, it becomes harder to maintain.
This means that whatever software strategy you choose, you will need to address these, too – and if you don’t, you’ll have to invest in more onboarding training.
It’s not just a tooling problem
The interesting thing is that all of this is no longer a tooling problem. The software tools themselves, in their isolated forms, can be perfect. The main factor is coordination, and the associated overheads.
This is where everything gets even more interesting. Most companies have their own delicate balance between the different functions and parts of the workflows, while tools like out-of-the-box WMS or CRM will operate on assumptions about them. Everything is perfect within the tool, and not so perfect on the seams between the tools.
At the same time, getting a big, majestic ERP for everything will solve the coordination problem partially – but also make things rigid. For many SMEs, making commitments too early is risky, too. Plus, large enterprise-grade systems often feel like overkill.
The important thing to realize is that no matter whether you use a combination of out-of-the-box tools, an all-in-one ERP or develop a custom system for your company – you are still tailoring the overall infrastructure yourself.
And that’s perfect, because you can control some very important nuances about how your software system matches your processes and evolves alongside them.
Scaling eCommerce Operations: How to Connect Product Data, Inventory, and Fulfillment Without System Chaos
In May 2026, we co-hosted a webinar with our long-time client, PassOn Solutions, discussing the practical ways of connecting business functions properly. The session is based on our joint experience developing the PassOn platform, which grew out of a custom cross-functional tool organically.
This evolution – from an industry- and company-specific solution to a platform that matches widely different company profiles – deserves a deep dive and explains quite a lot about the process.
You can watch the entire session on video below.
Chapters:
00:00 – Introduction and context
02:40 – What breaks first when eCommerce businesses scale?
12:40 – Integrated vs. modular systems: benefits & trade-offs
23:45 – How to translate workflows into software
38:12 – How to tackle industry specifics
You can also download the webinar slide deck as PDF below:
In this webinar, we explored how system decisions actually show up in real operational situations when companies scale: specific examples (from textiles to heavy machinery), checklists (when to know a workflow is to be reflected in custom software) and more.
Across all of these examples, the key pattern is the same.
System design is not just about implementing tools – it’s about making very concrete decisions about what gets formalized, what stays adaptable, and where human judgment is still part of the process.
If you’re thinking about ERP systems, custom development, or how to connect multiple tools into something that actually works in day-to-day operations, this is usually where the real challenge sits.
We’re happy to look at specific setups and help clarify where standardization makes sense – and where flexibility is still necessary. You can contact our team for consultations at any time.
