AEITCH

Delivery Policy

Delivery Policy

Effective Date: April 2026

This Delivery Policy governs how AEITCH (“Company,” “we,” “us,” or “our”) provides digital services, including but not limited to Product Development, Full-stack Engineering, DevOps Infrastructure, and AI Integration, to our clients.

1. Digital Service Nature

As AEITCH provides intangible, professional digital services, “delivery” does not refer to physical shipping. Delivery is defined as the successful transfer of code, deployment of infrastructure, or the granting of access to completed digital assets.

2. Delivery Methodology

We utilize a milestone-based delivery framework to ensure project alignment:

Phase 1: Onboarding. Delivery begins with a kick-off meeting and the establishment of shared project management tools.

Phase 2: Technical Staging. Software and AI features are delivered to a private staging environment for client review and User Acceptance Testing (UAT).

Phase 3: Production Deployment. For DevOps and Cloud services, delivery is confirmed once the configuration is live in the client’s production environment (e.g., Google Cloud Platform or AWS).

Phase 4: Final Handover. The final delivery of the project includes the transfer of GitHub repository ownership, administrative credentials, and technical documentation.

3. Timelines & Schedules

Individual delivery timelines are outlined in your specific Statement of Work (SOW). AEITCH commits to meeting all internal deadlines; however, delivery dates are estimates and may be influenced by:

  • The speed of client-provided feedback or data.
  • Provision of necessary third-party API access or cloud permissions.
  • Approved changes to the project scope.

4. Proof of Delivery

Delivery is considered legally complete when:

  • The client signs off on a milestone via our project management portal.
  • The code is merged into the production branch of the client’s repository.
  • The final handover documentation is sent via email.