When businesses evaluate ERP systems, most of the conversation centres on functionality. What modules are included? How flexible is it? Can it integrate with existing systems?
Those are all important questions. But there’s another one that’s often overlooked:
Who will you really be working with once the system is in place?
In many ERP models, the software is delivered through resellers or implementation partners rather than the original developers. That structure isn’t inherently flawed, but it does create distance between the business using the system and the people responsible for designing and evolving it.
That distance becomes really noticeable when something changes.
When Complexity Increases
ERP systems rarely stay static. Businesses grow, add channels, restructure teams, refine reporting, or respond to new market pressures. When that happens, questions become more detailed and requirements more specific.
In reseller-led models, those conversations can involve layers:
-
“We’ll raise that with the vendor.”
-
“We’ll need to confirm how that’s designed.”
-
“That enhancement sits outside our remit.”
Each layer introduces interpretation, delay, and sometimes uncertainty about who ultimately is responsible for the solution.
Over time, that separation can influence how confident a business feels in its platform.
The Value of Direct Access
When you work directly with the team that built the software, the conversation changes.
You’re speaking with people who understand the architecture, not just the user interface. Decisions about configuration or enhancement are grounded in knowledge of how the system was designed to scale. There’s no ambiguity about responsibility, and no translation between parties.
That proximity creates clarity. It shortens feedback loops. It ensures that product evolution reflects real operational needs rather than passing through multiple filters. Working directly with the original developers strengthens continuity. It creates a closer partnership and reinforces confidence that the system can adapt as the business evolves.
Features are important. Architecture is important.
But so is knowing that when you need to move forward, you’re speaking to the people who built the path.
At De Facto, development, implementation, and support sit within the same UK-based team. That means customers engage directly with the people responsible for designing, building and evolving the platform — creating a more transparent, accountable, and collaborative long-term relationship.