How you implement the platform, whether you do it in-house or work with a specialist, has a far greater impact than you might imagine. It has a direct effect on how well the platform gets adopted, how fast you can move, and how successful you will be in the long term.
What DIY Implementation Typically Looks Like
In a DIY rollout, internal champions lead the implementation. They handle configuration, change management, training, and support, often alongside their existing responsibilities.
This model can be effective for smaller groups with simple applications and high internal skill levels. However, as the scope increases, a DIY implementation can become stuck in an early phase. Only a few teams are using the system, and there are no standards or governance models.
So, instead of a single operating system, organisations have isolated islands of productivity.
What Partner-Led Implementation Adds
An implementation partner has existing implementation frameworks and patterns.
Rather than designing everything themselves, organisations can utilize existing reference designs, templates, standards, governance models, and automation frameworks that have already been used and validated in other environments.
This can reduce implementation cycles, eliminate costly rework, and avoid common pitfalls such as over-engineered designs, inconsistent processes, or disconnected automation rules.
Adoption: Where the Paths Begin to Diverge
DIY implementation processes start with a high level of enthusiasm and excitement among early adopters.
However, it has been observed that after some time, the rate of adoption tends to slow down because the next set of users are not able to adopt the system as well as the initial set of users.
Partner-led implementation processes place a high level of emphasis on implementation strategies.
Outcomes: Measuring Real Success
Launch of the platform is not a measure of success. Success can be measured after a certain period when operational results start improving.
Operational results can include cycle time reduction, error reduction, increased visibility, employee satisfaction, or revenue growth.
DIY implementation teams can definitely achieve these results, but it takes a longer time and a lot of experimentation to get an optimized structure.
Partner-led implementation processes define success metrics at an early stage. The workspaces, work flow, and reporting structure are defined around these metrics, and organizations are more likely to conduct a post-implementation review to optimize the system over a period of time.
When DIY Makes Sense
In some cases, DIY implementation is the right solution when the scope is limited, the risks are low, and there is strong ownership and technical ability within the organisation.
Organisations that value experimentation and iterative learning may benefit from designing systems in-house.
When a Partner Is the Better Choice
Partner-led implementation is more valuable when the solution is needed across multiple departments, organisational complexity is a factor, there are compliance considerations, or the business needs to move quickly.
In these cases, a partner can help implement governance, permissions, and change management frameworks that would otherwise require significant internal effort.
Choosing Where to Invest Your Time
The question is not just whether a team can implement the system on their own.
The question is where an organisation’s time and energy are best spent. Are we best spending that time and energy reinventing how we do things from scratch? Or are we best spending that time and energy using existing expertise to use the platform to transform how we actually do business?