Congruent's methodology for Microsoft Dynamics is founded on understanding your business.

That is why we have developed targeted questions about your how things get done in your organization. What are your business goals? What are you currently doing? How are you currently doing it? Where is your business growing? What will be your future needs? Once we understand your business, we can begin to define what features and functionality you need in a business application.

Our services range from short-term engagements on special initiatives to long-term ongoing business support. In every situation we follow a proven methodology, to ensure the success of our projects. We listen to your questions, ask our own, and then draw on each other's skills to understand what your business is, where it needs to go and what it will take to get there. You will receive answers that include options to match the timing, budget and priorities unique to your company.

Our proven methodology is one of our key success factors with all implementations.  We apply these steps to every one of our implementations, whether the project is big or small. 

Project Planning - The probability of Project success is greater when a project lead manages the following: client expectations, scope creep, client acceptance and ownership. Project planning occurs before continuing on to the Discovery phase, and continues through the project timeframe as changes occur.

Discovery/Requirements -The first purpose of discovery is to take the limited understanding CSS has of the client’s business processes from the sales cycle and perform enough analysis to develop a list of targeted business processes that will be designed in the next phase. These processes will include information relating to source documents, management reporting, and system integrations. The second purpose of discovery is to audit the network and system environment to determine the gaps that will need to be remedied before the Working Model and Implement phases can begin without issue.

Design -The first purpose of design is to determine the proposed functional and tailored design of the system to be implemented, and to enlist client approval of that design and the related project scope. The second purpose of design is to finalize (with the future possibility of change orders) the detailed project plan and complete the resource planning necessary to successfully complete the project.

Working Model - The purpose of the Working Model is to test the design, including targeted business process workflows, tailored functionality deployment, key user training, and migration plan executions. Using a Working Model allows for the resolution of issues and changes before moving to the Implement phase.

Implementation - The purpose of the Implementation phase is to build the live environment based on the final design developed in the Working Model phase. Changes in the design should not have to be made during the Implement phase, although situations can still arise that require changes. 

Support and Maintain -This phase marks the end of the project, and the beginning of supporting and maintaining the live implementation.