Project Delivery

Work begins once scope, commercial terms and required kickoff inputs are in place. Project timelines depend on scope, required inputs, approvals and client feedback.

1. 01 Discovery

2. 02 Scope

3. 03 Production

4. 04 Review

5. 05 Approval

6. 06 Delivery

7. 07 Handover

Scope is confirmed in writing — typically a proposal, statement of work, or MSA schedule. That writing is the reference for what will be produced.

Production depends on timely access to brand assets, copy, accounts, feedback and decision-makers. Missing inputs pause or stretch the timeline.

AIONIQ produces the work described in scope. Method varies by discipline. Internal tools, including AI assistance, follow the AI Policy and the engagement terms.

Work is shared at agreed review points. Reviews are for direction, accuracy and fitness against the brief.

Consolidated feedback from a nominated client owner is faster and clearer than scattered comments. We will say when feedback is blocking the next stage.

Revision rounds are defined per project. This page does not set a studio-wide revision count.

Written or otherwise recorded approval moves a stage to delivery. Unapproved work is not treated as final.

Final files, repositories, or live properties are delivered as specified in scope. Third-party accounts remain the client’s unless we have agreed to operate them.

Handover may include credentials, documentation or a walkthrough, when those are in scope.

Ongoing support, retainers or hosting are separate from project delivery unless the agreement includes them. Duration is not implied by this page.

Third-party platforms, printers, app stores, legal reviews and client availability can delay delivery. We will flag dependencies we can see; we cannot control every external queue.

New requirements are scoped as a change. See Master Services Agreement and Refund & Cancellation.