Delivery Policy

This Delivery Policy explains how, when, and in what form MCLBPO delivers digital products and services. Our deliverables are digital — no physical goods are shipped.

1. Nature of deliverables

MCLBPO delivers digital products and services only — source code, compiled applications, design files, documentation, deployed environments and ongoing operational support. No physical goods are shipped and no shipping fees apply.

2. Delivery timelines

Every engagement defines its delivery timeline in the signed Statement of Work (SOW). Typical durations for our packages are:

• Starter Website Package — 2 to 3 weeks from kickoff.
• Business Growth Package — 4 to 6 weeks from kickoff.
• Custom Software / Enterprise Package — 8 to 16 weeks, delivered in 2-week milestone increments.
• AI Workflow projects — 3 to 8 weeks depending on scope.
• Maintenance & retainers — continuous, with monthly reporting.

Timelines assume reasonable Client responsiveness (review feedback returned within 3 business days, access to required accounts provided promptly). Delays caused by the Client may extend the timeline proportionally.

3. Method of delivery

Depending on the engagement, deliverables are provided through one or more of the following channels:

• Source code committed to a Git repository the Client controls (GitHub, GitLab, Bitbucket).
• Deployed applications on the Client's cloud account (AWS, Vercel, Cloudflare, Google Cloud) or on a managed environment we provide.
• Design files via Figma with full editing rights transferred to the Client.
• Documentation and runbooks in PDF, Markdown or a shared workspace (Notion, Confluence).
• Credentials and secrets exchanged through encrypted vaults (1Password, Bitwarden) — never in plain email.

4. Kickoff and milestones

1. Kickoff is scheduled within 5 business days of deposit clearance.
2. Milestone deliverables are released as soon as they are completed and tested internally.
3. Each milestone enters a Client review window defined in the SOW (typically 5 business days).
4. Acceptance is confirmed in writing. Silence beyond the review window is treated as acceptance.

5. Handover

At project completion, we provide:

• Full source code and design files.
• Deployment, environment and credential documentation.
• A handover session (60–90 minutes) with the Client team.
• 30 days of complimentary defect-fix support (per our Terms).

6. Delays and force majeure

If a delivery date is at risk, we will notify the Client at least 5 business days in advance and propose a revised schedule. Force majeure events (as defined in our Terms) may extend timelines without penalty.

7. Acceptance and post-delivery

Once a deliverable is accepted, it transitions out of active development. Further changes are scoped as new work or covered by an active maintenance retainer.

8. Contact

For delivery-related questions, contact support@mclbpo.com. Response within one business day.