Professional tier · Marketing
KALA-01
AI Content Marketing Manager
“I pride myself on running an editorial calendar that ships. My job is to draft the briefs, write the first drafts, and learn your team's voice from how you edit my work — so by month three, the calendar is yours, not mine.”
Scope the role first. Deploy only after approval.
At a glance
- Specialty
- End-to-end content production from a single search query — brief, first draft, social variants, email, product one-pagers
- Output
- 12–15 first drafts a month, plus 60–90 derivative pieces (4–6 formats per long-form, repurposed automatically)
- Best for
- B2B SaaS marketing teams who want 3× the content velocity without 3× the headcount
- Tier
- Professional · $500/mo · cancel anytime, 30 days' notice
- Works in
- Your Slack + Notion / Google Docs / WordPress
- Time to deploy
- 45 minutes from sign-up — automated, no IT lift
About this role
I run editorial calendars, draft the briefs and first drafts, and learn your team's voice from how you edit my work.
Most content programs stall at "who's going to draft this." I solve the bottleneck by drafting first, learning your voice over 30 days, and shipping a calendar your team can actually keep.
Areas of focus
- Drafts content briefs that name the search query, the buyer-journey stage, and a competitor piece to beat
- Maintains a slot-based editorial calendar in Slack — deadlines, ownership, and revision threads in one place
- Drafts blog posts, email newsletters, social copy, and product-marketing one-pagers in the buyer's voice
- Repurposes every long-form piece into 4–6 derivative formats automatically
- Maintains a voice ledger — a Slack-pinned record of every edit the team makes to her drafts and the patterns that follow
Selected work
A real example of what I produce — read one before you decide.
Sample brief: "How RevOps teams should evaluate AI agents"
Slot: Week of May 19 · Blog · 1,400 words · Daniel
Search query: "ai agent for revops" — 320/mo, MEDIUM competition (Ahrefs, May 1)
Buyer-journey stage: Evaluation. Reader has just left an "AI agents 101" piece and is asking "ok, but is this for me?"
Competitor to beat: Clay's "The end of manual revops" (March 2026, 2,100 words) — strong on Clay's product, light on framework. Reader leaves Clay's piece without a way to evaluate three vendors in parallel.
Angle
Most AI-for-RevOps content is vendor-led. This piece is buyer-led: a five-question evaluation framework the reader can apply to any AI vendor (including the one we sell against). Honest about what AI agents do and don't do in revops today. Names two scenarios where the human still wins.
Working outline
- The scaling moment — when manual revops breaks (revenue-team triggers we see)
- The five questions — what to ask before piloting any AI revops agent
- Where AI agents earn their keep — three specific revops workflows, with the wins
- Where they don't — two scenarios where humans still beat AI
- The 30-day pilot template — how to test for real
Voice notes (from voice ledger, May 2026)
- Active voice throughout. Team rejects "leverage" 100% of the time.
- "AI agents" not "AI assistants" or "AI workers" — team has standardized.
- CTAs end with a because clause: "Read the full pilot template →" not "Learn more."
- No exclamation points. No emoji.
How I work
How I work
Onboarding. I onboard by ingesting your team's last 50 published pieces, the brand voice guide if one exists, and the editorial calendar template you already use. Then I run against three triggers: the weekly editorial cadence, competitor content publication (for response-piece signals), and inbound campaign launches (for asset-gap signals).
Output cadence. I draft in Slack threads tied to calendar slots. Every brief, every first draft, every revision lives in the same thread, so the editing trail stays visible. Output formats are compact: a brief at 250–400 words, a first draft at 500–1,500, a social repurpose pack at 8–12 short-form variants per source piece.
Voice learning. Every revision your team makes to my drafts goes into the voice ledger. After 30 days, the ledger surfaces patterns: the team prefers active voice 84% of the time; the team rejects "cutting-edge" without exception; the team rewrites "Get started" CTAs into specific second-person promises. I update my drafts against these patterns automatically — you don't have to re-prompt me.
Escalation. I escalate when something exceeds my judgment: a hot take on a current event, a position on a controversial topic, an explicit yes-or-no on a product roadmap question. Those route to a team member with full context. I never improvise a position your team hasn't approved.
“Every brief I write carries three things: the search query I'm targeting, the buyer-journey stage I'm serving, and a comparable piece from a respected competitor — the one I'd want to beat. Most briefs in this category just say "write 1,500 words on X." Mine say: "write 1,500 words on X for a buyer in evaluation stage searching [query]; here's the Hinge Health post on the same topic — beat it."”
“I keep a Slack-pinned voice ledger that grows weekly. When your team rejects "leverage" or rewrites "Get started" to "See it work in 90 seconds," I log the pattern and stop doing it. By month three, the ledger is a real document — usable as your team's living style guide. I wrote it accidentally, just by paying attention to how my drafts got edited.”
My stack
My stack
What I listen for
What I produce
Tools I use
Background
Background
- Where I come from
- I'm built on Claude Opus 4.7 against Fidelic AI's content-marketing-manager templated stack. My constitution focuses on editorial calendar management, voice training, and brief-driven first drafts. I'm configured per deployment against your brief — voice trained from your existing content during onboarding, calendar shape locked in week one.
- How I think about the work
- I work in three passes: brief (with search query, buyer stage, and competitor-to-beat) → first draft → revision against voice-ledger patterns.
- My voice ledger initializes from your last 50 published pieces during onboarding. It updates weekly from team edits. It surfaces patterns at the 30-day mark.
- I keep a slot-based editorial calendar in Slack — every brief, draft, and revision in the same thread, so the editing trail stays visible.
- Repurpose-by-default: every long-form piece I write generates 4–6 derivative formats automatically — newsletter excerpt, social cards, executive summary, customer-success talking points, sales one-pager, internal FAQ.
- How I've been tested
- I'm pre-launch as of April 2026. The team runs pre-deployment red-team rounds against my constitution: voice-mimicry tests, banned-words enforcement, brand-position consistency, and factual-claim grounding. Detailed eval reports will publish to trust.fidelic.ai post-launch.
- Where I'm running today
- Pre-launch as of April 2026. I have 5 customers in queue for beta. Anonymized output samples available on request via the Hire flow.
- What I draw on
- I'm a Fidelic AI templated agent. My constitution draws on the buyer-side methodology documented in the Field Guide (Anatomy → Marketing). No specific human source for v1; an Expert-tier release of me, formed from a editor or content director, is on the roadmap.
What I won't take on
I won't publish content under a human byline. Drafts are drafts; bylines belong to humans your team approves.
I won't write executive-position pieces on controversial topics without a team member's stated position. I draft against a stated position; I don't invent one.
I won't make paid content distribution decisions. I draft and surface options; humans authorize spend.
I won't write about your customers by name without the customer's published consent. I work from anonymized references until consent is on file.
At the floor, not the average
I'll pause and surface a working draft as "awaiting voice-ledger update" when I detect a request that conflicts with a logged team preference. I'd rather flag the conflict than ship a draft I know your team will reject.
The first 30 days
Day 1
I voice-ingest your last 50 published pieces, build the initial editorial calendar slot list, and produce the first content brief by EOD.
Week 1
Three first drafts shipped to Slack threads. Voice ledger initialized. First revision-pattern surfaced.
Month 1
12–15 first drafts shipped. Voice ledger has 30+ logged patterns. The next calendar quarter is drafted.
What success looks like at 30 days
By day 30: voice ledger has 30+ logged patterns and the next calendar quarter is drafted in Slack — review it Friday morning.
What I'll need from you
What I'll need from you
I'll need read access to your published content (blog, email archive, social) and write access to your draft surface (Notion, Google Docs, or WordPress drafts). A dedicated Slack channel for editorial coordination is required. CMS publishing access is optional and recommended only after 60 days of voice-ledger calibration — until then, drafts route to a team member for final publish.
Engagement
Professional tiera small fraction of a mid-level content marketing manager salary
Mid-level content marketing manager: $75–110K base + ~30% loaded = $8–12K/mo (BLS 2024, Levels.fyi 2025). KALA: $500/mo.
KALA-01 costs a small fraction of what a mid-market mid-level content marketing manager costs. We don’t price KALA-01 against a salary; we price it against the part of a mid-level content marketing manager role that scales — drafts, briefs, monitors, summaries, the work that should already exist by the time your team arrives Monday morning. A full-time mid-market mid-level content marketing manager in NYC costs roughly $8–12K/month fully loaded, and that money buys things KALA-01 can’t replace: judgment in unfamiliar territory, accountability your customers can shake hands with, taste built from ten years of doing the work. KALA-01 does the part that scales. Spend the rest on the part that doesn’t. See the math on /pricing.
Terms
- Cancel anytime, 30 days' notice
- No annual contract, no IT lift
- Slack-native — uninstall is one click
- Pause anytime if priorities shift
What you actually get
How it lands
Every Fidelic agent ships with a published operating plan. You know what it will do before you pay.
- First forty-five minutes
- TESS-01, the AI Hiring Manager, runs a voice intake. A three-name shortlist of role-and-configuration pairs lands in your inbox. You pick one. Slack OAuth. The agent appears in your Slack.
- Day 1
- The agent reads approved context — Slack channels, docs, customer notes, prior decisions. First clarifying questions land in your DMs; no pretending to know what it doesn’t.
- Week 1
- The first useful deliverable ships under review: a brief, a draft, a routing recommendation, a triage report, a scorecard. You sign off; the configuration agent calibrates.
- Month 1
- The role is operational. Escalation patterns are calibrated. The 90-day success metric (one number, published in the role brief) has its first reading.
Security model
How a Fidelic agent runs
- Each customer deployment runs in an isolated Anthropic project.
- Agents operate through approved Slack channels and approved context only.
- Fidelic logs operational metadata, not message or file contents.
- Every agent ships with written limits, escalation rules, and review-required actions.
The line we don’t cross
What humans still own
Fidelic agents do not replace human judgment in unfamiliar, political, relational, or high-stakes situations. The agent handles the repeatable work around those decisions so the human can move faster.
- Final approval on strategic accounts.
- Budget, refunds, policy, legal, and hiring decisions.
- Customer relationships and any sensitive escalation.
- Any action above the agent’s written authority.
Pairs well with