Make every ProductiveBot page, post, and screen look and sound consistent.

Approved glow tokens

Hero atmosphere:
radial-gradient(circle at 70% 20%, rgba(102,247,255,.16), transparent 48%)

Card glow:
box-shadow: 0 0 34px rgba(102,247,255,.10)

CTA glow:
box-shadow: 0 18px 38px rgba(102,247,255,.24)

• No purple or generic cyberpunk glow.
• No glow on every card in dense grids.
• No large transparent overlays on light print/PDF pages.
• No fake generated glow logos. Use the real logo assets.

Accent

Choose one cyan accent per composition. Cyan is an accent only — never a dominant background or large fill.

Icons

No emojis. Use Lucide line icons only, with a clear functional reason to be there.

Proof

Start with a number, a quote, an outcome, or real product proof. Keep explanatory copy short.

Restraint

Do not turn every card, line, or phrase into the moment. One element gets the energy; the rest creates space.

Approved semantic tokens

--navy: #09182F
--cyan: #00F2FF
--cyan-soft: #66F7FF
--heading: #F8FAFC
--body: #C8D6E5

• Multiple cyan glows on one slide.
• Gradient text on more than one phrase per slide.
• Background photos without a navy scrim.
• Recreated logos made from text or CSS.
• Busy glass cards with multiple glowing borders.
• Display fonts in presentations or UI.

Glow

Brand atmosphere, active system, primary focus.

Proof

Verified output, review, workflow, completion.

Control

Ownership, privacy, permissions, security.

Workstation

Mac mini, agent system, hardware included.

Canonical on dark: precise UI, documents, nav, compact placements.

Canonical on light: white/light neutral surfaces only.

Blog component pattern

Shopify strips classes and divs, so reliable article components use inline-styled tables. Keep rounded 8px corners, navy headers, ProductiveBot cyan column emphasis, and compact rows.

Reliable components:
- Comparison table: DIY vs ProductiveBot
- Spec table: neutral two-column
- Numbered steps: table-based
- FAQ: H3 questions + JSON-LD

Colors:
teal accent rgb(0,242,255)
PB bg rgba(0,242,255,.03-.10)
DIY bg rgba(15,47,87,.15-.40)

Campaign message framework

Build campaign messages around audience awareness, customer pain, relevant proof, creative format, and one clear next action. Each asset should make one focused promise.

Message examples by awareness stage:
Problem aware: "AI looks easy in demos. Making it
  useful in your business is the hard part."
Solution aware: "Skip the DIY setup.
  Start delegating real work."
  (No hour figure until one is measured.
  "40-hour" and the live page's "5+ hours"
  are both unsourced. Do not use either.)
Product aware: "ProductiveBot turns a Mac mini into
  an owned AI agent workstation for your business."
Most aware: "Setup, support, memory, and workflows
  included."

Resolution

Desktop source: at least 1440px wide, preferably 2×/Retina. Mobile source: native high-density capture. Never upscale a soft screenshot.

Readability

Text and controls must remain legible at the guide's displayed size. Split long pages into purposeful crops instead of shrinking them into a poster.

Privacy

Use demo data. Redact customer names, emails, tickets, tokens, URLs, IDs, terminal output, and private work before the asset enters the library.

Source record

Keep the original PNG, capture date, product version, surface name, owner, approval status, and any redaction notes. Replace stale references rather than silently mixing versions.

Tier vocabulary — the “included” rule

Decided 2026-08-22. The ProductiveBot+ free tier is open to everyone, is not time-boxed, and is subject to change. The essential promise is that the core capability of having an agent is part of the free base tier. Paid tiers arrive later and grow by adding capability, never by removing it from free.

Two different words, and they are not interchangeable:

• “Included” — free-tier features only: Scout support, Skill Store access, training and community resources, Agent System Updates.
• “Currently included” — Pro features that are free only via a global grant flag: Content Machine, Scout guide, premium skills, advanced training. Writing these as plain “included” makes a promise the entitlement code is built to break.

What Scout is, and is not

Scout is a support agent, not the customer’s agent. Confusing the two is a known onboarding failure — keep them visibly distinct in every surface.

Scout is also a membership entitlement, not resident software. It runs on ProductiveBot infrastructure, it is a tier feature key, and it ceases if membership lapses. Do not list it among the things a customer keeps on the machine.

The customer’s own agent is what runs locally and answers to them. Scout is how they get help using it.

Bundle facts — use these figures, do not re-derive them

Confirmed 2026-08-22. Every writer who reconstructs this from an old source gets it wrong, because the stale product-truth figure produces a phantom pricing error.

Mac mini M4 (16GB / 256GB)   $799 on its own
ProductiveBot Agent System   $900 on its own
ProductiveBot+ membership    included, $0

Bought separately            $1,699
Together as one workstation  $1,499
Customer saves               $200

The arithmetic checks, so the strikethrough and the savings claim are defensible. Do not print a static Affirm monthly figure — let the widget render its own compliant line.

Claims that need legal care

These are not style preferences. Each one carries real exposure, so route anything in this list through Alex before it ships.

• Ratings and review counts — the FTC’s consumer-review rule covers fabricated or unsubstantiated ratings. Only real, verified reviews. There are three on record.
• Advertised monthly payments — a monthly figure is a triggering term under Regulation Z. Let the financing widget render it.
• Warranty duration — say “Apple’s standard limited warranty, verifiable by serial,” not a promised term. Avoid “total peace of mind.”
• Security guarantees — no “hardened,” “no exposed ports,” “stops,” or “neutralizes.” No hardening specification exists to support them. Use “designed to detect and block.”
• Privacy absolutes — “private data never leaves your device” is false whenever a cloud model is used, which is the default setup path. Say “stays on your device except what you send to your chosen AI provider.”
• Transfer and resale — the licence is non-transferable and second-owner activation is rejected in code. Do not imply a machine can be sold or gifted.

The content formula

1. Start with the lived work bottleneck.
2. Name the relief in the customer's language.
3. Show one concrete ProductiveBot workflow.
4. State the relevant review, approval, or ownership boundary.
5. Close with a practical next step.

What the buyer actually wants

Not agent infrastructure. They want confidence, time back, business leverage, and a clear path to a first useful result.

• "I had meetings all day; now I have to remember every promise I made."
• "The right follow-up is somewhere in a recording, Slack, email, or document."
• "I need momentum without becoming a systems expert."

Lead with the business result. Introduce the owned AI agent workstation and technical layer after the reader can picture the outcome.

Founder voice vs. team voice

Alex can be warmer, more exploratory, and story-led: the "I built this for myself" origin, candid observations, and personal analogies are useful. Team content should retain the clarity and real-work specificity while being tighter: name the problem, show what ProductiveBot prepares, and make customer control explicit.

Do not imitate conversational filler or force founder anecdotes into team copy.

Content production with Elle

Give Elle the objective, audience, channel, format, CTA, source material, required claims, and available product proof. Before drafting, Elle should identify the customer moment, core message, source-backed claim inventory, and proof plan.

Before publishing, check: buyer understood before AI is mentioned; one concrete workflow; plain-English technical language; correct human-control boundary; and claims traceable to approved sources.

Team content checkpoint: "Would a busy operator feel understood, see one believable way ProductiveBot can help this week, and still know they are in control?"

01

Dark navy base

#09182F foundation, #0D2340 panels, controlled cyan accents.

02

Bold Inter headline

One dominant idea, weight 800+, tight line height.

03

One gradient phrase

White-to-cyan on the phrase carrying the promise.

04

Real logo

No redraws, no generated wordmarks, no approximations.

05

Soft exterior glow

Outside boxes, behind product proof, around primary action.

06

Real proof

Mac mini, UI screenshots, workflow output, verified review language.

07

Useful cards

Every card explains a rule, offer, outcome, step, or proof point.

08

Truth boundary

No invented claims. Roadmap, beta, and shipped-today stay visibly separate.