Occasionally I come across potential clients who, after initial introduction to a cloud solution, decide to self-implement. This is presumably because they can save costs, and because they believe they have enough tech-savvy about them to get the job done to the right standard and outcomes.
Firstly, let me clear that self-implementing is most definitely beneficial if your budget is tight and you know what you are doing.
The pitfalls, however, can come when you decide to give self-implementing a go, and whether you run out of time, enthusiasm, or belief in your own ability, the project stalls and you are left using half of a system, or not using it at all.
There are a number of risks that present when a project stalls, namely:
This will then leave you with a headache, and with a project that still needs to be completed (or completely scrapped!).
What tends to happen next is that the clients will call in help, to do a ‘rescue’ or a ‘fix’ and the fix can, in some cases, be more costly than engaging a professional to setup and implement your systems from the start. The time and money spent diagnosing the problems, and coming up with a solution is better spent designing a system that works before implementation.
In some cases, after trialing a certain system, it may turn out to be not quite right for your business. This happens when you are evaluating solutions. However, a little due diligence and care given to the task at hand can ensure you end up with a super effective and efficient system to run your business once you have settled on the right piece of software.