`Arcstory` sold for $42k after 180k+ downloads and steady ASO iteration

Distribution discipline mattered more than launch speed. Small, repeated ASO and localization updates turned a solo app into an acquirable asset; useful playbook if you ship consumer apps.

[ KEY POINTS ]

Built and launched in 2 weeks, but the exit came after 1.5 years of iteration; speed got it live, persistence created the asset.
Reached 180k+ downloads and $15k revenue in the last 12 months, then sold for $42k; modest revenue can still support a meaningful exit.
Added 2 languages every month and refreshed store listings every 2 weeks; steady localization plus ASO compounded discoverability.
Sharing progress on X and LinkedIn likely helped buyer discovery; public build-in-public posts can function as lightweight deal flow.

Originalwww.reddit.com/r/SideProject/comments/1tctwtp/sold_my_first_product_after_working_on_it_for_15/Read original →

// related

#0001
#0001Indie business r/SaaSyesterday
`Blip AI` Crosses $200K Revenue, Mostly From Lifetime Deals
70radar
Blip AIVoice-to-text app — action mode across devices
Lifetime deals turned distribution into cash, but not recurring revenue. Useful launch pattern if compute cost and post-sale usage are priced deliberately.
- Most revenue came through AppSumo lifetime deals, not MRR. Treat LTD as cash plus distribution, not a subscription engine.
- Thousands of paid users validated demand for voice-to-text across devices. Card pulls beat compliments, but retention quality remains unproven.
- Every lifetime user keeps generating dictation compute cost. Speech apps need hard usage limits, fair-use clauses, or upgrade paths before scaling LTDs.
- The honest metric split matters: total revenue can look strong while recurring revenue stays weak. Optimize the next offer around repeat payment.
Source: www.reddit.com/r/SaaS/comments/1tgohgd/crossed_200k_reveRead original →
FIG-0011:1
70radar
FIG-0011:1
#0002
#0002Indie business r/SaaSyesterday
A zero-coding founder reached 71 users without marketing
40radar
A beginner used ChatGPT, tutorials, and debugging to turn creator workflow friction into a product people use. Small, but enough to validate a niche before overbuilding.
- Started from zero coding knowledge three months ago. The speed matters less than picking a painful, repeated workflow.
- The pain was tool-switching for scripts, hooks, voiceovers, footage, and hashtags. That is a clearer wedge than another generic creator dashboard.
- No marketing yet still reached 71 users. Weak as scale proof, useful as early demand signal.
- The first milestone is not revenue here; it is real usage. Next step should be retention, not feature sprawl.
Source: www.reddit.com/r/SaaS/comments/1tgiuy4/i_know_71_users_iRead original →
FIG-0021:1
40radar
FIG-0021:1
#0003
#0003Indie business GeekNewsyesterday
Do Not Answer the First Question
40radar
Odd support questions often hide the real failure. Ask for context first; it turns confusion into product discovery.
- A strange request in a performance debugging tool is often a symptom, not the actual need.
- Asking for background exposes the user’s workflow and the missing affordance in the product.
- This goes beyond the classic XY problem: the confusion itself becomes diagnostic data.
Source: news.hada.io/topic?id=29623Read original →
FIG-0031:1
40radar
FIG-0031:1