Resend open-source wedge before core product pitch
Launch the open-source edge of the product before the full commercial pitch, so the market can try the taste of the thing before it has to buy the whole meal.
Why this can grow a startup
Developer products often try to sell the platform before they have earned the trust to do it. Resend took the opposite route. Before the main product was broadly known, React Email gave developers a concrete tool for a painful job: building templates that render properly across clients. That did two jobs at once. It solved a real problem on its own, and it built the audience that would later care about the paid product. The important part is not just 'do open source.' The important part is to pick the slice that makes the later product pitch easier to believe. When the wedge is useful by itself, it becomes proof, distribution, and education in one move.
Source-backed example
Resend says it launched React Email in December 2022 before the public Resend launch, then later reached more than 12,181 GitHub stars and 209,339 weekly npm downloads while growing toward 100,000 verified users.
Source-reported evidence
Source: Resend Blog: What's next after 100,000 users
Resend reported that React Email reached 12,181 GitHub stars and 209,339 weekly npm downloads by the time the company crossed 100,000 verified 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.
When to use it
Use this when Open Source, Product-led Growth, Developer Marketing is relevant to open source wedge, developer trust, npm distribution and you can run a bounded test with a medium 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.
- Adapt the tactic to Open Source and Product-led Growth, using evidence from Resend Blog: What's next after 100,000 users as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next 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
Build creator and community systems around real incentives, trust, and repeat participation.