One of the most positive experiences I had recently with a client involved telling them to buy a lower-cost solution than initially proposed… let me explain.
Part of the process of developing Biz Apps with a customer involves a small discovery piece of work to gather requirements and get a real understanding of what the client requires. After this period is complete, we review the requirements spec with the client. In this particular instance, the client had an initial plan of acquiring a CRM system to manage Sales, Customer Service, and Marketing tasks.
This is where the initial discovery phase is so useful. We discovered the following:
- Many of the requirements listed were “nice to have” rather than high priority requirements.
- Some of the tasks being performed by each Department didn’t necessarily require a full suite of tools for that department (eg some marketing work didn’t require an entire suite of marketing tools).
- There was no long term plan to expand the required functionality to necessitate an extensive tool.
Without these takeaways, the initial proposal suggested a multi-module CRM system such as Dynamics 365. After this work, we were able to suggest a configuration of a lower cost, a leaner system that would satisfy the client’s desires.
This process always outlines the importance of really nailing down requirements, as well as the potential benefits of offering a more limited initial application, rather than trying to satisfy too many requirements right away. While in the short term it may result in smaller projects or clients opting not to continue with a full-scale application, it provides the following long term benefits:
- Users are not overwhelmed with an extremely large and complex application, allowing for better user acceptance.
- Clients are not over-committed to a system that may not solve their problems, or may not match their changing requirements as the org expands or changes.
- The developer prevents the risk of the above two issues causing client dissatisfaction, allowing for potential additional opportunities with the client in the future.
If you would like a 1:1 demo or an overview of how Microsoft Dynamics could benefit your business, contact the Biz Apps team today.

Ian Jones - Biz Apps Solutions Architect
Ian has been working with Aspira for the past 9 years, with a heavy focus in developing solutions for business using Microsoft Technology. He works as a solutions architect with the business applications team, delivering solutions using SharePoint, Dynamics, Project Online and the Power Platform for a variety of clients across many industries.
Related Blogs
Microsoft Project – Beginner 2 * ½ Day Sessions
Overview: This course will help you effectively use Microsoft Project for setting up projects, resource management, tracking progress, reporting and communicating to stakeholders. It is for project managers, team leaders and

What we learnt on our journey to ISO 27001 certification
As Aspira turns 15 years old this year, we achieved ISO27001:2017 certification: the international standard for Information Security. The basic goal of ISO 27001 is to enable organisations to implement
Microsoft Project – Intermediate 4 * ½ Day Sessions
Overview: This course will help you effectively use Microsoft Project for setting up projects, resource management, tracking progress, reporting, and communicating to stakeholders. It is for project managers, team leaders

Aspira achieve ISO 27001:2017 Certification
“Delivering a company Information Security Management System and achieving ISO certification is a true team effort. The breadth of information security spans every aspect of the business, not just IT,

Getting Started with Dynamics 365 Marketing
Dynamics 365 for Marketing is an advanced Marketing Automation solution that enables organisations to complete the buyer’s journey from Prospect to Customer through building a relationship. The Dynamics 365 Marketing

The Benefits of Aligning sales and marketing
Misaligned teams have trouble coordinating, operate with separate information, and miss goals and benchmarks because their metrics and data are different. Separate solutions put both teams at a disadvantage because each team only sees