Honeybadger
Day 17 after signup
Validating changes in production
Why it works
- Open by explaining the newsletter’s purpose and promise of brevity so readers know what to expect.
- Pair an outside customer example with a first-person account of using the product to make the topic concrete from both angles.
- End the roundup with a low-pressure invitation to reply, turning a broadcast into a conversation.
How it is built
- Newsletter introduction
- Customer use case
- Team product example
- Recent product releases
Email copy
Hi [First name], We're rebooting our monthly product newsletter at Honeybadger. If you're reading this, it's because you signed up for our newsletter on our website, or you're a Honeybadger customer and receive our monthly product updates. We want to try something new. There's so much we could tell you about, but we know you're busy figuring out what your job even is in 2026—and the good stuff we're shipping is in the changelog anyway. So instead of sending you a wall of features each month, we'll keep our emails brief and focused on the interesting bits of building and scaling Honeybadger. Validating changes in production ClickFunnels had bots using their checkout forms to test stolen credit cards. Blocking the bots risked blocking real customers, so they ran bot detection in report-only mode first. Claude instrumented the feature with Honeybadger and built a custom dashboard to validate the results so that there were no surprises when they turned it on. Here's what VP of Platform Engineering Nate Vick had to say: That's one thing that I've just totally loved doing with these tools: validating and gaining confidence, and then flipping the switch and removing the feature gates. Read how ClickFunnels did it → This is how we use Honeybadger every day Earlier this week we deployed a feature to enable signed URLs in the web service we use to generate social media graphics (based on this cool Elixir OG image generator by our friends at SavvyCal). Instead of rejecting unsigned requests right away, we're monitoring the results in Honeybadger before requiring the new signatures. Good thing we waited: about 40% of requests are still unsigned. Most of those are crawlers and pages cached before the change. We'll flip the switch once that number drops. Notable things we shipped recently 48 new ways to slice and dice your logs Official Honeybadger connector for Claude Code/Desktop Honeybadger agent skills (now in beta, more on this 🔜) Around our orbit Josh is headed to SF Ruby in November. Say hello. Ben took a vacation and spent half his weekly tokens on Breakwater, his side project for selling self-hosted software. Kevin is working on some new behind-the-scenes blog posts. His latest is How we teach LLMs to write BadgerQL Blue Ridge Ruby returns April 2027. Yay! Uplifting news: CSS-Tricks has a new independent owner. Good to see quality developer education making a comeback. That's all for now. Are you validating changes like ClickFunnels, or using Honeybadger in a novel way? Shoot us a reply—we wanna hear your story. —Josh, Ben, and the Honeybadger Crew Unsubscribe · View in browser