This policy sets out how and when Bits N Pixels delivers its services. Because we provide professional services rather than physical goods, "delivery" means the handover of working software, documentation and access — not shipment.

1. What we deliver

  • Software: deployed to an environment you control, with source code in a repository under your organisation.
  • Documentation: architecture notes, deployment instructions, administrator guidance and, where agreed, end-user material.
  • Access: credentials, infrastructure accounts and third-party service configurations set up in your name.
  • Training: role-based sessions where included in the Statement of Work.

2. Delivery timelines

Timelines are agreed in the Statement of Work and expressed as milestones rather than a single completion date. Indicative durations:

  • Discovery and scoping: 2–3 weeks from kick-off.
  • Design phase: 2–4 weeks depending on the number of screens and roles.
  • Build increments: a deployed, reviewable build every 2 weeks.
  • Focused applications: typically 8–12 weeks to production.
  • Multi-role platforms: typically 4–7 months to production.
  • Platform implementations: 4–16 weeks depending on modules and data migration.

These are indicative. Committed dates appear in the Statement of Work and are re-forecast at the end of each increment against measured progress, so that slippage is visible early rather than announced late.

3. Digital delivery only

All deliverables are provided electronically — through your repository, cloud environment, email or a secure file transfer. Nothing is dispatched physically, so no shipping charges, customs duties or delivery addresses apply.

4. Environments

  • Staging: available from the first build increment, so you can review work as it progresses.
  • Production: provisioned before launch, in your cloud account unless a managed hosting arrangement is agreed.

Where you provide the hosting environment, delivery depends on access being available when required. Delays in providing access shift dependent milestones.

5. Acceptance

  1. We notify you when a milestone is ready for review, with notes on what it covers.
  2. You have 7 business days to review and report issues against the agreed specification.
  3. We correct defects against the specification at no charge.
  4. Requests beyond the specification are handled as change requests.
  5. A milestone is deemed accepted after 7 business days without written comment, or earlier on written confirmation.

6. Conditions affecting delivery

Timelines assume:

  • a nominated decision-maker is available and empowered to approve;
  • feedback on submitted work is given within agreed review windows;
  • required content, data, credentials and third-party access are supplied when requested;
  • third-party services and APIs we depend on remain available and behave as documented;
  • scope does not change without a corresponding schedule adjustment.

Where any of these does not hold, we notify you promptly, state the effect on the schedule and propose a revised plan. We will not let a date slip silently.

7. Handover

On completion of an engagement you receive:

  • full source code with commit history;
  • deployment and infrastructure documentation;
  • administrator credentials and ownership of all third-party accounts;
  • a walkthrough session with your technical team;
  • a defect warranty period of 90 days.

8. Support after delivery

The 90-day warranty covers defects against the agreed specification. Beyond that, support is provided under a separate agreement covering monitoring, security patching, dependency updates and an agreed allocation of enhancement time, with defined response targets by severity.

9. Contact

Questions about delivery on a live engagement should go to your project lead. Otherwise:
Email: support@thebitsnpixels.net

This document is provided for transparency about how we operate. It is not legal advice, and it does not replace the terms of any signed agreement between us, which take precedence where they differ.