Help center
Open dashboard

Getting The Most Out Of The InnerCircle

Six specialists who review your work, then do it — and how to get the most out of each of them.

Atarim team Updated 21 Oct 2026 · 15 min read
Atarim AI
The Atarim InnerCircle expert picker with the AI agent roster
Before you start

Relevant for

  • Anyone using the AI side of Atarim.
  • Anyone who wants a second opinion on a page.
  • Anyone who wants the work done rather than just flagged.

Required knowledge

  • Familiarity with projects and tasks in Atarim.
  • No specialist background needed — you describe the problem and the right specialist picks it up.
  • Comfortable reviewing an approval before accepting it, since applied changes affect a live site.

Tools & resources needed

  • An active project with credits available. Credits come from one shared workspace pool covering checks, chat and the work itself.
  • For the specialists to change a site: the Atarim WordPress plugin, on WordPress 6.9 or later with PHP 8.0 or later.
  • A filled-in brand kit — without it, design and copy work is generic.
  • A sentence of context before each check. It's the single biggest influence on how useful the results are.

The InnerCircle is six specialists. Five do the work — design, copy, SEO, accessibility, bugs — and one coordinates them. They'll review a page and tell you what's wrong, and they'll make the changes when you ask. Both halves matter, and most people only ever meet the first.

Who they are

SpecialistOwnsReaches them when you mention
PixelDesign, brand and visuals. Also builds — logos, images, sections, whole pages.How something looks, or nothing in particular.
LexiCopy and tone. Also writes — posts and proposals.What something says.
IndexSEO, structure and page speed.Search, ranking, or why a page is slow.
NaviAccessibility and usability.Contrast, keyboard use, screen readers, mobile.
GlitchBroken links, missing assets, faulty forms.Anything broken or not doing what it should.
ClaroCoordination. Turns vague feedback into clear work and directs the others.Nothing — Claro is who you talk to.
Note
Two kinds of specialist. Pixel and Lexi are the makers — an open question about an element goes to one of them, because most requests are about how something looks or what it says. Index, Navi and Glitch are the lenses — they take over when their concern is the actual subject. “Does this headline land?” is Lexi. “Can a screen reader use this?” is Navi.
Tip
You don’t assign them by hand. Describe the problem and the right specialist picks it up — naming them is only useful when you want a specific lens on something that would otherwise go elsewhere.

The two halves

ReviewingDoing
What happensThey inspect and report.They make the change.
Your siteUntouched. A review writes nothing, ever.Changed when you ask for it.
How it startsYou run a check.You ask for the work.
Warning
A review never turns into a change on its own. Nothing on your site moves because a specialist thought it should. Doing is always a separate request, and site changes that need sign-off wait for your approval.

Where they work

Five places, behaving differently in each. Most people only meet the first.

WhereWhat happensCan they change things?
Page checksA full pass over a page, section by section, plus full-page screenshots compared at desktop, tablet and mobile widths.No. Read-only.
On the pageSelect an element, ask about it, get an answer about that element.Yes — Show me previews it, Do It keeps it.
In a taskA specialist works inside a task and comments the result.Yes.
Workspace chatClaro coordinates work across every project and site you manage.Yes, through the specialists.
On a scheduleRecurring work that runs without anyone starting it — a monthly sweep, a check after every update.Yes, through the specialists.
Note
You schedule the work, not the specialist. A workflow creates a task when it runs and puts the right specialist on it, and they work it exactly as they would a task you opened yourself. Everything the run does is recorded on that task, so a recurring check leaves a trail you can show a client. Each run costs 10 credits, plus whatever the AI work in it uses.
Note
Where you won’t find them. The Inbox isn’t a separate place they work — it’s where you find task threads, and choosing Send to Claro there, or @-mentioning a specialist, is the same as asking in the task. Boards are the other way round: findings are ordinary tasks, so they move across a board like any other work, but nothing is analysed there. The project dashboard’s chat panel is Claro’s rather than the specialists’.
Warning
Changes only save on a connected WordPress site. On a site without the plugin, Do It saves nothing; only Show me works, and its live preview disappears on refresh. Useful for showing a client what you mean; not work that’s landed. Explore the WordPress Plugin.
Note
Applying a change is currently supported on WordPress, marked Beta while it settles. Lovable, Bolt and Webflow are listed as coming; on a site without the plugin, hovering Do It shows that list. Everywhere else you still get the advice and the change described, and apply it yourself. They advise on any site, anywhere — they only save changes on WordPress 6.9 or later and PHP 8.0 or later, with the plugin connected. If Do It is greyed out on a WordPress site, hover it to see why. The message is one of these:
  • Log in to your WordPress to use Do It
  • Your WordPress account can’t edit this page
  • Do It is turned off in the Atarim plugin settings
  • Do It works on individual pages and posts, not on listing pages like the blog or archives
  • Update the Atarim plugin to use Do It
  • Do It isn’t available on this page

Asking on the page

The quickest way in. Select any element and ask about it — the answer is about that element, not the page in general.

Instructions:

  1. Open a project from Projects in the visual collaboration view.
  2. Select the element you want to ask about.
  3. Type your question — “what do you think of this footer?”, “make this button clearer” — and select Send to Claro. The right specialist answers, based on what you asked about.
  4. Where they propose a change, use Show me to see it and Do It to keep it.
Lexi's reply on the Plausible headline with suggested copy and Show me and Do It buttons
Asking about an element and getting the specialist’s answer
Lexi's headline finding with the Show me preview applied to the Plausible hero heading; the arrow points at Hide the preview
Previewing a suggested change with Show me
Tip
Follow-up questions work well. “Can this CTA be more compelling?” after a general answer gets you something far more specific than asking cold.

Running a full check

The description you add is what steers the specialists, so a vague one produces vague findings.

Instructions:

  1. Open the page and open the Review tab in the sidebar.
  2. Choose a preset, or pick the specialists yourself with Custom. A preset fills in the description and replaces anything already typed there.
  3. Add a short description of what you want them to focus on. This is the single biggest influence on how useful the results are. Review This Page stays unavailable until there is a description.
  4. Select Review This Page. Claro reads the page and posts a Strategic Overview first.
  5. Read the overview, then select Start Review under Ready to include the InnerCircle? to bring in the specialists. The rest runs in the background. To have a check run straight through, switch off Ask me before Claro invites the full team when you choose the specialists.
Agent picker with Navi and Lexi switched on for the Increase conversion rate preset
Choosing the specialists after picking a preset
Increase conversion rate preset with Navi and Lexi switched on and Review This Page hovered; the arrow points at Review This Page
Starting the review with Review This Page
Claro scanning the page in the Review tab, with Stop below
Claro scanning the page

Full detail in How to Run an AI-Powered Page Review.

Recommendation
Always write the description. “Check this before it goes to the client on Friday” and “we’re trying to get more demo bookings” produce genuinely different reviews of the same page.

What happens when a check runs

Four stages, in order:

  1. Strategic Overview — Claro reads the page and reports back before anyone else starts. Unless you switched the pause off, the specialists start when you select Start Review.
  2. Team handoff — the specialists receive their instructions.
  3. On-page comments — findings appear pinned to elements.
  4. Summary and next steps — what was found and what to do about it.
Claro's Strategic Overview in the review task thread
Strategic Overview: Claro reads the page first
Claro's Team Handoff in the review task with the @Pixel brief expanded; the arrow points at Pixel's instructions
The specialists receive their handoff
Navi's contrast finding open on the page with the review's numbered pins grouped on the hero; the arrow points at the pins
Findings pinned to the elements they relate to
Claro's All done, Emma summary in the review task Comments, opening with Overall Impression; the arrow points at Overall Impression
Summary and next steps
Note
The specialists read a full snapshot of the page — how it’s built, how it looks, what it says, the behind-the-scenes details that decide how it shows up in search, and which screen size, browser and device it was seen on. The sections of the page are worked in parallel rather than one after another, but a check is a background job rather than an instant one — findings populate as each pass finishes. Once the specialists start, carry on with something else; you don’t need to keep the tab open.
Tip
You can stop a check while it’s running with Stop. Anything already found stays and nothing further is generated.

Reading the results

Findings appear as tasks pinned to the elements they relate to, alongside a high-level summary of the page. When the check finishes, you can download the whole review as an AI Review Cycle PDF from the review task in the Inbox, and a report is saved to Artifacts.

PriorityWhat it coversDo It
Critical (red)Things blocking the main action on the page.First.
High (orange)Things affecting conversions and clarity.Next.
Medium (yellow)Usability and hierarchy improvements.After those.
Low (green)Cosmetic refinements — line breaks, minor typography.When there’s time.
Priority menu open on Navi's finding with Low, Medium, High (selected) and Critical; the arrow points at the priority list
Findings with prioritization
Navi's finding Secondary CTA Contrast Compliance with Current, Solution and Impact beside the Subtasks list; the arrow points at it
Findings appear as tasks on the page
Tip
Every finding carries a device marker — hover it and it tells you which screen size the fault was spotted at. One page routinely produces findings across all three, and fixing the wrong breakpoint is the usual way time gets wasted.
Note
Reviews detect elements inside complex and nested layouts, so you may see more findings than you expect. That’s coverage rather than noise — work down the priority order and it stays manageable.

Acting on a finding

When the review finishes, every finding becomes its own task, pinned to the element it relates to. Findings that can be fixed for you come with a Do It ready. Nothing is applied to the site. You decide which ones to act on.

Instructions:

  1. Open the finding on the element it’s pinned to.
  2. Select Show me to see the change applied to the page in front of you. Nothing is committed. Toggle it off to compare against the original, or regenerate it if it isn’t what you meant.
  3. Select Do It to apply it for real. Your own click needs no approval: it queues and runs in the background. When it has applied, the task moves to Pending Review and an Undo control appears on that comment. When you ask Atarim to apply findings for you, a change to a published, private or scheduled page waits for your approval first; drafts run straight away.
  4. Work through the rest in priority order.

For the Do It Queue, undoing a change and what a page needs before you can apply a change, see What Do It Can Do on the Site.

Lexi's intro copy finding with the Show me preview applied to the paragraph under the headline; the arrow points at Hide the preview
Previewing a change with Show me
Glitch's finding with Do It hovered, opening WordPress (Beta), Lovable, Bolt and Webflow (Coming soon); the arrow points at Do It
Applying a change with Do It
Tip
Read a review through once before applying anything. A long list feels like forty jobs until you’ve seen which eight actually matter, and the priority order is there to tell you.

Credits

AI work uses credits from your workspace’s pool, shared across everything — checks, chat, and the work the specialists do. A check costs 10 credits for each screen-height section of the page, plus 10 for Index’s metadata pass when Index is in the check, so a long page costs more than a short one.

Note
Credits are checked before a check begins. If the workspace is out of credits, or a client’s monthly credits are used up, the check doesn’t start, so it never stops partway through. You can see what’s left in Settings › Credits & Usage. Explore Credits & Usage.
Tip
Credits are shared across everyone in the workspace. If several people run checks on the same day they go faster than expected, so it’s worth a word with the team before a big pass.

Turning vague feedback into work

When a comment arrives that nobody could act on — “make this pop”, “something feels off” — Claro offers the person three specific options to choose from, rather than guessing on their behalf.

Note
Clarification is visible to whoever left the feedback, including clients. It has to be — they’re the one who knows what they meant. Explore Clarify Feedback Instantly with Claro.
Tip
Tell clients to leave feedback however it comes out. Vague input is what Claro is for, and asking them to be precise just makes them hesitant to comment at all.

How they work together

Most real problems cross domains, and the specialists hand off between themselves rather than each answering in isolation.

A worked example. A client leaves “fix this section.”

  1. Claro turns it into a clear brief and routes it.
  2. Pixel looks at the layout and spacing.
  3. Lexi sharpens the wording.
  4. Navi checks the contrast and whether it’s usable.

One vague sentence becomes work in four domains, without you sorting it.

Note
Where a check raises something beyond routine work, it comes back scoped and quoted rather than quietly absorbed. Explore The Upsell Machine, and Collaborate with AI Inside Strategic Overview for the wider picture a review produces.
Recommendation
Run several specialists together rather than one at a time. A section usually reads badly and looks unbalanced for the same underlying reason, and fixing one without the other rarely settles it.
What they remember between jobs
Your experts read a workspace memory on every job, and a project’s own memory as well when they are working on that project. Both are edited at Settings, then AI Web Agency, then Memory. See Managing Your Account Settings for what each one holds and who can change it.

What they won’t do

They won’tWhy it matters
Change anything during a reviewReviews are read-only. Always.
Publish without approvalSite changes needing sign-off wait for your decision.
Take a live page downRebuilds are staged as a draft and swapped in once, on approval.
Invent factsNo statistics, testimonials, prices or brand values that didn’t come from your brief.
Replace your teamThey catch what gets missed and do the repetitive half. Judgement is still yours.
Note
Changes can be put back — a single element from the copy saved beforehand, a page through WordPress’s own version history, and a whole site only from a backup plugin installed on it.

Working with a reply

Every AI answer carries controls beneath it. Alongside Show me and Do It you can copy the response, and rate it a good or bad response with the thumbs — that rating is how the specialists get better at the work you actually do. While a reply is still being written, select Stop to end it. What was written so far stays, marked Stopped.

The composer has a Send to Claro button beside a Comment / Add a note split button. Comment posts normally. Send to Claro brings the AI in, and the right specialist answers. Add a note posts internally, visible to Admins and Team Members only. Notes depend on your plan. On a plan without them, Add a note shows the upgrade options instead of posting. To hide the whole task from guests and clients, select the internal icon at the top of the task (tooltip Set internal task). Select it again to share it once it’s ready.

White-label behaviour

Note
In a white-labelled workspace the specialists write on your agency’s behalf. Anything they produce for a client goes out in your agency’s name and voice, not Atarim’s.
Recommendation
Run a check on a live page and see what comes back. One pass covers design, copy, SEO, accessibility and bugs, compares full-page screenshots at desktop, tablet and mobile widths, and changes nothing until you ask. Explore How to Run an AI-Powered Page Review.

Frequently asked questions

Do I need to install anything?

Not to review. To let the specialists change a site, it needs the Atarim WordPress plugin, WordPress 6.9 or later and PHP 8.0 or later.

Do I have to choose which specialist answers?

No. Describe the problem and the right one picks it up. You can select them by hand before a check if you want a particular lens.

Can they change my site during a review?

No. Reviews are read-only. Making changes is a separate request, and anything needing sign-off waits for your approval.

Can clients see the AI?

Clients see feedback clarification on their own comments, because they’re the one answering it. To keep a task and its replies from guests and clients, make the task internal with Set internal task.

What’s the difference between Show me and Do It?

Show me previews the change on the page in front of you — you can toggle it off to compare, regenerate it if it isn’t what you meant, and screenshot the result into the thread as a comment. Do It applies it for real, queuing and running in the background, after which an Undo control appears on that comment. On a connected WordPress site, Do It writes the change properly.

How do I turn a finding into actual work?

Use Show me to preview the change and Do It to apply it. Applying one moves the task to Pending Review and leaves an Undo control on that comment if you change your mind.

Do checks use credits?

Yes, from one shared workspace pool covering checks, chat and the work itself. A check costs 10 credits for each section of the page, plus 10 for the metadata pass when Index is in the check. If the workspace is out of credits, or a client’s monthly credits are used up, you’re told before a check starts.

Can I run a review more than once?

Yes. Each run looks at the current version of the page, so re-running after a round of fixes shows what’s left.

Do they only review, or do they build things?

Both. Pixel builds logos, images, sections and whole pages; Lexi writes posts and proposals. The other three fix within their domains.

Do they find JavaScript errors?

Not as a separate check. Reviews read what is visible on the page. Index does run a separate pass over the page’s metadata.

Does this replace my QA or my designer?

No. They catch what gets overlooked and handle the repetitive half. The judgement, the client relationship and the final call stay with you.

Common issues

  • A specialist you wanted didn't take part — the preset didn't include them. Use Custom and pick them directly.
  • Results feel generic — add a description before running the check, and set up the brand kit. Both change the output substantially.
  • More findings than expected — detection reaches into nested layouts. Work down the priority order rather than top to bottom.
  • A change vanished on refresh — that was a Show me preview, which is never saved. Use Do It on a WordPress site connected through the plugin to keep a change.
  • A check won't start — the workspace may be out of credits, or the client's monthly credits may be used up. You're told before it begins rather than partway through.
  • There's no Review This Page button — collaborators and guests can't start a check. Ask an Administrator or Team Member to run it.
  • A check ends with “This review couldn't finish” — something went wrong, or the check was stopped. Select Start a new review to run it again.
  • Nothing changed after a review — expected. Reviews never change anything; ask for the work separately.
  • A fix is waiting and hasn't applied — a change you asked the AI to apply to a published, private or scheduled page waits for your approval. Read it, then decide. If nobody decides within 14 days, it is declined automatically.
  • Nothing can be changed at all — check the site is on WordPress 6.9 or later and PHP 8.0 or later, with the plugin connected.

Conclusion

The InnerCircle is most useful when you stop treating it as a review tool. Reviewing is the visible half; the specialists will also write the copy, build the section, fix the link and repair the contrast — when you ask, on a page that stays up, with a way back if it's wrong.

The two things that most change what you get out of them: a filled-in brand kit, and a sentence of context before each check. Both take minutes and both affect every result afterwards. Explore Agency Brief: Building Your Brand Kit.

Tips & best practices

  • Write a description before every check — it changes the results more than anything else.
  • Set up the brand kit; without it, design and copy work is generic.
  • Read the whole review before applying anything — work the priority order, not the page order.
  • Check the device marker before fixing — it may only fail on mobile.
  • Run several specialists together; problems rarely sit in one domain.
  • Ask for the work, not just the review. That half is easy to miss.
  • Use Show me in front of clients rather than describing a change.
  • Connect the plugin before a working session, so changes save.
  • Let clients leave messy feedback — clarification is built for it.

Related articles