Release CLEA
The Release CLEA moment
Release CLEA is the first real step. You give CLEA a domain to monitor, and the workspace starts moving from setup into evidence collection.
At this stage, do not expect every dashboard panel to be full yet. Some data needs prompt runs, account context, and connected sources before it becomes useful.
Domain enters monitoring
The domain is the anchor for the workspace. CLEA uses it to connect visibility prompts, website checks, competitors, sources, and later content work.
Use the domain that should be judged by buyers. If your marketing site is the main source of truth, start there.
Domain anchor
The first release should center on the site buyers use to judge the company.
Workspace takes its first breath
After release, the workspace has a place to store prompt runs, chatlogs, suggestion cards, and setup context.
This is when CLEA becomes more than a blank assistant. It can start learning from the account data that arrives.
Release state
The workspace is ready when the domain, account context, and first evidence path are in place.
Runs that begin after release
The first runs are there to create a baseline. A baseline does not need to be perfect. It needs to be honest enough to show what CLEA can inspect next.
Visibility prompts
Visibility prompts ask buyer-style questions and check whether your brand, competitors, and sources appear in the answers.
These prompts are the start of AI visibility tracking. They are also the start of competitor discovery.
First agent prompt
An agent prompt can review the first available data and turn it into next steps. In a new workspace, this often means setup suggestions, prompt review, and readiness checks.
The agent is more useful after the first data exists. Before that, it can only reason from setup context.
Release domain
Anchor the workspace to one site.
Start prompts
Create the first visibility evidence.
Review setup
Check missing context and connections.
Open cards
Use first suggestions as the guided path.
Default suggestion cards
Early suggestion cards should guide the first session. They might point you toward AI readiness, Search Console, Google Analytics, prompt quality, or competitor setup.
Treat them as a guided checklist, not as final strategy.
Waiting for the first signal
The first waiting period is normal. CLEA needs prompt results before the dashboard becomes real.
While you wait, use the time to check account context and make sure the domain, market, and team access are correct.
Chatlogs arriving
When prompt runs finish, the answers are saved as chatlogs. These chatlogs are the evidence CLEA can later inspect.
If a run looks strange, keep it. Strange first results can reveal prompt quality problems or missing website context.
Chatlog arrival
First chatlogs give CLEA the evidence it needs to explain results later.
Dashboard panels filling in
The AI Visibility Overview, prompt results, source analytics, and competitor views become more useful as data arrives.
Some panels also depend on integrations. Search Console and Google Analytics will not be useful until they are connected.
First signal
Wait for prompt evidence before judging whether the dashboard is useful.
Useful setup before data lands
Before the first signal arrives, focus on things that do not require analytics yet.
- Confirm the primary domain.
- Add the most obvious competitors.
- Check team access.
- Add important workspace files if you already have them.
- Prepare to review the first suggestion cards.
Confirm domain
Make sure CLEA watches the right site.
Add competitors
Start with obvious names before discovery.
Check access
Invite people who review setup and cards.
Prepare review
Wait for prompt evidence before deeper action.
Successful release state
Release is successful when the workspace exists, the domain is clear, and CLEA has started or queued the first visibility work.
The next real milestone is not a full dashboard. It is the first useful loop: prompt evidence, first cards, chat with CLEA, and one action you can complete.