Context
Farza Majeed is the founder of Clicky and previously built Buildspace, where video was a core part of how he attracted attention and users. In this episode with YC's Aaron Epstein, he argues that founders should stop treating launches as rare, expensive campaigns and start treating them as frequent demos shipped across algorithmic channels. That matters to PMs because the same discipline improves product marketing, prioritization, user discovery, and distribution. His core claim is that how a team explains a feature should shape how the team builds it, not just how the team markets it later.
The Big Idea
The best launch video is usually not a polished commercial. It is a clear, frequent demo that tells a small story, reaches the right audience, and creates a repeatable acquisition channel.
Farza's point is that launch content should be part of the product process, not a one-off event after the product is done. For PMs, that means a feature is not fully thought through until the team can explain why it matters, show it simply, and measure whether the explanation actually converts.
Key Insights
Launches became constant demos
Farza's biggest reframing is that founders are no longer making occasional "big launches." They are launching constantly on algorithmic platforms where users already spend time. He explicitly contrasts the older playbook, such as Product Hunt, Hacker News, Reddit, or press coverage, with today's environment where X, YouTube, Instagram, TikTok, and LinkedIn can all be ongoing launch surfaces.
For PMs, the lesson is that launch is no longer a date on the roadmap. Launch is a continuous feedback and distribution loop. A team that waits for a perfect reveal gives up many chances to learn what messaging lands, what use cases resonate, and which users actually convert.
Build backward from distribution
Farza says his team does not build a feature and only later wonder how to present it. The team works backward from the demo and the hook.
- He asks questions like: what are we launching this week, what is the copy in the Instagram caption, and what is the hook if this feature becomes a video.
- His argument is that communication quality is not separate from product quality. If a team cannot explain a feature in a simple, compelling way, that is often a sign the feature itself is still fuzzy.
- He says the team often knows a feature has potential before building it because it already "sounds good on paper."
This is highly relevant to PMs. A clear external story can act as a product design test. It forces the team to name the user, the problem, and the payoff before engineering effort is sunk.
Stories beat polished production
Farza rejects the idea that a successful launch video needs to look like a commercial. His view is that users respond to clarity and story, not production spend.
A few concrete details show how he thinks:
- He says a casual founder video can outperform a $20,000 produced video on engagement and traffic.
- He scripts videos that feel off the cuff. For one Clicky video, he wrote every line three days earlier and replayed it in his head repeatedly before recording.
- He believes the first 10 seconds of a one-minute video should do three jobs: say what is happening, say why it matters, and get into the demo.
- He is deliberate about the first frame. In one example, he opens on Xcode so curious developers recognize the context instantly. He also zooms into the cursor so a tiny visual detail becomes noticeable while people scroll.
The PM takeaway is that launch communication is product storytelling under severe time pressure. Good launch assets do not need polish first. They need a fast answer to: what is the interesting change, for whom, and why right now?
Measure downloads, not views
Farza repeatedly warns against confusing reach with traction. The important number is not how many people watched. It is what the right viewers did after watching.
The clearest example is the original Clicky launch:
- The video got nearly 3 million views.
- About 7,000 people downloaded the app.
- Roughly 100 of those 7,000 kept using it every day for five straight days.
- Farza says those 100 retained users, not the viral view count, are why he kept building the company.
He then reached out to those retained users and found they were using the product in ways he had not expected. That is a strong PM lesson: launch content is not just top-of-funnel distribution. It is also a fast way to find early power users and let actual behavior shape the roadmap.
Every channel converts differently
Farza is very explicit that channel strategy cannot be driven by intuition alone. He posts broadly, then tracks where real conversion comes from.
The examples are unusually concrete:
- A Clicky video on X got 2.9 million views, but he says the signup conversion was "horrendously low."
- A YouTube version of the same kind of content got about 20,000 views, but he says the download conversion was around 20%.
- He says about 70% of Clicky's traffic comes from Instagram.
- To reach design agency founders, his team made TikToks that directly opened with "Are you the founder of a design agency?" Those videos averaged about 4,000 views and produced around 50 design agency leads.
The product lesson is simple. A smaller, targeted audience can be far more valuable than a huge one. PMs should treat channels like experiments with different user intent, shelf life, and conversion patterns.
Repetition builds real judgment
Farza does not present himself as someone who got launch content right immediately. He says he got better by posting a large volume of mediocre work and learning from it.
His old Zip School videos are his evidence:
- One early Zip School launch video got 23 likes, one comment, and one bookmark.
- He still calls that a launch because the company shipped something new and told the world.
- He argues that those low-stakes posts taught him how to talk about products without sounding unnatural or overly salesy.
This matters for PMs because product storytelling is also a skill built through reps. Teams often expect the first messaging pass to be great. Farza's actual method is to publish, observe, improve, and keep going until the team's instincts sharpen.
Mental Models & Frameworks
Demo-driven development
Farza describes a workflow that is close to demo-driven development.
- Start with the moment that makes someone say, "check this out."
- Use that moment as the proof that a feature is ready to show.
- Let the planned demo influence what gets built and how it gets packaged.
He says that raw internal excitement is a signal. If a teammate naturally says "check this out" while building, that moment is often the seed of good external content. PMs can use this model to pressure-test whether a feature has a concrete, visible payoff or is still too abstract.
The mini-story formula
Farza says his formula is always the same: this is who I am, this is what's going on, this is what I'm working on, let me show you.
This works because even a short demo needs a story shape:
- a character,
- a situation,
- a reason to care,
- and visible proof.
He also says "everyone wants a story," which is why even a product demo should feel like a tiny narrative instead of a feature list. PMs can use this when writing demo scripts, release notes, or launch briefs.
The stop test
Farza uses a simple test before posting: would his own eyes stop on the post?
- He will literally compare draft text against other posts in a feed.
- He checks whether the first sentence creates enough curiosity to earn attention.
- He checks whether the first frame visually signals the intended audience.
This is a useful heuristic for PMs because it forces a brutally practical question. Does the packaging earn even one more second of attention from the right user?
Channel-specific learning loop
Farza treats each platform as a different system, not as a generic audience bucket.
- X gives broad reach but weak conversion.
- YouTube acts more like a library that keeps driving traffic over time.
- Instagram is a major conversion source for Clicky.
- TikTok can work as targeted prospecting if the opening lines speak directly to a niche.
He also mentions using destination links such as /IG so the team can trace which platform produced which actions. PMs can apply the same idea to feature announcements, waitlists, beta programs, and onboarding flows.
Decision Principles
Principle: Optimize for repeated acquisition
When: deciding whether launch content should be treated as a campaign or as an ongoing operating rhythm.
Why: Farza says the goal is not to get internet clout. The goal is to build a channel the team can use again and again to find users. A repeatable source of users is more valuable than a one-time spike.
Principle: Judge channels by conversion
When: choosing where to invest content effort across X, YouTube, Instagram, TikTok, LinkedIn, or other platforms.
Why: Farza's own examples show that millions of views can convert worse than tens of thousands of views. A PM should care about signup rate, download rate, retention, and qualified leads more than about raw reach.
Principle: Launch before confidence arrives
When: a team has something real to show but feels it is still too rough or too cringe to publish.
Why: Farza gives multiple examples where his own judgment was too harsh. The original Clicky demo was almost not posted, and another video he thought was terrible later did 3 million views on X. Publishing creates learning that internal debate cannot.
Trade-offs & Nuance
Polish versus speed
Farza is not saying polished launches never matter. He says his team may still do a more polished launch once a quarter for something especially important. The nuance is that polished launches should be the exception, not the default. If every feature waits for premium packaging, the team loses learning speed.
Virality versus fit
A viral video can help, but Farza does not optimize for virality itself. His design-agency example is the clearest case. Videos with about 4,000 targeted views produced around 50 leads, which can be much more useful than a general-interest video with millions of low-intent viewers.
Authenticity versus performance
Farza says founders are, in some sense, characters on a viewer's feed. He is not pretending that camera behavior is identical to private behavior. The nuance is that good launch content still needs to feel human and credible. Scripted does not mean fake. It means prepared.
Process versus founder lifestyle
Farza strongly prefers showing what the team is building over making "day in the life" founder content. His belief is that users and early adopters care more about seeing the actual work, the product changes, and the team's process than about startup lifestyle branding.
Common Mistakes
Mistake: Treating launch as one-shot
Teams often assume a launch must be rare, coordinated, and perfect. Farza argues that this mindset comes from an older media environment where one article or one event mattered disproportionately. On today's platforms, waiting for a single big moment prevents the team from learning continuously.
Mistake: Chasing vanity metrics
Farza explicitly says he does not care much about view counts by themselves. The better question is what happened next.
- Did people download the app?
- Did they keep using the app?
- Did the content attract the kind of users the team wants?
A PM who reports only impressions or views can miss the real signal entirely.
Mistake: Sounding like an ad
Farza says talking about products without sounding "shilly" is genuinely hard. One reason many launch videos fail is that they read like promotional copy instead of like a person showing something interesting. His workaround is to start from his own problem, his own curiosity, and his own "let me show you" energy.
Mistake: Ignoring audio quality
Farza calls out one production detail as unusually important: audio.
- He says he will bounce quickly from videos with poor audio.
- He is willing to tolerate lower video quality if the audio is crisp and the product is interesting.
- His practical advice is simple: use a dedicated mic rather than a laptop mic or AirPods mic.
That is useful for PMs because it is a cheap improvement with outsized impact.
Practical Application
Write the hook first
Before a team commits to a feature, write the external explanation first.
- Draft a one-sentence hook for the feature.
- Draft the first 10 seconds of the demo video or internal demo narration.
- Ask whether the draft clearly says what changed, who it helps, and why anyone should care.
If the team cannot do that, the feature may still be underdefined.
Add demos to planning
Make "what are we launching this week" a standing product question.
- In roadmap review, ask what visible proof each in-flight feature will produce.
- In sprint review, ask which feature deserves a public or internal demo.
- In release planning, treat distribution and explanation as part of the work, not as post-build cleanup.
This follows Farza's habit of working backward from the demo instead of bolting messaging on later.
Track channel-level conversion
Do not post the same announcement everywhere and only count views.
- Use source-specific landing pages or tagged links.
- Compare reach, signup rate, retained users, and qualified leads by channel.
- Review which channels behave like discovery, which behave like conversion, and which create lasting traffic.
Farza's examples show that YouTube, Instagram, X, and TikTok can play very different roles.
Interview retained responders
When a launch produces a pocket of retained users, talk to them quickly.
Farza says the people who used Clicky daily for five straight days were the group that convinced him the product mattered. PMs should treat those users as a priority interview cohort because they often reveal the strongest unmet need and the most surprising use cases.
Fix audio before visuals
If a team has limited time or budget, improve sound first.
- Buy one decent mic.
- Record in a quiet place.
- Test whether the spoken explanation is easy to hear on a phone speaker.
Better audio is often a more valuable upgrade than better lighting, better cameras, or more editing.
Questions to Consider
Which features lack a story
Which roadmap items would be hard to explain as a one-minute demo with a clear hook, a user problem, and visible proof that the feature works?
Where are views misleading
Which launch or announcement metrics in your team are mostly vanity metrics, and what would the equivalent of downloads, retained users, or qualified leads be instead?
What channel really converts
If your team compared X, YouTube, LinkedIn, Instagram, email, and community posts by actual signup or adoption rate, which channel would probably look much weaker or much stronger than its view counts suggest?
What deserves weekly demos
What did your team ship recently that would make a teammate say "check this out," and why was that moment not turned into a customer-facing or stakeholder-facing demo?
Bottom Line
Farza's playbook is less about filmmaking than about product discipline. Launch constantly, package each feature as a small story, and measure success by who converts and stays, not by how polished the video looked or how many people watched it once.
Tools & Products
| Tool / Product | What it does | Why it was mentioned |
|---|---|---|
| Screen Studio | Screen recording software | Farza uses it to record product demos on a computer, including cursor presentation and local audio. |
| Sony FX3 and FX30 | Camera hardware | Farza uses Sony cameras when he wants a more cinematic, thought-through video. |
| DJI Mic | Wireless microphone | Farza highlights dedicated audio gear as the most important production upgrade for launch videos. |
| DaVinci Resolve | Video editing software | Farza uses DaVinci on a laptop for editing. |
| Edits by Instagram | Mobile editing app | Farza says he sometimes edits directly on a phone using Instagram's editing tools. |
| Freewrite | Writing app | Farza uses his own free writing tool to script and think through launch videos before recording. |
People to Follow
Farza Majeed
Farza Majeed is the founder of Clicky and previously built Buildspace, one of the largest online schools for people working on their own ideas. He is worth following for practical lessons on product storytelling, founder-led distribution, and how to turn demos into repeatable acquisition channels.
Experiments to Try
Experiment: 30-day demo streak
- Hypothesis: daily low-production demos will improve product messaging and reveal which hooks actually earn attention.
- Change: record and post one short product or workflow video every day for 30 days.
- Test: keep production minimal so the only variables are the hook, the story, and the product moment being shown.
- Measure: track views, click-throughs, signups, and whether the quality of hooks improves over the month.
Experiment: Channel conversion test
- Hypothesis: the channel with the biggest reach is not the channel with the best conversion.
- Change: publish the same core demo on at least three channels, with channel-specific formatting when needed.
- Test: use tagged links or source-specific landing pages such as a dedicated Instagram destination.
- Measure: compare signup rate, download rate, retained-user rate, and qualified leads by channel.
Notable Quotes
"Everyone wants a story. And so how can a demo just be a mini story?" (Farza Majeed)
"How we communicate to other people is just as important as what we're building." (Farza Majeed)
"I'm not trying to keep your attention. That's actually the wrong way to look at it. I'm always like, all right, where is this going?" (Farza Majeed)
"In order to not be cringe, you must first be cringe." (Farza Majeed)
