The Buddy List Is Back, and It Says More About Your Ops Stack Than Your Social Life
Cross-border operators spend their days staring at dashboards nobody else can see: Seller Central health scores, 3PL inventory snapshots, ad-spend pacing curves, chargeback ratios. The lonely part of running a brand across time zones isn’t the work — it’s that nobody on your team knows whether you’re actually at the keyboard or just “online.” So when I saw Die With Me launch on Product Hunt, pitched by maker Weiwei as “an AIM buddy list for your AI usage,” my first reaction wasn’t nostalgia. It was: this is a presence layer, and presence layers are exactly what distributed e-commerce teams have been missing since Slack turned into a graveyard of green dots.
What Die With Me Actually Is (and Isn’t)
Strip away the Gen-X nostalgia and here’s the mechanic: Die With Me shows you which of your friends are currently locked into Claude Code or Codex, who’s stepped away, and whose AI session has “clocked out.” Weiwei’s framing is deliberately retro — the buddy list, the away message, the excuse to say hi. The launch even ships with a Product Hunt-specific invite code at diewithme.co/join for early testers.
That’s the whole product surface as described. No pricing, no team tier, no API docs, no enterprise SSO — all not disclosed. It’s a social presence toy with a developer-tooling hook, and the comment thread is where the real signal lives.
Chris Messina, who hunted the launch, opened with “I token-died this week, but fortunately I was not alone” — which is the entire emotional pitch in one line. Bud Broesky-Herron remembered the original iPhone app and called it a “cool spin.” And then Gal Dayan asked the question every operator should be asking: how are you pulling the allowance numbers, since neither Claude Code nor Codex expose that over a public API? That question went unanswered in the thread. Remember it — we’ll come back to it.
Why this matters more to Amazon sellers than Shopify ones
Here’s the split I keep coming back to. A Shopify DTC operator runs a lean team — often three to eight people, one founder wearing four hats, and a shared Slack channel where everyone can see who’s shipping. Presence is implicit. You know your ops lead is awake because the fulfillment exceptions channel lit up at 6am.
An Amazon FBA brand owner runs a different animal. You’ve got a VA in Manila handling Seller Central cases, a PPC contractor in Eastern Europe pacing Amazon Ads bids, a sourcing agent in Shenzhen, and a US-based brand manager. Nobody shares a timezone. Nobody shares a tool. The only signal that anyone is working is the lag between a stockout alert and someone reacting to it. A presence layer that says “your sourcing agent is locked in right now” is worth more to that operator than to a Shopify founder who can just walk over to a desk.
That’s the actual thesis hiding inside Die With Me: presence is an operational primitive for cross-border teams, and we’ve been treating it as a social feature.
The Comparison Set: Where This Sits Against Real Tooling
Let me be honest about the competitive landscape, because “AIM for AI usage” sounds cute until you ask what it replaces.
The obvious incumbent for “who’s working on what right now” is Linear — its activity feed and assignee presence are genuinely useful for product teams, but it’s issue-centric, not session-centric. It tells you what’s assigned, not who’s actually typing. Notion has presence dots, but they’re within a document. Slack has status, but status is a lie 90% of the time — “active” just means the app is open.
For AI-specific usage tracking, the real competitors are dashboards, not buddy lists. Helium 10’s Adtomic, Jungle Scout’s Cobalt, and the whole category of Amazon ops tooling give you aggregate spend and performance — never who on my team is currently burning tokens. That’s a genuine gap.
Die With Me’s differentiation is that it inverts the dashboard. Instead of “here’s your total AI spend this month,” it says “here’s a human, right now, working.” That’s a fundamentally different product category — closer to a Discord presence indicator or a Figma multiplayer cursor than to any analytics tool.
Where the math breaks
Gal Dayan’s unanswered question is the whole ballgame. If Die With Me is polling local usage logs — reading the files Claude Code and Codex write to disk — then it only works for people running those tools locally on a machine where the app can see the filesystem. That’s fine for a solo dev with a MacBook. It’s useless for a cross-border team where the VA is on a locked-down corporate laptop and the PPC contractor runs everything in a browser tab.
If instead it’s scraping session tokens or inferring activity from something else, that’s a trust and ToS question. Anthropic and OpenAI have both been tightening API access patterns, and a third-party tool that reads session state is one policy update away from breaking.
Either way: the presence signal is only as good as the coverage. A buddy list that shows three of your eight team members is worse than no buddy list, because it creates false confidence. You’ll assume the other five are offline when they’re actually grinding in a tool Die With Me can’t see.
What cross-border operators should actually borrow
Forget the AI-specific wrapper. The borrowable idea is this: treat presence as a first-class ops metric, and instrument it deliberately.
Concretely, three patterns I’d steal:
- Session-level, not task-level, visibility. Most ops tools show you tickets. Die With Me shows you sessions. For a cross-border team, “my sourcing agent has been in the Alibaba chat for 40 minutes” is more actionable than “ticket #4471 is open.”
- Away states as a feature, not a bug. The “touching grass” and “clocked out” states in Die With Me are jokes, but the underlying mechanic — explicit, visible off-states — is what prevents the always-on burnout that kills cross-border teams. If your team can see each other’s off-hours, they stop feeling guilty about taking them.
- A shared, low-stakes social surface. The buddy list worked because it was ambient. You didn’t have to post. You just had to be there. A cross-border team’s version of this might be a shared Loom channel, a pinned Slack canvas, or honestly just a shared Notion page where everyone drops one line at start-of-shift. The tool matters less than the ritual.
Where My Judgment Says It Falls Short
I want to like Die With Me more than I do, and here’s why the ceiling is low.
It’s a consumer social product wearing a dev-tool costume. The invite link, the buddy list metaphor, the away messages — this is a toy. Toys can grow into platforms (see: Figma started as a design tool, Notion started as a note app), but they do it by adding a wedge that makes them operationally necessary. Die With Me’s wedge is “fun.” Fun doesn’t survive the first time a founder asks “can I export this to a CSV for my ops review?”
The unanswered API question is a red flag. When a maker doesn’t answer the one technical question in the thread, it usually means the answer is “we’re scraping” or “we don’t fully know yet.” Neither is fatal, but both mean you shouldn’t build a workflow on top of it.
No team tier, no pricing, no SSO — all not disclosed. For a cross-border operator, that’s a non-starter for anything touching production workflows. You can’t put a tool in front of a VA in Manila without knowing how it handles access, and you can’t put it in front of a contractor without knowing what it costs.
The AI-usage framing is narrower than the problem. Cross-border teams don’t just use Claude Code and Codex. They use ChatGPT, Gemini, Perplexity, Cursor, and a dozen vertical AI tools. A buddy list that only covers two of them is a partial view — and partial views are dangerous when you’re making staffing decisions.
Why Amazon sellers should care more than Shopify ones (revisited)
I said this earlier and I want to sharpen it. A Shopify DTC brand can afford to be informal about presence because the feedback loop is tight — a broken checkout page gets noticed in minutes. An Amazon FBA brand has a feedback loop measured in days. A hijacked listing, a suppressed buy box, a competitor’s review-bombing campaign — these things can run for 48 hours before anyone notices. Presence isn’t a nice-to-have for that operator. It’s the difference between catching a problem in hour two and eating a week of lost sales.
So the real question isn’t “should I use Die With Me.” It’s “do I have any presence layer at all, and if not, what’s the cheapest way to build one this week?”
What I’d Watch / Test Next
Three concrete things I’d do in the next seven days.
First, audit your own presence gap. Open a spreadsheet and list every person on your cross-border team, their timezone, their primary tool, and how you currently know whether they’re working. If more than two rows say “I don’t know” or “I check Slack,” you have a presence problem. Die With Me isn’t the fix, but the audit will tell you what is.
Second, test the Die With Me invite link yourself at diewithme.co/join if you’re curious — it’s free to try and the nostalgia is genuinely fun. But go in with eyes open: this is a social experiment, not an ops tool. Don’t put it in front of a contractor and expect it to replace your standup.
Third, watch the API question. If Weiwei answers Gal Dayan in the thread and it turns out the usage data comes from a clean, documented source, this becomes a much more interesting product. If it stays unanswered, treat Die With Me as what it is: a clever nostalgia play that happens to point at a real gap in cross-border ops tooling. The gap is real. The product filling it probably isn’t this one.
