One loop from your context to published content

Set your context once, gather the evidence, plan the work, then create, review, publish, and measure from the same system. Every item you publish makes the next one easier to plan.

300+ people across 35 teams run their weekly content through this cycle97% publish without a rewrite

Built so context compounds

Context gets lost between tools, sessions and handovers, so Eclipse is built on four principles that keep it.

Research and writing share one surface

The sources that shape an article, research findings, documents, community threads, and competitor pages stay connected to the drafts they inform.

Nothing is pasted between tools and lost on the way.

Evidence stays attached.

The evidence is ready when planning starts

Keyword demand, competitor movement, AI visibility, and community language sit in the same workspace as your planning.

You start from what is known, not from a blank page.

Your rules are set once

Tone, audience, exclusions, and editorial constraints live in a Content Profile and apply to every draft that follows.

You do not brief it again.

Gaps come back as briefs

Visibility tracking shows where competitors are cited and you are absent.

Each gap can be turned into planned, sourced work instead of a finding that sits in a report.

How one article gets made

These are the five stages an article goes through. Each one keeps the context the last one built, so nothing gets explained twice.

Before anything is written

You can see where every claim came from

Checking whether a confident paragraph was built on anything is the slowest part of reviewing AI drafts. Eclipse changes the order. The evidence is assembled first, then the draft is written from it.

Cortex is where the raw material collects. Bring in documents from your connected tools, run deeper research, and pull in community threads, transcripts, and competitor pages alongside your own notes.

How much you put on the canvas is up to you. Eclipse reads what is there and works out whether it is enough. Thin material gets topped up with its own research, competitor intelligence and outside references before anything is drafted. A full canvas is used as it stands.

When you generate an article from that canvas, it is written from a linked, named evidence base. Claims trace back to their sources. When someone asks where a paragraph came from, the draft already has the answer attached.

Reviewing instead of rewriting

Ask why it wrote something and it tells you

Reviewing a draft usually means checking every claim and rewriting half of it.

Eclipse cuts that down to the part that needs your judgement.

Because the draft was written from your own evidence base and your editorial rules, review starts from a different place. Open Justification Mode and the article sits beside the reasoning behind it.

Why the title was chosen, why each section exists, how keywords are used, and which sources support which claims. Click a justification and the relevant passage highlights in the text.

The question stops being whether to trust the draft and becomes whether this is the angle you want live. That decision stays yours.

Close the loop

Reports that end in briefs

Approved content goes out through your connected CMS and social channels without leaving Eclipse. Then the more useful work starts. You find out what moved, and what should be made next.

Eclipse tracks how your content performs where buyers actually look. Rankings and search demand, AI visibility across the engines buyers ask, community conversations, and competitor movement all land in the same workspace as your planning.

Weekly visibility reports name the query, the engine, and the competitor being cited where you are absent.

Elsewhere that finding goes into a slide and waits for the quarterly review. Here you can turn it into work. Carry it into Cortex with the relevant references attached, shape the angle, and generate a sourced draft for review.

The distance between “we are invisible for this question” and “there is an article in review that answers it” is one workflow, not one quarter.

Context that persists

Stop repeating yourself

Every session in a chat tool starts with pasting the tone document, explaining the audience again and listing what you would never publish.

In Eclipse that context is set once and stays.

Content Profiles hold the decisions that should not need remaking. Audience, product context, article type, angle, tone, exclusions and editorial constraints.

Set them once and every draft that follows is written within them.

New evidence is added on top. Competitor movement, keyword data, research. The foundations are not rebuilt.

Those standards survive handovers and new hires who never read the original brief.

For agencies, the same mechanism runs separately for every client. Each one gets its own profiles, rules and context, kept fully apart.

The loop compounds

Nothing gets thrown away when you publish

Most content workflows end at publish, which in Eclipse is only the halfway point.

Everything the work produced stays in the system. The sources that shaped the article are saved and reusable. The phrases you banned are now permanent rules.

The visibility data shows what the article changed, and where the next gap is. When you plan the next article, you are not starting again. You are starting from everything the last one taught you.

An article produced in Eclipse leaves its sources, its rules and its results behind for the next one.

Set the context once and every article after that uses it.

Proof it compounds

What teams see when the whole loop runs in one place.

0+

articles published

Planned, written, reviewed, and published through Eclipse in 2026.

0%

no rewrite

Articles that went live without a rewrite.

Run the loop on your next article

Every claim in the draft links to its source, and nothing publishes until you approve it.