Documentation

Everything SimulateCX
can do today.

Command reference, workflow guide, and billing — all in one place.

How every edit works

01

Type your request

Use a slash command or describe what you want in plain English. Commands give the AI more precision; plain English works too.

02

AI proposes changes

Claude reads your site files, makes the edit, and returns a diff. Usually 5–30 seconds depending on complexity.

03

Preview before approving

Click Preview (page) to see exactly how the page will look — scripts disabled, full layout rendered. For SEO changes, see a live snippet preview.

04

Send to UAT (optional)

Deploy to a private Firebase preview URL to test on the real hosted version. Useful for layout-sensitive changes. Same URL every time — no new channels created.

05

Approve → PR opens

One click opens a GitHub PR from the edit branch to your main branch. Review the diff there if you want.

06

Merge → site goes live

Merging the PR triggers your production deploy workflow. Your live site updates within ~1 minute.

Command reference

Billing at a glance

You pay for the AI processing behind each request — measured in tokens. Simple changes use Haiku (fast, inexpensive). Complex work uses Sonnet (more capable, costs more). No subscription. No maintenance fee.

ChangeModelEst. cost
SEO metadata update (/seo)HaikuCents
Navigation or contact update (/nav, /contact)HaikuCents
Testimonial (/testimonial)HaikuCents
Page copy rewrite (/page)Sonnet< $1
New blog post with full SEO (/blog)Sonnet$1–3
Integration embed (/integration)Sonnet< $1
Page duplicate (/duplicate)Sonnet$1–2

Exact cost shown in the usage badge after each request. Month-to-date total always visible in your console top bar.

Coming next

Features in active development. Vote on what matters to you in the Ideas Lab.

Site health dashboard (Lighthouse scores)/scan — broken link detectionContent scheduling (publish at time)Mobile consoleMonthly client usage reportAgency / white-label accountsProactive site suggestions