CONTENT HAS TO EARN ITS KEEP
Eclipse turns research into content, gets it through review, and records what happened after publication. Here is the evidence so far.
Teams run their weekly content cycle through Eclipse, with 300+ people working in them.
AI engine responses analysed across live accounts, re-run automatically every week.
Hours to a first published article for most teams after onboarding.
How these numbers are measured
Each account tracks the buyer questions it wants to be found for. Those questions go to ten AI engines every week, and we record which answers name the brand. A citation is the brand named in an answer; a link is not required for it to count.
The 34% covers the first 11 accounts to reach 90 days on Eclipse, measured on ChatGPT, which is where the sample is deepest. Each account is compared with its own first week rather than with a control group, so the figure shows what changed over those 90 days rather than what Eclipse caused on its own. Search demand, a funding announcement or a competitor’s own publishing all move the same number.
Eleven accounts is a small sample and we would rather say so than round it into something vaguer. We will restate it as more accounts pass 90 days.
We work behind the scenes
Most of our clients are agencies and content teams who publish this work as their own. Their edge is that it reads as in-house, so they do not hand out logos or named quotes, and we would never ask them to. That discretion is the job. This is what we can share.
Eclipse was the first time the draft came back sounding like us, because it had actually been built from our material, our tone rules, and research I could see. I still review everything before it goes out, but reviewing is a very different job from rewriting. It replaced three of our subscriptions and most of a freelancer.
Before Eclipse, our content workflow was spread across six different tools and three separate AI subscriptions. Now everything lives in one place: keyword research, Search Console data, drafting, and our entire social calendar. We cut our software spend by about 40% and our team actually enjoys publishing content on schedule. It is the first tool that treats content as an operation, not a series of disconnected tasks.
As an agency juggling a dozen clients, visibility was our biggest headache. Eclipse gives us live analytics and keyword tracking per client, drafts we can actually build on, and social management all under one login. We onboarded our whole team in a week and now upsell our clients to Reddit management. It has become the backbone of how we run every account.
The operation remembers
The strongest result is not a single output. It is a team that can see why the work was made, what happened next, and what the next move should be.
Research remains visible
Editors can see the evidence behind the argument instead of checking every claim from zero.
Review becomes a decision
Teams approve, revise, and publish from one workflow with the context still attached.
The next brief inherits the work
Approved knowledge, content rules, performance, and market context stay available for the next asset.
Put one workflow to the test
Bring a current article, campaign, or client process. We will show you how the evidence and decisions move through Eclipse.
