Frequently asked questions, clear answers

Every DigitFlow project starts with a free initial conversation in which we understand your situation and goals. This is followed by a workshop where we jointly identify and prioritize use cases. We test the most promising idea as a proof of concept on your own infrastructure. From there, a pilot project can emerge, which we gradually develop into productive use. You decide after each phase whether and how to continue.

That depends on the scope, but with DigitFlow you typically see first results after a few weeks. A proof of concept with real data on your infrastructure is usually ready within four to six weeks. More complex projects with multiple data sources or integrations take longer, but we always work iteratively so you can see early whether the approach works.

At DigitFlow, the architects responsible for your project are at the table from the start. Armin Pfauser (Managing Director, ITSM expert) and Mohamed Dhif (CTO, ML engineering) personally support every project. No senior pitch followed by handover to juniors. If needed, experienced specialists from our network join, but responsibility always remains with the founders.

Yes. DigitFlow works phase by phase, and you decide after each step whether to continue. There is no long-term contract and no minimum term. If the proof of concept shows that the approach does not fit, we stop. The risk stays low because you never commit more than the next phase.

No. DigitFlow is used to working with heterogeneous and incomplete data landscapes. Perfect data is the exception, not the rule. Where necessary, DigitFlow handles data cleansing and harmonization as part of the project. We adapt the technical infrastructure to your environment, whether Docker, Kubernetes, VMs, or dedicated servers.

In large consultancies, a senior person often leads the pitch and then a team of juniors takes over. DigitFlow is different: the architects responsible for your project are involved from the beginning and stay involved. There is no overhead and no hierarchy in between. DigitFlow also delivers working solutions, not slides. What we build belongs to you.

With SaaS providers, you pay ongoing licenses, your data sits in someone else's cloud, and you depend on the provider. DigitFlow builds custom solutions that run on your infrastructure and belong to you. No ongoing license costs, no vendor lock-in, full control over your data. The initial investment is higher, but in our experience it pays for itself within a few months.

Open source gives you freedom of choice. You are not tied to a provider and can continue developing the solution yourself or have someone else develop it further at any time. DigitFlow builds on open standards and modular architecture so you remain flexible in the long term. This is not an ideological decision, but a pragmatic one: open source offers better building blocks in many areas.

DigitFlow sees itself as service architects for established system landscapes. That means we do not replace what you have; we understand your existing landscape and build the right AI solution on top of it. Like architects who modernize an existing building instead of demolishing it. We call this retrofitting: fitting new technology into existing structures, pragmatically and with respect for what has grown over years.

DigitFlow primarily works with organizations between 250 and 3,000 employees in the DACH region that have an established IT service landscape. Typical industries include healthcare, finance, utilities, and mechanical engineering. In addition, DigitFlow works with law firms, engineering offices, and service providers that want to solve a concrete automation problem, for example in document analysis or knowledge management.

That depends on the scope. DigitFlow works project-based and transparently; there are no subscription models and no per-seat fees. The implementation belongs to you. A proof of concept typically starts in the low five-figure range. Maintenance and further development can optionally be added as a retainer. In the first conversation, we clarify the scope and give you a realistic assessment.

Yes. The free initial conversation is non-binding. After that, you can start with a clearly defined proof of concept that runs on your own infrastructure. You see real results before deciding on a larger project. DigitFlow recommends this step-by-step path because it minimizes risk for both sides and lets you decide freely after each phase whether to continue.

The Incident Radar is a joint offering from DigitFlow and Verenburg Consulting. In ten days, DigitFlow uses AI to analyze your existing ticket data and delivers a BI dashboard with concrete insights and a prioritized action plan. Verenburg interprets the results from an ITSM and organizational perspective. Fixed price, no risk, no commitment afterward. The Incident Radar is ideal if you first want to see what is in your data before starting a larger project.

Yes. DigitFlow relies on open architectures, and the source code belongs to you. You can take over operations yourself if you have the resources. Alternatively, DigitFlow offers ongoing support as a retainer: proactive monitoring, retraining models, and further development. You decide what fits your organization.

DigitFlow sets up automatic monitoring that detects changes to data sources and interfaces early. Usually, small adjustments are sufficient. If you do not want to handle maintenance yourself, DigitFlow offers managed services. This keeps the solution stable and up to date over time.

At DigitFlow, the standard case is that your data stays in your own infrastructure. On-premise, on your servers, in your data center. Alternatively, DigitFlow uses German or European cloud providers. Your data never leaves your control and does not go to US providers. This is not an optional setting; it is how the architecture is built from the ground up.

GDPR compliance is not an add-on feature at DigitFlow, but a design principle. Data processing takes place on your infrastructure or in a German cloud. Access controls are role-based, all processing steps are documented and traceable. DigitFlow builds solutions so that you can show at any audit where which data is stored and who accesses it.

Yes. DigitFlow builds on open standards, and the source code belongs to you. There is no vendor lock-in. If you decide to have the solution operated or further developed by someone else, nothing stands in the way. This is a deliberate design principle at DigitFlow.

DigitFlow adapts the solution to your existing environment: Docker, Kubernetes, virtual machines, or dedicated servers. We define the minimum requirements together during scoping. In most cases, standard resources are sufficient. For larger requirements, we size the infrastructure together with your team.

DigitFlow uses encrypted transmission paths, encryption of stored data, and role-based access controls. The concrete setup depends on your compliance requirements and is documented per project. For customers in the financial sector, DigitFlow has built solutions that meet banking-level security requirements.

DigitFlow builds modularly and on open interfaces. If a new system is added or an existing one is replaced, the solution can be extended without rebuilding everything. In a retainer, DigitFlow monitors technological developments and proactively adapts the solution so you do not have to keep track of everything yourself.