Skip to main content

​
The result you want

Give each client and offer a clear home without creating a new Project for every task.
  • Keep stable brand and offer context in Products.
  • Use Projects for repeatable workflows or campaigns.
  • Start one focused Chat for each deliverable.

​
Practical use cases

Prevent client context from mixing

Keep each client’s stable voice, offer facts and customer context in the correct Product.

Repeat one process

Use one ad or advertorial Project across offers when its files and short instructions apply to every execution.

Switch offers without rebuilding

Keep one Product per offer, then mention the relevant Product in each Chat inside the reusable Project.

Keep a launch together

Create a dedicated Project when a promotion needs its own brief, files, deadlines and decision history.

Reuse a workflow across clients

Keep client-specific context out of the shared Project. Add the correct Product and evidence in each focused Chat.

Make handoffs predictable

Change a Project from Personal to Team, then verify the required Product and Chat access separately.

​
Use the default hierarchy

Use each layer for one kind of context:
Keep Project instructions short. Use them for constraints that apply to every Chat, such as Never use the word "quietly." Put the actual brief and evidence in the relevant file or Chat.
More context is not automatically better. Do not add hundreds of pages to a Project when only a few sources affect the current workflow.

​
Build a reusable client workflow

1

Create one Product per offer

Keep stable brand voice, customer context, approved facts and offer assets in the relevant Product.
2

Choose the Project boundary

Use a Project for a repeatable workflow or a campaign with shared files and decisions. Do not create one for every ad or deliverable.
3

Add only reusable Project context

Keep the instructions short. Add only files that every Chat in the Project should be able to use.
4

Start one focused Chat

Name the deliverable, mention its Product and attach any evidence used only for this execution.
Focused Project Chat showing one Product mention and one deliverable request

A focused Project Chat adds one Product for the current deliverable.

Create another Project when the campaign brief, shared files or decision history changes.

​
Ask for the deliverable

If the Product and Project are already selected, do not repeat their full context in the prompt.

​
Make the Project available to your team

1

Open the Project

Find the person-shaped control in the Project header. It shows Personal or Team.
2

Change it to Team

Select Personal and confirm the control settles on Team.
3

Share the required Product and Chat

Use the Product row menu and the Chat’s own visibility control. Project visibility does not cascade.
4

Reverse the change when needed

Select Team to return the Project to Personal visibility.
Project, Product and Chat visibility are separate. Check all three before a teammate takes over the work.

​
Common mistakes

  • Creating a Project for every deliverable. Reuse the workflow and start a focused Chat.
  • Putting stable brand facts in Project instructions. Maintain them in the Product.
  • Loading every client file. Keep only the sources each Project should reuse.
  • Linking every Product to the Project. Mention the Product needed for the current Chat.
  • Assuming Team visibility cascades. Share the required Product and Chat separately.