Skip to main content
SaliencyLab Docs
Get started

Projects and brand context

Organize SaliencyLab analyses around a durable project so brand context, creative history, and follow-up work remain connected.

Why projects matter

A project is the durable context layer in SaliencyLab. It groups work for a brand or campaign and prevents every analysis from starting with an empty understanding of the decision.

Use separate projects when the brand, audience, market, or decision owner is materially different. Keep variants of the same campaign together so you can reopen and compare them.

What to add

Useful brand context includes:

  • Brand and product name
  • Category and market
  • Audience and buying situation
  • Positioning or proposition
  • Distinctive assets, visual codes, and mandatory cues
  • Relevant campaign or brief notes

Only add information you are comfortable using as analysis context. Do not paste secrets, personal data, or confidential customer lists into free-text fields.

Reusing context

Start each new creative from the relevant project. This keeps prior outputs discoverable and makes the handoff from RoastIQ to BuyerLens auditable.

Structure projects around decisions

A project works best when its contents share a decision context. Good boundaries include a campaign, product launch, market, or coherent creative platform. Avoid using one catch-all project for every asset a brand has produced; the accumulated context becomes harder to interpret.

Create a new project when:

  • The target audience or market changes materially
  • The proposition, product, or offer changes
  • The campaign has a different strategic role
  • A different client or decision owner needs separate access

Keep work in the same project when you are comparing executions, durations, hooks, end cards, or other variants of the same underlying campaign decision.

Write useful context

Prefer short, verifiable statements over broad marketing language. “Primary buyer: first-time urban dog owner; product proof: veterinarian-formulated” gives the analysis clearer constraints than “premium product for everyone.”

Distinguish between:

  • Facts: product, market, required claims, mandatory assets
  • Strategy: intended audience, proposition, communication role
  • Hypotheses: what the team believes may improve the creative

This separation makes it easier to see whether a result challenges a fact, interprets the strategy, or supports a testable hypothesis.

Project hygiene

  • Use recognizable names and keep variants consistently labeled.
  • Archive obsolete work instead of reusing it for an unrelated campaign.
  • Review brand context when positioning, packaging, or campaign strategy changes.
  • Remove information that is no longer correct.
  • Do not store secrets or unnecessary personal information in project notes.

Next, learn how to run a first analysis or interpret a completed result.

On this page