# Issue or PR link instead of status handwave

> When a technical buyer asks whether a fix or feature is real, link the live issue or pull request instead of replying with a vague progress promise.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/issue-or-pr-link-instead-of-status-handwave/
- Source: [newsletter.posthog.com](https://newsletter.posthog.com/p/the-hidden-benefits-of-being-an-open)
- GrowthDex source hub: [PostHog: The hidden benefits of being an open-source startup](/sources/posthog-the-hidden-benefits-of-being-an-open-source-startup-newsletter-p/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: free
- Channels: Support, Brand, Product
- Stages: brand trust, technical buyers, support proof, open product work


## Why this can grow

Trust often leaks in the gap between the company's words and the buyer's ability to verify them. A live issue or pull request closes that gap with evidence. It shows the work exists, gives the buyer a place to inspect details, and invites feedback while the solution is still moving. That is more convincing than a support reply that asks the user to believe the team is on it.

## 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. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where issue or pr link instead of status handwave can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Brand 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: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

PostHog wrote that open source lets the team answer 'we're working on it' with a link to a live issue or pull request, so users can see the work and give direct feedback before the solution ships.

## Adjacent tactics in the same lane

- [Open roadmap comments for beta-tester recruiting](/growth-ideas/open-roadmap-comments-for-beta-tester-recruiting/) - same source, 1 shared channel
- [Public decision log for technical trust](/growth-ideas/public-decision-log-for-technical-trust/) - same source, 1 shared channel
- [Self-serve code audit for skeptical buyers](/growth-ideas/self-serve-code-audit-for-skeptical-buyers/) - same source, 1 shared channel
- [Clickable group titles for expert ladders](/growth-ideas/clickable-group-titles-for-expert-ladders/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The trust surface should show the work](/blog/the-trust-surface-should-show-the-work/) - brand trust, community-led growth, SEO

## Advisory

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