Notes on founder-led support
Practical, opinionated writing on answering your own customers — live chat, email, and keeping support lean as you grow.
They're often framed as rivals, but they're built around different surfaces: one lives in your terminal, the other in your editor. That's the whole decision.
The two frontier labs both ship a terminal coding agent now. They're more alike than the benchmarks suggest — the real differences are ecosystem and fit.
Mention @claude on a GitHub issue and a PR shows up. The setup takes five minutes; the interesting question is what fills the issue queue.
Laptop closed, agent still working: there are now six real ways to get there. A map of all of them — and the queue problem none of them solve.
The $5-a-month always-on agent box is now a standard founder setup. The part nobody writes about is what fills its queue. The answer: your customers.
The remote-control layer of agentic coding got commoditized in one quarter. The layer above it — deciding what the agent works on — is where the leverage moved.
Talking to users early is the highest-leverage thing you can do — and the easiest to put off. Here's how to make it happen by default, not by willpower.
Telegram is a surprisingly good support channel for founders — fast, on your phone, already open. Here's how to turn it into a real support inbox.
Self-hosting your live chat sounds appealing — until you're the one keeping it alive at 2am. Here's how to actually decide between open-source and hosted.
You don't need a six-seat helpdesk to answer customer email well. Here's the lean version — and the honest line for when you've outgrown it.
Live chat and email aren't rivals — they're two moments in the same conversation. Here's when each wins, and why one queue beats picking a side.