Content systems
A content production system — research, draft, fact-check, ship — designed around how your team actually writes.
I build the editorial pipeline you'd build if you had three more engineers. Brief generation, research aggregation, draft scaffolding, fact-check passes, and publishing integration. AI handles the boilerplate; your writers do the part that matters.
The teams getting AI right share one habit: they treat the integration layer as the product, and the model as a swappable dependency. Here's what that looks like in practice.
- Brief and outline generation from a topic + audience
- Source aggregation and competitive research
- Draft scaffolding tuned to your editorial voice
- Fact-check pass with citation tracking
- Publishing into your CMS (Sanity, Contentful, Webflow, etc.)
Companies treating content as a serious channel and feeling the cost of doing it manually.
Teams looking to flood the internet with thin AI-generated articles — that's bad for your domain and bad for the open web.
Audit & scope
We start with a conversation about what you actually do day-to-day. I map the workflows, identify what's worth automating and what isn't, and write up a scoped proposal with a fixed price.
Design
Architecture, data flow, integration points. You see the full system on paper before I touch any code — so we catch the wrong call cheaply, not after it's built.
Build
I build, iterate, and test against real data from your business. You see progress weekly in a shared environment, not as a single reveal at the end.
Deploy & handoff
We launch together. I document everything in your tools (Notion, your repo, wherever you keep things), and I stay on call for the first few weeks while your team gets comfortable.