Skip to content

PROJECT.md

Latest commit

 

History

History
68 lines (53 loc) · 2.88 KB

PROJECT.md

File metadata and controls

68 lines (53 loc) · 2.88 KB
Raw

CMO.XYZ — Project brief

Source of truth for what the product is and how to talk about it on the site. Pair this with the CMO.XYZ Style Guide DESIGN.md (typography, voice, scope rules). Where this brief and DESIGN.md disagree, see "Open conflicts" at the bottom — do not silently pick one.

What it is

CMO.XYZ is an AI CMO. The agent is named Cuso. He is the only marketing hire a business needs. He manages:

  • Social media accounts
  • Google Ads
  • Meta Ads
  • Website SEO
  • Newsletter

He learns your brand, builds a strategy, and continuously executes and improves it. The output fits the brand and does not sound like AI slop.

Cuso is referred to as "he".

The Brand Brain

When Cuso learns a business he analyzes the website, brand, products, target audience, competitors, and existing marketing, and builds a persistent Brand Brain that everything else draws from.

User lifecycle

  1. Sign up. User gives basic info: website URL and marketing goals.
  2. Cuso learns the business. Analyzes site, brand, products, audience, competitors, existing marketing, and builds the Brand Brain.
  3. Cuso creates a 1-month strategy. Presented visually: content calendar, social posts, ad previews, SEO content, newsletters. The user can discuss and change it with Cuso until happy.
  4. Subscribe. The user subscribes to put Cuso to work.
  5. Daily loop. Every day Cuso looks at the strategy, upcoming content, past performance, and what's happening in the business, then plans and executes the next actions across all connected channels.
  6. Weekly measure. Each week he analyzes performance and suggests or automatically makes improvements.
  7. Repeat. Plan -> execute -> measure -> improve, continuously.

At any point the user can talk to Cuso to change course: post something spontaneously, change the strategy, or create a short-term announcement. He handles spontaneous requests, remembers them, and adapts on the fly.

Core loop (one line)

Learns the brand -> builds the strategy -> executes daily -> measures weekly -> improves. Forever.

Decisions (confirmed with the user, 2026-10-01)

  1. Naming. CMO.XYZ is the company/brand. Cuso is the agent's name. Use "Cuso" for the agent in copy (he/him); keep CMO.XYZ as the brand in the logo and nav. This supersedes the DESIGN.md "never hardcode an agent name" rule, since Cuso is the brand's agent name, not a per-user instance name.
  2. Pre-launch / waitlist. The product is NOT launched yet. The site's primary action is to collect the user's email for the waitlist, not "Get started" into an app. CTAs = join the waitlist. (This is a pre-launch waitlist, separate from the product's Newsletter capability.)
  3. Newsletter. Per the brief, Cuso manages Newsletter as a capability. DESIGN.md's "roadmap only" note predates this brief; show Newsletter as a real capability on the site.