Net revenue retention, one table at a time
The formula is one line. Getting the rows right takes the rest of the post: which accounts count, what to do with annual prepayments, and the cohort table we use every month.
Notes from the Brightkeel team
How we run revenue reviews and incident reviews, why the product works the way it does, and what changed in each release.
Posts
Column stores, a sort cache keyed by view, and the two indexes we removed.
EVElliot Vance7 minRecent items first, commands that show their keys, and why we cap results at 12.
RCRafael Costa6 minFour questions, one table of affected accounts, and no blame. The template we use.
KHKai Halvorsen5 minDensity settings, touch targets and the compact mode half our users turn on.
RCRafael Costa4 minRetry timing, the email that recovers the most cards, and when to pause billing.
DMDiego Marín8 minWhat we record, how we store it for seven years, and the export format we settled on.
NBNoor Bakr6 min
Release notes
Every version, newest first. Breaking API changes get 90 days' notice and a line here.
- Nov 4, 2026
4.12: audit log exports
ShippedExports now include API key events and the IP address behind each change.
- New filter: actor type (person, key, automation)
- CSV columns keep the same order across exports
- Oct 15, 2026
4.11: compact density everywhere
ShippedEvery table and menu now follows the 32px compact setting, and it syncs across devices.
- Shift Cmd D switches density from any screen
- Sparklines keep their height in compact mode
- Q4 2026
Cohort tables in reports
In progressRetention by signup month, with each cell opening its accounts.
- 2027
ap-south data region
PlannedA Mumbai region with the same features as eu-west.