- A clear methodology from inception to delivery | Last updated: July 14, 2026
Contracting & Execution Guide
How we plan, execute, and deliver our projects with precision and transparency, maintaining full commitment to timelines and the highest quality standards.
Section 01
Cost & Payment Mechanism
In this section, we clarify how the Agile methodology ensures full financial and technical flexibility for the client. Instead of paying large upfront amounts, payments proceed in parallel with the delivery of functional software increments (Sprints)
Milestone-Based Payment Mechanism (Agile Milestones): We adopt a flexible payment model where financial installments align with the delivery of tested, fully functional software phases (Sprint Delivery). This guarantees you never pay for any feature before verifying its technical quality.
Initial Scope-Based Costing: The estimated project cost is determined based on an initial requirements study, dividing technical execution into consecutive, manageable development cycles known as Sprints.
Commitment to Execution: An agreed-upon initial deposit is paid prior to starting the first development cycle to secure technical team allocation, necessary software resources, and staging server environments.
Flexible Scope Adjustments (Backlog Management): The Agile framework allows you to adjust priorities, add new features, or pivot development direction mid-project. These enhancements are scheduled into upcoming Sprints and priced separately and transparently based on the required engineering effort.
Section 02
& Mutual Commitments Communication Framework
This section outlines the daily and weekly operational engagement during the development phase. It emphasizes the importance of prompt client feedback for cycle success, as well as the official channels used to document technical decisions.
Responsiveness & Testing: The flexibility of the Agile methodology requires prompt responsiveness. The client commits to reviewing and testing delivered features and providing feedback within a specified timeframe (e.g., 3 to 5 business days) to prevent delays in kicking off subsequent development cycles.
Communication in an Agile Environment: We utilize clear and direct communication channels (such as daily standups), along with regular periodic meetings (such as sprint reviews) to keep you updated on software progress and address immediate feedback.
Official Channels & Formal Sign-offs: Despite the flexibility of daily discussions, formal sign-offs on scope of work or pivotal decisions affecting project infrastructure must be documented in writing via official email to protect the rights of both parties.
Request Management & Documentation: All change requests, feedback, or discovered software bugs must be submitted through our designated task management system. This system serves as the single source of truth for prioritizing and scheduling tasks for the team.
Section 03
Intellectual Property Rights & Code Ownership
This section aims to reassure the client that their investment is fully protected, while safeguarding the company’s software rights regarding the use of its proprietary libraries and core framework tools.
Full Ownership Upon Final Delivery: Upon project completion and settlement of all agreed financial payments, full IP rights, system source code, and UI/UX designs are fully and permanently transferred to you.
Progressive Transfer of Ownership: Ownership of features and custom Source Code transfers to you gradually and automatically upon completion, delivery, and financial approval of each development cycle (Sprint) for its corresponding payment.
Ozone’s Proprietary Assets & Components: If pre-developed Ozone software components or frameworks are used to enhance system efficiency, the client is granted a perpetual, non-exclusive, irrevocable license to run, operate, and modify their project freely with no additional fees.
Open-Source Libraries & Auxiliary Tools: The developer reserves the right to utilize open-source libraries or licensed components to accelerate the build process. These parts remain subject to their original licenses and do not affect your absolute ownership of the core custom system and database.
Section 04
Core Assumptions & Third-Party Costs
The success and development of the project rely on a set of technical and financial parameters to which both parties adhere, ensuring system continuity and stability:
Independence of Third-Party Services & Subscriptions: All external platforms and services required to run the system are funded and legally managed directly by the client, and are not included in the software development value agreed upon with Ozone.
Data & Requirements Dependencies: Project timeline success and sprint alignment depend on the client providing accurate data, information, and access credentials in a timely manner. Any delay in supplying the development team with these requirements will automatically defer tasks to subsequent sprints and delay final delivery.
Payment Gateways: Registration fees, transaction fees, and commission percentages charged by payment gateways (such as Stripe, Tap, Checkout).
Cloud Hosting & Domain: Cloud hosting services (such as AWS, Google Cloud, Azure) and domain name registration fees.
Paid Data Integration APIs: External API integration costs, including Google Maps API, AI service subscriptions, or third-party data platforms.
SMS & Verification Gateways (SMS/OTP): Outbound SMS verification and security authentication service costs (such as Twilio, Firebase Auth).
Store Licenses & Developer Accounts: The client is responsible for creating and paying developer account fees on app stores: Apple Developer Account ($99/year) and Google Play Console ($25 one-time fee), while granting our team deployment access to publish and launch the applications.
Technical Scope Limits: Project software development costs do not include services outside the technical programming and UI/UX design scope (such as copywriting, translation, digital marketing campaigns, or advanced product data entry), unless explicitly stated in an independent agreement.
Section 05
Changes & Modifications
The Agile methodology is characterized by flexibility and adaptability to your evolving requirements during the development process. Modifications are governed by the following guidelines:
Major Modifications & Redesigns: If requested modifications are substantial and require rebuilding previously approved software modules or altering core database architecture, they will be treated as a "New Scope of Work," with their cost and timeline calculated independently.
Managing Modifications via Task Backlog: The client may request modifications or add new features at any time. These requests are logged in the task backlog, discussed thoroughly with the project manager for scheduling, and prioritized within upcoming development sprints.
Adherence to Current Sprint Scope: Once a development cycle starts and its tasks are finalized, no modifications or additions can be introduced during the active sprint. This ensures the technical team remains focused on on-time delivery; any new requests are automatically deferred to subsequent sprints.
Post-Launch Modifications & Final Handover: Ozone is committed to resolving software bugs occurring in developed systems during the agreed technical support period. Requests for new features or technical updates following final handover are subject to an annual maintenance contract or scoped as an independent project.
Section 06
General Terms & Dispute Resolution
These legal clauses govern the overall relationship, ensuring a transparent and professional workflow for all parties:
Force Majeure & Emergency Circumstances: Neither party shall be held liable for delays or failures in executing software or financial obligations resulting from circumstances beyond reasonable control (such as natural disasters, wars, internet and international telecommunication outages, or sudden security policy updates by payment gateways or global app stores).
Title: Confidentiality & Non-Disclosure: Both parties commit to maintaining the strict confidentiality of technical, commercial, database, and project source code information. Neither party has the right to disclose or share such information with any third party without prior written consent.
Amicable Dispute Resolution: In the event of any disagreement regarding software deliverables or scope of work, both parties commit to making earnest efforts to resolve the issue amicably via direct negotiations between Ozone’s technical management and the client’s representative within a period not exceeding fifteen (15) days from the notification date.
Governing Law & Jurisdiction: Should an amicable resolution prove unreachable, this agreement and executed contracts shall be governed by the applicable laws and regulations of Ozone’s legal headquarters, and competent courts within that jurisdiction shall hold exclusive authority to hear and settle all disputes.
Section 07
General Terms
The company bears no liability for any improper or incorrect system usage following handover.
Project outcomes depend on multiple external factors, including market conditions, management, and usage.
Both parties commit to professional conduct and mutual respect throughout all stages of collaboration.
The company reserves the right to halt work in the event of a breach of any of these terms.
Section 08
Law Applicable
These Terms shall be governed by and construed in accordance with the laws of the United Arab Emirates, and the competent courts of the Emirate of Dubai shall have jurisdiction over any dispute that may arise therefrom.
Important Note
Please read these terms carefully before starting any project to ensure clear expectations and achieve the best results. Signing the project contract constitutes your acknowledgment of having read and agreed to these terms.
Have a Question?
Our team is ready to answer all your inquiries and help you start your project with confidence.