GTM Sauce

A plant identifier app · B2C · guest's second app

Ship many one-feature apps from one codebase instead of perfecting one

~90% caught the new-app boost for $500-1K/month; reached 3-4x salary

Workedportfolioaso

What they did

Inspired by an Adam Lyttle video ('build one app, one feature, ship, let it go and go to another one'). Built AI identifier apps (plant identifier etc.) by reusing one codebase and changing ~5% of the code per app; shipped one after another on iOS and Android, peaking at 46 apps per store. No big features, no emotional attachment: revisit old apps only for bug fixes and small updates. Relied on the App Store new-app boost (usually 3-5 days of extra visibility). Built during 6:05-8am and 8pm-midnight around a full-time job for ~6 months. Stopped building new apps in spring 2026 after the boost weakened (July 2025), half the apps made zero, and Apple started terminating accounts with many similar apps ('design spam' rejections).

What happened

About 90% of apps hit the App Store boost and made $500-1K/month, though most faded after a few weeks; portfolio reached 3-4x his salary by Oct-Nov 2025 and he quit his job. After July 2025 the boost weakened and 50% of apps made zero; he now considers the strategy dead.
Stage
Early (early revenue)
4:54
“Stop building, you know, multi- uh one app, start building multiple apps. Build one app, one feature, ship, and, you know, let it go and go to another one.”
Max
“it's easy to build one app and just change like 5% of code or whatever, and ship a second one, third one, fourth one, and so on”
Max
22:06
“Which, you know, kind of made me think that this is 100% no longer a go-to strategy.”
Max

Related topics

Get tactics like this every Monday

New tactics from the week's founder interviews, each linked to where it was said.

More from this episode