2.3 Brands, products, and projects
6 min read2 Workspace
2.3 Brands, Products, and Projects
2.3.1 How they relate
Brands, products, and projects are the three most important workspace objects in Marcto.
- Brand answers: who we are, who we speak to, how we speak, and what we should avoid.
- Product answers: what we sell, why it matters, and what facts or proof support it.
- Project answers: what marketing goal we are working on now, which channel it targets, and what deliverables are needed.
Brands and products are long-lived context. Projects are execution context for one concrete job. When all three are organized well, agents can produce consistent, accurate, reusable marketing work.
2.3.2 Maintaining brands
Brand records should store durable information. Do not put temporary discounts or one-campaign slogans into brand positioning.
Steps:
- Open Brands.
- Create a brand.
- Enter brand name, description, positioning, and audience.
- Add voice, banned phrases, and preferred phrases.
- Upload logo, brand colors, visual references, and brand book.
- Save and open the brand detail page.
- Use page chat to check missing context.
- Complete durable fields based on the suggestions.
Key fields:
| Field | What to write | Why it matters |
|---|---|---|
| Positioning | Who you serve, what problem you solve, and how you differ | Drives strategy and copy angles |
| Audience | People, situations, pains, motivation, objections | Stops agents from writing for everyone |
| Voice | What to say, what to avoid, preferred words, banned words | Keeps channels consistent |
| Constraints | Compliance, claims, price, channel limits | Reduces risky output |
| Visuals | Logo, primary colors, references | Supports creative direction and image work |
| Key facts | Certifications, reviews, cases, origin, data, story | Provides evidence for benefits |
2.3.3 Maintaining products
Product data should be factual. Avoid vague labels like “premium”, “great”, or “bestseller” unless there is evidence.
Steps:
- Open Products.
- Add a product.
- Select the brand.
- Enter product name, description, and core benefits.
- Add specs, audience, and use cases.
- Upload product images, manual, reviews, or competitor references.
- Save and open the product detail page.
- Use page chat to create a product completion checklist.
Recommended fields:
| Field | Example | Use |
|---|---|---|
| Description | What it is, what problem it solves, main use case | PDP and content intro |
| Benefits | Leakproof, lightweight, commute-friendly, 30-day warranty | Ads, titles, hooks |
| Specs | Material, size, weight, ingredients, package, compatibility | Prevent hallucination |
| Audience | First-time mothers, office commuters, outdoor users | Audience segmentation |
| Use cases | Travel, gifting, post-workout, family stock-up | Visual and content angles |
| Source assets | Product photos, review screenshots, manuals, competitor links | Evidence for agents |
Mark uncertain claims, certifications, materials, prices, or inventory as needing confirmation.
2.3.4 Maintaining projects
A project is a container for one marketing job. It should have one clear goal instead of becoming a catch-all folder.
Steps:
- Open Projects.
- Create a project.
- Select brand and linked products.
- Enter project name and goal.
- Add channels, audience, deliverables, timeline, and constraints.
- Upload or choose project assets.
- Save and open the project detail page.
- Ask the project assistant to summarize context before execution.
Recommended project brief:
| Module | Description |
|---|---|
| Goal | Awareness, conversion, retention, launch, clearance, research |
| Audience | Target people, situations, pains, and motivation |
| Products | Products being promoted or analyzed |
| Channels | Shopify, TikTok, Instagram, email, community |
| Core message | Claims, benefits, proof, and banned phrasing |
| Timeline | Preparation, generation, review, launch, retrospective |
| KPI | CTR, CVR, ROAS, GMV, engagement, saves |
| Deliverables | Copy, scripts, images, landing modules, reports, checklists |
2.3.5 How they work together
A typical project uses all three:
- Brand provides voice, audience, and boundaries.
- Product provides benefits, specs, and evidence.
- Project provides goal, channel, and deliverables.
- Resources provide images, documents, historical outputs, and references.
- Page chat reads this context and produces executable work.
For TikTok scripts, the brand decides tone, the product decides benefits, and the project decides script count, audience, and review criteria.
2.3.6 Maintenance rhythm
Use this rhythm:
- After creating a brand, complete positioning, audience, voice, and constraints.
- After adding a product, complete benefits, specs, images, and evidence.
- Start a new project for formal marketing work.
- After each project, save final resources and review results.
- When a durable insight appears, write it back to the brand or product.
2.3.7 Common issues
If brand, product, and project content overlap, separate them by lifespan. Long-lived rules go to brand or product. One-campaign goals go to project. Reusable files go to resources.
If a project links multiple products, make sure each product has clear benefits and specs, or the agent may mix them.
If brand context changes often, keep campaign slogans inside projects and save only stable language back to the brand.
If you are unsure where information belongs, ask how long it will remain true: long-lived means brand or product; campaign-specific means project; file-based means resource.