Kernel handed Goosewin its launch calendar. Reach tripled in a month.

About Goosewin

Goosewin is a fractional DevRel team led by Dan Goosewin. Kernel got Dan plus a writer, a video editor, and a designer, all working inside Kernel's Slack and repos. On this page, Goosewin and the team mean that group.

Background

Kernel builds browser infrastructure for web agents and automations: cloud browsers an AI agent can drive, with proxies, managed auth, session replay, and payments built in. By August 2026 the platform had launched its 50 millionth browser, and the product team was shipping fast, with a run of releases due within weeks of each other.

The challenge

The launches were ready, but the capacity to launch them well was not. Each one needed a script, a recording, an edit, and a post that held up next to the best developer brand accounts, and there was nobody free to make that happen on the schedule the product team was keeping.

Why Goosewin

Catherine knew Dan from hackathons and from his time leading developer relations at Vapi. The first call was July 28. The proposal went out the same day, and the pilot month was signed on July 29.

“I knew Dan from hackathons and had seen his work during his time at Vapi. When I found out that he has his own fractional DevRel practice, I knew immediately he was what we needed.”

“We had launches we wanted to run the following week, and I knew from his time at Vapi that he knows how to talk to and market to developers. I did two reference checks with other founders I knew, and both spoke incredibly highly of him as well. Dan sent a proposal within an hour and we were in a shared Slack channel same afternoon. That gave me confidence that his team would be able to move as quickly as we do.”

Month one

Kernel never wrote a brief. Goosewin joined the shared Slack channel and got to work. The team learned Kernel's brand and voice before the first video shipped, then took work the way an in-house team does: a launch, a clip, a page, a demo, dropped into a shared channel and picked up from there.

“When I started dropping work into our shared channel the way I do with my own team. A podcast clip, a case study, a landing page section, a demo. No briefs, no kickoff calls. The Goosewin team picked it up, tracked it, and it got done.”

Eight launches went out in the first thirty days, from Hypeman on August 4, which passed 60K views on X, to Proxies v3 on September 1. Each came in as a product spec and left as a finished post in Kernel's voice: scripted, recorded, edited, scheduled, and shipped through Kernel's review.

When something on the website or in the docs needed fixing, the team opened the pull request rather than filing a ticket. Sixteen went in during month one, across the landing page, pricing, docs, and Kernel's example repos.

Along the way Kernel asked for help beyond launches: out-of-home advertising and venue research for a November campaign, and its September Fireship ad. Priced options with sources came back within days, and Kernel handed both over.

Outcomes

Kernel's X account in August against July. Nearly three times as many posts went out, every one with a custom visual, and reach followed. Followers grew 9.6% month over month.

• Eight launches shipped in the first thirty days, five of them in the first two weeks
• Sixteen pull requests opened against Kernel's website, docs, and examples, fourteen merged
• Pilot month upgraded to a full retainer in three weeks
• Fireship ad and the November campaign handed to Goosewin

“After two weeks I'd seen enough. Five launches went out and every one of them looked like us. I asked about billboards and party venues and had priced options with sources back in a couple of days. It stopped being a question of whether to expand and became a question of how much to give them.”