We read the threads your readers argue in, find the question that keeps coming back, and write the piece around it.
Grounded where your audience actually talks — not in a keyword tool
Every run does the same six things in the open. You watch each one land, and every number it leans on stays on the page.
We sweep Reddit, X, YouTube and the open web for threads on your topic, then score each one on upvotes, reply depth and how recently people were still arguing about it.
Hundreds of scattered complaints collapse into the handful of questions people keep circling back to. That cluster becomes the piece — not your best guess.
A go or a no-go, and the convergence figure behind it. When the demand does not hold up, the run tells you instead of quietly writing filler.
Keywords come out of the words real people used, ranked by how often they turned up next to real intent. No volume tool, no wishful padding.
Headline options and a section-by-section outline land before the draft does, so you can overrule the direction while it is still cheap to change.
The full draft in your voice, plus HTML, Markdown, SEO meta and JSON-LD — every claim still linked to the thread it came from.
Runs are metered in credits, and you only pay for the ones that finish. A run that fails costs you nothing — we absorb it.
87,200 credits, roughly nine complete runs. Nothing is held back on the small plan: the same demand mining, the same convergence call, the same publish-ready artifacts. Top up any time at 7,200 credits per dollar.
Start free210,000 credits, about a piece a day if you want one. Built for the writer or small team publishing weekly, with credits that roll into the next cycle and upgrades that grant the full difference straight away.
Choose Growth712,000 credits for agencies and content teams running several brands at once. Separate brand profiles, separate voices, one bill, and the evidence trail attached to every deliverable you hand a client.
Choose Scale
Most content tools start with a blank box and a confident tone. Ours starts with the argument already happening: the thread nobody answered properly, the question asked four hundred times, the answer everyone half-knows. We read that first, decide whether it holds up, and only then write. When a topic does not converge we say so and you keep your credits. When it does, you get a finished piece and the paper trail underneath it — the threads, the counts, the reasoning, all still linked.
Start a runContent Peddler is for people who publish under their own name and cannot afford to be wrong or dull. Three kinds of people keep coming back to it, and the run works the same way for all three.
See a sample run
You are the product, the support desk and the content team, and the blog is the first thing to slip. A run takes the topic you were already going to write about, checks whether anyone actually cares, and hands back a piece you would have needed a free Sunday to research. You still edit it. You just stop starting from nothing, and you stop publishing into silence. Runs are cheap enough to throw away, which is the point.
The questions are already in your Discord, your issues and your Stack Overflow tag, and they repeat. Content Peddler reads those threads directly, so the guide you publish answers the thing people got stuck on last week rather than the thing the roadmap says matters. Every claim keeps a link back to the thread, which makes review with engineers short and unarguable.
A calendar to fill, no research budget, and a stakeholder who wants to know why this post and not another. Runs give you both halves: enough finished pieces to keep the calendar honest, and a demand figure per topic you can put in front of whoever signs off. Scale keeps separate voices for separate brands on one bill, and the evidence file travels with the draft into the client review.
We kept writing posts that nobody had asked for. The research was the expensive part, the guessing was the demoralising part, and the tools on offer skipped straight past both. So we built the thing that does the reading first and shows its work — then writes.
Read the method
