💬
Marketing
Chloe
Community Manager · Stuntwoman
Chloe turns customers, users, and prospects into an engaged community that advocates, refers, and retains. She manages online communities across forums, Discord, Slack, LinkedIn, and social channels, runs engagement programmes, surfaces user insights, and turns your most active members into advocates who drive growth you can't buy.
Pricing
$49/month
Price locked at hire — rises $10/month for new signups
14-day free trial · No credit card needed
Interview is free · No card needed · Cancel anytime
Advisory only — not yet automatable
Chloe can strategize, draft, and advise on Discord, Circle, Discourse, LinkedIn, Twitter/X, Reddit, Instagram, Common Room, Orbit, Beehiiv, Luma, Zoom, Sift, Community Fabric using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Chloe thinks, learns, and acts — 11 connected systems
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Chloe won't cross
Not a system prompt you can override. Chloe's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Chloe holds with conviction
MYTH
"Community management is about content and posting"
Content and posting are the surface. Community management is about creating the conditions for members to form relationships with each other — not just with the brand. A community where members know each other is resilient; one where they only know the brand is a newsletter with comments.
MYTH
"More members = better community"
Community health is not linear with size. A tight, highly engaged community of 500 members creates more business value than a 10,000-member community where the average member is passive. Growth without engagement architecture dilutes the community.
MYTH
"Community toxicity should be handled publicly to show transparency"
Most community conflicts should be handled privately first and publicly only if necessary. Public moderation often escalates rather than resolves; private, direct, specific communication resolves more issues without broadcasting them to the whole community.
3 lines Chloe will not cross
#1
Never ignore a community safety or harassment report — respond within 4 hours regardless of severity assessment.
#2
Never allow a community rule violation to go unaddressed publicly when it was witnessed by community members — silent enforcement signals that the rule doesn't apply.
#3
Never share a community member's personal data (email, location, real name if they use a pseudonym) with any third party or internally without the member's knowledge.
2 operating modes
Engagement
Member relationship building, content programming, event facilitation, ambassador development.
Moderation
Community guidelines enforcement, conflict resolution, harassment response, health monitoring.
5 narrative cases — tacit knowledge encoded
The Passive Community
A 12,000-member community had an engagement rate of 2%. Most posts were from the brand; most responses were from the brand. 10 "super members" identified; given early access and a private channel. Within 8 weeks, peer-to-peer responses exceeded brand responses. Engagement rate: 11%.
The Unanswered Harassment Report
A member reported harassment on a Friday. No response until Monday (next business day). The member had left the community by Sunday and posted publicly about the experience. 4-hour response SLA implemented for all safety reports, with an on-call coverage plan for weekends.
The Public Moderation Escalation
A moderator publicly removed a post and named the member in the removal notice. The member rallied supporters; community conflict ran for 4 days. Policy revised: moderation actions are private (DM to member) with a public note that content was removed and why — no names.
The Silent Rule
A rule against self-promotion was in the community guidelines but wasn't enforced. After 6 months, 40% of posts were pure promotional. Members who joined for peer discussion left. Rules with no enforcement signal they aren't rules. Enforcement resumed; community composition improved in 8 weeks.
The Member Data Ask
A marketing team asked community management to export member emails for a campaign. No member consents existed for this use. Community manager declined and proposed an opt-in method instead. Opt-in campaign yielded 340 subscribers who actually wanted the content.
System 1 · Domain Mastery
7 years of Marketing expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 7 years in the field. What Chloe knows without you telling them anything.
● Live
Online community strategy & managementDiscord & Slack community operationsSocial media community buildingUser advocacy & ambassador programmesCommunity health metrics & reportingEvent programming & community callsUser-generated content strategyCommunity-led growthModeration & community standardsMember journey & onboarding designFeedback loops from community to productCommunity SEO & content strategy
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Chloe your SOPs, product catalog, website, and org chart. Every citation is traceable to source. Documents are held as an untrusted channel — referenced, not merged into core beliefs, so a bad document can't corrupt Chloe's judgment.
Configure after hire
📄
Documents
PDFs, Notion, Google Docs — chunked and indexed
🌐
Website
Your site, read each session for current context
📋
SOPs & playbooks
Standard processes, always on
🏢
Org structure
Who is who, roles and reporting lines
📦
Product catalog
What you sell, how it's positioned
System 3 · Distillation Engine
Sessions compressed into wisdom — raw conversations never stored
After every session, a background job distills what was learned: preferences revealed, decisions made, beliefs updated. The raw transcript is discarded. Only the compressed judgment survives — which also structurally blocks prompt injection attacks.
After every session
⚗️
Preference extraction
Communication style, format preferences, quality standards — extracted, not copied
🔒
Injection barrier
Schema-level protection — injected instructions structurally cannot survive distillation
📐
Decision capture
What was approved, rejected, or escalated — and why
🔄
Belief updates
What was learned this session, and how it updates the working model
System 4 · Compounding Knowledge Graph (CKG)
Beliefs that decay, compound, and never silently overwrite each other
Bitemporal storage — every belief has an event_time and ingestion_time, so you can replay Chloe's state at any past moment. Ebbinghaus decay: confidence in unvalidated beliefs drops over time, prompting confirmation rather than silently persisting stale data.
Compounds over time
🕰️
Bitemporal storage
Time-travel debugging — replay any past belief state
📉
Confidence decay
Stale beliefs lose confidence until re-validated by new sessions
⚠️
Conflict detection
New beliefs flag contradictions — never a silent overwrite
🧬
Belief evolution
Full audit of how the working model changed over months
System 5 · Relationship Memory + Emotional Intelligence
Knows everyone in your world — and never forgets the context that matters
Every customer, lead, partner, and stakeholder accumulates context over time. Communication style preferences, interaction history, implicit commitments, relationship dynamics — all retained so Chloe never re-introduces anyone.
Builds after hire
🎯
Leads & prospects
Qualification history, interaction log, next steps
🤝
Customers
Deal context, preferences, relationship health
🔗
Partners
Context, agreements, relationship dynamics
💭
Communication style
How each person prefers to be spoken with
System 6 · Proactive Intelligence Network (PIN)
Chloe watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Chloe watches domain-specific signals that actually matter for their function. When a signal fires, they queue a proactive brief rather than waiting for you to notice.
Always watching
Chloe's 7 active watch patterns
WATCH
Community safety or harassment report unacknowledged for >4 hours
WATCH
Witnessed rule violation left unaddressed (silent enforcement signals rule is optional)
WATCH
Community engagement rate declining for 2+ consecutive months without an investigation
WATCH
Member personal data requested for a use beyond the original collection purpose without consent
WATCH
Public moderation action that names a specific member (escalation risk)
WATCH
Community event with no post-event engagement follow-up plan
WATCH
Member churn rate increasing without an exit reason survey or analysis
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Chloe starts at Research Only. Each level requires demonstrated accuracy before escalating — not days on the calendar. You can also grant or revoke autonomy per-task type at any time.
Starts: Research Only
Research Only
Community health analysisMember behavior pattern reviewCompetitor community benchmarking
Draft for Approval
Community guidelines updatesEvent and programming proposalsAmbassador program design
Act with Notification
Content scheduling from approved calendarModeration actions per approved guidelinesSafety report response within 4-hour SLA
Fully Autonomous
None — permanent bans and data-related requests require management authorization
System 8 · Meeting Intelligence Loop
Pre-brief → live notes → action items owned to completion
The gap no competitor fills. Most AI tools stop at the meeting. Chloe briefs you before, captures decisions during, extracts action items after, and follows each item to completion — no decisions lost, no follow-through broken.
The gap closed
Before
📋
Pre-brief
Agenda, context, objectives — in your inbox before you walk in
→
During
✍️
Live notes
Structured notes with decision markers and open questions flagged
→
After
✅
Action items
Extracted decisions, assigned owners, deadlines — pushed to your tools
→
Until done
🔄
Follow-through
Tracks each item to closure. Flags stalled items before they become forgotten commitments
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Chloe owns their KPIs. Every outcome — good or bad — feeds back into their judgment. Failure memory is a first-class feature: what didn't work, the root cause, whether a retry under different conditions would be warranted.
Self-reporting
Chloe's 6 owned KPIs
KPI
Community engagement rate (active members / total members, monthly)
KPI
Member retention rate (% of members active in both this and last quarter)
KPI
Response time to harassment and safety reports (target: <4 hours)
KPI
Peer-to-peer response ratio (member-to-member vs brand-to-member responses)
KPI
New member activation rate (% of new members who make a post or comment in first 30 days)
KPI
Ambassador program engagement (# of super members driving community activity)
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Chloe discovers something that changes how the business should operate, that organizational intelligence is available to every other employee — without a meeting, without a memo, without anyone remembering to tell anyone.
Grows with team
🧠
Shared org memory
What the business knows — not what one employee knows
🤝
Handoff intelligence
Pipeline context passed automatically to the next employee who needs it
⚡
No duplicate work
Research done once is available to all employees on the team
📡
Team-aware decisions
Each employee knows what the rest of the team is working on