Writing
We build with your product before we write a word.
Every line of code in a draft has run before you see it. We write tutorials, guides, explainers, comparison pages, and essays under your founder's name.
A technical content marketing agency for developer tools
Argot writes tutorials, guides, explainers, and opinion for developer tools and AI products. Every piece is written for developers and clear enough for their agents.
Tell us about your project
Share your product and your readers. We'll come back with ideas for what to write.
We've written for devtool and AI companies including
Deno
Modal
Stream
“Can't recommend Argot enough. They have deep technical knowledge—you get authentic, developer-to-developer material that adds value. They can write thought-leadership just as well as technical content, which is very hard to find. Responsive and never miss a deadline.”
Three ways to work with us
We write from scratch, fix what you already have, or work out what to publish next.
Editing
We cut the slop from your drafts.
Send us what your team or your model wrote. We run the code, cut anything wrong or generic, and send it back ready to publish. Old tutorials too, since coding agents now follow them step by step.
Strategy
We plan for developers and their agents.
Both work from what you've published. We find where that breaks down on the way to a working integration and what to write to fix it, plus the comparison pages and explainers that help your product get picked in the first place.
Read the work
Everything Argot writes goes out under the client's name. Here is some of it, as published.
Built for technical scrutiny
Our clients are developer-focused companies whose readers will check the work. So we hold every piece to three standards.
- The words
- Jargon matters. When developers see technical concepts used wrong, trust evaporates. We use the correct nomenclature, explain what the code is doing, and keep it interesting to read.
- The code
- A good code sample runs, uses realistic data and shows one thing clearly. Samples are part of a working whole, never orphaned snippets that only look right.
- The numbers
- A benchmark needs a stated methodology, a reproducible setup and honesty about what it doesn't measure. That is what separates a claim from an assertion.
More on how we think about this in What is technical content marketing?
How it works
We talk
A conversation about your product, your audience and what you're trying to achieve.
We write
We propose topics, write drafts and handle everything from ideation to final polish.
You review, we revise
We iterate until the content is right. Then you publish.
Questions
Start a project
Tell us about your product and your readers. We'll come back with ideas for what to write.
Go to the formPrefer email? work@argot.dev