Cygate

Konstrukt's first customer Cygate needed to replace an existing system that users were no longer happy with. Additionally, the system had become too expensive and inflexible for their needs.

Before Konstrukt

Cygate has a complex matrix organization whose business rules could not be fully implemented in the old system. The need to do something about it grew. Therefore, before the budget process in autumn 2014, Cygate decided to test Konstrukt to see if it could better meet the needs of the business in the short and long term.

After Konstrukt

Ultimately, Cygate selected Konstrukt and the product was implemented within the business in stages. In 2014 the essential parts were rolled out, and in 2015 more business rules were implemented into Konstrukt to fully support the complex needs of the business. This meant that the users of the product got a solution that became more and more complete with time.

Product sales

Planning based on revenue per salesperson and product area. Here, the coverage ratio (TG%) is also planned and the system calculates the coverage contribution (TB) based on TG% and planned revenue.

Internal Purchases

Internal purchases are planned for using an efficient acceptance process by the counterparty. For example, if internal revenue is planned then the counterparty must accept it by planning for a cost. In this way, both parties must actively accept the planned transaction and in this way the budget is consistent between different divisions.

Consultant budget

Here the consultant availability and utilization is planned, allowing for factors such as normal availability, annual leave, sick leave, and so on.

Analysis of budget process

Konstrukt has control of where you are in the process, but if there are more complex needs it's possible to build something in the BI system. Here's an example setup using QlikView to visualise the task completion.