The story of why CMS Chat exists
We ran a web agency. We built beautiful sites for our clients. Custom designs, clean code, fast load times. We were proud of the work. Then the emails started. “Can you update the phone number on the contact page?” “We changed our hours.” “There's a typo in the third paragraph on the About page.” Every one of these took about 30 seconds to fix. But each one came with a support ticket, a context switch, and a billing question nobody wanted to answer. We added it up one quarter and realized we were spending 15+ hours a week on edits that took no skill at all.
So we tried the obvious solutions. We gave clients WordPress access. They changed a font, moved a div, and broke the layout within a week. We tried headless CMS tools. Our developers loved them. Our clients, the dentists and plumbers and law firms who just wanted to change a phone number, stared at the dashboard like it was written in a foreign language. The tools were built for developers, not for the people who actually needed to make the edits.
The problem was never about technology. It was about trust. We didn't trust clients to touch the site without breaking it. Clients didn't trust themselves either, so they emailed us instead. Both sides were stuck.
CMS Chat exists because we needed it ourselves. You open a chat, describe the change you want, and the AI makes it. Safe edits go live instantly. Anything risky gets flagged. Anything complex gets sent to your web team. No one breaks the layout. No one waits two days for a typo fix. No one sends another email asking to update the holiday hours.
Our Mission
Make website editing as simple as sending a text message.
Every feature we add has to pass one test: would a non-technical person understand it without instructions? If the answer is no, we either redesign it or we cut it.
We would rather block an edit that might be fine than let through one that breaks a page. Guardrails aren't limitations. They're what make self-service editing possible in the first place.
Everything runs through Git. Every change is tracked, every edit is reversible, and your team always has the final say on what goes live. We're a tool in your workflow, not a replacement for it.
CMS Chat is free to try. Connect a repo, describe a change, and watch it happen.
Try CMS Chat free