Delivery Policy

Introduction

This Delivery Policy explains how Tekbyt manages project timelines, deliverables, approvals, and final handover of services including web design, web development, product design, full-stack development, MVP development, and branding services.

By engaging with our services, you agree to the terms outlined below.

1. Project Initiation

Work on any project begins only after:

• Receipt of initial deposit or agreed payment
• Confirmation of project scope
• Submission of required project materials by the client

Delays in providing necessary information may affect the project timeline.

2. Estimated Timelines

All delivery timelines provided are estimates based on the agreed scope and timely client cooperation.

Timelines may change due to:

• Scope modifications
• Delayed feedback or approvals
• Addition of new requirements
• Technical dependencies or third-party delays

3. Project Phases

Projects are typically delivered in structured phases such as:

• Discovery & Research
• Wireframing / Planning
• UI/UX Design
• Development
• Testing & Quality Assurance
• Final Deployment / Handover

Each phase may require client review and approval before proceeding.

4. Client Feedback & Approvals

Timely feedback is essential for on-time delivery.

• Feedback must be provided within agreed timelines
• Delayed feedback may pause project progress
• Approved deliverables are considered final for that phase

Once a phase is approved, reverting changes may require additional cost and time.

5. Revisions

Revisions are limited to the scope defined in the project agreement.

• Minor revisions are included within scope
• Major changes or new features are treated as additional work
• Excessive revision requests may impact delivery timelines

6. Deliverables

Final deliverables may include:

• Website or application source code
• UI/UX design files (Figma or equivalent)
• Branding assets (logos, guidelines, design systems)
• Documentation where applicable

Deliverables are shared via secure links, repositories, or agreed platforms.

7. Final Delivery & Handover

A project is considered delivered when:

• Final files are shared with the client
• Deployment or launch is completed (if included in scope)
• Client provides written or implicit approval (including live usage)

After final delivery, any additional changes will be treated as new work.