Marketing · Colleague: Mel

Briefs, audits, and spend anomalies — from your data, not the internet

Mel, your Marketing Colleague, drafts content briefs from your positioning, audits campaign performance weekly, flags spend anomalies, and coordinates launches.

Phase 4 · Q2-Q3
Capability 01

Source-backed content briefs

Instead of drafting from the internet, Mel drafts from your own positioning: product docs, past blog posts, launch briefs, changelog. Every recommendation shows the paragraph it drew from, so the writer can verify or push back before publishing.
grounded answer · sources
answer

Priya’s Okta lockout can be cleared via self-serve MFA challenge — no IT intervention required. If MFA fails, escalate to IT on-call.

cited from
01
IT · Okta account lockout policy
runbook · updated 4d ago
02
HR · Emergency access procedure
policy · updated 2w ago
03
Ticket #48211 · priya · resolved
past ticket · similar match
Capability 02

Weekly campaign audits

Every Monday morning Mel digests last week's GA4, Google Ads, Meta Ads, LinkedIn Ads, and Segment data into one Slack post: what moved, what didn't, what the funnel drop-off looks like. No dashboard-crawling; the anomalies come to you.
approvals · pending 4
unlock okta account
priya.sharma · self-serve · read-only
denyapprove
refund $128.40
stripe · ord_A4b2c · manager approval
denyapprove
revoke prod IAM role
aws · role/analyst · step-up MFA
denyapprove
reset zoom SSO
kiran.mehta · self-serve
denyapprove
Capability 03

Spend anomaly detection

Ad spend over 2σ above baseline gets flagged before month-end. So does spend under baseline — sometimes the more painful signal. Mel names the channel, the delta, and the plausible explanation drawn from campaign history.
context · priya.sharma
priyateamon-calloktagithubworkday
Capability 04

Competitor mention watch

RSS feeds, web scrape of specific competitors, LinkedIn posts, Reddit mentions, Twitter — filtered against your competitor list, ranked by signal, delivered as a weekly digest. Nothing anecdotal; every mention linked back to the source.
reports · this week
Auto-resolved
78.4%
+4.1 pt
Avg. loop time
11.4s
-2.1s
Approvals pending
12
-3
Coverage
94%
+1.2 pt
monsun
Capability 05

Launch coordination

One playbook that keeps a launch on rails: content brief → asset drafts → asset review → publish → post to channels → measure. Cross-functional owners get their sub-tasks; missed handoffs escalate. Post-launch retro drafts itself from the actual data.
grounded answer · sources
answer

Priya’s Okta lockout can be cleared via self-serve MFA challenge — no IT intervention required. If MFA fails, escalate to IT on-call.

cited from
01
IT · Okta account lockout policy
runbook · updated 4d ago
02
HR · Emergency access procedure
policy · updated 2w ago
03
Ticket #48211 · priya · resolved
past ticket · similar match
Capability 06

Case-study drafter

On every closed-won that opts in, Mel drafts a case study from the win-notes, the negotiation Slack channel, and any post-launch metrics the customer has shared. Draft goes to the customer for approval before publish.
approvals · pending 4
unlock okta account
priya.sharma · self-serve · read-only
denyapprove
refund $128.40
stripe · ord_A4b2c · manager approval
denyapprove
revoke prod IAM role
aws · role/analyst · step-up MFA
denyapprove
reset zoom SSO
kiran.mehta · self-serve
denyapprove
The BeforeQuery method

Visibility. Reasoning. Action.

Every playbook, every action, every answer follows the same three-beat rhythm — one that keeps every write behind evidence and every decision behind policy.

01

Visibility

Read the full context — who is asking, what they own, what they can access, what breaks if we touch it. Nothing acts on incomplete signal.

02

Reasoning

Match the request to a grounded answer or a playbook. Cite the source paragraph, weigh the risk tier, and route to the correct approver where policy demands it.

03

Action

Execute the write on your systems with an audit-log id, an entity list, and a rollback path. Confirm the outcome with the requester in the same thread.

How every request flows

From ask to resolution in one loop

Six stages every request travels. What changes is how many stages policy lets the agent execute without waiting on a human.

01
Request

In Slack, email, widget, MCP, or the helpdesk. Same voice, same context.

Slack · Teams · Zendesk · Widget · MCP
02
Retrieve

Grounded lookup against your knowledge with source paragraphs held aside.

Knowledge Studio
03
Reason

Read the Context Graph — who, what they own, what breaks if we touch it.

Context Graph
04
Approve

Route to the correct approver per policy. Reversible writes gated, destructive step-up.

Approval matrix
05
Execute

Act on Okta, Stripe, Workday, GitHub, or your own systems. Logged and attributable.

Actions runtime
06
Verify

Confirm the outcome with the requester. Feed the result back into future decisions.

Feedback loop
Enterprise-grade by default

The controls your security team is going to ask about

SOC 2 Type II
audited annually
GDPR
EU data residency
HIPAA-ready
BAA available
SSO / SAML
Okta · Entra · Google
SCIM 2.0
auto-provision
Audit log
every write, traceable
Bring your key
AES-256-GCM at rest
Bring your model
Anthropic · OpenAI · self-host
Zero training
your data stays yours
Rollback
every write reversible
TLS 1.3
in transit
99.9% uptime
SLA on Enterprise

Frequently asked questions

Common questions about Agentic Marketing

Marketo, HubSpot Marketing, Mailchimp, Braze, Iterable, ActiveCampaign, Customer.io for automation; GA4, Amplitude, Mixpanel, Segment for analytics; Google Ads, Meta Ads, LinkedIn Ads, Adobe Analytics for spend; Webflow, Contentful, Sanity, WordPress for CMS. All ship in Phase 4.
Drafts, not final copy. Every brief and every case-study draft is a starting point grounded in your product truth — you review and rewrite before publishing. Speeds up the first 60% of the work; the polish stays human.
Nightly cron reads spend by channel from GA4/Ads APIs, computes a 30-day rolling baseline per channel + campaign, flags deviations beyond 2σ. Flags surface in a Slack digest with the delta, the plausible cause (creative fatigue? bid change? weekend?), and a link to the campaign.
Yes — the competitor-mention watch extends to brand mentions across social and news. Negative-sentiment spikes trigger an alert to comms + the CMO. Grounded in the actual mention, not a summary that loses the tone.
Mel Colleague + content-brief drafter + weekly campaign audit + spend-anomaly detector + competitor mention watch + launch coordination playbook. Additional workflows (attribution reconciliation, ad-creative testing, newsletter drafter) roll out through Phase 5.

Run marketing on BeforeQuery

Book a demo and see what Agentic Marketing does on your own data — usually within 45 days.