What this covers.
Content modelling and migration
Taxonomies, field models and the move from one content management platform to another across hundreds of domains, without the publishing stopping while it happens.
Pipelines and automation
AI-assisted production with the evaluation step attached, and the automation that removes a three-team handoff rather than speeding it up.
Internal tooling
Small tools that remove a specific, measured cost. The judgement that matters is knowing where a language model belongs and, more often, where it does not.
What I have built.
Two internal and public tools. The case studies for the platform migration itself are being written.
The platform migration
Moving 750+ domains and 25,000+ URLs between content management platforms, in 7 to 14 languages. Figures locked, narrative being written.
What I actually work in.
- Payload
- Prismic
- WordPress
- VectorShift
- n8n
- Google Apps Script
- Claude Code
- Codex
- Antigravity
- Replit
- Lovable
- Figma
- Balsamiq
- Claude Design
Someone who worked on this.
What sets him apart is his technical vision—he built CMS architectures and internal programs with in-built AI generation features that automated complex workflows and made our content operations exponentially faster and easier.
Sheetal AgnihotriLet’s build something that scales.
If you are trying to make content compound rather than accumulate, that is the problem I like most. Email is quickest, and my calendar is open.