Flywheel

Sign in
Private beta

Community marketing,
run by agents you trust.

Flywheel watches the corners of the internet your customers actually live in, surfaces the threads worth answering, and drafts replies in your voice. You approve every post. Real accounts, human cadence, no surprises.

Sign in to continue→Invite-only for now.

The loop

Five steps. One queue. Always.

Every reply your team posts moves through the same predictable pipeline — discoverable, auditable, and quietly relentless.

1
Scout finds the threadScans the communities you care about, scores each thread for relevance using AI, drops the worthwhile ones into your queue.
↓
2
Caretaker drafts the replyComposes in your product’s voice using your content API, then validates against your strategic objectives. Nothing off-message gets through.
↓
3
You approveEvery post is reviewed by a human before it goes out. Edit, approve, or reject — the queue never moves without you.
↓
4
Cultivator routes itPicks the right account from your pool, applies per-community rate limits, paces posts 3–8 minutes apart on a human cadence. Karma-aware. IP-rotated.
↓
5
Browser Agent posts — and Thread Watch listensHeadless Chrome handles the actual posting. When someone replies, the conversation comes back into the queue as a follow-up opportunity. The cycle continues.

Who does what

Four agents, narrowly scoped.

Each agent does one job well. Together they keep the loop turning without ever stepping on each other’s toes.

Sees

Scout

Watches every configured community on a schedule. Scores threads with an LLM, filters by your topics and keywords, only queues what’s actually worth answering.

Writes

Caretaker

Composes replies through your product’s own content API, so the voice belongs to you. Cross-checks every draft against your strategic marketing objectives.

Routes

Cultivator

Manages the account pool. Assigns posts to eligible accounts based on tier, karma, and history. Enforces rate limits and rotates IPs through WireGuard.

Acts

Browser Agent

Stateless executor. Receives a post task, drives a real Chrome profile via Playwright, returns the result. Replaceable, predictable, dumb on purpose.

What’s in the box

One engine. Many products.

◍

Multi-product, multi-tenant

Run as many products as you want from a single workspace. Each has its own voice, communities, accounts, and queue.

↺

Follow-up replies

When someone replies to your comment, the full conversation comes back highlighted in the queue with one-click approval for a follow-up.

◎

Conversion attribution

Every post carries a campaign token. When a visitor signs up, the conversion fires back to Flywheel and closes the attribution loop.

⌬

Account pool with karma awareness

Real accounts with real history. Cultivator tracks karma per community, warms cold accounts, and never asks one to do more than its tier permits.

⏱

Patient by design

Posts are spaced 3–8 minutes apart with random jitter. Cron jobs run on the hour, not on impulse. No flood, no spam patterns.

◇

Pluggable voice

Bring your own content API and your product owns its voice end-to-end. Or fall back to voice guidelines configured in the admin UI.

Quietly opinionated

The principles, in plain English.

—

AI proposes. Humans dispose. Every post is reviewed by a person. We don’t trust models with the send button.

—

Patience beats velocity. Posts are paced. Communities notice when bots flood; they don’t notice when a thoughtful voice shows up once a day.

—

The codebase has zero product knowledge. Voice, strategy, and communities live in configuration. Move fast across products without forking the engine.

—

Real accounts, real conversations. Personas map to actual people. The goal is to be useful in the room, not to spam it.

—

Boring infrastructure on purpose. Cron jobs, Postgres, Playwright. Nothing exotic. The interesting parts are the agents and the queue.