CEO @crafterq_ai and @crafter_cms that power AI-first digital experiences for businesses. Prev founder/CEO of Rivet Logic (acq by Capgemini). VC investor.
USA
Joined January 2009
- Tweets932
- Following322
- Followers377
- Likes581
The CMS repository used to be the boring part of the evaluation. AI agents just made it the decisive one. 🧵
Framer shipping an MCP connector is the tell.
Design tools, IDEs, and CMSs are all racing to the same place: let agents act on the system, with a human still in the approval loop.
If your CMS can't expose content + capabilities to agents (and roll back what they change), you're building for last year's workflow.
Walmart put ~200K products in ChatGPT Instant Checkout.
Purchases inside ChatGPT converted at 1/3 the rate of click-outs to Walmart.com. Instant Checkout is gone.
Discovery moved into the assistant. The sale did not.
AI-referred shoppers convert ~60% better on the merchant’s site. Cart, account, loyalty, trust still live on your servers.
Walmart’s next move: Agent Profiles + an MCP Agent Gateway so other agents shop through Walmart’s systems, and not by scraping a human UI. Sparky travels into ChatGPT as Walmart’s agent.
Every company needs both:
• An AI agent on your site for humans ready to convert
• An agent-facing API so other agents talk to you like agents
Assistants discover you. Your agent converts them.
If your only plan is “show up in ChatGPT,” you’re optimizing for discovery and giving away the conversion.
Mike Vertal retweeted
AI agents don’t care about your CMS UI. They care whether they can see the system, and whether you can undo what they change.
New post: Git-based vs database CMS for AI agents
craftercms.com/blog/technica…
1/ Open source used to be the budget CMS choice.
In 2026, for enterprise content platforms, it’s often the strategic one.
Why — and how to evaluate the shortlist:
3/ Then architecture, not feature bingo:
- Decoupled authoring vs delivery
- Content as code (Git) for real DevContentOps
- Native search/vectors for RAG + agents
- Enterprise-grade backend tech stack (Java/Spring vs Node vs PHP vs Python)
- Deploy where compliance needs (on-prem / your cloud / managed)
4/ We compared CrafterCMS, Strapi, Drupal, Payload, Directus, Wagtail against those criteria and included a decision framework for architecture reviews.
We build CrafterCMS; we’re transparent about that.
Full post: craftercms.com/blog/technica…
Our platforms are not written in Node, or PHP, or any other less than enterprise-grade scripting platforms. All secure on the Crafter front.
Mike Vertal retweeted
Vercel has proactively rolled out Firewall-level mitigations for today's Node.js RCE vulnerability, in advance of the official patch release.
All traffic for all deployments is automatically protected. We're actively monitoring and rolling out managed runtime upgrades.
Node.js Security Advisory: a high-severity RCE flaw in Node's Brotli decoder affects Node.js 22, 24, and 26.
Vercel WAF rules are live for every project and block known exploit patterns.
vercel.com/kb/bulletin/node-…
Mike Vertal retweeted
AI shouldn’t be another browser tab your content authors have to open.
Our AI Assistant brings AI directly into the CMS for content creation, rewriting, SEO/GEO/AEO optimization, translation, and increasingly, agentic content operations.
Meet the Crafter Studio AI Assistant 👇
Mike Vertal retweeted
Appreciate the positive review @jayjohnsonai 🙌
The bigger idea? Websites may become less about clicking through menus and more about simply asking for what you need. CrafterQ is an interesting example of that shift. #WebsiteAI #EverydayAI
👉 Get Perfecting Prompts jayjohnson.co.uk/product-pag…