Loading page…
A digital closet app with 4,000 downloads and a paid-conversion problem to solve.
$500 lifetime revenue · 4,000 downloads · 0.5% paid conversion
“I’ve proven I can get users. Now I just need to give people a better reason to pay for it.”
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Cloey is a digital closet app launched on the App Store. It helps users log outfits and wardrobe spending and get personalized fashion advice. In its first three months, the app reached more than 4,000 downloads, but only 0.5% of users converted to paid. Monthly revenue was $130 and lifetime revenue was $500, while the founder had spent almost $2,000 on ads and influencers. The founder shortened the paywall and onboarding flow, shifting the presentation toward the outcome rather than a list of features. Onboarding completion rose from 60% to 72%, but paid conversion did not improve. Cloey’s core challenge is now monetization: users can do nearly everything in the free app, so the founder is building a virtual try-on feature that places outfits on a user’s real body. The clip captures a useful early-stage consumer app case: distribution can produce thousands of downloads while leaving the paid value proposition unresolved.
Cloey reached more than 4,000 downloads in its first three months while nearly $2,000 went to ads and influencers. That combination is useful, but reach and paid acquisition efficiency are different questions.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: The founder reports the download, conversion, revenue, promotion-spend, and onboarding figures in a TikTok clip. No third-party dashboard or financial records are cited, so the numbers are founder-reported and unaudited.
Cloey already has $500 in lifetime revenue and $130 in monthly revenue, so some users have crossed its paywall. Treat the first dollar as a product event that should be reproducible: record the user’s path from install, through closet setup, to the screen that triggered payment.
Cloey has a measurable activation improvement: onboarding completion rose from 60% to 72% after the flow was shortened. That gives the product a better starting point, though the change did not increase paid conversion.
Three months into launch, Cloey has 4,000 downloads, $130 in monthly revenue, and a 0.5% paid conversion rate. The founder has tried shortening the paywall and onboarding; completion improved, while payment conversion stayed flat.
Cloey combines wardrobe logging, outfit tracking, wardrobe-spend awareness, and personalized fashion advice. The next planned feature is virtual try-on, which would let a user visualize an outfit on their own body. These pieces can become a coherent product if they share one job: helping someone decide what to wear with items they already own. Our read: the app should make the closet useful before it asks users to catalog everything. Start with a quick add flow, let users save a few reliable outfits, and return value immediately through a practical suggestion. The product becomes harder to replace when it remembers fit preferences, occasions, and what the user actually wears, rather than simply storing photos. Virtual try-on is attractive, but it can become an expensive technical centerpiece; validate whether it changes a purchase decision before building a large imaging pipeline.
Cloey reports $130 in monthly revenue and $500 in lifetime revenue, with a 0.5% paid conversion rate. The founder describes the current free experience as generous enough that users can do almost everything without paying. The current pricing and paywall design are not part of the reported figures, so this breakdown does not assume a subscription price or customer count. Our read: charge for a repeated outcome rather than for a longer feature list. Possible paid jobs include unlimited saved outfits, occasion-specific planning, or virtual try-on credits, but each should be tested against real use before becoming the core offer. Keep one meaningful free loop so users can form a habit, then make the paid tier save time or improve confidence. Track paid conversion, renewal, cancellations, and contribution after store fees; downloads alone will not tell the founder whether monetization is working.
The clip identifies App Store distribution and almost $2,000 spent on advertising and influencers, but gives no technical stack or operating-cost breakdown. Our read: measure acquisition costs by channel before spending further, and treat virtual try-on as a variable-cost feature until its image-processing approach is proven. Image storage, inference, moderation, and customer support can all grow with usage, while subscription revenue arrives slowly at a 0.5% paid conversion rate. Keep an event ledger for installs, closet setup, first saved outfit, paywall view, purchase, and renewal. For any image model, test a small set of real garments for latency, representation, and cost before opening it to every user. Keep image deletion and account export easy to find. The margin target should be defined per active paying user after Apple fees, model calls, and storage, not as a gross-revenue percentage guessed from downloads.
Copy Cloey’s willingness to revise onboarding after seeing where users leave: completion moved from 60% to 72% when the flow was shortened. That is a concrete product improvement, even though it did not lift paid conversion. Copy the discipline of checking the next metric instead of declaring the redesign a win. Change the sequencing by validating the premium job before building a complex feature. Interview users who repeatedly save outfits, then test whether they would pay for a specific result such as planning a week from their existing wardrobe. Segment the nearly $2,000 of promotion spend by source so creator content and paid ads can be compared on activated users and paid starts. Our read: the model is worth copying when the builder has a sharp fashion niche and can create a distinctive paid outcome; a generic closet database is easy to ignore and expensive to promote.
The main risk is weak willingness to pay. Cloey has 4,000 downloads and $130 in monthly revenue, while only 0.5% of users convert to paid; almost $2,000 in promotion spend makes acquisition economics especially important. If users enjoy outfit logging but see no reason to subscribe, more installs can deepen losses rather than fix the business. Virtual try-on adds another risk: unreliable body rendering, privacy concerns around personal photos, and image-processing costs could damage trust and margins. App Store dependence also leaves discovery and billing inside a platform the founder does not control. Our read: protect the product’s credibility by making clear that virtual try-on is a visualization aid, not a guarantee of fit, and give users clear deletion controls for body and wardrobe images. The next funding decision should depend on paid retention and channel-level acquisition cost, not download volume alone.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click