← All work

Case study · Operations consulting firm · In progress, 2026

A website the team updates by talking to ChatGPT or Claude

A consulting firm wanted to be named in AI answers and ranked in search when someone asks about operational consulting, M&A support or supply chain work. That takes a site built for machine reading and a steady flow of new insights and case studies. Their WordPress site had neither, and publishing was a manual job, so it rarely happened.

How content moves

What we are building

Agent-ready website

A static Next.js site built from the design partner's Figma wireframes. Every page carries structured data, clean semantic HTML, a sitemap, an llms.txt file and a feed of new content, so Google and AI assistants can read and cite it.

Headless CMS

Sanity, with content models for pages, insights, case studies, white papers, leadership and careers. People can still edit in Sanity Studio with a live preview. Publishing triggers a rebuild, and the change is live in minutes.

MCP connection and update skill

The CMS is connected to ChatGPT and Claude through an MCP server. A skill package tells the assistant what every content type is for, the house rules, and what it must never touch. The team says "publish this case study" in chat.

Writing skill

Turns a raw idea, notes or a call transcript into a draft in the firm's own voice, removes the tells of machine-written text, and saves it to the CMS with the SEO fields filled.

Guardrails

  • The assistant works with a least-privilege token: it can create and edit drafts, but cannot delete content or change the schema.
  • Every agent change is a draft. The assistant returns a preview link and a screenshot, and a person clicks publish.
  • Each person signs in with their own CMS account, so every change is attributed to someone.
  • Eight to ten scenarios are tested end to end before handover, from "add a job posting" to "update a stat", each with a written check of the result.

Ownership and delivery

  • Every account is created in the client's name: code, content, CMS and hosting are theirs from day one.
  • The skill packages are handed over with the code. Nothing is licensed back.
  • Static site on free-tier hosting and the CMS free plan: no maintenance retainer needed.
  • Every change is deployed to a preview link, so the client and their designer watch the build as it happens.

Want your team to publish from chat?

The same setup works for any content site: marketing pages, help centers, product catalogs.