Marketing teams
Your team is already using AI, and the results depend on who’s driving. One workflow, one set of rules, owned by the people who own the brand.
Your team is already using AI. The trouble is the results depend on who's driving. I build AI workflows into the tools your team already uses — drafting, rewriting, repurposing, and publishing — governed by brand rules your marketing team owns, with a person approving everything that goes out.
Not a chatbot on the side. Workflows built into your CMS and your publishing process, so the AI does the repetitive work and your team keeps the judgment.
The same guardrails go into every AI workflow I build, because the hard part isn't getting AI to write. It's getting it to write like you, every time.
Voice, terminology, and style rules live in your CMS with drafts, revision history, and permissions — not in a prompt buried in code. Marketing changes a rule, and the next draft follows it. No developer ticket.
AI creates drafts. People review and publish. Automated videos and posts attach to drafts or wait for an editor to hit publish, so nothing goes out on its own.
Drafts only use facts from your brief and your content. No invented numbers, customers, or quotes — if the brief doesn’t support a section, it gets left out and flagged.
Caps on how often workflows run, so an open form or a busy week can’t quietly run up an AI bill.
Open-source template
Marketing writes rules in Sanity; AI turns a brief into a draft landing page that cites every rule it used. Edit a rule and the next page follows it in about a minute.
Read how it works →Featured build
My own content platform. A brand-voice system drafts and edits in three registers, and each review becomes an article, platform-sized videos, a newsletter, and a social post.
Read the case study →The same marketing teams, studios, and enterprise clients I build websites and web apps for.
Your team is already using AI, and the results depend on who’s driving. One workflow, one set of rules, owned by the people who own the brand.
Hand a client a site that keeps enforcing their brand guidelines after launch — or bring me in to build the AI layer of a project you’re leading.
Many writers, many channels, one voice — with the permissions and revision history your CMS already provides.
Hand me a defined workflow at one fixed price agreed up front, embed me in your team hourly or on retainer, or bring me in to plan your AI approach before anyone builds anything. Every engagement is quoted individually. See how I work →
It’s AI built into the way your team already creates and publishes content, instead of a separate chat window. A brief turns into a draft page, a review turns into a video and a newsletter, an editor rewrites a paragraph in your brand voice with one click — all inside your CMS, following rules your team controls, with a person approving what goes out.
No. It takes the first draft and the repetitive reformatting off their plate. Your team still writes the briefs, owns the brand rules, and decides what publishes. The point is to let good writers spend their time on the parts that need them.
Your voice and style guide become rules stored as content in your CMS, which the AI looks up every time it writes. Drafts cite the rules they used, get checked against your page structure, and only use facts from the brief. When something comes out wrong, you fix the rule, and every draft after it improves.
Most of the AI workflows I build run on Sanity, because it treats brand rules, prompts, and drafts as content with history and permissions — I’m an Official Sanity Partner. If you’re on another platform, tell me what you’re using and I’ll tell you honestly what’s possible there, or whether moving makes sense.
Usually, yes. For example, a marketer can submit a brief from Claude, and developers’ coding agents can read the same brand rules the page builder uses. Every entry point feeds the same workflow, so the rules apply no matter where a request starts.
Every engagement is quoted individually: a fixed price for a defined workflow, hourly or retainer if I’m embedded in your team, or consulting if you want help planning before anything is built. AI usage is billed by the providers you use, and I build in caps so it stays predictable.
Tell me where the busywork is. I'll give you a straight answer on what a workflow could take off your plate.