From initial contact to the official kickoff
An ERP project sometimes starts with a simple question. In this case, it began with an email from Emerald Eternal Green in Eindhoven to Uniconta.
This was followed by a meticulous process. It involved not only meetings and demos, but also a preliminary study, coordination with relevant third parties, and the development of a blueprint. The official kick-off has now taken place, and Emerald Eternal Green and Promentum Consulting the implementation of Uniconta.
Emerald Eternal Green specializes in lifelike artificial flowers, artificial plants, and green decorative solutions. Based in Eindhoven, the company serves business customers both domestically and internationally. An organization with commercial, logistical, and international processes requires an ERP platform that not only supports administrative tasks but also helps to effectively organize processes, data, and integrations.
Why start with a blueprint?
At Promentum Consulting , we don’t automatically Promentum Consulting a blueprint for every project. Sometimes the scope is clear enough to start implementation right away. In other cases, it makes more sense to first clarify the details and provide more specificity.
A blueprint helps you make better decisions in advance—not based on theory, but on the customer’s actual experience.
There may be several reasons to go through a blueprint phase first.
Sometimes it’s mainly a matter of planning and phasing. For example, an organization may not want to migrate all its processes and departments to a new ERP platform at once. That can be a sensible choice, but it does have consequences. If, for example, a customer wants to start with Uniconta a PIM solution while keeping the old ERP system active for the time being, a temporary interface between Uniconta the existing ERP system may be required.
Such a temporary integration is, in itself, a “waste of money” because it will eventually be phased out. Nevertheless, it can be a sound business decision. It allows the organization to get accustomed to Uniconta, improve processes step by step, and avoid burdening the entire organization with a full-scale transition all at once.
In other situations, however, there may be several possible approaches. In such cases, it is important to determine in advance which approach is the best fit—not only functionally, but also technically, financially, and organizationally.
The blueprint for Emerald Eternal Green
One of the key questions at Emerald Eternal Green was what the future application architecture should look like.
One specific topic was the new B2B portal. Further details were worked out during the blueprint phase. What exactly should the portal support? Which parties are eligible? Is there a modern integration with Uniconta ? Who will build the integration? And does the chosen solution align with how Emerald Eternal Green intends to operate in the future?
In addition, Emerald Eternal Green uses middleware. This naturally raises an important question: should we continue to use middleware, or would it be wiser to Uniconta certain applications directly to Uniconta via APIs?
This isn’t purely a technical discussion. The choice has implications for costs, management, flexibility, and future-proofing. Especially when proven API integrations already exist, a direct connection may make more sense than continuing to use an additional middle layer. At the same time, middleware can remain useful in some situations. The right choice depends on the applications, the available integrations, the complexity of the landscape, and the desired phasing.
This is exactly why a blueprint can be valuable. During the sales phase, it’s easy to say, “There’s an integration with UnicontaorUniconta communicate with multiple applications.” But that’s not enough for a successful implementation. The real questions are: which integration is the best fit, does it already exist, has it been proven, who is responsible for building and managing it, what are the costs, and what does this mean for the schedule?
A Deep Dive into the Technical Details
During the blueprint phase, we therefore look not only at processes but also at the applications related to Uniconta.
For each application, we assess its role within the overall landscape. What data flows in and out? Is a standard integration available? Is there a modern API? Will custom development be required? Who will manage the solution after it goes live? And what happens if a process is implemented in phases?
Answering these questions in advance will result in a more realistic implementation plan. The blueprint provides clarity on the scope, dependencies, choices, risks, and phasing. This helps prevent important decisions from coming up only during implementation, when the pressure is higher and there is less room to make adjustments.
At Emerald Eternal Green, this phase has now been completed. The key decisions have been made, the dependencies are clear, and implementation can now begin in earnest.
From preparation to implementation
With the official kickoff, the project has now moved from the planning phase to the implementation phase.
In the coming period, the teams at Emerald Eternal Green and Promentum Consulting will be working Promentum Consulting on the configuration, validation, integration, and further implementation of Uniconta. Thanks to the preliminary phase, a clear foundation has been laid for a structured approach to the project.
The team is excited. The kick-off was a great first celebratory moment, but we’re already looking forward to the next one: the successful launch of Uniconta Emerald Eternal Green.
We would like to thank Emerald Eternal Green for their trust and look forward to working on a great project together.
Are you also considering Uniconta an ERP implementation?
Not every ERP project requires a detailed blueprint. However, when decisions still need to be made regarding phasing, integrations, applications, or process design, a blueprint can actually help prevent a lot of debate and uncertainty during implementation.
Promentum Consulting organizations prepare for and implement Uniconta. We take a practical, content-focused approach, paying close attention to both processes and technology.
