{
  "title": "Developer Marketing field guide — examples",
  "updated": "2026-07-27",
  "count": 7,
  "examples": [
    {
      "id": "heimwall-publishes-the-noise-with-the-benchmark",
      "title": "HeimWall publishes the noise next to the signal",
      "company": "HeimWall",
      "summary": "A vendor benchmark that prints its own false-positive breakdown — 1.12% alert rate, 48% of alerts from one noisy rule, a middling F1 it admits to — on a public dataset anyone can rerun, making the headline finding believable instead of dismissible.",
      "artifact": "blog",
      "channel": [
        "blog"
      ],
      "why": "The headline find is real (three live-format API keys in 27,075 public ChatGPT prompts from the DevGPT dataset), but the tactic is everything around it: the post prints the 1.12% alert rate, admits 48% of alerts came from a single noisy UUID rule, discloses a CredData F1 of 0.449 that beats no one's marketing copy, and names the limitations it can't measure. Developers read vendor benchmarks looking for what's hidden; publishing the noise first removes the thing they'd have dunked on and turns the comment thread into a methods discussion. The whole play is reproducible — the dataset is public — which is what separates it from a claim.",
      "demonstrates": "05-content-that-earns-trust",
      "demonstrates_url": "https://developer-marketing.vercel.app/guide/05-content-that-earns-trust/",
      "tags": [
        "content",
        "benchmarks",
        "trust",
        "security"
      ],
      "source": {
        "label": "HeimWall — We scanned 27,075 developer prompts to ChatGPT",
        "url": "https://heimwall.ai/blog/we-scanned-27075-developer-prompts"
      },
      "sources": [
        {
          "label": "The Week — the security benchmark that published its own false-positive rate",
          "url": "https://albertogrande.github.io/developer-marketing/articles/2026-07-21-honest-benchmark-noise"
        }
      ],
      "date": "2026-07-27"
    },
    {
      "id": "godaddy-builds-the-checkout-for-the-agent",
      "title": "GoDaddy builds the checkout for the agent",
      "company": "GoDaddy",
      "summary": "Docs served as markdown and OpenAPI with a quickstart that says \"hand this spec to your LLM\" — and a purchase flow (quote-token, idempotency keys, consent record) an agent can run without over-buying.",
      "artifact": "docs",
      "channel": [
        "web",
        "docs"
      ],
      "why": "Launched July 14, 2026, this is the first mass-market platform to treat the\nagent as a first-class reader *and* actor. Every docs page is available as\nmarkdown, the whole set ships as one `/llms-full.txt`, and the quickstart's\nopening move is handing `domains-v3.json` to your LLM \"so your agent reads the\nsame docs you do.\" The part worth copying is the transactional design:\nregistration is quote-then-execute (exact price plus a short-expiry\n`quoteToken`), every attempt carries an idempotency key so a retry can't buy\ntwice, a consent object records which agreements were accepted — and there is\nno card-number field anywhere in the API. The guardrails are the pitch: they're\nwhat makes delegating a purchase to an agent feel safe.",
      "demonstrates": "02-docs-as-front-door",
      "demonstrates_url": "https://developer-marketing.vercel.app/guide/02-docs-as-front-door/",
      "tags": [
        "docs",
        "dx",
        "distribution",
        "launches"
      ],
      "source": {
        "label": "GoDaddy Developer Platform",
        "url": "https://developer.godaddy.com/"
      },
      "sources": [
        {
          "label": "GoDaddy — Introducing the GoDaddy Developer Platform (2026-07-14)",
          "url": "https://www.godaddy.com/resources/news/introducing-the-godaddy-developer-platform-domain-apis-for-developers-and-their-agents"
        }
      ],
      "date": "2026-07-20"
    },
    {
      "id": "juggler-launches-on-reputation-and-a-runnable-repo",
      "title": "Juggler launches on reputation and a runnable repo",
      "company": "Juggler",
      "summary": "A solo, unfunded open-source launch topped Hacker News because the maker's decades of public credibility did the marketing and the artifact was runnable the moment you hit the repo.",
      "artifact": "launch",
      "channel": [
        "hackernews",
        "github"
      ],
      "why": "Julian Storer — creator of JUCE and the Tracktion DAW — shipped an open-source\nGUI coding agent built solo over six months and took 276 points and 100+\ncomments on Hacker News with zero launch budget, in the most saturated devtool\ncategory of the year. Every element is the earned-channel playbook: credibility\naccumulated in public over decades, a repo you can clone and run immediately,\nno waitlist, no signup, no telemetry, and an AGPL core with an Apache-licensed\nextension SDK so commercial builders aren't scared off. The title even leads\nwith the reputation (\"by the creator of JUCE\") — the trust shortcut *is* the\nheadline. If you don't have a famous founder, the runnable-artifact half of the\nplay still works on its own.",
      "demonstrates": "06-channels-and-distribution",
      "demonstrates_url": "https://developer-marketing.vercel.app/guide/06-channels-and-distribution/",
      "tags": [
        "launches",
        "distribution",
        "channels",
        "community"
      ],
      "source": {
        "label": "Show HN — Juggler, an open-source GUI coding agent, by the creator of JUCE",
        "url": "https://news.ycombinator.com/item?id=48883305"
      },
      "sources": [
        {
          "label": "Juggler on GitHub",
          "url": "https://github.com/juggler-ai/juggler"
        }
      ],
      "date": "2026-07-17"
    },
    {
      "id": "tailscale-explains-exactly-how-it-works",
      "title": "Tailscale explains exactly how it works",
      "company": "Tailscale",
      "summary": "A long, honest architecture explainer — WireGuard, NAT traversal, DERP relays — that markets by teaching the mechanism instead of hiding it.",
      "artifact": "blog",
      "channel": [
        "blog"
      ],
      "why": "Most VPN marketing waves its hands at \"military-grade encryption.\" Tailscale\ndoes the opposite: one long post walks the whole system bottom to top — the\nWireGuard tunnels, the NAT-traversal dance, the DERP relays for networks that\nblock UDP. It is the signature-content play. A developer who reads it comes away\nable to reason about the failure modes, which is exactly the person who then\ntrusts the product enough to run it. Explaining the mechanism *is* the\ndifferentiation, because the competitors won't.",
      "demonstrates": "05-content-that-earns-trust",
      "demonstrates_url": "https://developer-marketing.vercel.app/guide/05-content-that-earns-trust/",
      "tags": [
        "content",
        "positioning",
        "dx"
      ],
      "source": {
        "label": "Tailscale — How Tailscale works",
        "url": "https://tailscale.com/blog/how-tailscale-works"
      },
      "sources": [
        {
          "label": "Tailscale Docs — technical overviews",
          "url": "https://tailscale.com/docs/concepts"
        }
      ],
      "date": "2026-07-11"
    },
    {
      "id": "supabase-caps-your-bill-by-default",
      "title": "Supabase caps your bill by default",
      "company": "Supabase",
      "summary": "A public pricing page with tiered plans, separated fixed vs variable cost, and a spend cap on by default — priced without a sales call.",
      "artifact": "pricing",
      "channel": [
        "web"
      ],
      "why": "The number is on the page. Supabase separates fixed from usage-based cost, links\nthe meter to a dashboard, and ships a spend cap that's *on by default* — the\nrunaway-bill fear that kills usage-based signups is pre-empted before the\ndeveloper asks. Opacity reads as something to hide; a real price with a cap is\nitself a trust signal. This is the verifiable-claims play applied to the one\npage where dev tools most often hide behind \"Contact sales.\"",
      "demonstrates": "01-positioning-for-developers",
      "demonstrates_url": "https://developer-marketing.vercel.app/guide/01-positioning-for-developers/",
      "tags": [
        "pricing",
        "positioning",
        "plg"
      ],
      "source": {
        "label": "Supabase Pricing",
        "url": "https://supabase.com/pricing"
      },
      "sources": [
        {
          "label": "Schematic — Supabase pricing page and costs explained",
          "url": "https://schematichq.com/blog/supabase-pricing"
        }
      ],
      "date": "2026-07-11"
    },
    {
      "id": "stripe-injects-your-test-keys-into-the-docs",
      "title": "Stripe injects your live test keys into the docs",
      "company": "Stripe",
      "summary": "A three-pane API reference with runnable, copy-once code that carries your own test key — the docs are the product tour.",
      "artifact": "docs",
      "channel": [
        "docs"
      ],
      "why": "Stripe's reference popularised the three-column layout — a stable nav on the\nleft, prose in the middle, runnable code on the right — but the tactic worth\nstealing is smaller and harder to copy: when you're logged in, the code samples\ncarry *your* test API key. There is no gap between reading and running. The\nskeptic pastes one block and sees a real charge object come back, on their own\naccount, before they've decided to trust you. The docs aren't describing the\nproduct; they are the first successful call.",
      "demonstrates": "02-docs-as-front-door",
      "demonstrates_url": "https://developer-marketing.vercel.app/guide/02-docs-as-front-door/",
      "tags": [
        "docs",
        "dx",
        "activation"
      ],
      "source": {
        "label": "Stripe API Reference",
        "url": "https://docs.stripe.com/api"
      },
      "sources": [
        {
          "label": "Moesif — the Stripe developer experience and docs teardown",
          "url": "https://www.moesif.com/blog/best-practices/api-product-management/the-stripe-developer-experience-and-docs-teardown/"
        }
      ],
      "date": "2026-07-11"
    },
    {
      "id": "cloudflare-turns-launches-into-a-recurring-week",
      "title": "Cloudflare turns launches into a recurring week",
      "company": "Cloudflare",
      "summary": "Themed \"innovation weeks\" batch a year of shipping into a daily-drop cadence that manufactures anticipation and measurable signups.",
      "artifact": "launch",
      "channel": [
        "blog"
      ],
      "why": "Instead of scattering releases across the calendar, Cloudflare batches them into\nrecurring themed weeks — Developer Week, Birthday Week, Security Week — each a\ndaily drop of real product, mostly free tier. The rhythm does the marketing:\ndevelopers learn the dates, the press pre-books coverage, and every day compounds\nthe last. It's the runnable-launch play at an operating cadence — the 2024\ninference launch during one such week drove a reported ~15% spike in new\ndeveloper signups. The format is the moat; a single big-bang launch can't create\nthe same standing anticipation.",
      "demonstrates": "07-launches",
      "demonstrates_url": "https://developer-marketing.vercel.app/guide/07-launches/",
      "tags": [
        "launches",
        "distribution",
        "content"
      ],
      "source": {
        "label": "Cloudflare — Welcome to Developer Week 2025",
        "url": "https://blog.cloudflare.com/welcome-to-developer-week-2025/"
      },
      "sources": [
        {
          "label": "Cloudflare — Developer Week 2024 wrap-up",
          "url": "https://blog.cloudflare.com/developer-week-2024-wrap-up/"
        }
      ],
      "date": "2026-07-11"
    }
  ]
}