Issue 58: In an era where 'building' takes 48 hours, the game is won entirely 'before launch'
The thing that impressed me most today was the design that 'makes users screenshot their ranking card'.
While following today's overseas growth case studies, what really made me groan in admiration was how the voice input app Wispr Flow built its waitlist. Usually, a waitlist is positioned as nothing more than a 'box to collect email addresses before public release.' However, they completely transformed it into a 'referral engine'.
The more you refer, the higher your rank goes. The remaining time and number of referrals update in real-time. Users screenshot their ranking cards and post them on X or Slack, saying, 'I'm almost there to get early access.' In other words, every single share became a recommendation to friends saying, 'This is worth the wait'.
The company itself states this clearly: 'We didn't gamify it for the sake of looks. Referrals, shares, and uploaded screenshots are all acts of someone telling their friends.' I feel that this one sentence encapsulates the essence of growth in 2026.
Today, starting with Wispr Flow, I found a series of cases where they 'had an audience before building.' The common thread is the fact that building the product itself is no longer the bottleneck; the game has shifted entirely to how many people you can gather before launch and how much of a structure you have built for them to spread the word voluntarily. Today, I will dissect the raw details of this from both the technical and the gritty marketing sides.
Today's Highlight 1: Wispr Flow — Gamifying the waitlist to reach 375,000 people
First, let's look at the numbers. Wispr Flow's user count and ARR (Annual Recurring Revenue) have recently been growing at a pace of 40% month-over-month (MoM). These are public figures. And as of February 23, 2026, when the Android version launched, it was reported that 375,000 people had already shared the product with their own networks in advance. The estimated ARR is around $10M, and it is said that they were valued at $2B in a Series B round in 2026 (please take these valuation and ARR figures as estimates, as they include third-party aggregations).
What I focused on, more than the amount itself, is the single point that 'they launched in a state where 375,000 people were already talking to their friends about it.' Usually, new products start from a 'state of anonymity where no one knows them.' However, they started from a completely different starting point: '375,000 people have already introduced it to their inner circles'.
Breaking down the underlying flow, the key was in the UI. They visualized the rank, number of referrals, and remaining time as a card that updates on the spot. When people see their own score or rank, they want to screenshot it and show it off. Moreover, that screenshot becomes an advertisement saying, 'This product is trending right now.' In other words, they designed the UI on the premise that it would be screenshotted. In addition, the experience of voice input itself has a nature that 'makes you want to demonstrate it in front of others,' so it was a perfect match for UGC (User Generated Content).
Let's think about adapting this to Japan. In domestic individual development, waitlists are still mostly stuck as 'boxes to collect emails.' I see a huge void in game design where your rank goes up based on the number of people you refer, or only the top X people get early access. Especially since the Japanese-speaking world has a very strong screenshot culture, just making the 'ranking card' look good enough to screenshot can become fuel for diffusion. Even just adding one flow where your rank goes up if you share on LINE or X changes the meaning of the waitlist entirely.
The difficulty of reproduction, in my sense, is 3 stars. The waitlist mechanism itself can be built with no-code or dedicated SaaS. The only difficult part is whether you have the core of a product that makes people think, 'I want it even if I have to wait.' That is all it comes down to.
Today's Highlight 2: Launch Fast — A non-engineer built an MCP in 48 hours and distributed it to 'customers they had already bought'
The second one is the case where I personally felt most strongly that 'the times have changed.' Hasaam Bhatti, who created Launch Fast, is a non-engineer founder who cannot write a single line of code himself. Even so, he used the AI coding environment Cursor to build the first version in just 48 hours. And in 30 days, he reached $10k MRR, and a few months later, $30k MRR (these are all public figures he shared on Indie Hackers). The delivery format is a Chrome extension, and it is reported that there are about 330 active users.
What he built was an MCP (Model Context Protocol) tool for Amazon sellers. It allows users to perform tasks like product research, catalog management, and ad optimization all at once through AI without having to go back and forth between multiple tools. For those who are not familiar with the term MCP, MCP is a common standard for AI agents to connect to external tools and data. By making it MCP-compatible, users can call the tool directly from within the AI assistant they usually use (for example, Claude).
Well, if it ended here, it would just be a story about 'how it became easier to build with AI.' The part that really makes me shiver is from here on. The reason he really grew was not the quality of the product. Two years ago, he bought a coaching program called Legacy X. Thousands of Amazon sellers were already enrolled there. In other words, long before he built the product, he had a 'list of people who wanted that product'.
He summarizes it like this: 'Distribution > product.' It is a reflection that we often spend too much time building and too little time delivering. This phrase resonates deeply precisely because anyone can build with AI now. Moreover, by releasing it via MCP, he secured a flow where it could be called from within the AI assistants that sellers use daily. As the hurdle for building technology has lowered, he was quick to adapt to a new axis of competition: 'which AI to reside in'.
As an adaptation for Japan, what I think is that the order of 'having a community or customer list first, then turning their repetitive tasks into MCP' is almost untouched domestically. Thinly automate the repetitive tasks that domestic EC sellers, for example, on Rakuten, Amazon, or BASE, do every day using Cursor and MCP, and distribute it to existing communities. I see a lot of room for reproduction in this model. The reproduction difficulty is 3 stars. The technical hurdle has dropped dramatically. The difficult part is whether you can secure an 'already existing audience' first; that is the only point.
Today's Highlight 3: SuperX — Reverse-engineering his own buzz and turning content into distribution
The third is Rob Hallam of SuperX. Over two and a half years, he built five products, all of which failed, and his earnings were zero. Even so, he kept posting on X, including his failures and small successes. One day, a post summarizing his failures reached 200,000 views. In the comments section, he was advised to 'try doing development agency work,' and when he announced it the next day, a $3,000 project came in from that same post, and since then, work has been coming in continuously from X.
Here, he had a decisive realization: 'Content is distribution.' Even though all the projects were coming through X, he couldn't target and reproduce it. He didn't know the reason why some posts went viral and others flopped. So, he started building his own internal tool to reverse-engineer and reproduce viral posts. He turned that into a product called SuperX.
Let's confirm the numbers. $1k MRR on launch day, $23k MRR in 6 months, approximately 650 paid users ($39/month), and 20-25% monthly growth (based on the founder's own statements and public data as of February 2026).
The underlying flow was also interesting. He teamed up with Tibo, who already had an audience in the X growth space and had previously acquired a Chrome extension called SuperX from another maker. On top of that, he rebuilt the Chrome extension, web app, tweet embedding search, and analytics infrastructure from scratch. He also moved payments from Lemon Squeezy to Stripe to streamline operations. In short, it was a 'dogfooding' style of development where he solidified the pain points of his own workflow directly into a product. The structure was that by building what he truly wanted and continuing to share it, an audience was already waiting at the time of launch.
As for an adaptation for Japan, I feel that the model of 'turning one's own dissemination know-how into a tool that others can reproduce' is still weak in the Japanese X and note circles. Tools that analyze buzz patterns for Japanese posts, or tools that turn operational templates for note or X into products, are currently blank spaces. The idea of solidifying individual 'tacit knowledge' into SaaS is the key to adaptation. The difficulty of reproduction is 4 stars. While tool creation itself is possible, the premise of 'being a buzz-worthy creator first' is quite heavy.
Themes that emerged across strategy types
Let's re-bundle the three points so far from the perspective of strategy types. Today, clear trends were visible in all four areas.
First,the direct connection between short videos and products is key. Looking at industry data, UGC videos have about 28% higher engagement compared to polished brand videos, and the click-through rate for UGC ads is about four times higher. The 2026 TikTok algorithm prioritizes authentic content over polished ads, and what users prefer is 'how-to videos' rather than reviews. The optimal length is considered to be 5-7 seconds for quick tips and 27-35 seconds for feature explanations. What actually works here is your own product's onboarding screen. You can take the onboarding explanations, turn them into scripts, and cut them into short videos for each feature. This is the easiest to mass-produce and connects directly to the product.
Next,onboarding and acquiring UGC is crucial. The screenshot flow of Wispr Flow was a symbol of this. In addition, regarding UGC in general, it is reported that about 79% of consumers prioritize UGC in their purchasing decisions. The point is to insert a sharing flow at 'the very moment' the user experiences their first success. While the excitement is still fresh, they can create a shareable image with one tap. Whether or not this design exists changes the volume of UGC generated significantly. In the world of newsletters, Chenell Basilio, who runs Growth in Reverse, provides a 'Community Spotlight' section where names are listed in the newsletter for 10 referrals, and that section generates 50-80 clicks every week. The essence is the same in that you provide a 'visible' reward for referrals.
Third,growth through AI, MCP, and API disclosure is important. The MCP tool for Launch Fast is exactly that, and Wispr Flow also won high usage frequency like an OS by keeping voice input resident in every app. Now that the cost of building has dropped, differentiation has shifted to the distribution side: 'which AI agent is it called from' and 'how much does it reside in daily life'.
Fourth,influencers, pre-launch, and waitlists are essential. The referral game of Wispr Flow, the 'pre-purchased members' of Launch Fast, and the Product Hunt launch strategy all fit here. In 2026, Product Hunt has come to value engagement (comments, time spent, bringing in new users) more than raw upvote counts, and it is said that top-tier teams start preparing 4-6 weeks in advance. The rule of thumb that Tuesday, Wednesday, and Thursday are the best days for a launch remains unchanged. What they have in common is the structure where 'how much you prepared the audience and supporters in advance' determines everything, rather than the instantaneous power on the day.
Creator to watch: Chenell Basilio, the 'reverse-engineering artisan'
Today, between the case studies, I paid renewed attention to Chenell Basilio of Growth in Reverse, whom I mentioned earlier. She grew her newsletter to 21,000 subscribers in 10 months and is now growing it to the 40,000 scale. What she does is spend 20-25 hours thoroughly breaking down the growth story of one newsletter every week. How they gathered the first 1,000 people, what kind of referral mechanism they built, which lead magnets were truly effective, where they hit a wall, and why. The feature is that she shows not just 'what worked,' but also 'the order of decision-making that led to that conclusion.'
What I want to learn from this is that content itself can be a powerful distribution device. Rob from SuperX and she were doing the same thing in terms of structure. They build the information or tools they truly want with overwhelming depth. Then, that itself brings in the audience. I felt my spine straighten again, realizing that what we are trying to do with this 'Time Machine Management' is essentially a continuation of this.
This concludes the educational part on 'why it grew, market proof, and what the blank spaces in Japan are.' From here on, we enter the concrete part for actually moving your hands starting tomorrow, rather than just reading material. I will write out the procedures and tools I would use if I were acting on this topic now: how to create scripts for short videos, the design for inserting a sharing flow immediately after a success experience, the steps to thinly MCP-ize repetitive tasks, and the funnel to create initial launch momentum with 'borrowed audiences'.
Initial actions starting tomorrow (to act as a seller)
From here on, I will summarize the concrete parts for actually moving your hands starting tomorrow, rather than as reading material. The educational part ends here, and what follows is a layer of more practical 'procedures, tools, and funnels'.
If starting from a short video flow. First, choose just one feature of your product. Then, make just one 27-35 second 'how-to' short. Don't overthink the script; just reading the explanation text from the onboarding screen is enough. Place a hook like 'You'll regret it if you don't know this' in the first 2 seconds, and close with 'You can try it from my profile.' Post this simultaneously to TikTok, Reels, and X Shorts. You don't need to show your face; just screen recording with captions is fine. It is also effective to use a public challenge like 'continue one per day until reaching XX MRR' as the hook itself.
If strengthening onboarding and UGC. Identify the moment when a user achieves their first result, such as 'first data output' or 'first reservation received.' Insert a button that says 'Generate share image with 1 tap' on the screen immediately after that. The generated image should be a 'result card' that looks good in screenshots. A design where numbers and achievements are clear at a glance and people want to post it is ideal. The important thing here is not to 'ask' for a share, but to silently provide the tool to share at the moment they want to share. As for tools, image generation can be sufficiently built with dynamic OGP generation, Canva's API, or a light custom script.
If utilizing AI and MCP. Identify just one repetitive task that you or your customers do every day. The ideal is 'something annoying but done every day, a simple repetition.' Implement it minimally as a thin MCP server or browser extension using Cursor. Don't aim for perfection; just get one feature working first. Then, prepare a flow that can be called from the AI assistant the user normally uses. As Launch Fast showed, the hurdle for 'building' is already low enough, so please devote most of your time to 'who to deliver it to'.
If preparing influencers and pre-launch. For the next launch, set up a waitlist today that 'distributes early access based on referral ranking.' It can be no-code or a dedicated waitlist SaaS. The key is that the ranking and number of referrals are visible in real-time, and there is a card that makes people want to take a screenshot. Also, think of just one person you know who 'has an audience' and reach out to them today. This is a solicitation for a co-hosted event or mutual promotion, what is called a 'Borrowed Audience.' Being able to temporarily borrow the other person's entire list in one co-hosting is the shortest way to create initial momentum in individual development.
Summary: Now that you can build, go all-in on 'designing for delivery'
If I had to summarize today's biggest lesson in one sentence, it is that in an era where 'building' can be finished in 48 hours, the game is decided entirely before the launch. Wispr Flow had introduced itself to 375,000 people before going public, Launch Fast had thousands of customers before the product even existed, and SuperX was cultivating an audience before they even started building. The one thing all three had in common was not the quality of their product, but the fact that they had 'pre-installed the delivery structure'.
What we should try first is a waitlist that lets people screenshot their ranking, a sharing flow inserted immediately after a successful experience, and thinning out repetitive tasks into MCP. None of these require large-scale development. Tomorrow, I plan to start quietly by choosing one feature and filming one short video. Next time, I plan to dig deeper into how to specifically assemble this 'borrowed audience' by relating it to domestic examples.
Taking profitable businesses from overseas, arranging them for the Japanese market, and growing them without missing the mark. I run a community that researches the process from candidate selection → numerical verification → Japanese localization → manual verification → MVP → pricing → expansion. Register on LINE here: https://lin.ee/8Yyw7wk
*Numerical values distinguish between public data and estimates. Since specific figures and valuations include third-party aggregations or self-declarations, please verify each primary source yourself when making investment or business decisions.
#GrowthHack #IndividualDevelopment #SNSMarketing #TimeMachineManagement #buildinpublic #MCP #Waitlist #IndieHacker