# From brief to tickets

> Upload a statement of work and get a reviewed, dependency-mapped ticket backlog you can import into your tracker in one click.

_CommerceCopilot documentation · Getting started_

If you already have a brief, a statement of work, or a requirements document, the Business Analyst can turn it into a complete ticket backlog in minutes. You review the result before anything is created, so the run costs you nothing until you confirm.

## What you need

A project document in any of the supported formats: PDF, Word, plain text, Markdown, or images (PNG, JPG, WebP, GIF, SVG). Multiple files are fine; upload the SOW alongside design exports and any supporting material.

The quality of the output tracks the quality of the input. A brief that states goals, scope, constraints, timeline, and the target ecommerce platform gives the Business Analyst everything it needs; a two-line email gives it very little. It will not invent what is missing, so a thin brief produces open questions rather than made-up tickets. If the brief names or clearly implies a platform, the Business Analyst reads it and sets up the project for that platform; if it does not, the platform becomes one of the open questions instead of a silent assumption.

## Step 1: Upload the brief

From **Projects**, click **New Project** and keep the default **I have a brief** mode. Name the project and drop your files into the upload area.

![The New Project wizard with a brief file attached and the Analyze Requirements button below](/docs/new-project-brief.png)

If your designs are still in Figma rather than exported files, choose **Add to tickets later** under Designs: you can [connect Figma](/docs/figma) afterwards and the agents pick the designs up from there.

Click **Analyze Requirements**.

## Step 2: The dry run

The Business Analyst reads every document and drafts the backlog. This takes a few minutes, and the page streams progress as tickets take shape.

This phase is a **dry run**: nothing has been created in your workspace or your ticket tracker yet, and no credits have been spent. You are looking at a preview.

![The dry-run review page showing drafted tickets and a dependency diagram](/docs/dry-run-review.png)

For a typical agency SOW, expect a backlog of 20 to 40 tickets, each with:

- Business requirements pulled from your brief, with nothing invented
- User stories in a consistent, developer-ready format
- Dependencies mapped across the whole backlog, shown as a live diagram
- Open questions flagged wherever the brief was ambiguous

## Step 3: Review and confirm

Read through the drafted tickets and the dependency graph. The header shows the ticket count and the estimated credit cost of the full delivery workflow before you commit, and the Business Analyst's scoping decisions are collected in a review panel so you can see what it chose and why.

Not happy with the result? Click **Redo** to run the analysis again, or adjust the brief and start over. Nothing is spent until you confirm.

When you confirm, CommerceCopilot creates the project with the full backlog. If [Notion](/docs/notion) or [Jira](/docs/jira) is connected and bound to the project, the tickets are exported to your tracker, dependencies intact.

## After the import

The new project appears on your **Projects** page with its ticket board populated.

![The Projects page listing projects with phase badges](/docs/projects-list.png)

From here you can:

- Bind the project to a repository so the Developer and Tech Lead agents can work the backlog. See [GitHub](/docs/github).
- Open the project's discovery workspace to keep capturing changes in scope. Brief-first projects get the same living discovery model as [discovery-first projects](/docs/your-first-discovery-project).
- Answer the open questions the Business Analyst raised. Every answer sharpens the backlog.

> **Tip:** the dry run itself is free, and the review bar always shows the exact credit cost before you commit. Running an analysis on every inbound SOW, even ones you might not win, is a cheap way to scope proposals.

## Next steps

- [Connect Notion](/docs/notion) or [Jira](/docs/jira) so backlogs land in your tracker
- [Connect GitHub](/docs/github) to unlock automated delivery on the backlog

---
Canonical page: https://www.commercecopilot.ai/fr/docs/your-first-brief-to-ticket-project