Our services
From assessment to day-to-day operations.
We combine business process expertise with technical delivery to implement Flowtion. We support customers from assessment and solution design through training and operations, then evolve the system as requirements change.
Let’s discuss your requirements →Our implementation process
Documented design, controlled delivery.
1. Discovery and project preparation
Together with business stakeholders and IT, we review current operations, the problems to address and the expected outcomes. We define the project scope, key requirements, system interfaces and delivery prerequisites, then prepare an indicative proposal and initial schedule.
2. Process modelling and solution design
We document the design in Enterprise Architect and Camunda. Business processes are modelled using BPMN 2.0 notation, defining activities, responsibilities, decision points and exception handling. Alongside the process models, we specify data, access control and integration requirements, together with acceptance criteria. Delivery is based on the specification approved with the customer.
3. Configuration, development and integration
Using the approved design, we configure standard functionality, forms, workflows and permissions. Custom requirements and system interfaces are delivered within the agreed project scope. We prepare data loading and migration, and document changes arising during implementation.
4. Testing and quality assurance
We validate the solution against the approved requirements and acceptance criteria. Functional and integration testing is followed by customer acceptance testing using scenarios that reflect day-to-day operations. Defects and their resolution are tracked, and fixes are verified.
5. Training and go-live
We prepare key users and other staff with training tailored to their responsibilities. Go-live follows an agreed transition plan defining data loading, verification and launch activities, owners and timing. We review the initial experience together and support adoption of the system.
6. Support and ongoing development
After go-live, we support users and handle requests within the agreed service scope. New business requirements are assessed against existing functionality, and the necessary configuration changes or enhancements are planned. This allows the system to evolve with the business.
AI-assisted implementation
We use modern AI tools, including Claude and ChatGPT, to accelerate implementation and development and support quality assurance. They assist our specialists with preparing and reviewing documentation, working through implementation tasks and preparing tests. Our specialists review the results; acceptance remains based on the approved specification and documented testing.
Operations and customer support
Azure operations
We operate the Microsoft Azure environment under a fixed-fee package. The service includes the server and database, separate test and production environments, regular backups and operational monitoring.
Support and incident management
Our customer support is available within a 5 × 9-hour service window, with a four-hour response time. Reported incidents are classified and handled according to severity and priority using an ITIL-aligned approach, under the terms of the support agreement.
Remote support with controlled access
We often provide support through remote access, aligned with the customer’s information security policies and technical requirements. Access is protected by measures suited to the environment, which may include centralised password management in Bitwarden, VPN connections, a jump server and IP-based access filtering. The controls used and the access conditions are agreed with the customer.
Predictable support capacity
Ongoing support includes a minimum commitment of eight hours per month. Additional work is billed on a time-and-materials basis; the scope and billing rules are defined in the support agreement.
Business and technology expertise
We understand the accounting behind your processes.
Our team has substantial finance and accounting expertise, with several colleagues holding Hungarian professional accounting qualifications (mérlegképes könyvelő). When designing workflows, we consider settlement logic, financial controls and management information needs alongside technical operation.
Deployment and licensing
Licensing that fits your operations and investment plans.
Flowtion can be deployed on your own infrastructure, on premises, or in the cloud. Both deployment options are available with a one-time licence fee or a monthly subscription: deployment location and the licensing payment model can be chosen independently.
One-time licence fee and annual maintenance
The one-time licence model includes an annual software maintenance fee. This fee continuously provides the right to use the latest product version, making access to new releases a predictable annual expense.
Monthly subscription
The system is also available on a monthly subscription, whether deployed on your own infrastructure or in the cloud. The licence mix is tailored to the selected modules, user requirements and number of servers needed.
Licence types by product
BusinessDesk, FieldOps and Studio
These products use a combination of a server licence and user licences. Both named and concurrent user licences are available and can be combined within the same system.
Connect and Data Exchange
The Connect and Data Exchange modules require only a server licence. This licence allows an unlimited number of users to use the module, without separate user licences.
Named user licence
A named licence is assigned to a specific user. It is a suitable option for employees who regularly use the application as part of their daily work.
Concurrent user licence
A concurrent licence determines the number of users who can access the system at the same time. It can be useful for a wider user base whose members do not all use the system simultaneously.
One server licence, three environments
One server licence is required per server and provides three environments: development (dev), test and production (prod). Development, validation and day-to-day operations can therefore be organised in separate environments.
Licensing, software maintenance, infrastructure operations and customer support are specified as separate items in the proposal. Software maintenance provides the right to use the latest version; the scope of operations and support is defined by the respective service terms.