Work/ngrok
Watch hours tripled
We worked with ngrok's DevRel, marketing and GTM teams to rebuild their YouTube channel around the developers who use it, in ngrok's own voice. Subscribers went from 450 to over 800 in the first week.
- Video strategy
- YouTube growth
- Motion graphics
- Short-form
3×
increase in watch hours
300+
new subscribers in week one
78%
subscriber growth in the first week
Accurate video that showed nobody
Developers love ngrok. You couldn't tell from the videos. They covered features accurately and competently, and never once showed a person on either side of them.
The team needed the channel to work for PLG, GTM and DevRel at the same time: grow on its own, make product announcements land, and keep running on a process ngrok's own people owned after we left. And it had to make infrastructure memorable, for developers at every level.
The framework
Voices
Voices is about highlighting the humans behind the infrastructure and how ngrok empowers developers to do more, faster, safer. Let's make infrastructure relatable.
- 01
Positioning first
We started from ngrok's core personas: how the company wanted to be seen, and who was actually watching.
- 02
The developer is the protagonist
Every story moved off the feature and onto the developer solving a problem with it.
- 03
A picture for the abstract parts
Most of what ngrok does has no natural picture. Storytelling and visual metaphor gave it one, so the hard parts stay with people after the tab closes.
Packaging, tested on ngrok's audience
We designed ngrok's YouTube identity, then A/B tested thumbnails to learn what their audience actually clicks on. Every new video's packaging started from whatever had already won.
Two packages for the same launch, shown to ngrok's own audience. What it clicked decided what shipped.
Product announcements, rebuilt as a repeatable system
Announcements had to keep shipping after the engagement ended, so we built the system and handed it to ngrok's team:
- Briefing templates
- Script frameworks for product launches
- Recording and delivery best practices
- Publishing and distribution strategy
Visuals rich enough for infrastructure
Load balancing, failover and traffic policy are hard to picture from a voiceover. Each concept got motion graphics built for it, in ngrok's brand, showing where the traffic goes and what happens when an upstream drops.
Requests spread across three upstreams, then rerouted the moment one goes down. Scroll to run it.
Every launch, cut for the feed
Each launch and long-form video also became a set of Shorts that open on the value, built to reach developers who had never heard of ngrok.
We cut ngrok's podcast and interview moments from events like KubeCon the same way. Those pulled in even more views and subscribers, and put ngrok in front of the cloud native community as one of the companies leading it.
Four launches, and the Short each one became.
The launches
Five launches, explained on screen
Launch and explainer videos for ngrok's channel, each with the motion graphics its feature needed.
Universal Gateway
ngrok.ai · routing AI traffic
Traffic Policy · OWASP CRS
Docker Desktop extension
Go SDK 2.0
Cut for awareness
The same launches, as Shorts
Each one gets to the value in the first few seconds.
From the event floor
Podcast moments, cut into Shorts
Interviews with ngrok's CEO and engineers, cut down to the moment that lands.
Subscribers
450 to 800+ in the first week, and steady growth every week after.
What shipped
Everything we delivered.
Strategy
- The Voices framework
- Voice and brand development
- YouTube channel strategy
- Thumbnail A/B testing
- Content production playbook
Production
- Launch and explainer videos
- Motion graphics for infrastructure concepts
- Shorts cut from every launch
- Podcast Shorts from events like KubeCon











