# Founder 30-second reply SLA for early users

> Treat early-user replies like a live operating console: answer almost immediately while the user still has the tab open and the problem in front of them.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/founder-30-second-reply-sla-for-early-users/
- Source: [newsletter.posthog.com](https://newsletter.posthog.com/p/how-we-got-our-first-1000-users)
- GrowthDex source hub: [PostHog Product for Engineers](/sources/posthog-product-for-engineers-newsletter-posthog-com/)
- Last checked: May 24, 2026
- Rarity: rare
- Budget: free
- Channels: Support, Onboarding, Community
- Stages: 0-100, activation, retention
- Key metric: PostHog's target was a reply within 30 seconds for early user messages

## Why this can grow

Fast responses do two jobs at once. They rescue the user before momentum dies, and they teach the team what went wrong while the memory is still fresh. In the early stage, responsiveness is not a support nicety. It is a product input and a trust signal that stronger incumbents often cannot match.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. For this tactic, I would watch PostHog's target was a reply within 30 seconds for early user messages before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where founder 30-second reply sla for early users can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Onboarding channel.
3. Use the evidence from newsletter.posthog.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: PostHog's target was a reply within 30 seconds for early user messages.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

James Hawkins wrote that PostHog aimed to reply within 30 seconds when an early user messaged back because startups win on speed and should stay glued to those conversations.

## Adjacent tactics in the same lane

- [Repeat-usage gate before big launch](/growth-ideas/repeat-usage-gate-before-big-launch/) - same source, 1 shared channel, 2 shared stages
- [Manual chat onboarding before self-serve](/growth-ideas/manual-chat-onboarding-before-self-serve/) - same source, 1 shared channel, 1 shared stage
- [Concierge onboarding with direct messages before self-serve](/growth-ideas/concierge-onboarding-with-direct-messages-before-self-serve/) - same source, 1 shared channel, 1 shared stage
- [One-click deployment bridge to self-serve](/growth-ideas/one-click-deployment-bridge-to-self-serve/) - same source, 1 shared channel, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [Credibility is usually built before the big launch](/blog/credibility-is-usually-built-before-the-big-launch/) - trust, SEO, early-stage growth

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.