9:41

Bramblewick

Transactional email for engineers

How Bramblewick turned a launcher into its command layer

Priya Raghunathan has shipped developer tooling since the beta days. Today her team runs onboarding, support triage and release notes through one keyboard-first surface.

41Internal tools replaced
6.4×Faster support lookups
18sMedian answer time
Backlit keyboard at a night desk — photo by Karol D on Pexels
Keyboard-first by default — every runbook, doc and changelog one keystroke away.
The challenge

Knowledge scattered across too many tools

Documentation lived in a wiki, walkthroughs on video, support tickets in a third place. Onboarding meant handing a new hire a list of forty logins and hoping for the best.

“We were paying for context switching in minutes a day, every day, per person.”

Priya Raghunathan, DX Engineer at Bramblewick
The results

Seconds instead of minutes

  • Support answers in one keystroke. Ticket queries that once meant three tabs now resolve inside the palette.
  • Manual busywork removed. Asset renaming and clip compression run as a single scripted command.
  • Onboarding without a scavenger hunt. New engineers get one hub for every resource on day one.
  • Shared vocabulary. Teams describe workflows by command name, not by tool name.
Read the full story
Customer storiesUpdated March 12