No. You can start by describing the operational problem or outcome you are trying to achieve. Discovery helps determine whether the right path is ERP, custom development, integration, process improvement, or something else.
Back to FAQs
Discovery & Consultation
Direct answers to the most common questions about our work and methodology.
We review how the business operates today, the systems already in place, how information moves, where work slows down, who uses the systems, what management needs to see, and what the organization is trying to improve.
Because a problem that appears technical may actually be operational, and vice versa. Understanding the process first reduces the risk of investing in software that does not address the underlying issue.
A demo can be useful, but it becomes far more meaningful once the business requirements are understood. This allows the discussion to focus on relevant workflows rather than a generic tour of unrelated features.
Yes. In many cases, reviewing why the current environment is underperforming is a better first step than assuming the entire system needs to be replaced.
Yes, when it makes sense for the project. Not every technology initiative needs to begin with a company-wide transformation.
A project scope and commercial proposal can be prepared once there is enough information to define the work with reasonable clarity.
Reflection is particularly relevant when the business needs to understand the problem before choosing the technology, has interconnected or specialized workflows, or requires improvement, integration, or development that demands both operational and technical thinking.