Our methodology
Nearly 60% of the companies we start working with describe the same experience: timelines keep extending, the budget increases after every meeting, and the implemented system remains underused. Over 25 years, we have studied the causes behind these problems and developed a methodology that eliminates them before the project even begins.
Official Microsoft Partner
of ERP Automation Experience
Completed Projects Across 12 Industries
BAS and Microsoft Dynamics 365 Business Central
The problem is rarely the system itself. The problem is the project approach.
When an ERP project is delivered in one large cycle instead of Agile sprints with intermediate results, the team and the client receive the first real feedback only at the launch stage.
For months, there is no intermediate result that can be reviewed. If something does not meet expectations, correcting it at the final stage becomes time-consuming and expensive.
The project begins without a clearly defined list of functions and implementation boundaries. Every meeting adds a new requirement that is neither formally assessed nor re-approved.
The budget increases after every meeting, while the deadline gets lost in the expanding scope of work.
The team configures a standard solution without going deeply into how the client’s actual processes work. The system goes live from a technical standpoint, but it does not match the established way of working.
The system works, but the team goes back to Excel and old ways of working.
This is the stage where the project scope, timeline, and budget are defined. The deeper the assessment, the more accurately these parameters reflect reality, making the budget and risks easier to control.
◻ A series of interviews with users across all areas subject to automation, with formal meeting documentation;
◻ Development and demonstration of the target model using the client’s real-life examples, mapping actual business processes to standard functionality and future subsystems;
◻ Fit-Gap analysis to identify areas where standard functionality does not meet business requirements;
◻ Technical specifications for each required customization;
◻ Final project estimate.
To understand the actual project scope before implementation begins.
High estimation accuracy, with a deviation of up to 10%, and predictable project costs.
◻ Confirmed model of the future system
◻ Technical specification
◻ Project estimate
◻ Project schedule
◻ Roadmap
A separate stage completed before the project begins. The cost ranges from 5% to 30% of the project budget, depending on the project’s level of customization: the closer the requirements are to standard functionality, the lower the assessment cost.
Process: Conducted through two to three meetings with the client, during which we interview stakeholders and identify the key business pain points. Based on our expert assessment, we prepare a list of the required work and present it to the client.
Primary Purpose: Provides a high-level understanding of the project scope needed for the initial decision: which platform to choose and whether to proceed.
Outcome: We provide a preliminary estimate of the project scope, timeline, and budget. At this stage, the figures are indicative, and the actual costs and timelines may differ significantly from the initial forecast.
Duration and Cost: Takes from one day to two weeks and is provided free of charge.
Most ERP project challenges arise not from the system itself, but from the implementation approach. We have refined our methodology over 25 years and more than 200 projects. Here is how it works.
We conduct a series of interviews with users across all areas subject to automation and document the processes and requirements in formal records. We model the processes using the standard system configuration and validate their accuracy together with the client. Based on the Fit-Gap analysis, we identify discrepancies between business needs and standard functionality, prepare the technical specification, and assess the feasibility of each customization.
Based on the results of the Discovery phase, CBPM Service specialists present the client with the model of the future system, the technical specification, project estimate, and implementation approach. We agree on the project schedule and roadmap with the client and project team before implementation begins.
CBPM Service analysts define the list of objects to be migrated, the format and sequence of the migration, and agree on these with the client.
We implement the solution using a sprint-based methodology, with coordination meetings every two weeks and a mandatory monthly meeting with the project sponsor. This ensures controllability and transparent project status at every stage. We carry out all customizations in accordance with the approved technical specification and demonstrate the completed functionality to the client.
We provide initial training for the client’s team so that users can work in the system while testing it against their own business processes.
We process master data and product catalogs separately from balances, including inventory, cash-related liabilities, settlements with customers and suppliers, and payroll. Before migration, we perform account mapping and remove outdated data. We carry out the export using dedicated scripts as of a specific date and transfer the agreed data scope to the test database.
The client works in the new system in test mode. Based on the results, we either proceed directly to production operation or document a list of required refinements.
We implement the agreed refinements and confirm readiness for production operation. We then switch the operational environment to the new system. CBPM Service consultants work alongside the client’s employees during the first reporting period close, identify any issues, and promptly resolve deviations. Our specialists then provide ongoing support and maintenance in accordance with the SLA.
Leave your contact details and briefly describe your situation, including your current system, number of users, and the issues you would like to resolve.
A 30-minute conversation to discuss your pain points, timeline expectations, and the project delivery approach so we can select the right team for your needs.
Technical audit of the IT architecture, project scope and boundaries, system concept, and preliminary roadmap.
A specific document outlining the scope of work, timelines by stage, and cost.
