Custom software at a fixed price — built in-house, with our own toolchain

Roughly from 50 employees upwards — or wherever a standard product does not go far enough. What decides it is not the headcount but two things: someone on your side can articulate requirements, and there is a budget and decision process. Where that is missing, a standard product is the better route — and we say so.

Because otherwise it would be worth nothing. An unspecified initiative cannot be priced responsibly; the alternative would be time-and-materials billing — exactly what mid-market buyers rightly fear. In the analysis phase we take on the specification work and deliver a written scope plus a fixed-price quote. You buy something small first and can stop afterwards, with a usable result in hand. The consultation before it stays free.

For custom development, the source code can be handed over to you in full. The reason is logic, not goodwill: what we build only for you has no reuse value for us. Put simply — what we build for everyone stays our product; what we build only for you belongs to you. Our standard product krafteq Handwerk works differently: there you get a perpetual right of use with your own installation, and the source code is included when you self-host — for inspection and further development for your own business, no redistribution; under krafteq operation it stays with us. The price difference is exactly that difference.

14 days after contract signature the first engineers are working. Before that comes the analysis phase, which takes one to two weeks depending on scope. We deliver first visible results within a few weeks — for new builds as well as for migrations.

No. But you do need someone who can describe your processes and make decisions — that is not an IT role, it is knowledge about your business. The technical specification is our job in the analysis phase. Development, operations and updates sit with us, unless you prefer to operate the system yourself.

Your data stays in Germany or the EU. We operate on servers of European providers — Hetzner, OVHcloud or IONOS, depending on requirements. The architecture supports GDPR-compliant operation: tenant separation, permission models, logging, an Art. 28 GDPR DPA and the TOMs are part of the standard, not an add-on. On request the installation runs entirely inside your own network, with no internet connection. Even with EU-wide development, data stays in the EU — and your German-speaking contact is based in Germany.

Included is whatever the agreed scope says, plus fine-tuning after go-live to the agreed extent. Not included is new scope: anything that comes up during the build gets its own quote instead of a quiet slip in the timeline. The fine-tuning afterwards absorbs adjustments, not new initiatives.

We work in our own environment, with our own tools — not in someone else's. That is where the price comes from: the same AI-powered toolchain we used to build our own product also builds your project. Inside a client's environment that advantage would stop at the door, and what gets sold is interchangeable capacity at a day rate. That is why staff placement is a side offering for us, not a focus.

It covers the start of projects and capacity engagements. Within the first 14 days after the start you can end the engagement without giving reasons; work delivered up to that point is not invoiced. The exact terms are set out in your offer. That is why every engagement begins with a clear focus on quickly visible results.

Yes. Legacy-to-Cloud covers the structured migration of on-premise systems to the cloud: system analysis, a migration plan with milestones and rollback strategies, delivery, post-migration optimisation and knowledge transfer to your team. Step by step, without business interruption, with a fixed price per phase.