I build marketing engines out of AI — and keep the judgement human.

An AI content engine I own end to end — and the one I actually test things on

An English-language site about paddleboarding the Turkish coast, built from nothing: positioning, keyword architecture, the site itself, the writing setup behind it, and affiliate revenue. No team, no budget, nobody to hand a draft to. It is also my sandbox — if a workflow does not survive here, I do not take it into client work.

• One brief file, not one-off prompts. Audience, tone, approved facts, internal linking rules and product criteria live in a single source the whole workflow starts from — so the model never begins from a blank page.
• A prompt library someone else could run. Reusable setups per content type: route guide, gear review, seasonal explainer. Handover-ready, because a system only counts if it survives the person who wrote it.
• QA is part of the workflow, not a mood. Every draft is checked for sources, product specs and claims before publishing. In affiliate content one wrong number costs the reader's trust permanently.
• Built for both audiences. Structured so search engines rank it and AI assistants can find and quote it — and written so a human wants to keep reading either way.
• Interactive where prose is worse. A board-size calculator, a wind-hour timeline and a paddled-routes map, because some answers should be a control the reader moves, not a paragraph they parse.

150+ AI-powered presentation templates, shipped in two weeks

A product launch needed a template library and there was no version of that timeline where a person wrote them one by one. So I built the production line instead: agents generating prompts, descriptions and metadata in bulk, keyword and competitor research deciding what was worth building at all, and me choosing the 24 that would represent the launch.

• Research set the brief. Search demand and competitor gaps decided the categories, so volume went where there was actually a reader waiting.
• Bulk generation, hand-picked selection. The agents made the set possible; the featured 24 were chosen on search volume, design quality and use-case spread.
• Discoverability in two places. Structured with product and design so templates surfaced in search and in ChatGPT-style assistants — before that had a name.

An RSVP apps directory that became a real acquisition channel

I owned this one end to end — what the directory should contain, who it was for, how each entry earned its place, and the copy that made someone act once they arrived. Persona research first, keywords second, because a directory that ranks and converts nobody is just a well-optimised dead end.

• Built on user needs, not keyword volume alone. Research into what people were actually trying to do decided the structure.
• Worked with landing page designers so the page did the same job the copy promised.

One page, position #6, seven paying customers

Permission slip templates: an unglamorous niche nobody was fighting over, which is exactly why it was worth taking. One asset, researched and written properly, still returning customers long after publication — the argument for depth over volume in a single line item.