A price range without a process or scope would be misleading. We can explain exactly which choices determine the price, how Tixer spreads payment and which information is needed for a sound estimate.
The building blocks of an estimate
Custom software has no meaningful catalogue price. Two applications with the same number of screens can differ greatly in complexity because of roles, exceptions, data migration and integrations.
A focused first version solves the most important problem completely without building every possible extension immediately. This reduces uncertainty and makes feedback from real use valuable sooner.
Extending later is not a lack of preparation. It is often the most sensible way to base decisions on actual use.
Tixer works with one fixed company-wide subscription, not per-user licences. You pay 20% of the annual price at the start and 50% when the first version launches. The fixed subscription then begins.
The exact price, scope, term and conditions are set out in the proposal. Large new modules are quoted separately; small improvements within the agreed scope are part of the model.
The annual price is twelve times the agreed monthly amount. The start payment equals 20% of that annual price. At launch, another 50% of the annual price is due and the monthly subscription begins. The start and launch payments are the joint investment in development and are not presented as future subscription months.
At launch, we agree on an initial fixed period. After that, the subscription continues monthly and you can stop at any time. The monthly fee remains predictable and there are no per-user licence costs.
A first conversation becomes more concrete when you can define one process. Bring information about who uses it, where the data lives, which exceptions occur and which systems need to connect.
This allows us to define what the first version must solve, which technical uncertainties need investigation and which parts can follow later. We then provide a proposal covering price, scope, payment stages and the initial term.
Include hosting, maintenance, security updates, support, per-user licences and future adaptations in the comparison. A low initial price can become expensive when internal manual work or separate external maintenance hours remain necessary.
A reliable price follows an initial analysis of the process, scope, integrations and risks. The agreements are then set out in a proposal.
A customer portal, internal workflow and system integration can differ greatly in technical complexity even when they have the same number of screens. We therefore attach a price only to a defined first version, so you do not compare an amount that later proves irrelevant to your request.
No. Tixer uses one fixed company-wide price within the agreed conditions.
Large new modules are scoped and quoted separately. Small improvements within the agreed scope are included.
Yes. After the initial fixed period, the subscription continues monthly and you can stop at any time.
Describe the problem, users and systems involved. This lets a first conversation focus quickly on the relevant cost factors.
