Service Delivery Policy

1. Nature of Services

The services offered — including website development, web application development, full-stack development, frontend/backend development, e-commerce development, API development & integration, and website maintenance — are digital/software services. There is no physical product to ship, and physical shipping does not apply unless explicitly agreed otherwise in a specific Project Agreement.

2. Delivery Method

Deliverables are provided digitally through one or more of the following, as applicable to your project:

• A deployed, live website or web application accessible via a URL;
• Source code, shared via a Git repository (e.g., GitHub/GitLab) or a compressed file archive;
• Project documentation, where included in the scope;
• Access credentials for hosting, domain, or admin panels relevant to the project, where applicable;
• Other digital files or assets agreed as part of the project scope.

3. Project Timeline

Delivery timelines depend on the size and complexity of the project and are communicated in the quotation, proposal, or Project Agreement for that specific engagement, rather than a single fixed timeline for all projects.

4. Scope-Based, Milestone Delivery

For larger projects, deliverables may be provided in stages/milestones (for example: design/wireframe review, development preview, staging deployment, final production deployment) rather than as a single final delivery, so that you can review and approve progress along the way.

5. Client Dependencies

Timely delivery depends on receiving required inputs from you, such as content, brand assets, feedback, approvals, and access to any third-party accounts (domain, hosting, APIs) needed for the project. Delays in providing these inputs will correspondingly delay delivery.

6. Review & Approval Stages

Before final delivery, I typically share a staging/preview version of the work for your review. Please review deliverables promptly and share feedback within the timeframe agreed for your project so the project can progress to final handover without unnecessary delay.

7. Third-Party Dependencies

Where a project depends on third-party services (such as a hosting provider, domain registrar, payment gateway, or external API), final delivery may also depend on the availability, approval, or configuration of that third-party service, which is outside my direct control.

8. Final Handover & Acceptance

Once development and agreed revisions are complete and full payment has been received, I will deliver the final agreed deliverables (see Section 2) and consider the project delivered. If you identify a genuine defect against the agreed scope shortly after handover, please report it promptly so it can be addressed.

9. Physical Shipping

As a digital service, physical shipping generally does not apply. If a specific project genuinely requires a physical deliverable, this will be explicitly agreed in writing beforehand, along with any associated shipping terms.