01
Proposals and scope
We define the intended outcome, deliverables, assumptions, timetable, and fees in a written proposal or statement of work. Work begins after the required approval, initial payment, and project inputs are received.
Requests outside the agreed scope are assessed separately. We will explain any effect on cost or timing and obtain approval before proceeding.
02
Invoices and payments
Payment amounts, milestones, methods, currencies, taxes, and due dates are stated in the applicable proposal or invoice. Unless the project agreement says otherwise, invoices are non-refundable once the related work has been performed.
Late payment may pause work and move delivery dates. The client is responsible for bank, transfer, or currency-conversion fees charged on its side of the transaction.
03
Feedback and approvals
Clear, consolidated feedback helps a project stay on schedule. Review windows and included revision rounds are defined per project. Delayed feedback, access, content, or approvals may require the timetable to be adjusted.
04
Pauses and cancellations
Either party may request a pause or cancellation in writing. Unless a signed agreement provides different terms, the client remains responsible for work completed, committed third-party costs, and approved expenses through the effective cancellation date.
If a project remains inactive because required client input is unavailable, we may reschedule it according to team availability before work resumes.
05
Delivery and acceptance
We test deliverables against the agreed scope before handover. Acceptance criteria and review periods are set in the project agreement. A new feature or a change in preference after approval is treated as new work rather than a defect.
06
Support and maintenance
Post-launch support, response targets, hosting, monitoring, backups, security updates, and ongoing maintenance are included only when stated in writing. Otherwise, follow-up work is quoted separately.
Third-party platforms, hosting providers, APIs, and software may change or become unavailable outside our control. We will recommend practical next steps when such a change affects active support work.
07
Open-source software
Open-source projects published by Atlantiqs are governed by the licence included with each repository. Community software is provided separately from paid client services and does not include support or service-level commitments unless agreed in writing.
08
Questions
Questions about this page can be sent to hello@atlantiqs.org.