After laying the groundwork for digital transformation in our previous article, we now tackle the practical challenges of implementing Software as a Service (SaaS) CRM solutions such as Dynamics 365. With the CRM market set to surge from $101.41 billion in 2024 to $262.74 billion by 2032, a CAGR of 12.8% (Fortune Insights), the shift to cloud-based deployments is accelerating. SaaS, as Gartner describes, is software delivered remotely and accessed on a subscription basis, making it a flexible and scalable choice. In this article, we’ll share actionable strategies and lessons from real projects to help you succeed with your SaaS CRM implementation.
Why Implementation Success Matters
Successful implementation is crucial to any digital transformation journey. Yet a Gartner research shows that 50-70% of SaaS CRM projects either incur losses or fail to deliver meaningful improvements. For instance, I worked with a higher education institution that embraced the Nexus approach to digital transformation and crafted a business-driven roadmap, but still encountered major hurdles. The root cause? A lack of understanding between deploying a SaaS solution and building a custom on-premise system.
Here are the five main reasons organisations repeatedly encounter these challenges:
- Replicating Legacy Solutions
Many organisations fall into the trap of replicating their legacy systems due to limited internal expertise. This common pitfall leads to missed innovation opportunities and reduced usability. SaaS solutions such as Dynamics 365 are designed using insights from thousands of customer processes and industry standards, providing a valuable baseline that can be tailored to specific needs.
- Over-Customisation
Customising SaaS solutions is a powerful way to adapt standard processes to your organisation’s needs. Yet, many businesses fall into the trap of excessive customisation, treating SaaS projects like traditional on-premises implementations. This often leads to simply transferring old custom CRM systems to the cloud, missing out on new efficiencies and failing to realise the full ROI. Over-customisation can also disrupt the provider’s technology roadmap, cause compatibility issues, increase maintenance costs, and create extra work to manage custom code. Upgrades then become more complex, requiring thorough testing to ensure everything still works.
- Adapting Instead of Adopting
Many organisations adapt their existing processes to fit the SaaS solution, rather than adopting the provider’s baseline processes. This often leads to underutilised features and wasted subscription fees. It’s more effective to start with the embedded processes offered by the SaaS provider and then tailor them as needed. For instance, Microsoft’s Business Process Catalogue for Dynamics 365 provides customers with a strong foundation for transformation, enabling them to adopt proven processes and customise them to their specific requirements.
- Limited Use of Training Resources
The more you customise, the less you can leverage the extensive training and documentation available for SaaS products. Your SaaS investment includes access to high-quality learning resources, reducing the effort required for training and documentation. For instance, Microsoft Learn offers comprehensive technical documentation for extending and tailoring the platform, as well as business training paths with gamification to support user adoption.
Addressing These Challenges: The Success by Design Approach
Finsights leverages Microsoft’s Success by Design (SbD) framework to overcome these challenges. Originally developed by Microsoft’s FastTrack team for Dynamics 365 deployments, SbD draws on insights from thousands of complex SaaS implementations. While designed for Dynamics 365, Finsights has adapted the approach for broader SaaS solutions, combining SbD principles with industry best practices.
Our SbD approach provides prescriptive guidance for architecting, building, testing, and deploying SaaS solutions. It complements, rather than replaces, your existing implementation methodology, such as agile, by strengthening governance and aligning projects with SaaS best practices. Built on three core principles, early detection, proactive guidance, and predictable success, SbD drives faster deployments, maximises ROI, and, according to Microsoft, can increase SaaS adoption by 2.2x.
How SbD Works
SbD organises the implementation into methodology-agnostic phases and recommends a series of reviews and deep-dive workshops. Two sessions, the Solution Blueprint Review and Go-live Readiness, are mandatory. These checkpoints enable critical discussions, risk assessments, and validation of best practices. They also ensure timely alignment with project milestones and allow early identification of key delivery elements to prevent delays.
SbD essentially acts as a comprehensive checklist of the most critical factors in a SaaS implementation project. These items can be organised into success measures and monitored throughout the project lifecycle. In fact, 30 success measures highlight how SaaS implementations differ from traditional custom-built solutions. The diagram below illustrates these measures for Dynamics 365 online, though they are equally relevant for many other SaaS products.
The Five Design Pillars for SaaS Success
Now that we’ve explored the SbD approach, let’s dive deeper into the core pillars of the SbD SaaS solution architecture. The diagram below highlights five design pillars that ensure your solution aligns with your business vision, goals, and strategy. For more insights on aligning vision with implementation, refer to our DX Transformation Success Framework.
- Governance
Establishes rules, roles, responsibilities and processes for decision-making and accountability throughout the project lifecycle. It ensures sound architecture decisions and effective scope management.
- People
Ensures stakeholder involvement at the right intervals. Key elements include:
- User-centric design: Building solutions for end-users using human-centred design techniques.
- Change management: Preparing users for change using the ADKAR methodology.
- RACI framework: Clarifying project roles and responsibilities to prevent confusion and delivery issues.
- Process
Focuses on redesigning business processes, a critical and complex step in transformation. Vendors like Microsoft provide tools such as the Business Process Catalogue to help organisations adopt SaaS features rather than replicate legacy systems.
- Data
Requires a robust strategy for governance, architecture, quality and integration to:
- Understand customer needs and enhance experiences.
- Provide a 360° customer view and actionable insights.
- Identify operational bottlenecks and optimise processes.
- Technology
Acts as an enabler across all pillars. Adopting a cloud mindset is essential, as SaaS products are updated frequently. Embrace change as constant and establish architecture principles such as:
- Favour configuration over customisation.
- Simplify technology landscapes using modular, composable components.
Conclusion
At Finsights, our SbD approach is designed to eliminate complexity, accelerate delivery, and align every step with your business goals. By combining proven methodology with deep expertise, we help you unlock the full potential of SaaS and maximise ROI. Let’s talk about how we can make your next implementation a success.
Written by Adel Flici, Founder of Finsights Ltd, a Microsoft AI Business Solutions Partner.