The price of a custom system cannot be put in a table — it follows from the scope.
To be readable at all, it first has to be clear what the price is for. And that is rarely a licence.
The cost you pay consists of analysis, design, development, customisation, deployment and handover into operation.
The source code and the data are yours from the first moment.
We go through the process the system is to cover with you — what is needed, what can be left out, and where the exceptions are that the operation rests on.
The analysis produces a design: which registers, which fields, which permissions, and how the steps follow one another. The scope and the price are derived from it.
Programming hours: screens, logic, integrations with surrounding systems, testing.
Adapting the platform to your processes — your code lists, procedures, reports and exceptions.
Going live on your infrastructure or on ours, including migration of existing data.
We hand over the system and its documentation, and train the people who will work in it.
The greatest value our platform adds is the ability to shape the environment so that it matches, as closely as possible, the processes it is there to handle.
Your data, your processes, your procedures = your system.
Customisation is badly underrated when new systems are introduced. Yet it is a natural process — not only at the start, when the solution is being designed, but also in everyday use afterwards.
In every field, working processes develop and change. Fitting a company's processes into fixed rails effectively stops them moving any further.
The cost of implementation can be estimated fairly precisely in advance. The scope and depth of customisation can, however, shift some of the parameters considerably, so for a quote the brief always has to be defined precisely, together.
Fixed costs cover the initial framework set-up, database initialisation, establishing the user structure, baseline security and starting a test instance. All of these have to happen on every project, whatever its scope.
Expertise
Most development companies estimate the work from the number of hours they think the coding itself will take. From our own proven experience, we know how much depends on the right architectural design of the whole solution. We have specialists who know what our platform makes possible, and who also have wide experience of bringing very different working processes into digital form.
Without proper analysis and an understanding of your needs, the right solution design cannot be produced. Working together on each design is therefore essential.
Any information system can be judged from two angles. The first is the saving that can be calculated directly, against the state \u201Cbefore deployment\u201D. The second is harder, because it covers the \u201Csoft benefits\u201D: owning the source code, the ability to keep customising, and through that a continuing rise in efficiency and performance.
Process saving
Comes from higher efficiency, automation, control mechanisms and central management.
Cost of the process
The total cost of the whole process (wages, workplace, overheads).
Length of payback
Investment in the new system / (Process saving × Cost of the process).
Two registers that a single spreadsheet and a single person look after today.
2 registers · 30 fields · 1 role · 1 integration
One process that several people run in a spreadsheet today.
10 registers · 120 fields · 2 roles · 1 integration
A process spanning several departments, with integrations to surrounding systems.
20 registers · 300 fields · 4 roles · 3 integrations
Running an entire operation, including planning and evaluation.
35 registers · 600 fields · 6 roles · 5 integrations
You pay only after go-live
Nothing is paid during development. We agree the total at the start, but the first instalment comes only once the system is running in production.
Paid off while in use
Typically 24 months in fixed monthly instalments. It is therefore paid off out of the benefit the system brings in the meantime.
What is built is yours
The software is yours, not rented. Once it is paid off, only the cost of support remains.
The model is based on an hourly rate of CZK 1,100 and an average gross wage of CZK 51,000. The payback compares the total implementation cost with the time the application gives back to the people who work in it. For a specific brief it is calculated from its actual scope.
Try entering parameters that match the brief you have in mind, and see how easily a payback estimate can be argued.
Recalculated on every change.
This is a model, not an offer. It is based on an hourly rate of CZK 1,100and an average gross wage of CZK 51,000. The estimate of hours worked comes from the scope you entered — for a specific brief we will refine it against the real processes.
support and operation for a single instance
CZK 4,200per month
Request a quotesupport for multi-instance solutions
CZK 7,000per month
Request a quoteSend us the details of your project and we will prepare a preliminary quote.