In this final post following How to identify the different types of Accelerator (Part 2). I look to highlight areas of consideration, questions and closing thoughts when making this key decision.
What should I be aware of when considering accelerators?
Accelerators can be exceptional value for an organization when fully understood. Where their full benefits, risks and opportunities can be managed properly. Knowing what the accelerator will do for the project and it’s ongoing impact, means you can make an informed decision across the total cost of ownership (TCO) and not miss costs or risks that might be unknown or assumed.
The more you know about the accelerator on offer, the better. Comparing two different accelerators on the market, such as configuration vs software, may not even be like comparing apples to oranges, it might be like comparing an apple to a helicopter (feel free to substitute your own non-fruit based comparison, but you get my point).
Here are some areas you should consider and explore, accelerators of all flavour’s are a good thing, but only when you know what you are procuring;
- Does the accelerator persist any IP or software packages after deployment? Understand if this is just configuration or software. If you are left with IP as part of the Implementation, or black box / managed solutions you are not fully in control of.
- What charges are due (one off or ongoing) for the use of the accelerator? Understand what the commercial charge is for the use, or the ongoing maintenance / licensing cost of the solution. Has the partner made a commitment to keep this up to date and what assurances do you have around its continued maintenance.
- Is the accelerator portable to another implementation partner should we change during an implementation or move to another support partner once we are live? Understand what the implication is for changing partners, either as an exit plan (if needed) once live, or if the unfortunate event arises of wanting to change a partner mid implementation.
- Where has the accelerator been successfully adopted? Understand the historic use and scope of the accelerator to see if those organizations are a fit for your use case. Does a solution implemented for a facilities management company represent the needs of a housing association in your context, providing at least some insight and basis to form additional questions around the offered functional capability.
- Does the accelerator require ongoing maintenance once live? and if so, what is the roadmap for future capabilities and how do we realise these ongoing? Understand what the application lifecycle requirements are for the accelerator and if there is either software deployments required for new versions as per the Software based variety, or any obligation for managed services for configuration based.
- Is the Accelerator documented and what information can be provided on its depth and scope of functional capability to understand what has deviated from standard software? Understand if the accelerator is going to provide a right fit to your organizations needs, this goes much deeper than one simple question, and requirements gap fit analysis needs a whole article on its own, but it is important to understand how pervasive the accelerator is and make a decision on the value it beings distinct from the standard Dynamics F&O.
Closing Thoughts
The most important thing for your organization is that you get the best solution to support the goals, objectives and mission for the foreseeable future. This might mean adopting an accelerator, which could be the catalyst for your project providing the biggest return on investment and quickest time to value. But you need to question the underlying reasons you are seeking an accelerator, what you are expecting from the adoption and if provides the value that you need for the additional cost / risk when compared to standard. Understanding this will highlight the real value and speed you can expect from the delivery.
So many options exist in highly flexible solutions like F&O (and CECustomer Engagement is the collective title of D365 first party apps built on CRM technology (Sales, Service, Marketing, etc). More), especially when viewed with the wider Power Platform when designed right. Choosing an accelerator on which to base your implementation is a major project decision, and you have to ensure that the accelerator solution matches your desired outcomes without resulting in restrictions that could cost more to adapt, than the benefits the accelerator proposes to deliver.
Having seen implementation projects needing to be completely started afresh, being quicker to do so than build on top of previously deployed accelerators, and also having seen projects delivered for industries in a matter of weeks that just would not have been possible any other way, accelerators are as big a benefit as they are a risk when not fully understood. Be sure to understand the combination of configuration, software and methodology at play.
I hope this post helps shine a light on the topic, promoting a healthy conversation in your selection process to accelerate the right outcomes (see what I did there?). Onward and Upward!