Features · What to do about it
An AI that reads your analytics and names the fix
Most analytics tools give you charts and leave the reading to you. Clerion does the reading. It finds the patterns in your traffic, conversions, errors and speed, writes a briefing on what changed and why, ranks every change by impact, answers questions in your own words, and writes the documents you would have had to write from the numbers. Every figure comes from your data; the model never types one.
The briefing
Open the Overview and the briefing is already written: one line on top, then what changed, why, and the one fix to make first, ranked by the goal you set for the site. Click any sentence and the numbers behind it open. It is rewritten when your numbers move, not on a timer, and if a rewrite fails you keep the last good one.
Tell Clerion what the site is for in a sentence, and pick an industry from ten presets, and every finding is ranked against that.
Signals
Every change on your site, ranked by impact: a traffic spike, a drop-off, a page that stopped converting, a new country, a slow page, a dead end. Each one is a line under the chart with the biggest change first, and each links to the sessions behind it.
Ask Clerion
Press ⌘K and type the question: why did trial starts fall last week, where do Perplexity visitors land, what broke on the 8th. The answer comes from your own data and shows the pages it came from. Ask for a plan and it is built from your numbers, not a template.
Written work
Ask for the traffic section of your investor update and it is written with exact numbers: sessions, growth, signups, and the one thing that changed. Ask for the meta descriptions your pages are missing and they are drafted from each page, ready to paste. Ask which bug to fix first and get a ticket with steps, the likely cause on your stack, sessions affected and the breadcrumbs.
No made-up numbers
The model chooses which metric matters and writes the sentence. Clerion fills in the figure from your data. A briefing cannot contain a number that is not in your analytics, and every claim clicks through to its evidence.
Your own model
Connect Claude, Cursor or any client that speaks MCP, and it reads the same figures as seven read-only tools, where you already work. Aggregates only, never visitor rows. On Growth and above, and in every trial. How to connect.
Limits
| Limit | What it means |
|---|---|
| Your site's data | The briefing reads what the snippet collects and what you import. It does not read your product's database, your CRM or your bank. |
| An allowance per plan | Briefings and answers count against a monthly AI allowance shown in Usage. MCP calls do not; they are database reads. |
Questions
Where does my data go?
Aggregate statistics, counts, shares and rankings, go to the model for the question at hand. Individual visitor rows never do. Everything is stored in the EU.
Can the briefing be wrong?
It can misjudge what matters, and you can tell it your goal to fix that. It cannot invent a figure: every number comes from your data, and every claim opens its evidence.