The long version.

Where it started: the discipline of precision.

I spent six years translating and proofreading technical and marketing content for companies like Dell, Microsoft, Apple, Samsung, and NetApp. The work taught me something that sounds simple but isn't: words are load-bearing structures. Every choice has a consequence. A mistranslation in a product manual costs money. An ambiguous sentence in a marketing campaign costs conversion.

The clients were large, the volumes were high, and the tolerance for error was low. I learned to work fast without getting sloppy, and to care about language as a functional tool, not just an expressive one.

This is where my editorial instinct was formed: not in a creative writing class, but in the discipline of making someone else's words work.

The publisher side: where content has to earn its place.

I moved into editorial at two of Italy's most-read tech properties, managing affiliate content partnerships across VPN providers, cloud services, and eLearning brands. It was high-traffic publishing at scale, and the pressure was constant: every piece of content had a performance number attached to it. Not the channel, not the month. The piece.

This changed how I think about content. In most organizations, content is measured by output — how many pieces were published, how many words were written. Here, it was measured by outcome. Did it rank? Did it convert? Did it justify the time it took to produce?

I was on the editorial side of the affiliate relationship — the team deciding which brands got covered and how, not the brands buying the coverage. That perspective taught me what separates content that earns its place from content that just fills a page. The difference is rarely about quality of writing. It's almost always about systems: how the brief is written, how the brief is researched, how the output is reviewed before it goes live.

Managing at scale: when one person's quality isn't enough.

I moved into editorial management at Blazemedia, leading the affiliate content operation with full ownership of hiring, onboarding, quality standards, and delivery. For the first time, the output didn't depend on me — it depended on a team, and on the systems I built to make that team work.

This is where I understood, in practice, that content operations are a distinct discipline. It's not about being a better writer. It's about building the infrastructure that makes consistent quality possible at scale — regardless of who is executing on any given day.

It's also where the limitations of manual processes become visible. When you're managing a team across verticals, the bottlenecks are always the same: brief quality, review cycles, unclear ownership, metrics that don't reflect what actually matters. The problems are structural, not individual.

Building the tools: from observation to system.

I started building. First a job market intelligence tool — a system that scans hiring signals before job postings go live, scores companies by their content ops pain, and surfaces the ones worth approaching. It runs every week and it's public on GitHub.

Then an editorial pipeline for my own content. A four-agent system that handles topic research, writing, editorial review, social distribution, and publication scheduling — end-to-end, with every step logged and measured. The same newsletter, produced in a fraction of the previous time, with consistent quality and measurable results.

Building these systems confirmed something I had suspected: the problems I was solving for myself were the same problems most content teams have. The gap isn't capability — it's infrastructure. Teams that have good writers but no system consistently underperform teams with average writers and a well-built system.

The data backed this up. The average B2B content cycle takes 326 days and involves 10 different stakeholders. 54% of companies that scaled AI content lost 30% or more of their organic traffic. More volume isn't the answer. A system that makes every piece earn its place is.

The service: bringing the system to other companies.

I now build and run AI-assisted content operations for SaaS and eCommerce companies. The work is the same as what I did for myself — audit the existing process, identify where quality drops and hours disappear, build the system that fixes it, and manage it directly.

Not an agency that writes content and hands it over. Not software you install and forget. A managed system: I build it, I run it, and I stay accountable for the results.

The entry point is a Content Ops Audit: a structured diagnosis of how the current operation works, where the gaps are, and what a 90-day roadmap to fix them looks like. From there, the engagement extends into building and managing the system.

The background matters because it's not a theory — it's ten years of watching content operations work and fail, at scale, in real publishing environments. I bring that to the companies I work with.