CHABOT

AI-era DevRel signals

8 minute read 1,896 words

These thirteen practices are visible in current DevRel programmes at named companies. The examples establish adoption. They do not establish causation.

1. Cookbook repositories as a maintained DevRel deliverable

Pattern. A public GitHub repository organised as a collection of small, complete, runnable recipes covering different use cases of your product. Each recipe is self-contained, has a README.md, and demonstrates one thing clearly.

Why teams use it.

  • Search and retrieval systems can surface a focused recipe for a specific task.
  • Human developers clone individual recipes as starting points for their own integrations.
  • One repository gives the team a canonical implementation to test and update.
  • Each recipe is a small, reusable unit that can be tested and updated independently.

Notable exemplars.

  • OpenAI Cookbook (github.com/openai/openai-cookbook). Hundreds of recipes and a substantial external-contributor community.
  • Anthropic Cookbook. Direct competitor and arguably the more curated version. Recipes are tightly scoped, well-tested, and include explicit version metadata.
  • Stripe Samples (github.com/stripe-samples). Per-language repositories with complete deployable examples.
  • Vercel Templates (vercel.com/templates). Templates that can be deployed with a click.
  • LangChain templates and LlamaIndex examples. Recipe-style code reflecting common integration patterns.

Across these examples, the cookbook is a maintained collection of runnable integrations rather than a stream of standalone posts.

2. Founder-led written content

Pattern. Founders and senior technical leaders publish signed analysis on topics adjacent to, but not always about, their product. The work draws on technical or strategic decisions the author made.

Why teams use it.

  • Readers can connect an argument to a named person’s record. Patrick Collison, Mitchell Hashimoto, Guillermo Rauch, and Clem Delangue each bring decisions and experience that a company account cannot claim for itself.
  • A decade of signed essays gives readers a record of the author’s decisions and revisions.
  • Signed technical writing gives retrieval systems an attributable source and gives readers a public record against which to judge it.

Notable exemplars.

  • Stripe Press. Stripe’s broader intellectual project: books, essays, sustained long-form publishing.
  • Mitchell Hashimoto’s personal blog (mitchellh.com). Post-HashiCorp writing on systems software and Ghostty terminal-emulator work.
  • DHH’s writing across two decades. Hey, Basecamp, REWORK, his personal site.
  • Sam Altman’s blog and OpenAI announcements. Even at scale, the voice is identifiable.
  • swyx’s writing across his personal site and Latent Space. A sustained record of signed essays about AI engineering.

The pattern requires someone willing to write under their own name. A senior technical leader can do this when the founder is not the right author, provided the piece draws on decisions the author actually made.

3. Build-in-public Launch Weeks

Pattern. A company publishes several releases over a defined week, with a post, demo, and question period for each one.

Why teams use it.

  • A scheduled sequence gives the audience several occasions to follow the release and ask questions.
  • Each day’s content is shareable and amplifiable.
  • The public schedule gives engineering, documentation, and product teams shared release deadlines.

Notable exemplars.

  • Supabase Launch Weeks (running since 2021). Multiple features per week, daily posts, livestreams, and community participation.
  • Cloudflare Developer Week. Annual, content-saturated week of new product announcements.
  • Vercel Ship. Annual customer-event-as-launch-week.
  • Linear’s smaller launch series.

Supabase, Cloudflare, Vercel, and Linear all used variants of this format between 2024 and 2026.

4. MCP server as a maintained product interface

Pattern. Publishing an MCP server alongside your SDK and CLI, treating it as a maintained product. Tool naming is deliberate; documentation is complete; updates ship with the product.

Why teams use it.

  • One server can expose product capabilities to compatible clients such as Claude Code, Cursor, Windsurf, ChatGPT, and Gemini, subject to differences in client support.
  • Developers using those clients can invoke the product without a vendor-specific adapter.
  • The discipline of writing clean tool descriptions improves the rest of your API documentation as a side effect.

Notable exemplars.

  • GitHub MCP, Sentry MCP, Cloudflare MCP, Linear MCP, Notion MCP, Stripe MCP, Supabase MCP, Snowflake MCP. Partial list of major developer-product MCP servers in 2026.
  • Vercel AI SDK with MCP support.
  • Microsoft Playwright MCP for browser automation.

See MCP for DevRel.

5. Disciplined llms.txt plus llms-full.txt plus OpenAPI plus schema

Pattern. A clean, well-maintained set of machine-readable surfaces:

  • Auto-generated llms.txt and llms-full.txt (often via Mintlify or similar).
  • Publicly accessible OpenAPI spec at a stable URL.
  • Schema.org markup on key product pages.
  • Consistent canonical URLs across the docs site.
  • Robots.txt explicitly allowing the major AI crawlers.

Why teams use it.

  • Public schemas and stable canonical pages give retrieval and code-generation systems explicit product information.
  • Maintaining the files also exposes stale links, inconsistent terminology, and incomplete API descriptions.
  • llms.txt has uncertain direct effects; OpenAPI coverage, runnable examples, and valid metadata can be measured independently.

Notable exemplars.

  • Anthropic docs at docs.anthropic.com: clean llms.txt and llms-full.txt, well-structured pages, consistent vocabulary.
  • Mintlify-hosted documentation generally. Anthropic, Cursor, Resend, Perplexity, dozens of others.
  • Stripe docs. Long-running documentation with stable structure and runnable examples.
  • Vercel docs and Next.js docs. Clean, well-versioned, machine-friendly.

6. Sponsored YouTube placements on established channels

Pattern. Paying for sponsored segments on YouTube channels whose audience overlaps your ICP. The channel’s creator presents the segment and may demonstrate the product in use.

Why teams use it.

  • The creator can demonstrate a specific workflow inside material their audience already watches.
  • The video remains available after the campaign ends.
  • Public view counts and tracked links give the sponsor observable reach and referral data.

Notable exemplars.

  • Fireship. Sponsored segments in The Code Report and product features.
  • ThePrimeagen. Sponsored segments for software-development products.
  • Theo Browne (t3.gg). Sponsorships aimed at frontend developers.
  • Web Dev Simplified, Net Ninja, NetworkChuck, ByteByteGo. Other channels used by developer-product sponsors.

Approximate rates are documented in YouTube for developers. Sponsors still need campaign-specific referral and activation data before comparing the channel with other paid media.

7. Podcast guesting by senior team members

Pattern. Senior engineers, founders, and DevRel leaders appearing as guests on respected developer podcasts. Often discussing topics adjacent to but not strictly about their product. The product comes up naturally in conversation.

Why teams use it.

  • A long conversation gives the guest time to explain decisions, constraints, and technical trade-offs.
  • The conversation reaches the podcast’s existing audience.
  • The recording and show notes remain available after release.

Notable exemplars.

  • Latent Space appearances. Reach an audience focused on AI-engineering products and practice.
  • The Changelog appearances. Broad industry reach; Adam Stacoviak and Jerod Santo run high-quality interviews.
  • Syntax.fm appearances. Front-end audience.
  • Acquired episodes. Broader company-strategy audience; less developer-focused.
  • Community Pulse appearances. For DevRel-practitioner audience (i.e., influencing other DevRel teams).

8. AI Engineer Summit / specialised conference presence

Pattern. Companies whose products serve AI Engineers invest deliberately in specialised AI-engineering conferences and channels rather than generic developer events.

Why teams use it.

  • Audience concentration. The AI Engineer Summit, MLOps World, NeurIPS, Ray Summit, GTC, Snowflake Summit AI tracks, and Databricks Data + AI Summit bring together practitioners who evaluate AI-infrastructure products.
  • Speaking gives practitioners an opportunity to inspect the team’s technical argument and ask questions.
  • In-person discussions can continue into product evaluation or enterprise procurement, although the event alone does not establish causation.

Notable exemplars.

  • Pinecone, Weaviate, Chroma, Qdrant all show up consistently at AI-engineering conferences.
  • OpenAI, Anthropic maintain visible AI Engineer Summit presence.
  • Modal, Together AI, Replicate have appeared at AI-engineering conferences.

9. Discord office hours and structured community presence

Pattern. Predictable, regular times when company engineers are visibly available in the community Discord (or equivalent). Office hours; AMAs; bug-triage hours; “ask me anything about X” themed sessions.

Why teams use it.

  • A fixed schedule tells members when an engineer will be available.
  • Repeated questions expose documentation gaps and can be turned into durable answers.
  • Named engineers can take responsibility for ambiguous bugs and product decisions.

Notable exemplars.

  • Vercel’s Next.js Discord with regular team presence.
  • Supabase Discord with founder participation.
  • Cloudflare Discord for Workers / Pages community.
  • Anthropic Discord for developer community.
  • The Rust language community’s Zulip (technically not Discord, same pattern).

10. Open-source maintainer sponsorship and ecosystem investment

Pattern. Companies investing financially or via paid roles into open-source projects their product depends on or competes with. GitHub Sponsors, Tidelift, direct grants, hiring maintainers.

Why teams use it.

  • Public funding lets communities judge whether a company supports projects it depends on.
  • Paid maintainer time can improve the maintenance of dependencies the company uses.
  • The work also gives companies sustained contact with experienced maintainers who may become candidates for relevant roles.

Notable exemplars.

  • Cloudflare’s open-source funding across multiple projects.
  • Sentry’s open-source dependency fund.
  • Vercel’s funding of Next.js and many adjacent JS ecosystem projects.
  • The various MOSS (Mozilla Open Source Support) grants historically, plus successor programs.

11. Treating documentation as a versioned product with a roadmap

Pattern. Documentation has an owner, a quarterly roadmap, version controls, named writers, and measurable goals (TTFHW, completion rate, search-query coverage).

Why teams use it.

  • A regular review creates a schedule for fixing stale pages, broken examples, and incomplete metadata.
  • Complete examples and stable structure help both developers and retrieval systems.

Notable exemplars.

  • Stripe’s documentation. Long-running, versioned documentation with complete examples.
  • Mintlify-hosted documentation at most AI-era developer products.
  • Twilio’s documentation. Substantial team and roadmap.
  • AWS, Google Cloud, Azure all maintain documentation teams that operate like product teams.

12. Founder or CEO running the launch personally

Pattern. The CEO or founder presents the keynote, writes or signs the launch post, demonstrates the product, and answers questions. Marketing handles production and distribution around that named presenter.

Why teams use it.

  • The founder can connect the product announcement to decisions they made and answer questions about the company’s direction.
  • A named presenter gives press, podcast hosts, and community members a specific person to question after the announcement.

Notable exemplars.

  • OpenAI DevDay (Sam Altman, Greg Brockman, etc.). Founder-led format is the default.
  • Anthropic launches. Dario Amodei, Mike Krieger, Alex Albert all visible at major launches.
  • Vercel launches. Guillermo Rauch leads.
  • Linear releases. Founders consistently in the foreground.

13. Combining a fast-iterating cookbook with quarterly long-form essays

Pattern. Day-to-day content production focuses on cookbook recipes (small, complete, runnable). Long-form quarterly essays focus on strategic positioning, architectural arguments, opinionated takes on the field.

Why teams use it.

  • Cookbook recipes answer narrow implementation questions with runnable code.
  • Essays explain architectural choices, trade-offs, and product direction.

Notable exemplars.

  • Anthropic’s blog combined with cookbook. Strategic essays plus tactical recipes.
  • OpenAI’s blog plus Cookbook.
  • Vercel’s product launches and technical writing.
  • LangChain blog plus templates repository.

Patterns with weaker evidence

Several patterns common in 2024 to 2026 marketing advice have weaker evidence of effectiveness:

  • Aggressive llms.txt optimisation (covered with appropriate scepticism in llms.txt).
  • “AI-generated content at scale” approaches (mostly failure mode).
  • Generic “AI thought leadership” content from companies without genuine AI products.
  • Heavy reliance on a single AI-search visibility tool.

See also