Shared Projects as Acquisition Channel

The important point is that Replit turned every working app into both proof of value and a distribution channel. A shared project was not an ad, it was a live product someone could open in the browser and start using immediately, which meant acquisition happened after the product had already demonstrated usefulness. That tends to produce better conversion and better retention than paid traffic or top of funnel content.

• Replit’s growth engine looked more like Figma than traditional SaaS. The link to a project dropped a new user directly into the product, so the share itself acted as onboarding, demo, and invitation in one step.
  1 sacra
• This mattered because Replit was built around instant browser use, collaboration, and one click deploy. That product shape made projects naturally portable and easy to pass around, unlike desktop IDEs where a recipient would need to install tools before seeing anything.
  1 sacra 2 sacra 4 sacra
• The broader category is converging on the same idea. Lovable is building a GitHub style graph of forkable projects, which shows that shared apps and remixes are becoming a core acquisition loop for AI development platforms, not just a side feature.
  3 sacra

Going forward, the winners in AI coding will keep pushing product sharing closer to publishing. As more tools make apps instantly viewable, forkable, and deployable, distribution will come from users showing work rather than companies buying clicks. That favors platforms like Replit that already bundle creation, collaboration, and launch in one browser workflow.