projects/POEMELLI_RESEARCH.md

Pomelli Research & The Real Vision

July 2026 Google Pomelli: https://labs.google.com/pomelli Polsia: https://polsia.com Case Study: Julian Goldie (https://juliangoldie.com)

---

What Pomelli Actually Is

Pomelli = a marketing tool that extracts brand colors/fonts/tone from a URL, then generates social posts, ads, product photos, a brand book PDF, and a landing page.

It calls itself a brand tool. It is not. It is a marketing asset generator with brand as the input. The brand is static — scraped once, never learned from, never evolves. The website feature is a single landing page, not a real website. No commerce, no delivery, no knowledge management, no client operations, no support, no growth loop.

---

What Polsia Actually Is

Polsia = an AI employee system — agents that code, tweet, email, support, run ads, do finance. It runs a company. But brand is just one agent in a stable. It's an operating system for company operations, not for brand.

---

The Core Problem with Both

Neither puts brand where it belongs.

Brand is not a feature. Brand is not an agent. Brand is the consistency layer across every business function.

A business has many internal functions:

• Core product/service delivery (what makes money)
• Marketing (getting clients/customers)
• Commerce & monetization
• Operations & delivery
• Support & community
• Knowledge management

And marketing itself depends on what the business actually does. A course seller's marketing is different from a freelance developer's marketing. Pomelli treats marketing as one-size-fits-all asset generation.

Every single function produces something that touches the customer. Every single one should be consistent in look, voice, and feel. That consistency is brand.

---

Case Study: Julian Goldie

Julian Goldie runs a fully documented digital business. Here's every function and what it touches:

Business Functions

Function	What It Produces	Current Tools
Agency Delivery	Client proposals, audits, reports, invoices	Custom AI stack, Notion, email
Content Creation	Daily YouTube videos, scripts, thumbnails	n8n + Claude + HeyGen + 11Labs
Content Distribution	Posts on YouTube, TikTok, Instagram, X, LinkedIn	Blow Auto, n8n
Community	Live coaching, Q&As, member content, Skool posts	Skool, Zoom
Education Products	Courses, books, digital downloads	Udemy, Amazon, Skool
Marketing	Social posts, email funnels, lead magnets, ads	n8n, Claude, Firecrawl
Client Intake	Strategy sessions, proposals, onboarding	Calendly, CRM, email
Support	Community questions, client communication	Skool DM, email, Telegram
Revenue Management	Subscriptions, invoices, affiliate tracking	Stripe, Skool, Amazon

What's Missing (Where Brand OS Fits)

Touchpoint	Current State	With Brand OS
YouTube video thumbnails	Manually designed or AI-generated with no brand template	Auto-generated from brand core
Agency proposals	Written in brand voice but no visual consistency	Compiled from brand colors, fonts, tone
Skool community posts	Text posts only, no brand styling	Brand-themed posts with consistent look
Course landing pages	Separate platform, separate look	Brand-native, compiled from same source
Invoices/receipts	Stripe default or generic	Brand-themed, consistent with everything else
Client reports	PDFs with agency logo but no design system	Brand-compiled reports with DNA styling
Email sequences	Plain text or generic Mailchimp templates	Brand-voiced and branded emails
Affiliate pages	Separate system, no brand	Brand-native affiliate flows

The Core Insight from This Case

Julian's business has 6 distinct revenue streams and probably 15+ tools to manage them. Each tool has its own look. His brand identity exists in his head and in scattered assets, but it's not a living system that every function compiles from.

If a brand OS existed, he would:

1. Define his brand once (colors, fonts, tone, voice, visual style)
2. Every function compiles from that core
3. Marketing knows what the agency looks like. Community knows what the courses look like. Everything is consistent automatically.

---

The Real Vision

One system. Brand is the OS. Business functions are services running on it.

┌────────────────────────────────────────────────────────────────┐
│                    BRAND CORE (The OS)                           │
│                                                                  │
│  - Visual identity (colors, fonts, logos, imagery style)        │
│  - Verbal identity (tone of voice, personality, vocabulary)      │
│  - Audience understanding (who you serve, what they need)        │
│  - Value system (what you stand for, how you operate)            │
│  - Knowledge base (what you know, your IP, your content)         │
│                                                                  │
│  This is not static. It learns from every interaction.           │
└────────────────────────────────────────────────────────────────┘
                              │
         ┌────────────────────┼────────────────────┐
         │                    │                    │
         ▼                    ▼                    ▼
┌─────────────────┐  ┌─────────────────┐  ┌─────────────────┐
│  CORE SERVICE    │  │   COMMERCE      │  │   MARKETING     │
│  (what you do)   │  │                 │  │                 │
│                  │  │                 │  │                 │
│ Depends on       │  │ - Paywalls      │  │ - Social posts  │
│ business type:   │  │ - Subscriptions │  │ - Ad campaigns  │
│                  │  │ - One-time sales│  │ - Email flows   │
│ - Course seller  │  │ - Memberships   │  │ - SEO/content   │
│ - Freelancer     │  │ - Checkout      │  │ - Distribution  │
│ - Creator        │  │ - Licensing     │  │ - Analytics     │
│ - Agency         │  │                 │  │                 │
│ - SaaS           │  │                 │  │                 │
└─────────────────┘  └─────────────────┘  └─────────────────┘
         │                    │                    │
         └────────────────────┼────────────────────┘
                              │
                    ┌─────────▼─────────┐
                    │  OPERATIONS        │
                    │                    │
                    │ - Client intake    │
                    │ - Project tracking │
                    │ - Invoicing/pay    │
                    │ - Support/tickets  │
                    │ - Team management  │
                    │ - Analytics        │
                    └────────────────────┘

Every module compiles from the same brand core. The course portal looks like the marketing site. The invoice looks like the landing page. The support email sounds like the Instagram caption. Consistency is not enforced — it's automatic.

---

Concrete Examples by Business Type

Course Seller

Function	What the system does
Course development	Knowledge studio + AI-assisted curriculum builder
Hosting/delivery	Native course player with gating
Paywall	Built-in payment bridge with brand-themed checkout
Marketing	Brand-consistent posts, ads, email from the same identity
Client support	Brand-voiced ticket/reply system
Community	Brand-themed community space
Invoicing	Brand-themed invoices and receipts

Freelance Developer

Function	What the system does
Service offering	Brand-styled portfolio + case studies + pricing
Client intake	Branded proposal generator with scope/timeline
Communication	All client emails in brand voice, tracked
Project delivery	Branded client portal with progress, deliverables
Invoicing	Branded invoices, automatic payment reminders
Marketing	Social posts in brand voice, case study distribution
Support	Branded ticket system, maintenance requests

Creator (YouTuber, Writer, Podcaster)

Function	What the system does
Content studio	Write, record, edit, all in-brand
Newsletter	Brand-consistent email with paid tiers
Membership	Gated content, community, brand-themed
Sponsorships	Rate cards, pitch decks, all on-brand
Merchandise	Product pages, checkout, all on-brand
Marketing	Cross-platform distribution, consistent voice
Analytics	Know what works, feed back into brand

Agency Owner (like Julian Goldie)

Function	What the system does
Client proposals	Branded proposals compiled from brand DNA
Service delivery	Brand-consistent reports, audits, deliverables
Team operations	Internal brand guide for all output
Client portal	Brand-themed client dashboard
Invoicing	Branded invoices, payment tracking
Marketing	Consistent brand across YouTube, community, social
Community	Branded community space with consistent voice
Education products	Branded courses, books, templates

---

What Pomelli Does vs What This Does

	Pomelli	This system
Scope	Marketing assets	Every customer-facing function
Brand	Scraped once, static	Living, learning, evolving
Website	Single landing page	Whatever user needs: landing, portal, store, blog
Commerce	❌	Paywalls, subscriptions, memberships
Course delivery	❌	Native course player + gating
Client operations	❌	Intake, projects, invoicing, support
Knowledge management	❌	Content/KB studio integrated with brand
Community	❌	Brand-themed community layer
Marketing	✅ (core)	One service among many
Distribution	Download only	Auto-publish to platforms
Performance feedback	❌	Learn what works → evolve brand

---

The Architecture

┌─────────────────────────────────────────────────┐
│                    BRAND CORE                     │
│  JSON profile: { colors, fonts, tone, voice,     │
│    audience, values, knowledge, visual_style }   │
└──────────────────┬──────────────────────────────┘
                   │
    ┌──────────────┴──────────────┐
    │       Compiler Layer         │
    │  Takes brand + function      │
    │  → produces branded output   │
    └──────────────┬──────────────┘
                   │
    ┌──────────────┴──────────────┐
    │       Function Modules       │
    │  Core │ Commerce │ Marketing │
    │  Courses │ Portal │ Billing  │
    │  Support │ Community │ ...   │
    └─────────────────────────────┘

Every module requests output from the compiler with { brand_id, function, parameters }. The compiler returns the branded result. The brand core evolves as performance data comes back.

This is the thing that doesn't exist yet.