Section 1 · The Problem
Yasmin and Felipe found Loocro through a TikTok video because they were looking for an expert to help them launch their app successfully in the market. They met Loocro not through an ad. It was a simple video where Paulo was talking about growth strategies for apps. By Sunday afternoon they had reached out. Within days, they had signed.
The brief was simple to state and difficult to execute, though: find out if the market would respond. No historical data to lean on. No comparable app to benchmark against. The competitors available didn't have a product as strong as theirs, but they gave us a slight idea of where to move first. But it still was a cold launch into a category the audience didn't yet know they wanted.
"Before we worked with Loocro, we didn't exist. The app was launched and we had to start from zero, understanding the audience, understanding how it would work in the market."
A funded pre-revenue app burning runway on paid media that can't yet measure itself is the riskiest configuration in growth marketing. The challenge wasn't only to acquire users. It was to acquire them while preserving enough runway to find out if anyone would pay.
Section 2 · The Diagnosis
Three things shaped the approach.
01Cold launches need validation, not scale.
With zero install history, zero audience data, and zero comparable benchmarks, optimizing for scale in month one means optimizing on noise. The first job wasn't to maximize installs. It was to learn fast and cheaply which audiences responded, what creative formats converted, and whether the underlying market demand was real.
02Install and subscription are two different jobs that can't run together.
Trying to acquire installs and convert subscribers simultaneously, on a cold app, splits budget and creative attention between two campaigns that need very different audiences, very different messages, and very different feedback loops. Phase 1 had to validate the install economy. Phase 2 could then layer monetization on top of the audience Phase 1 built.
03Android and iOS are not the same channel.
CPI on iOS is structurally 3 to 5x higher than Android due to platform dynamics (Apple's privacy rules, narrower targeting, more competitive auction). Running them under the same campaign, with the same creative and the same bid logic, would either overpay for Android or underdeliver on iOS. They needed parallel structures.
The diagnosis: phase the launch, separate the platforms, optimize for validation before optimizing for scale.
Section 3 · What Changed
We built two phases. First: validate. Then: monetize.
Phase 1 (Month 1): Build the install base.
App install campaigns on Meta for Android and iOS simultaneously, but as fully separate structures. Distinct campaigns, distinct audiences, distinct creative per platform. Each platform got the bid logic, ad format, and message that matched how users on that platform actually behave.
The goal was to find the audience fast and cheaply, then learn before scaling. What we found:
| Android CPI | $0.42 |
| iOS CPI | $1.85 |
| Blended CPI | $0.84 |
For a brand new app entering an untested category, those numbers are exceptional. The market was there. It just needed to be found.
Phase 2 (Week 3 onward): Convert to subscribers.
Subscription campaigns launched alongside the install campaigns, targeting the existing user base for trial-to-paid conversion. The app runs a 3-day free trial at approximately $6/month.
The $6 price is strategic, set internally by Hair Try-On. An aggressive entry point reduces adoption friction at launch, when the priority is proving demand and seeding the subscriber base. The plan is to scale price progressively toward $30/month once the MRR base reaches break-even and the cohort retention data confirms the LTV holds. Cheap in to validate. Optimize price up once the floor is real.
The reporting layer separated install economics from subscription economics from day one. Cost per install told one story. Cost per trial start and trial-to-paid conversion told another. Both had to work for the unit economics to compound.
Section 4 · The Metrics
The numbers that matter at month three are the ones that tell us whether the hypothesis is real.
Installs held steady at the $0.84 blended CPI established in month one, with Android coming in at $0.42 and iOS at $1.85. By month three, the active user base had grown to 2,065. The first subscriber cohort was live, generating MRR under the strategic entry pricing while the campaigns kept feeding new installs into the funnel.
Three months in. New category, new product, cold start. The unit economics are pointing the right direction. The compounding hasn't started yet. The conditions for it to start have.
Section 5 · The Business Impact
Launching a new app into a new category is the hardest growth challenge there is. No audience to retarget. No data to optimize against. No benchmark to beat. Just a product, a hypothesis, and a budget that the team can't afford to spend twice.
The hypothesis was right. The market exists. The product converts. The unit economics, while early, are pointing in the right direction.
For Yasmin and Felipe, what changed at month three wasn't a revenue number. It was the answer to the question they couldn't answer at month one: does anyone want this? The data now says yes. Everything from here is execution on a validated hypothesis instead of speculation on an unproven one.
A pre-revenue app that knows its market is fundamentally different from a pre-revenue app that hopes it has one. The difference is what a properly phased launch buys.