Your AI Marketing Team.
Works While You Sleep.
Cohort assembles a team of specialist agents -- content monitor, analyst, strategist, writer, campaign orchestrator -- into an autonomous pipeline that turns RSS feeds into publish-ready content overnight.
Monday Morning: Before vs. After
Without Cohort
- [1] Check 12 RSS feeds manually
- [2] Read 40+ articles, pick 3 worth sharing
- [3] Draft a blog post from scratch
- [4] Reformat for LinkedIn, Twitter, Reddit
- [5] Write newsletter snippet
- [6] Schedule everything across platforms
With Cohort
- [1] Open inbox -- briefing + drafts waiting
- [2] Review pre-scored article picks
- [3] Skim blog draft, light edit
- [4] Approve social bundle (already formatted)
- [5] Hit publish
- .
The Pipeline
Five agents, one schedule, zero manual steps. This runs every night.
Content Monitor
Fetches your configured RSS feeds nightly. Deduplicates against article history. Stores new entries in the intelligence database. No human input needed -- runs on cron.
Analysis Agent
Scores each article on relevance, timeliness, novelty, and seasonal fit. Extracts key claims, tags categories, flags trending topics. The filter between noise and signal.
Content Strategy
Selects top articles and plans the content bundle. Decides angles, maps to platform formats, drafts blog posts (600-1000 words, SEO-optimized). Proposes -- never asks open-ended questions.
Content Writer
Polishes drafts, adds context and transitions, adapts tone for each platform. LinkedIn gets professional insight, Twitter gets punchy hooks, Reddit gets community-native voice.
Campaign Orchestrator
Coordinates cross-channel timing, tracks campaign KPIs, manages A/B test variants. Compiles the executive briefing so you see results, not raw data.
01:00 AM content_monitor Fetch RSS feeds, deduplicate, store new articles 01:30 AM analysis_agent Score relevance, extract key claims, tag categories 02:00 AM content_strategy Select top articles, draft blog posts + social bundles 03:00 AM content_writer Polish drafts, adapt tone per platform 06:00 AM campaign_orch Compile briefing, queue drafts for human review 06:01 AM [COMPLETE] 3 blog posts, 9 social posts, 1 executive briefing
Not Another AI Writing Tool
Most AI marketing tools are chatbots with a text box. Cohort is a pipeline.
Pipeline, Not Chatbot
Runs on a schedule without human prompting. You don't type "write me a blog post" -- the system identifies topics, drafts content, and formats output autonomously.
One Source, Five Formats
One trending article becomes a blog post, LinkedIn update, Twitter thread, Reddit comment, and newsletter snippet. Each adapted to the platform's native tone and format.
Intelligence-Driven
Topics come from real RSS feeds, industry news, and trend data -- not from a blank prompt. The analysis agent scores relevance before a single word is drafted.
A Team, Not a Tool
Five specialist agents with distinct roles -- monitor, analyst, strategist, writer, orchestrator. This mirrors how a real marketing department operates.
Domain-Aware
Configure industry-specific RSS feeds and seasonal calendars. The pipeline knows when to push winterization content vs. spring opening guides -- because your domain tells it.
Runs on Your GPU
Local inference via Ollama or llama.cpp. No per-token API charges. Produce 100 social posts a month for the same cost as producing zero: your electricity bill.
What You Wake Up To
Real output from the pipeline. Not mockups -- these formats are generated every night.
Why Your Freeze Protection System Needs a Backup Plan
Last week, a polar vortex caught the Southwest off guard. Pool owners who relied on single-point freeze sensors woke up to burst pipes and cracked filters. The damage: $2,000-$8,000 per pool.
But here's what the insurance claims don't tell you: most of these systems were "working." The sensor read 35F. The pump turned on. The problem? The sensor was in the wrong spot -- measuring ambient air while the plumbing froze six feet away...
[Draft continues for ~600 more words with subheadings, actionable tips, and subtle product mention]
How It Fits Your Workflow
Configure Your Feeds
Add industry RSS feeds, subreddits, and news sources to a YAML config. Set seasonal calendars if your content has cyclical timing (spring campaigns, holiday pushes, regulatory deadlines).
Set the Schedule
The pipeline runs on cron -- default is nightly at 1 AM. Agents execute sequentially: monitor, analyze, strategize, write, compile. You wake up to finished work.
Review and Publish
Open the executive briefing for an overview. Skim the drafts. Make light edits if needed. Approve the social bundle. Total time: 20-30 minutes for a full week of multi-platform content.
See It In Action: A Real Run
This is not a hypothetical. On March 9, 2026, the pipeline ran against live RSS feeds. Here is exactly what happened at each step, using real logs and real output.
Step 1: Content Monitor fetches RSS feeds
The content monitor hit 7 feeds on its first run of the day. This is the actual log output:
[09:00:02] [>>] Starting rss_fetch [09:00:03] [OK] Fetched 25 entries from r/pools [09:00:04] [OK] Fetched 25 entries from r/swimmingpools [09:00:05] [OK] Fetched 25 entries from r/PoolPros [09:00:06] [OK] Fetched 25 entries from r/hottub [09:00:07] [OK] Fetched 25 entries from r/HomeImprovement [09:00:12] [OK] Fetched 10 entries from Pool & Spa News [09:00:13] [OK] Fetched 10 entries from Pool Magazine [09:00:15] [>>] Web search supplement: 2 new articles [09:00:17] [OK] Fetched 7 new articles (138 duplicates filtered)
145 entries checked across 7 sources. 7 were new. The rest were already in the database from previous runs.
Step 2: Analysis Agent scores and tags
The analysis agent scored 24 articles on relevance (1-10), extracted key claims, and tagged interest categories. Here are two real entries from the articles database:
Step 3: Content Strategy picks a source and plans the bundle
The strategy agent flagged this Reddit post from r/pools as high-value content -- 529 upvotes, 342 comments, strong pain-point signal:
The strategy agent identified this as high-relevance (score 5/10 = threshold for drafting) and queued it for the post drafter with template: "problem_solution".
Step 4: Content Writer drafts platform-specific posts
From that single Reddit thread, the post drafter generated 2 posts in 3 seconds. These are the actual drafts -- unedited, as stored in the system:
Part sourcing problems waste time and money.
Real story from r/pools today.
PartSpec AI makes parts identification instant:
- Photo recognition
- Part number lookup
- Price comparison
- Direct ordering
Quick ROI calculation for pool service businesses:
Time wasted per technician per week:
- 2 hours searching for parts = $150
- 1 wrong part ordered = $75
- 0.5 extra trips = $50
Total weekly waste: $275/technician
PartSpec AI savings:
- Instant part identification = 2 hours saved
- Photo verification = No wrong parts
- Order integration = No extra trips
Annual savings per technician: $14,300
System pays for itself in the first month.
4 posts (2 Twitter, 2 LinkedIn) generated from 2 source articles in 9 seconds total. Each post is stored with full provenance: source URL, template used, pain points detected, relevance score, and approval status.
Step 5: Agents discuss strategy in the team channel
Meanwhile, the content intelligence feeds into SMACK team channels where agents coordinate strategy. Here's a real exchange from the content planning channel:
This is the real discussion from the SMACK internal chat. Agents coordinate asynchronously -- each contributing from their domain expertise. The email agent focuses on conversion triggers, the documentation agent focuses on technical credibility, and BOSS orchestrates the workflow.
End Result: March 9, 2026
Total human involvement: zero. Everything above ran on a cron schedule against a local 9B parameter model on a single GPU. The drafts sat in a queue marked "pending review" until a human opened them the next morning.
Stop Writing Content.
Start Publishing It.
Open source. Self-hosted. Your GPU, your data, your content pipeline.