Spray-and-pray PR is the dominant strategy in developer tooling, and it is easy to recognize: the same boilerplate press release goes to a list of 200 journalists who have never covered your category, the Product Hunt launch is posted at 8 PM on a Wednesday with no pre-seeding, the Hacker News "Show HN" gets two upvotes and falls off the front page in forty minutes, and the Discord server sits at 340 members with six messages per week. The team hires a PR agency at $15,000 a month, which produces more press releases nobody reads and a spreadsheet of "outreach" to journalists who never respond. Earned media does not work that way. Reporters write about stories that serve their readers, not products that serve founders. Community does not grow from Discord invites, it grows from a reason to participate. Developer relations does not mean hiring a "DevRel" who gives conference talks. The failure is not effort, it is strategy: treating visibility as a distribution problem when it is a relevance problem. Buzz is Tonone's AI PR and community engineer, built to solve the relevance problem first, then execute the distribution.
Why bought media is losing to earned media
Paid distribution is in long-term decline for developer-facing products. Ad blockers, sponsored-content skepticism, and the collapse of trust in "promoted" placements mean that developers increasingly arrive at new tools through one of three paths: a trusted person in their network mentioned it, they found it on Hacker News or a subreddit while researching a problem, or they read a piece of genuine journalism that treated the product as news worth covering. All three paths require earned credibility, not purchased placement. A single TechCrunch article with genuine editorial endorsement produces conversion quality that a $50,000 sponsored banner campaign will not approach, because the reader's trust in the medium transfers to the product. None of those outcomes are purchasable.
The problem is that earned media strategy is operationally expensive in a way that paid media is not. Earning press coverage requires knowing which journalists cover your category, understanding what story angle serves their readers, writing a pitch that does not read like a press release, and timing the outreach to a news hook that makes the story timely. Executing a Product Hunt launch requires coordinating upvotes from real users, writing a maker comment that drives discussion, and monitoring the ranking in real time. Executing a Hacker News post requires a title that is interesting without being linkbait, an understanding of what gets shadowbanned, and prepared responses to inevitable skeptical comments. Each task requires domain expertise that most early-stage teams do not have, and none of them are tasks a generic AI assistant executes well.
What a PR and community engineer actually does
The job title "PR and community engineer" does not exist at most companies. The function is split between a PR agency (media relations), a community manager (Discord), a DevRel hire (conference talks and tutorials), and a social coordinator (LinkedIn). Each role is siloed, which produces the most common failure: the press coverage, community, and developer program say something slightly different, none reinforce each other, and there is no coordinated moment that creates a step-change in awareness. A genuine PR and community engineer does the whole job: audits the visibility position, designs a launch that coordinates press, community, and social into a single reinforcing moment, and runs the developer relations program with defined tiers, ambassador incentives, and metrics. Done well, that produces compounding returns: community members become the press sources, press coverage brings community members, and developer ambassadors create organic word-of-mouth that paid media cannot replicate.
The conventional alternative is a PR agency retainer at $10,000 to $25,000 per month. That buys journalist list access, a press release writer, and outreach on your behalf. What it does not buy is community strategy, developer relations, HN expertise, or the coordination intelligence that turns a launch moment into a compounding growth event. Agencies are optimized for press coverage, not for the full earned media ecosystem that developer tool companies need.
Meet Buzz
Buzz is Tonone's dedicated AI PR and community engineer: a purpose-built agent for the full earned media and community workflow, from visibility audit through press pitching, coordinated launches, open source community building, and developer relations programs. It does not write generic press releases from prompts. It audits the current press and community health first, identifies the story angles that will resonate with specific journalists covering your category, designs coordinated launch moments that bring press and community into alignment, and runs the developer relations program with the same rigor as a dedicated DevRel team. Buzz treats earned media as a system with compounding mechanics, not a one-time distribution event.
Tonone's Buzz is the AI PR and community engineer that audits your visibility position, designs coordinated earned media launches, crafts personalized press pitches, and builds developer communities with real retention mechanics so your growth compounds from trust rather than purchased placement.
What Buzz actually does
Auditing your press coverage, social presence, and community health
Before any launch or outreach work begins, Buzz needs a baseline. The buzz-recon skill audits the current state of your earned media position: press coverage volume and quality over the last 12 months, social presence and engagement rates across relevant channels, community health metrics (member count, activity rate, topic distribution, retention), and competitor visibility benchmarking. The output is a visibility health brief that identifies the specific gaps: which journalist segments are aware of the product and which are not, where the community is active and where it is dormant, which social channels are producing distribution and which are producing nothing, and what the competitive visibility gap looks like in quantitative terms. buzz-recon also surfaces the story angles already present in the coverage record, the themes that reporters have already shown interest in, which are the highest-probability hooks for future pitches. Running recon before pitching prevents the most common PR mistake: pitching an angle that has already been covered or that the journalist has explicitly rejected in past work.
Designing and executing coordinated launch plans
A product launch is not a ship date, it is a coordinated argument made to the right audiences through the right channels in a sequence that amplifies each channel's contribution to the next. The buzz-launch skill designs and executes that coordination: the pre-launch seeding plan (who gets early access and when, to prime the community for launch day activity), the Product Hunt submission strategy (timing, gallery assets, maker comment template, upvote coordination with existing users), the Hacker News post plan (title, body, submission timing based on HN traffic patterns), the newsletter distribution (which newsletters cover your category and what lead time they require), and the day-of monitoring and response playbook. The launch plan is sequenced so that community activity on launch day informs the press narrative, press coverage extends the launch's tail, and the newsletter distribution captures readers who missed the launch week. buzz-launch treats each channel as an input to the others, not as a parallel but independent distribution event.
Social media strategy and post drafting
Social media for developer tools is a distinct discipline from consumer social: the audience is skeptical of hype, responsive to technical specificity, and more likely to engage with a post that demonstrates competence than one that announces a feature. The buzz-social skill produces a social strategy calibrated to the developer audience: the right posting cadence, the content mix (technical depth versus accessibility versus community spotlights), the platform-specific format differences between Hacker News comments, Twitter threads, and LinkedIn posts, and a library of draft posts for each planned content type. buzz-social also drafts the social content for specific moments, the launch week social schedule, the response to press coverage, the community milestone announcement, and the technical deep-dive thread. Every draft is written in a voice that reads as a competent practitioner, not a marketing department, because developer audiences disengage immediately from copy that sounds like a press release.
Writing media pitches and press releases for journalist outreach
The median press release lands in a journalist's inbox, is read for four seconds, and is deleted. The four seconds produce one question: is there a story here that serves my readers? Generic product announcements answer that question with a no. The buzz-pitch skill writes media pitches and press releases that answer the question with a yes: the pitch leads with the story angle (what is changing in the world that makes this product newsworthy), not with the product description; it is written for the journalist's specific beat and audience, not for general circulation; it includes the evidence that makes the story credible (data, traction, notable customers); and it is short, because long pitches signal that the writer does not understand what a reporter needs. buzz-pitch also produces the full press release for situations that require one: a funding announcement, a major partnership, a product pivot, a regulatory development. The press release follows AP style, includes a genuine news hook, and is structured so that a reporter can derive their article without needing to rewrite the material from scratch.
Building and managing open source community
Open source community health is measurable, and most communities are less healthy than their member counts suggest. The signal is contribution depth: the ratio of active contributors to lurkers, the time from first to second contribution, and the ratio of issues filed by non-core members to issues resolved by non-core members. The buzz-community skill builds the mechanics that improve those metrics: the contribution onboarding guide that converts first-time contributors to regulars, the Discord channel structure that routes conversations to the right depth, the community recognition program providing non-financial incentives, and the health dashboard that tracks what matters rather than vanity counts. buzz-community also produces the engagement content that keeps the community active between releases: the weekly digest, contributor spotlight, and the RFC process for community input on product direction.
Running a developer relations program with tiers, ambassadors, and metrics
Developer relations, done properly, is a growth program with defined mechanics: community tiers that give developers increasing recognition as their contribution grows, an ambassador program with explicit benefits and obligations, a content program that turns community expertise into distributed visibility, and a metrics framework that connects DevRel activity to business outcomes rather than conference talk counts. The buzz-devrel skill designs and operationalizes that program: the tier structure with entry criteria and benefits, the ambassador recruitment and onboarding process, the content calendar and support resources, the referral mechanics that let the program prove its business value, and the quarterly DevRel review. buzz-devrel is the difference between a community that feels like a marketing list and one that behaves like a distributed advocacy team.
Crafting Hacker News posts with anti-shadowban rules and response templates
Hacker News has a distinct culture, and products that do not understand that culture either get ignored or get ratio-ed. The buzz-hn skill is a specialist for HN distribution: it crafts the post title using the specific patterns that HN rewards (technical specificity, genuine novelty, no marketing language), writes the body text for Show HN and Ask HN posts that meet the community's expectations for substance, applies the anti-shadowban rules (no direct link promotion in the first comment, no upvote coordination requests, no fake grassroots seeding), and produces a response template library for the categories of comments the post will predictably receive: the skeptical question, the "why not just use X" objection, the feature request, the bug report, and the hostile comment that deserves a measured rather than defensive response. HN front-page placement for a developer tool can produce thousands of qualified visitors in a day; a poorly-executed HN post that gets flagged or shadowbanned produces nothing. buzz-hn is the difference between those two outcomes.
Personalized media and podcast pitches per journalist or host
The difference between a pitch that gets a response and one that does not is almost always specificity: the pitch demonstrates that the sender read the journalist's recent work, understands their beat, and has a story that serves their readers, rather than a story that serves the sender's marketing goals. Generic pitches, even well-written ones, read as generic. The buzz-outreach skill produces personalized pitches per target journalist or podcast host: it researches the journalist's recent coverage to identify the specific beat and story pattern they follow, writes the pitch angle that aligns the product's news with a story the journalist would want to tell, and calibrates the pitch length and format to the journalist's apparent preferences based on their public writing. For podcast pitches, buzz-outreach identifies the specific topic framing that fits the show's format and audience, and writes the pitch from the host's perspective, what would make this guest a good episode rather than what would make this a good marketing appearance.
A worked example: launching a developer tool with Buzz
A team has built an open source database migration tool. It has 800 GitHub stars, no press coverage, a Discord with 120 members, and no developer relations program. They are planning a v1.0 release in three weeks. Here is the sequence they run with Buzz.
Week one begins with buzz-recon: the audit reveals no major publications have covered the product, two relevant journalists at The New Stack and InfoQ have recently covered competing tools, the Discord is primarily used for bug reports, and GitHub star velocity has been flat for two months. The recon report identifies three viable story angles: the performance benchmark against the leading competitor, the migration from a deprecated tool (timely as its sunset date approaches), and the open source governance model as a differentiator. Week one also runs buzz-community to restructure Discord and produce the contribution guide ready for v1.0 traffic.
Week two runs buzz-outreach to write personalized pitches for those two journalists using the benchmark angle, the most concrete and verifiable story. The pitches go out with a two-week embargo aligned to the v1.0 date. Simultaneously, buzz-hn produces the Show HN post: the title leads with the tool's specific capability, the body includes the benchmark data and an explicit acknowledgment of what the tool does not yet do (which HN readers trust more than a post that claims everything). The response template library covers the "why not just use Flyway" objection and predictable licensing questions.
Launch day, buzz-launch coordinates the timing: the HN post goes live at 9 AM Eastern on a Tuesday (peak HN traffic); the Product Hunt submission is seeded by the 120 Discord members briefed pre-launch; the two journalists publish under the embargo, producing backlinks that extend HN traffic into a second day. The buzz-social schedule runs through launch week: technical deep-dives on Twitter, a LinkedIn post on the governance model, and a community digest spotlighting early contributors. By end of week: 3,400 new GitHub stars, 680 new Discord members, two pieces of genuine press coverage, and a front-page HN placement. None required a PR agency retainer.
Run buzz-recon before planning any launch activity. The most common launch failure is executing the right tactics in the wrong sequence, pitching journalists before the community is ready to amplify the coverage, or posting to HN before the benchmark data that makes the post substantive is available. Recon reveals the gaps before the launch calendar is set, so the tactics reinforce each other rather than landing in isolation.
Buzz vs the alternatives
Buzz is not a press release generator and it is not a social media scheduler. It produces the earned media strategy and community mechanics that make press pitches land and communities grow, then executes the content that implements the strategy. The comparison below makes the functional differences concrete.
| Capability | Tonone | Generalist chatbot | Cursor / Copilot |
|---|---|---|---|
| Visibility audit before outreach | Yes, buzz-recon audits press coverage, community health, social presence, and competitor visibility before any pitch or launch activity | No, writes pitches from whatever description is provided without auditing current visibility position | Limited, tracks media mentions but does not connect them to community health or story angle recommendations |
| Coordinated multi-channel launch (HN, Product Hunt, press, newsletter) | Yes, buzz-launch designs sequenced coordination so each channel amplifies the next, including day-of monitoring playbook | No, produces individual launch assets without coordination logic or channel sequencing | Partial, manages press outreach timeline but does not coordinate with HN, Product Hunt, or community seeding |
| Personalized pitches per journalist or podcast host | Yes, buzz-outreach researches each journalist's recent beat and writes the pitch angle from the journalist's reader-service perspective | No, produces a generic pitch template that does not reflect the journalist's specific beat or recent coverage | Partial, maintains journalist database and tracks coverage but writes the same pitch for all recipients on a list |
| HN-specific post crafting with anti-shadowban rules | Yes, buzz-hn produces title, body, submission timing, and response template library calibrated to HN culture and moderation rules | No, writes a post without knowledge of HN shadowban triggers or community expectations | Not applicable, PR agencies do not manage HN distribution |
| Developer relations program with tiers and ambassador mechanics | Yes, buzz-devrel designs tier structure, ambassador recruitment, content calendar, and the metrics that connect DevRel to business outcomes | No, produces DevRel content ideas without program structure, tiers, or measurement framework | Not applicable, PR agencies do not design developer community programs |
| Open source community health and contribution mechanics | Yes, buzz-community builds contribution onboarding, Discord structure, recognition programs, and tracks contribution-depth metrics | No, produces community post drafts without analyzing contribution health or designing retention mechanics | Not applicable, PR agencies track media mentions, not community contribution rates |
Tonone's Buzz buzz-outreach skill researches each journalist's recent beat and writes a pitch angle from the journalist's reader-service perspective, not a product announcement that serves the sender. That specificity is the difference between a pitch that gets a response and one that gets deleted.
Install and try
Tonone is free and MIT-licensed. Install it once and all agents, including Buzz, are available in your Claude Code session. You pay only for the Claude Code token usage during work. Start with buzz-recon on your current press coverage and community to identify the gaps before planning any launch activity.
1. Add to marketplace
2. Install Buzz
Frequently asked questions
- What does Tonone's Buzz do?
- Buzz is Tonone's AI PR and community engineer. It audits press coverage and community health (buzz-recon), designs coordinated launch plans for Product Hunt, HN, and newsletter channels (buzz-launch), drafts social media strategy and posts for developer audiences (buzz-social), writes personalized press pitches and press releases (buzz-pitch), builds open source community mechanics (buzz-community), designs developer relations programs with tiers and ambassadors (buzz-devrel), crafts HN posts with anti-shadowban rules (buzz-hn), and writes personalized media and podcast pitches per journalist or host (buzz-outreach).
- How is Buzz different from just using ChatGPT for PR writing?
- ChatGPT writes press releases and pitch templates from whatever product description you provide. Buzz audits your current visibility position first, identifies which journalists cover your specific category and what story angles they have recently responded to, writes pitches personalized to each journalist's beat and audience, and coordinates the launch across channels so each amplifies the next. The difference is the presence of research, strategy, and coordination rather than generic content production.
- What does buzz-hn do differently from just posting to Hacker News?
- buzz-hn applies the specific knowledge required for HN success: title patterns that the community rewards, body copy that meets the expectation for substantive technical content, submission timing based on HN traffic patterns, anti-shadowban rules (the behaviors that trigger HN's moderation systems), and a response template library for the predictable comment categories including skeptical questions, competitor comparisons, feature requests, and hostile comments. Posting without that knowledge produces either a post that gets ignored or one that gets flagged.
- Can Buzz replace a PR agency?
- Buzz covers the earned media workflow that agencies typically handle (press pitching, press releases, outreach coordination) plus the community, DevRel, HN, and social media dimensions that agencies do not cover. What Buzz does not replicate is pre-existing personal journalist relationships, which an established agency brings. For early-stage teams that have not yet built those relationships, Buzz provides the strategy and content quality that makes those relationships possible to build without a retainer.
- What does buzz-devrel produce?
- The buzz-devrel skill produces a developer relations program design: community tier structure with entry criteria and tier benefits, ambassador recruitment process and onboarding materials, content calendar and support resources for ambassadors, referral and attribution mechanics that let the program prove its business value, and a quarterly DevRel review framework that assesses program health against metrics connected to business outcomes rather than activity counts.