How a Series A dev-tools company replaced a content team with a Content Operating System
Where they were before the engine
Synthex’s founder was the only person on the team who could write convincingly about LLM observability – but he was also building the product. Every freelance experiment produced articles that ranked but didn’t sound like Synthex. Articles drafted by GPT in a generic SaaS voice never made it past internal review.
How the engine got to work
Founder-voice training
Upfront-AI trained the brand voice on the founder’s 40+ Hacker News comments, blog posts, and conference talks. The engine learned the exact rhythm – direct, opinionated, technically precise, slightly skeptical.
Engineering-blog pipeline
Twenty articles per month routed through a custom review queue: engine drafts → technical reviewer flags one specific section → engine refines that section only → ships.
Code-aware drafting
Articles include working code snippets validated against Synthex’s own product – not abstract pseudocode. We integrated the engine with their staging environment so examples stay current.
GEO for developer queries
Developer search behavior is unique – they want specific answers fast. We optimized for AEO (Answer Engine Optimization) explicitly, structuring every article around the ‘answer-first’ pattern.
What changed in 90 days
I stopped being the bottleneck on my own content. Upfront-AI sounds more like me than the writers I was paying. That sentence should not be possible – but it is.