Home/Growth experiments/Dev Marketing for Developer Products

Developers find and try your product

We run dev marketing around the code you ship: release posts, technical pages, community replies and a site coding agents can read. Your experiments are chosen by experienced founders and engineers who build with those agents themselves. Every post and page is read by a person on our team before developers see it.

Book a call

What is dev marketing?

Dev marketing gives developers ways to find a product, read about it and try it. The material often starts in the repo: an integration worth explaining, an error worth documenting or a release worth announcing. Guides, docs, posts and listings carry it beyond the team. For developers asking a coding agent, markdown copies and a site index provide another way to find and read those explanations.

A founder can post a launch and answer questions between releases. A developer relations hire can give docs and speaking their full attention. We test several ways to reach developers, drawing on people who build with coding agents and understand the pages those agents read. The question for any of these choices is the same: can someone looking for this kind of product find it wherever they ask?

Features shipped in silence cost you developer signups

The release is in the changelog, but someone looking for its new feature has no post or page to find. The engineering work is done; explaining it still waits.

  • Useful material goes unread. The repo and changelog hold explanations that never become pages or posts developers encounter.
  • Error searches lead elsewhere. Developers search an error message, but your docs have no page explaining its cause and fix.
  • Agents have little to read. Missing markdown pages and an llms.txt index leave coding agents without a clear route through the site.

We turn shipped changes into pages, posts and listings that developers and their agents can read.

We turn your changelog and repo into developer pages

We make public material from the changes in your repository, covering the questions developers ask when they choose a product and when they use it.

Write from shipped changes

We use the changelog to prepare release posts for LinkedIn, X and Reddit, with a person writing the final text.

Answer searched errors

We rank error messages worth a page and explain their causes and fixes from the code.

Make pages agent-readable

We handle markdown copies, llms.txt and schema checks so coding agents can find and read the product's explanations.

Find relevant conversations

We research suitable GitHub awesome lists and Reddit questions, then write entries and replies that disclose the company's role.

We read your code before we write about it

The repository tells us what developers can use. We read it alongside the company's data before choosing where to publish.

  1. First

    Map the product

    We read its user-facing features, integrations and errors, linking technical claims to the code behind them.

  2. Then

    Choose the release tests

    We select pages and channels from the code map and company data, and direct the agents' research.

  3. Next

    Put the material to work

    We publish developer pages, posts and listings; site changes arrive as pull requests for your company to merge.

  4. Each week

    Read the developer response

    On the call and in shared Slack, we discuss what developers did and what to continue, change or stop.

Example: giving coding agents a readable copy of our site

Every public page on our site has a markdown copy at the same address. Our /llms.txt index helps agents find those pages, and /ask?q= returns the page that best answers a question. Tin Analytics records agent requests with emails, tokens and keys removed, showing us which tools read the site and what they come for.

See how agents read our site →

We write about what shipped, in a person's words

A changelog gives us a concrete change to explain: what a developer can do now and how it works. We use that material to write posts with something useful to say about the product.

  • Start from the repo. We draw on code and release notes to explain features developers can use today.
  • Keep the founder's voice. Agents find material and outline it; a person writes the posts that carry the founder's name.
  • Explain the choice. As building products becomes easier, we help developers understand why they would choose yours for their work.

It fits startups that sell to developers

Reach technical buyers

We work with pre-seed to Series A B2B startups with clients and no experienced marketing lead.

Show the first call

For an SDK, API or webhook, we can prepare a runnable starter that demonstrates the first integration.

Reach coding-agent users

We work with founders building for coding-agent users, drawing on our experience building our own marketing system for them.

Talk to Tin

Let's talk about what shipped recently and where developers would look for it. We can take on the pages, posts and listings with no long-term commitment.

Book a call

FAQ

Can you write for developers without getting the technical details wrong?

We start with the code and the product map, including the integrations and errors developers encounter. The team includes AI engineers from MIT. That technical work gives the writer something to check a claim against: a feature in the repo, or the cause and fix behind an error message.

Will you post on X and Reddit for us?

We handle posts for X and Reddit as part of the work, with a person writing the final wording. Reddit replies explain that the company makes the product and respond to the question in the thread. The founder approves the important steps before the posts go live.

Do you help plan a product launch?

Yes, we plan launches as part of the engagement. The launch plan sets out where the posts will appear and when, and we write them from the changes being released. We consider the surrounding growth experiments too, including the pages a developer would read after hearing about the launch.

How much engineering time does this take from us?

The starting point is repository access and short conversations about the product. We do the research and writing from there, including the pages and posts drawn from releases. Engineers see site changes as pull requests they can inspect and merge, with a concrete edit in front of them.

Talk about where your developers look for tools

Talk with the founders and engineers who turn releases into growth experiments. We can discuss how developers discover your product today, what they ask about it and which of your releases could give them a reason to try it.

Book a call