AI Automation

DXP vendors built AI agents. Marketers adopted Claude and ChatGPT. Almost nobody has connected the two. Here is the architecture that bridges them without new tools.

A client sent us their 15-year-old website and a list of what was broken. Ten minutes later they had a new ten-page site in production. Here is how, and what speed alone doesn't cover.

WebMCP has moved from proposal to Chrome origin trial. Most of the work to get a site agent-ready has nothing to do with the API, and none of it fixes your AEO or GEO visibility. Here is what does.

AI agents are already clicking through interfaces built for humans. WebMCP lets your site declare what its tools actually do, so agents call them directly instead of guessing at your DOM.

The AIQ Blueprint turns how your organization evaluates and decides into a continuously operating intelligence system, powered by purpose-built AI agents.

Every CMS vendor claims to be "agentic." Most aren't. Here's a framework for distinguishing genuine autonomous content operations from AI features with a new label

How we use Claude and Sanity CMS to continuously audit, research, and refresh our technical content turning content maintenance into an intelligent background process with human review.

What used to be forgotten ideas and half-typed emails to myself is now a published blog before my first sip of coffee. Our engineering team turned my 15-minute commute into a content pipeline.

Content teams invest in production but neglect protection. Without both, your library becomes a bathtub with the drain open.

How do you keep track of old, irrelevant, aging content on your CMS Platform? We automated ours.

The problem with most AI content isn't the writing quality. It's the absence of real research. A research-first pipeline changes everything.

Reflecting on Dario Amodei’s “The Adolescence of Technology,” and what it means for how HT Blue designs agentic, values-driven, and transparent AI systems for enterprise content operations.