# FireJet demo video before marketplace polish

> Post a clear workflow demo to developer and design communities before waiting for the marketplace listing to do all distribution.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/firejet-demo-video-before-marketplace-polish/
- Source: [firejet.io](https://firejet.io/assets/files/ApplytoYCombinatorS23FireJet-dde3491c9c4216bd3d1a77c8d6102d44.pdf)
- GrowthDex source hub: [FireJet YC application: Figma plugin growth timeline](/sources/firejet-yc-application-figma-plugin-growth-timeline-firejet-io/)
- Last checked: 2026-06-09T10:56:35.000Z
- Rarity: uncommon
- Budget: low
- Channels: Figma, Reddit, Developer Marketing
- Stages: demo video, developer subreddits, figma to code, community launch, signup proof
- Key metric: FireJet reported 123 signups in the first 24 hours from a demo video and 221 total signups after an MVP subreddit post.

## Why this can grow

A plugin listing is rarely enough on its own. FireJet's timeline is useful because the first traction came from showing the workflow in motion and posting to relevant communities before the product had a mature listing machine. The demo gave developers and designers a fast way to judge the promise: turn a Figma design into readable code. That is better than a vague launch post because the user sees the before-and-after. A founder should use the marketplace as the home base, then use Reddit, Telegram, Facebook, or niche Slack groups to put the actual workflow where the audience already argues about the pain.

## 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. I would treat this as earning the right to be in the room, not dropping a campaign into a room. In community-led growth, the first job is to notice what people already care about, then bring a useful proof, tool, teardown, or question that makes the conversation better. 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 firejet demo video before marketplace polish can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Figma and Reddit channel.
3. Use the evidence from firejet.io 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

FireJet's YC application says the founders posted a demo video to developer, founder, and designer communities and gained 123 signups in the first 24 hours; a later MVP post to three developer subreddits brought the signup count to 221.

## Adjacent tactics in the same lane

- [FireJet output quality before feature sprawl](/growth-ideas/firejet-output-quality-before-feature-sprawl/) - same source, 1 shared channel

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The plugin should prove the work before the marketplace scales it](/blog/the-plugin-should-prove-the-work-before-the-marketplace-scales-it/) - platform-led growth, marketplaces, developer tools

## Advisory

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