Pricing
Two companies with the same headcount are rolled out differently: one needs nothing but sales and production, the other needs crews, a warehouse and two legal entities. So we look at the process first and name a figure second.
Example: a workshop with its own installation team
Estimate
The core is always on: nothing else works without it. Beyond that you add only the modules you will actually use.
A starting point for three typical companies. From there tick and untick whatever you like — the figure recalculates.
A second legal entity means separate contracts, its own bot and its own reporting, so the configuration work nearly doubles.
From spreadsheets it is quick. From an old system it takes longer: we reconcile what does not match, and why.
The first ten are included in support. Headcount barely affects the configuration — only the training and the support.
This estimate is preliminary: it shows the order of magnitude and the structure of the price. We name the exact figure after a short conversation — and it usually goes down rather than up, because some modules turn out to be unnecessary.
What it is made of
01
One-off work. We do not just “switch on a box” — we line the system up with the way an order really moves through your company.
02
It depends on the state the data is in today. The longest part is not the spreadsheets but agreeing on what counts as a client and what counts as an order.
03
Monthly. The first months after launch are the heaviest: people are getting used to it and asking questions.
What moves the figure
So you can gauge the order of magnitude before we even talk.
One legal entity and one process is the base case. Two lines with different contracts, bots and reporting is almost two configured systems in one.
significantlyIf there are twelve stages and each has its own owners and rates, the configuration takes longer than for a company that resells finished goods.
significantlyA tidy spreadsheet migrates in days. Five notebooks, three files and a manager’s memory is a job of its own, and it is fairer to price it separately.
significantlyIt matters less than you would think: the system is built for a department, not for a single operator. It affects the training, not the configuration.
moderatelyA separate stage of the rollout. In the first conversation we agree which reference books and documents move in each direction, and build that into the timeline.
A separate stageHow a rollout runs
You describe how an order moves today. We show the system on that example and say what we will do.
Stages, roles, reference books and metrics. You are looking at your own system, not at a demo.
The data moves across and people go through the in-system guide for their own role.
The first month is the densest: people’s questions, small fixes, checking the first reports.
The timeline depends on how much data moves. We will name it after the first conversation, and not before.
The questions people ask first
The example above and the calculator show the order of magnitude. We name the exact figure after half an hour of conversation: without understanding the process, a number only grows later.
Yes, and that is what most do: sales first, then production. Modules are switched on gradually and the data is never migrated twice.
Yours. CSV export is in the sections, and it is not “an extra charge”.
Stages, roles and reference books are changed in the settings. Nobody has to rewrite the system for that.
If your processes do not fit the ready-made modules — the studio builds an ERP for one specific company.