One system to run all your companies — instead of one program per company

Yes. Your group gets one instance in which all companies are run and administered in one place — one login, one view, one administration. What does not happen is a merging: the separation between your companies is a function of the system, and you steer it per data type. Number ranges, letterhead and invoice appearance stay individual per company; what runs across companies is configured, not guessed. And because your group has its own instance rather than sitting in a system shared by all customers, this structure can be built at all — in standardised multi-tenant operation the room for it is typically far narrower.

No. For us the group is one engagement: one contract, one invoice, not one per company and not per head. The number of your employees does not change the price, site accounts are included, and hiring does not make the software more expensive — with per-user billing that is exactly what multiplies across all the companies. Who in the group receives the invoice is flexible: one of your companies can pay, and how you split or recharge the costs internally is your decision. Concrete terms are fixed in your offer — we deliberately publish no figures on public pages.

The rights are separated, and both halves are clearly named. The product core stays licensed and is not transferred: perpetual licence, perpetual right of use, your own instance, and source code included when you self-host — for inspection and further development for your businesses, no redistribution. For everything we build exclusively for your group, the two-way rule applies: what we build for everyone stays our product. What we build only for you belongs to you. If an extension later turns out to be generally useful, it goes into the product and comes back to you with the next update.

That depends on why you want it — and the question is worth asking, because the right answer is completely different depending on the reason. If it is about security in case we are no longer around one day, self-operation is the right answer: if you run it yourself — on your server, with your IT provider or offline — we hand you the source code of the delivered version. Under krafteq operation the source stays with us; you can switch to self-operation at any time, and we then hand over images, documentation and source code. If you want to develop it yourself, the same arrangement applies: for inspection and further development for your own businesses, no redistribution. And if it is about full ownership, the route is a full custom development, which is considerably more expensive. Both are possible; both together at the product price are not.

No, and we would rather say so than leave it open: we have no group in operation yet, and we are not inventing a reference for it. What does exist is twofold. First, the product itself — the day-to-day operation of a single company is reflected and in use, which you can check on a test instance of your own before anything is discussed. Second, a clear decision on how we serve a group: one instance, company separation in the system, one engagement. That decision was not made at a desk — the case reaches us from the market, with requirements already written out. Where exactly we stand, we will tell you openly in the first call. If you want software that ten groups are already working with, we are the wrong vendor, and that is a fair answer.

Then a company is added in the system — no second program, no second contract, no new project. That is exactly what the design is for: the structure is laid out from the start for an open number of companies, not for the number you run today. We know that such groups found and acquire further entities. If the group as a whole grows well beyond the product's size range, we will talk openly about whether a standalone project is the better route.

Only as far as you define. The separation is the starting point and stays that way — it is built into the system, not a setting in a menu, and it is enforced on the server. Whatever becomes visible across companies is explicitly released for that, and you decide who may see it. That is not only a matter of convenience: your companies are legally independent, and a shared customer record across independent entities requires an agreement between them. We set that up as part of the work — economic connection alone is not sufficient. Within a single company, the product's own scoping applies as well: the office sees the full scope, the site only what it needs for the day — no prices and no customer data, enforced on the server rather than merely hidden in the menu.

No. Every company is pre-configured in the system for its trade and arrives with that trade's terms, units and templates — electrical alongside plumbing, roofing alongside carpentry. Which trades the product covers today is shown in the overview trades software without a subscription. For the cross-company part, a mix of trades is not an obstacle but a question of description: which key figure is meant to be comparable across different trades? We clarify that in the analysis, before anything is built.

No. Group managements can generally state their requirements well — which figure is missing, which maintenance runs twice, which data the companies should share and which not — but nobody has to turn that into a technical description. That is our work and the content of the paid analysis. And because the day-to-day operation of each company already exists as a standard product, we are not talking about a whole system but only about the group structure inside it.

That is in fact the recommended route. One company goes live, operations run there and get fine-tuned, and the second follows in the same system with what was learned. The group part is then created on a running system rather than on assumptions. That spreads the risk and keeps the decision small: you can stop after every stage.

We clarify data migration per company in the first call and describe it in the analysis — what can be taken over depends on what the previous program hands out. For the future: data export at any time, the right of use is perpetual, and if you want to take over operations yourself or move to your IT provider, your instance keeps running.