Published Product3 min read
PostHog's account team stopped booking check-ins and started competing for attention
A customer success manager published the actual Slack messages he uses to pull feedback out of steady-state accounts. The mechanism is worth copying; the evidence is thinner than the confidence.
Not a builder's beat, but builders have a standing stake in it.See today for builders

What happened
- Customer success managers at PostHog spend a lot of time getting customers to talk to them.
- The author publishes the actual messages he has sent that worked, and notes that not every one includes giving away free merch.
- At PostHog, by the time a customer makes it to the author's book, the expectation is that they are in a steady state.
- The author writes that when the product is set up and working, a direct ping from some employee of a software vendor 'might as well have the urgency of a glacier', and jokes about being the guy who only types Slack messages in lowercase letters.
- The author writes that if he was going to be competing for attention, the outreach needed to be short, attention grabbing and valuable, with a '2x strength multiplier' if somebody laughs.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
A customer success manager at PostHog has published the outreach he actually sends to customers, and none of it is a meeting cadence: it is short, jokey Slack pings, usually attached to a merch code [1][2][9]. The framing is the useful part for anyone running post-sales. He describes the problem as competition for attention rather than a gap in the calendar, because by the time an account reaches his book the expectation is that it is in steady state, and a direct ping from a vendor employee to a working installation has, in his words, "the urgency of a glacier" [3][4].
That is a different diagnosis than most account teams work from. The default assumption is that feedback is a scheduling problem solved by a recurring call. His conclusion was that outreach had to be short, attention grabbing and valuable, with a stated bonus if the recipient laughs [5]. He contrasts this with earlier post-sales roles spent in back-to-back meetings alongside a backlog of Jira tickets he had to beg colleagues to look at [6].
The published examples are worth reading as mechanics. Four messages are quoted as having produced quick calls or continued engagement [14]. One offers a straight trade, thirty minutes for merch, with a green square or a no-entry emoji as the reply mechanism, which reduces the cost of answering to a single click [7]. One delivers a dashboard the manager built while impersonating the customer's account, and reports seven emoji reactions [8]. One tells a user they are in the top ten of all PostHog users for the company's MCP and asks for time in exchange for a merch code [9]. One hands out a gold medal to a top user and a t-shirt code, and produced a confused DM from an engineering manager, which after clarification became an opening to press for product feedback and to pull more users into a shared Slack channel [10]. Three of the four attach an incentive, and two lead with a usage leaderboard [15][16].
The author's own read is that the merch is not the driver, and that the messages work because they deviate from the process and corporate speak customers are used to receiving [11][12]. That is a claim about tone, and it is unverified. The post reports no response rates, no comparison against the scheduled calls it implicitly replaces, and no count of accounts contacted; the outcomes on offer are emoji reactions, one DM and a general assertion of engagement [8][10][14]. It is one operator describing his own results, on a customer base technical enough to be using PostHog's MCP and reachable in Slack [9][10].
Two things to watch. First, whether any of this survives delegation: the persona is explicitly personal, down to the lowercase typing and a raccoon graphic tee worn on calls, and a template written in that voice by someone else is a different artifact [4][13]. Second, the selection effect in the leaderboard plays. Congratulating your heaviest users is the cheapest way to get a reply, and it is also the surest way to hear from the people least likely to churn. If PostHog publishes the response rates, the number that matters is how much of this feedback came from accounts that were not already thriving.
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Customer success managers at PostHog spend a lot of time getting customers to talk to them.
- [2]
The author publishes the actual messages he has sent that worked, and notes that not every one includes giving away free merch.
- [3]
At PostHog, by the time a customer makes it to the author's book, the expectation is that they are in a steady state.
- [4]
The author writes that when the product is set up and working, a direct ping from some employee of a software vendor 'might as well have the urgency of a glacier', and jokes about being the guy who only types Slack messages in lowercase letters.
- [5]
The author writes that if he was going to be competing for attention, the outreach needed to be short, attention grabbing and valuable, with a '2x strength multiplier' if somebody laughs.
- [6]
In past post-sales roles the author sat in back-to-back-to-back meetings and had a backlog of Jira support tickets he had to beg people to look at.
Sources & coverage · 1 publisher
The reporting this story was synthesized from, earliest first. Every link goes to the original.
- posthog.comJake SciottoAug 12I bribe customers to talk to me
Additional citations
- PostHog blog post 'I bribe customers to talk to me'
- PostHog blog post



