COMMERCIAL TERMS SUMMARY

Clear boundaries before booking.

This page is a plain-language summary. The buyer-specific written proposal and signed agreement control each engagement. Submitting an intake does not create a booking or contract.

Offers and payment

For a Serbian-resident buyer, the CI pilot is invoiced and settled in RSD under the exchange-rate source and date stated in the written proposal. For a non-resident buyer, the individualized proposal states the lawful invoice and settlement currency and any bank charges. SaveX does not add Serbian VAT while lawfully outside VAT registration. The provider's current Serbian VAT-register status and turnover are checked before invoicing and whenever circumstances change. Buyer-country tax, reverse-charge, place-of-supply treatment and invoice requirements are checked for the specific buyer and stated in the individualized proposal where applicable. Payment is by bank transfer to the provider account shown on the invoice.

Paid third-party services are excluded unless the proposal states otherwise. Payment instructions are supplied only through the approved contracting and invoice process.

Scope and change control

Every engagement names the project or journey, deliverables, exclusions, acceptance criteria and accountable reviewer. UI work also names screens and states; the CI pilot names the GitLab project, one agreed CI change, diagnostic evidence and rollback. Work outside that boundary begins only after a written change request confirms the schedule and price impact.

Backend, API, database, content production, translation, paid tools, protected-branch merge and production deployment are excluded unless separately approved in writing.

Review, correction and acceptance

The Sprint includes one consolidated correction round for documented deviations from the agreed acceptance criteria. New preferences or requirements are change requests, not corrections.

Acceptance occurs when the agreed implementation and evidence are delivered, blocking conditions are documented, and the included correction round is completed or waived. The exact acceptance terms are stated in the proposal. The CI pilot's second installment is due on delivery of its final evidence report, as stated above.

Repository, merge and production control

Implementation is performed in an isolated branch or worktree. The client or agency keeps authority over repository access, merge, release and production deployment. SaveX does not merge protected branches or deploy production without separate explicit approval.

Ownership, confidentiality and data

The signed agreement defines code ownership, licensing, confidentiality and any subcontracting terms. Initial fit review requires only public context and must not include passwords, API keys, private keys, payment data, production datasets or unnecessary personal data.

Warranty and support

Any warranty or post-acceptance support window must be stated in the approved proposal. SaveX does not promise unlimited support, guaranteed conversion, revenue outcomes or defect-free behaviour outside the agreed environment and scope.

Cancellation and scheduling

A delivery slot is reserved under the service-specific payment milestone stated in the accepted proposal. The Evidence Audit is booked after full payment; the UI Upgrade Sprint after its booking installment; the CI pilot starts after its first installment clears; the retainer is prepaid by month. Cancellation, rescheduling and refund terms must be stated in the buyer-specific proposal before acceptance or payment.

Contact

Commercial and contracting questions: hello@savex.rs. Do not send credentials or confidential repository material by email.