Back to GrowthDex
Growth idea action plan

Two-sentence founder ask for user interviews

When you ask for an intro, meeting, or feedback session, keep the note to two or three direct sentences so the recipient can decide fast.

uncommon tactic
Best-fit channelEmail · Founder-led · Sales
Stage + contextuser interviews · outbound · 0-100 · founder sales
BudgetFreebudget tier
Suggested operator signalQualified conversations that advance to the next sales stage

Why this can grow a startup

Most early outreach fails because the founder is trying to explain too much before the other person has agreed to care. A short note lowers the reading cost, sounds more confident, and makes the ask easy to answer. It also leaves room for the real conversation to happen live instead of inside a dense paragraph.

Source-backed example

James Hawkins wrote that founders should ask for meetings in two or three sentences, not a wall of text, and be explicit about whether they want feedback or want to sell.

Source-reported evidence

Source: PostHog Newsletter · Browse PostHog Newsletter tactics

PostHog treated concise asks as one of the practical lessons from getting to its first 1,000 users

Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.

Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.

Source discovered: May 26, 2026

EmailFounder-ledSalesuser interviewsoutbound0-100founder sales
GrowthDex operator note

When to use it

Use this when Email, Founder-led, Sales is relevant to user interviews, outbound, 0-100 and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

How to do it

  1. Choose one target segment and define the exact next action this tactic should prompt.
  2. Adapt the tactic to Email and Founder-led, using evidence from PostHog Newsletter as context—not as a promised result.
  3. Record a baseline for: Qualified conversations that advance to the next sales stage. Set a guardrail that would make you pause the test.
  4. Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
  5. Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Next move

Compare a stack for your situation

Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.

Build my stack

Explore the context

Close the loop

Did you launch this experiment?

Report a launch to help us understand which growth ideas founders put into practice.

This report uses a pseudonymous browser ID. Prompts, names, email, or free-text are not included in outcome events.

Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian

SOURCE HUB

More tactics from PostHog Newsletter

Explore related GrowthDex examples and evidence connected to PostHog Newsletter.

Open PostHog Newsletter source hub