Pricing and payment structure depend on the delivery variant — there are two distinct procedures depending on whether the software requires customisation.
Variant 1 — Custom / New Software (Standard Procedure)
This variant applies to bespoke development engagements where functional requirements are defined together with the client. The process is as follows: negotiations and detailed discussion of functional requirements; contract agreement with defined payment milestones; invoice issued by the contractor; partial or full payment as per contract terms; software deployment; client testing and formal acceptance. Variations to scope are priced and documented separately as they arise.
Variant 2 — Ready-Made Software (Simplified Procedure via Invoice Generator)
This variant applies to the delivery of existing, ready-made software products that require no customisation or only minimal configuration. The process is streamlined with zero correspondence between the company and the client: the client selects the desired software using the Invoice Generator; accepts the formal offer; self-generates an invoice through the platform; provides necessary deployment access credentials; and the software is deployed with a 5-business-day trial period. The client independently tests the software during the trial. If the client pays the invoice, trial restrictions are removed and full acceptance of the software is confirmed. If the client does not pay, access to the software is terminated after the trial period expires and the delivery is deemed not completed by mutual agreement.
Important: When using the Invoice Generator (simplified delivery procedure), payment recall procedures, as well as chargebacks, reversals,, and any similar banking or payment procedures are not applicable and are expressly waived by the client upon acceptance of the offer.