Everything people ask before the first call.

We are a content studio for devtool companies. We produce tutorials, integration and comparison pages, documentation, video shorts, and social posts, built to be read by developers and cited by AI assistants. The work is done by engineers who run your product, using machine research to find what is being asked and human judgment to decide what is worth publishing.

Engineers who ship in your stack, working from machine research rather than guesswork. Every tutorial and integration guide starts as a working repository that runs on a clean machine, on the versions you support, and the article documents what actually happened during that build.

Across four dimensions rather than one. SEO: rankings, crawl health, and internal linking. Performance: Core Web Vitals on the templates your content sits in. AEO, answer engine optimisation: whether featured snippets and AI assistants can extract a clean answer from the page. GEO, generative engine optimisation: whether your content is actually being cited by ChatGPT, Perplexity, and AI overviews. Ranking and being cited have become different problems, and we report on both.

Scope and price come out of a 30-minute call. We quote the work in front of us rather than publishing a rate card that fits nobody, and you leave that call with a scope and a number whether or not you go ahead.

Typically one to three weeks from brief to publish-ready draft. Most of that is the build and the technical audit rather than the writing.

Yes, outright, including the demo repositories. Nothing is licensed back to us and nothing is reused for another client.

Yes. Delivery is publish-ready in your CMS with assets, metadata, structured data, and internal links already in place, or as a pull request if you run docs-as-code.

We tell you before it is written. If the honest answer is that something will not rank, will not convert, or will embarrass you in six months, saying so early is cheaper for both of us.