Founder journey posts for technical front pages
Write honest build-and-pivot stories for technical audiences that care about how the company actually learned, then let those posts earn repeated front-page attention.
Why this can grow a startup
Technical communities tend to ignore polished marketing but still reward plain stories with concrete product lessons. A founder journey post works when it reads like field notes rather than brand content. That makes it shareable on places like Hacker News, brings in the right kind of curiosity, and creates a durable content loop around the product's actual progress.
Source-backed example
PostHog wrote candid founder posts about pivots and early company decisions because developers did not want to be sold to. James Hawkins said the approach earned a couple more front-page Hacker News hits and helped validate content as a repeatable channel.
Source-reported evidence
Source: PostHog Newsletter · Browse PostHog Newsletter tactics
PostHog said the posts produced a couple more front-page Hacker News hits on the way 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 24, 2026
When to use it
Use this when Hacker News, Blog, Founder Brand is relevant to awareness, founder-led growth, technical audiences 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
- Choose one target segment and define the exact next action this tactic should prompt.
- Follow Hacker News community guidelines: do not solicit votes, comments, or submissions; share a useful working demo and an original explanation.
- Record a baseline for: Target users from this channel who complete the intended first action. Set a guardrail that would make you pause the test.
- 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.
- 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.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from PostHog Newsletter
Explore related GrowthDex examples and evidence connected to PostHog Newsletter.
Open PostHog Newsletter source hub