> For the complete documentation index, see [llms.txt](https://help.blings.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blings.io/guides/project-lifecycle.md).

# Project Lifecycle

An enterprise Blings project works best when every team understands the same lifecycle. Creative, data, integration, QA, launch, analytics, and optimization all depend on each other.

Use this guide as the high-level flow for a new project or a major project update.

## Lifecycle Overview

{% stepper %}
{% step %}

### Define the Outcome

Agree on the campaign goal, audience, delivery channel, primary CTA, conversion event, and required viewer data. This keeps creative, data, and analytics decisions aligned.
{% endstep %}

{% step %}

### Design the Viewer Journey

Plan the scenes, decision points, interactive choices, form fields, and fallback paths. Confirm which parts should be personalized, editable, or measured.
{% endstep %}

{% step %}

### Build the Creative Template

Designers build or update the motion work in After Effects and Studio. Studio turns the experience into scenes, layers, timelines, connectors, data bindings, and flow behavior.
{% endstep %}

{% step %}

### Define the Data Model

Create the project fields, types, defaults, live controls, catalog groups, and any form-submission fields needed for the viewer journey.
{% endstep %}

{% step %}

### Connect Dynamic and Interactive Behavior

Use Studio connectors to bind text, media, color, visibility, links, branching, inputs, form submission, and other runtime behavior to data or user actions.
{% endstep %}

{% step %}

### Validate With Representative Data

Use Studio preview and Platform simulation to test normal values, edge cases, missing values, alternate branches, mobile behavior, and the selected lineup.
{% endstep %}

{% step %}

### Prepare Delivery

Configure the landing page, CRM integration, spreadsheet workflow, SDK embed, dynamic thumbnail, or custom code path that will deliver the project.
{% endstep %}

{% step %}

### Launch and Monitor

Review player settings, publish the approved state, monitor plays and engagement, confirm conversion tracking, and watch for unexpected data or routing issues.
{% endstep %}

{% step %}

### Improve the Experience

Use analytics, viewer behavior, form submissions, and optimization results to refine copy, scenes, routing, CTAs, variants, and live controls.
{% endstep %}
{% endstepper %}

## Role Handoffs

| Handoff              | What must be clear                                                                                         |
| -------------------- | ---------------------------------------------------------------------------------------------------------- |
| Strategy to creative | Goal, audience, CTA, scenes, personalization points, interaction points, and success metric.               |
| Creative to data     | Field names, field types, fallback values, editable values, catalog needs, and form fields.                |
| Data to integration  | Payload format, CRM tokens, SDK data object, URL parameters, spreadsheet columns, and security rules.      |
| Integration to QA    | Test profiles, delivery URLs, thumbnails, player settings, tracking expectations, and channel context.     |
| QA to launch         | Approved lineup, published state, known limits, fallback behavior, analytics readiness, and rollback path. |

{% content-ref url="/pages/G0kw7nD1sfkCJSvHYxKU" %}
[Data Fundamentals](/guides/data-fundamentals.md)
{% endcontent-ref %}

{% content-ref url="/pages/2BUqz2lBAdvyEBKDmcl1" %}
[Platform and Studio Workflow](/apps/apps-workflow.md)
{% endcontent-ref %}