Trust & Transparency
Understand recurring costs, development scope, price stability and the agreed transition terms.
Scope, rights, service levels and commercial terms are agreed for your solution.
| Part | What it covers |
|---|---|
| Licence | The right to operate the solution on the ReApptor platform, including three minor features or improvements per month after active development. |
| Infrastructure and maintenance | Cloud hosting, database, file storage, backups and monitoring; keeps the solution operational. |
| SLA | Support hours, incident priorities and target response times at the chosen SLA level. |
| Planned development | Fixed-price modules or a subscription-based development fee. |
| Optional work | Additional modules or larger enhancements agreed separately. |
Yes. The agreed monthly infrastructure fee includes the cloud hosting, database, file storage, backups, monitoring and other infrastructure required for normal operation of the solution.
The infrastructure price is fixed for the agreed term. Normal variations in infrastructure usage do not create additional charges for the customer.
We propose a three-year term with fixed pricing: no unilateral price changes during the term. Any adjustment is possible only at renewal; it is limited to inflation and announced in advance.
The commercial structure is designed to be predictable and clearly defined:
The agreed terms define the commercial terms (licence, infrastructure/operations, SLA, IPR, exit/transition clauses). Each scope change or additional module is agreed via a separate Work Order with explicit scope, price, and timeline.
Prices and the licensing model are fixed for the agreed term. Any change has to be agreed anew (at renewal or in a new Work Order). There are no “automatic” price hikes or forced model switches mid-term.
New functionality beyond the agreed scope is not introduced implicitly; it is either covered by the “ongoing development” allowance in the licence (minor improvements) or agreed as a paid Work Order/development subscription.
TCO is calculated transparently as the sum of three parts:
For long-term cooperation, we can offer an instalment plan for a fixed-price, fixed-scope module, including 12 equal monthly payments over one year. This does not change the agreed scope or delivery milestones; it only smooths cash flow while keeping the total cost agreed in advance.
If you choose the subscription-based development model, pricing is based on a measurable unit economics approach: the monthly fee corresponds to an expected delivery capacity (feature throughput) derived from historical delivery data across our backlog, and it provides better unit price efficiency at higher monthly capacity levels. The pricing logic is reviewed at renewal (every 3 years), not continuously.
The start of each fee is agreed explicitly, so you see the whole payment schedule before committing.
Maintenance normally starts together with the project, because the project environment, infrastructure and operating services are already running during implementation.
Licence activation can follow a date, go-live or agreed module milestones.
Maintenance keeps the solution operational: environment upkeep, monitoring, security and compatibility updates, incident handling, bug fixing and service restoration, together with the agreed infrastructure and operational services.
The licence provides the right to operate the solution on the maintained ReApptor platform and includes three minor features or improvements per month after the active development phase.
The SLA defines support hours, incident priorities, communication and target response or restoration times.
A basic SLA can be included in the licence, or SLA services can be agreed separately.
Not without your written consent. Recurring charges — maintenance, the licence and the chosen SLA — are agreed in writing, so the monthly total is known in advance.
New modules, larger changes and extra development are scoped and agreed separately. They do not silently change the recurring fees.
Optional services, such as source code escrow or additional transition support, are agreed separately and only if you choose them.
Recurring fees are invoiced monthly in arrears, at the end of the calendar month.
Fees are charged per calendar month, and the agreed schedule shows which fees apply to each month.
When cooperation ends, recurring fees stop from the agreed final date.
Understand the commitment, notice rules and practical handover before signing.
Understand how reusable foundations, readable code and customer-specific development work together.
Tell us how your business works and which requirements matter to your decision. We can review the relevant scope, supporting evidence and agreed terms with your team.
Get a high-quality app built to match your needs. Fill in your contact details and needs, and let’s get started.
Choose a time for a video call with our team. Tell us briefly what you would like to discuss so we can prepare.
