PBPraneet Brarinpraneetbrar.hashnode.dev·10h ago · 9 min readDon't open Stripe for every support email. Keep three billing columns on the user.Say you have 40 paying customers. Not huge, but enough that billing emails start showing up every week. "What plan am I on?" "When do I renew?" "Did my card go through, the app says something weird." 00
PBPraneet Brarinpraneetbrar.hashnode.dev·2d ago · 7 min readAdd a last_seen_at column. Your quiet-user list writes itself.Say you have under 100 users. Maybe 70 signed up, around 25 actually did the thing your product exists for, and some of those 25 have stopped showing up. Quick question: which ones? Most founders at t00
PBPraneet Brarinpraneetbrar.hashnode.dev·5d ago · 5 min readKeep a decision log. Future you has no idea why you did that.Last month I spent most of a Saturday undoing a change I had made in April. Moved the pricing toggle back, rewrote the onboarding email again, the whole thing. Then on Monday I found a Slack message t02A
PBPraneet Brarinpraneetbrar.hashnode.dev·Oct 7 · 6 min readRemove the feature nobody uses. Here's how I do it without upsetting the few who do.Every small SaaS I've worked on has a feature that nobody uses and everybody has to maintain. Usually it shipped because one loud user asked for it, or because I thought it would make the pricing page02N
PBPraneet Brarinpraneetbrar.hashnode.dev·Oct 5 · 6 min readDon't build an admin panel yet. Save five SQL queries instead.Every SaaS I've started had the same week two. The product barely works, there are maybe a dozen users, and I'm building an admin dashboard. Tables, filters, a little search bar, a "view as user" butt03R
