Turning developer love into an enterprise category.
I work with AI infrastructure companies whose developers are in love and whose enterprise buyers aren't.
The split looks the same everywhere. The homepage is written for an engineer with a task. The open GTM role is written for someone selling to a platform lead. Nothing in between argues why an enterprise standardises on you rather than building it themselves. That isn't a marketing problem. It's an unwritten argument.
I write the argument, and the machine that makes the right five hundred people read it.
One deep-dive technical essay under your name, co-built with your team. The distribution playbook that seeds it: named list, publication mechanics, the first ninety minutes, and the version your AEs send into live deals. One kickoff, one review, two rounds of revision.
Built to hand the method to your team, not to make you dependent on me. Two weeks isn't the limit — it's the point.
Not included: additional pieces, ongoing publishing, other channels, or execution past publication week. Each is a separate engagement.
Book a 30-minute call →Two founding slots at $7,500.
- Companies still deciding what they sell.
- Teams who want a content calendar rather than an argument.
- Anyone who needs the essay to say something their own engineers would dispute.
The Control Plane series is the method run on my own thesis. The Head of DevRel at a $44M-Series-A infrastructure company read it and told me I was spot on. A Field CTO at an $80M company connected off the back of it. That reaction is engineered, not lucky.
Read the series →