BrandMan · Operator console

Demo Brand

30-day growth mission, editorial pipeline, and governed execution.

No public publish controls

Mission trajectory

Loading
Loading mission progress…

Assisted workflow · next safe action

Loading

BrandMan prepares and governs the work. A human approves the exact revision; the browser/MCP helper only executes that approval.

Finding the next safe step…

Connections

—
Checking connection health…

Connect an account

Start browser-assisted today, or choose standalone for scheduled operation without an open browser. Nothing sends automatically in either mode.

Exact access requested

Live readiness

Loading

Code capability and live deployment state are tracked separately.

Checking launch readiness…

Standalone API usage and cost

Loading

Payload-free request counts use your versioned rate cards. BrandMan never bundles or guesses vendor prices.

Loading provider usage…
Add a price from my provider agreement
Use the current price from your provider agreement. Provider invoices remain authoritative; this creates an estimate only.

Third-party sources

—

Syndicated metadata only. Changes require confirmation and a reason.

Loading governed feeds…

Canonical source checks

—

Current public-page metadata only. This never replaces claim-level fact checking.

Loading source evidence…

Morning priorities

Required pace
Building today’s plan…

Today’s scorecard

—
Loading scorecard…

Approval queue

—

Only complete fact checks and exact current revisions appear here. Editing invalidates approval.

Loading governed actions…

Approval evidence

—

Immutable snapshots bind account, action, destination, schedule, revision, approver, time, and material fingerprint.

Loading approval evidence…

Approved handoffs

—

Operator approval and helper execution remain separate. This guided surface can bind a destination, activate a browser helper, claim exact work, mark the pre-provider boundary, and reconcile a receipt. None of those controls sends or publishes content.

Checking browser helper…
Loading approved execution handoffs…

Editorial center

Candidates + issues

Prioritized candidates

Loading candidates…

Newsletter issues

Loading issues…

Experiment measurement

—

Declared metrics are collected and evaluated only inside persisted windows. Missing, stale, partial, and late evidence stay visible; winners are never accepted automatically.

Loading experiment windows…

Campaign graphs

—

Readable source-to-channel lineage first. Reusable anchors, touchpoints, supporting assets, relationships, and named flights follow. Every asset remains draft-only until separately approved.

Loading package lineage…
Loading campaign graphs…

Campaign recipes

—

Choose a guided recipe and preview its asset graph before BrandMan creates anything. Hard approval and source boundaries cannot be overridden.

Measurement and Beehiiv aggregate pulls

—

Beehiiv measurement work is read-only and aggregate-only. Never enter subscriber names, emails, or records.

Loading Beehiiv aggregate pull status…

Tracked links

Performance planning

—

Fresh, same-channel outcomes are a time-decayed and confidence-aware prior—not an instruction. Influence is capped and every retrieval is audited.

Composing recent measured outcomes…

Product gaps

—

Recurring failures stay visible through resolution and verification.

Loading product feedback…