Growth PlaybookWorking document

The Ugly Ads
Doctrine

A working playbook for creative testing, localization, organic strategy and portfolio focus, extracted from a decade of app growth at BetterMe, Ewa, Palta, Replika, Higgsfield and Solid Starts.

Never settle for mediocrity. Always be looking for those creatives that will move the needle to a point where you never expected.
Yuliya Lennox
Every idea here
Yuliya Lennox — ~10 years in app growth at BetterMe, Ewa, Palta, Replika, Higgsfield and Solid Starts
Asked the questions
David Barnard — host of Sub Club, the podcast by RevenueCat
The episode
“Make Ugly Ads to Grow Your App” — watch it on YouTube. Everything below is a summary of this one conversation.
Only organised it
Mert Demirdelen with Claude Code, Opus 4.8
Status
Working document. Sections 03–09 carry assigned actions.
  • 7Doctrines
  • 27Plays & actions
  • 90Day plan
  • 71Checklist items
Contents 0/0

Section 01

Who Is Speaking, And Why It Matters

Calibrating how much weight to give each claim in this document.

Yuliya Lennox came out of traditional brand marketing at Coca-Cola in Ukraine and was thrown into mobile as effectively the CMO of BetterMe, with no prior app experience. That trajectory matters: she has run both the brand-building playbook and the direct-response playbook, and she is unusually clear about why the second one wins for companies at this stage.

The through-line across her portfolio is instructive, because each company taught a different lesson:

CompanyCategory & contextThe lesson she extracted
BetterMe Fitness / health, scaled to a very large business Performance marketing should be volatile. Ugly, pattern-interrupt creative wins. She claims the “make ugly ads” idea originated here.
Ewa (Learn English) Bootstrapped, reached #2 behind Duolingo No silver-bullet CMO exists. The founder was in every marketing meeting writing creative concepts himself. Also: start with the local market you actually understand.
Palta (parent of Flo) Large multi-app portfolio Cross-company knowledge sharing compounds. Also: build for where the market will be in five years, not where it is.
Replika AI companion, massive organic Huge organic feels like a gift and becomes a trap. Commoditization by ChatGPT wrappers was unforeseeable and unhedged.
Higgsfield AI video generation, early to market Extreme execution intensity as a moat. Being early looks like being wrong right up until it doesn’t.
Solid Starts Baby-led weaning, very strong brand The one context where brand genuinely constrains creative. Mission-driven team density produces category-changing output.

One more note on credibility: she is candid about her own failures, including a Japan localization bet at Replika that did not work, and a brand misjudgment at Solid Starts that she got backwards. Advice from people who narrate their misses is generally worth more than advice from people who only narrate wins.

Section 02

The Ten Core Arguments

The entire thesis compressed. Every row is expanded into plays later in this document. Open one to see what it means operationally, and where I land on it.

01 Stable performance is a red flag, not a success Adopt fully

Operationally. If CPM, CTR and CPA are flat week over week, you have stopped testing meaningfully. You are looking for the day one creative triples purchases.

My read. Adopt fully. It reframes how you report. See Section 03 →

02 Ugly ads outperform beautiful ads Adopt + gate

Operationally. The job of the first frame is to break the scroll, not to look good. Polished, TV-style creative gets filtered out as advertising.

My read. Adopt with a brand-risk gate. See Section 04 →

03 Brand mostly does not exist at your scale Adopt, with exception

Operationally. “Nobody cares about your brand but you.” Brand marketing cannot be justified on short-term ROI. Earn it with performance first.

My read. Adopt, with the Solid Starts exception. Trust-sensitive categories are different. See Section 12 →

04 Validate demand with marketing before building Hard gate

Operationally. Run ads to a landing page, sell a PDF, refund it. Prove people will pay before engineering time is committed.

My read. Adopt as a hard gate. Cheap insurance. See Section 05 →

05 Founders and senior leaders must be in the creative trenches Adopt

Operationally. No hire will save you. The Ewa founder attended every marketing meeting and generated concepts himself.

My read. Adopt. Directly relevant to how any growth leader allocates their time.

06 Test creative in cheap markets, scale in expensive ones Highest ROI

Operationally. 500 ad tests per week on US CPMs bankrupts you. Run the same volume in low-CPM markets with comparable conversion behavior, then port winners.

My read. Adopt — the highest-ROI single tactic in this document. See Section 06 →

07 Localization is the most underrated growth lever Adopt

Operationally. AI makes translation nearly free. Most teams default to the US and ignore markets that convert well. Turkey named explicitly as a strong market.

My read. Adopt. If you operate outside the default US-first markets, this is a structural advantage you already hold. See Section 06 →

08 Large organic traffic is a trap in disguise Adopt

Operationally. Organic saturates its niche, then flatlines. Paid layered on later often cannibalizes rather than adds. You cannot steer organic.

My read. Adopt. It changes how you evaluate your strongest apps. See Section 07 →

09 Running many products in parallel is her biggest recent failure Contested

Operationally. Attention does not divide cleanly. One product should be run like a war room with a daily standing question: what are we doing today?

My read. Adopt with portfolio nuance — the most contested point in the whole conversation. See Section 08 → and Section 12 →

10 Black hat growth is ending and should end Policy

Operationally. Deceptive quiz funnels and hidden pricing drew regulatory attention and damaged the whole category. Drift into it happens gradually.

My read. Adopt as policy. Codify a monetization standard. See Section 09 →

Your first tries, your first creatives, your first results shouldn’t be good in any way. Has there ever been a moment when you thought, wow, this is so much better than everything I’ve done before — where your CPAs went down, doubled down, when your amount of purchases tripled in one day? This is the moment when you know that this is actually happening for you.
On why flat performance means you have stopped trying

Section 03 · Doctrine I

Volatility Is The Signal

Stable performance means you have stopped searching. Re-instrument reporting around step changes, not averages.

The claim: if you are spending $100–$500/day and seeing the same CPM and the same cost per user — $30 CAC against a $50 LTV, a workable margin — you will conclude you have found the model and start scaling. She argues you have actually found a local maximum and stopped looking for the real one.

The reasoning is that outsized returns in paid social come from discontinuities, not from grinding out a few percentage points. One creative, one concept, one angle produces a day where purchases triple. If that has never happened to you, you have not yet found the thing that works — you have found something that merely does not lose money.

This has a direct implication for how you report. Weekly average CPA hides exactly the signal you are hunting for. A week containing one spectacular day and four mediocre days averages out to look identical to a week of five flat days, but those two weeks mean completely opposite things.

Play 3.1

Add a volatility panel to every UA report

Alongside your existing averages, every weekly UA report should show:

  • Best single creative-day vs. account median, expressed as a multiple. If nothing exceeded 1.5× median in 30 days, the report is flagged.
  • Spread of CPA across active creatives (p10 vs. p90). Narrowing spread over time means the creative pool has converged and needs disruption.
  • Days since last step change, defined as a creative that beat the incumbent best by 25%+ and held for 3+ days.
  • Share of spend on creatives launched in the last 21 days. Target floor: 20%.

Play 3.2

Ring-fence a discovery budget that is not held to CAC targets

Carve out 10–15% of monthly UA spend per app as an explicit discovery budget. It is judged on one question only: did it produce a step change? It is not judged on blended CAC, and it must not be raided when the month is running behind on targets. Without a formal ring-fence this budget always gets absorbed into the safe campaigns, which is precisely the failure mode she is describing.

Play 3.3

Change the language in growth reviews

The question in weekly review shifts from “are we hitting CAC?” to “what did we learn, and what was the biggest outlier?” Hitting CAC with zero outliers is reported as a yellow status, not green. This is a small change that alters what the team optimizes for.

Instrumentation checklist

0/6

Section 04 · Doctrine II

The Ugly Ads Playbook

The first frame’s only job is to break the scroll. Polish is a filter that gets you ignored.

You don’t remember the skinny girls that were working out, obviously, but you do remember something that shocks you. It’s completely about taking the person out of the grid of scrolling your feed. Sometimes your feed is so pretty that you need something ugly to take your attention from it.
On why pattern interrupt beats production value

The canonical example discussed is a BetterMe illustration of belly fat — visually crude, borderline unpleasant, and so effective that the host still vividly recalled it roughly a decade later. That is the entire argument in one artifact: memorability and attention capture are the metrics, and they are frequently inversely correlated with aesthetic quality.

Her warning even names the tool, and it is worth quoting directly: “Don’t listen to Claude when they tell you which creatives to create and then they give you a fifteen-second creative.” The instinct of any general-purpose AI tool is to produce something that looks professional, which is exactly the thing that gets scrolled past. (Noted with some irony, since this page was prepared with Claude. The point stands: use AI for volume, not for taste calibration.)

What “ugly” actually means in practice

Ugly is not a synonym for low effort. It is a deliberate set of choices:

DimensionPolished default (avoid)Pattern-interrupt version (test)
First frame Logo, clean product shot, brand colors An unresolved visual problem, a raw face mid-sentence, crude illustration, text that looks typed not designed
Production Colour graded, stabilized, scored Handheld, native camera, ambient audio, visible imperfection
Length 15s narrative arc Hook resolved or escalated within 1–2 seconds
Message Brand feeling, lifestyle aspiration The specific pain, named plainly, and the function that solves it
Format Feels like an ad Feels like a post, a screen recording, a text thread, a complaint

The brand objection, handled properly

Her position is deliberately provocative: unless you are Coca-Cola, your brand does not exist and nobody cares about it except you, your family, and some of your employees. Nike sells prettiness; a subscription app sells function. Brand marketing will never outperform performance marketing on short-term ROI, so the honest sequence is to earn revenue with performance first and buy brand later.

But she also volunteers the counter-example, and it is important. At Solid Starts she assumed brand did not matter and ran a fruit-baby creative concept. The feedback was users asking whether a company that made that ad could be trusted to advise them on feeding their infant. In trust-critical categories, ugly creative can attack the core value proposition itself.

Ugly is safe here

  • Utility and productivity apps
  • Entertainment, games, casual creative tools
  • Generic self-improvement and habit apps
  • Any category where the user’s risk of being wrong is low
  • Early-stage apps with no meaningful brand equity to protect

Apply the trust gate here

  • Anything involving children or infants
  • Health, medical, mental health, medication
  • Financial products and money management
  • Safety, legal, or regulated advice
  • Established brands with genuine equity at risk

Play 4.1

Institute a weekly ugly quota

Every app team ships a minimum number of deliberately unpolished concepts per week. These are not optional, and they are not the ones left over after the “real” creatives are done. Suggested floor: at least 30% of new concepts per week must fail a conventional brand review. If everything passes brand review, the quota was not met.

Play 4.2

Build a hook library, separate from creative production

Treat the first 1–2 seconds as its own asset class. Maintain a shared library of hooks with recorded performance, categorized by mechanism: shock, unresolved question, visible flaw, wrong-context object, mid-conversation entry, negative claim, “you’re doing X wrong”. New creative is assembled by pairing a proven hook with a new body, which multiplies throughput dramatically compared to producing complete creatives from scratch.

Play 4.3

Use AI video tooling for volume, human judgment for selection

She describes handing an app logo to an AI UGC tool with no prompt and no script and receiving a usable UGC-style asset that did not read as AI-generated. That matters because the binding constraint on ugly-ad volume has always been production cost, and that constraint has largely dissolved. Set up a pipeline that generates variants at volume, but keep a human deciding what ships — AI tools optimize toward polish, which is the exact failure mode you are trying to escape.

Play 4.4

Apply the trust gate, not a brand gate

Replace generic brand review with one specific question: “Could this creative cause a reasonable user to doubt our competence on the thing they are trusting us with?” If no, ship it regardless of how it looks. If yes, it needs sign-off. This is a much narrower filter than conventional brand review and it lets almost everything through while still catching the Solid Starts failure.

Creative operations checklist

0/7

Section 05 · Doctrine III

Validate With Marketing Before You Build

Sell the idea before the product exists. Refund if you must. Engineering time is the expensive resource.

You cannot vibe code the whole product and then hope for it to be needed. Just start with marketing. Sell a PDF, sell an idea, sell something, and then refund — because you don’t have a product. Just see if there are enough people even interested.
On sequencing marketing ahead of development

Her worked example is her husband’s aquarium app idea. It is a real passion, there is genuine enthusiast content on social platforms, and the adjacent spend per user is high. Her position is that a small amount of paid testing would have revealed the audience is too small and the acquisition cost too high for the monetization to work — before any development began.

The host pushed back reasonably: niche passion categories with expensive adjacent purchases are often exactly where UGC and affiliate models work. She partially conceded, and the resolution is the useful part. The idea might work as a $20k/month independent business and simultaneously fail as a portfolio app, because the LTV:CAC required to justify studio resourcing is much higher than the bar for a solo operator.

She also names a social failure mode worth flagging: friends and family validate ideas because they want to be supportive, not because the idea is good. She frames it as a cultural contrast, with American feedback culture being more encouraging and Eastern European feedback more bluntly skeptical. The practical lesson is that enthusiasm from people who like you is not data, and should never be logged as evidence.

The pre-build validation gate

No new app concept receives engineering resource until it has cleared this gate. The whole thing should cost a few hundred dollars and under two weeks.

StepActionPass criteriaOwner
1 Write the ad before the spec. If you cannot write a compelling hook, the value proposition is not clear enough to build. 3+ distinct angles, each articulating a specific pain Growth
2 Build a landing page with a real price and a real checkout Live page, honest pricing, working payment path Growth
3 Run paid traffic in a low-CPM test market $200–500 total spend, 2–5 days UA
4 Measure intent at the point of payment, not at the click Checkout initiation rate, not CTR or signups Growth
5 Refund every purchaser promptly and transparently, with a clear explanation 100% refunded within 48h, honest message Growth
6 Model implied CAC against required LTV at studio cost structure Clears your portfolio bar, not a solo-operator bar Product

Play 5.1

Add “ad-first” to the product brief template

Every new concept document opens with three written ad hooks and a one-sentence pain statement, before any feature list. This is a forcing function: concepts that cannot generate a hook usually cannot generate demand either, and it takes twenty minutes to discover that instead of a development cycle.

Play 5.2

Maintain a validated-but-parked concept queue

Concepts that pass the gate but lose prioritization go into a queue with their test data attached, rather than being forgotten. When capacity opens up, you pull from a list of pre-validated ideas instead of starting a fresh debate from opinion. This also makes the Section 08 focus discipline much easier to hold, because saying “not now” is less painful when the idea is genuinely preserved.

Validation checklist

0/6

Section 06 · Doctrine IV

Localization As The Cheapest Growth Lever

Two separate plays that are frequently confused: cheap markets for testing volume, and overlooked markets for revenue.

This section contains what is, in my assessment, the single highest-ROI tactic in the entire conversation — and one where teams outside the expensive English-speaking markets hold an advantage most of their competitors do not.

It is not only my assessment. Asked in the closing lightning round for the most impactful change of her past year, she answered localization — “the way to open markets that you have never took money from” — and said she would bet on it over everything else.

Play A — Test in cheap markets, scale in expensive ones

You need to test like 500 ads per week, and if you do that on US CPMs you will definitely go broke. But if you do that with countries that have similar conversion rates — you will see the same results for the same tests for $10 a day instead of $1,000 per day.
On decoupling creative testing from market economics

This is the mechanism that makes Doctrine I and Doctrine II financially survivable. High-volume creative testing is unaffordable on US CPMs, which is why most teams test twenty creatives a week instead of hundreds, which is why they rarely find step changes. Moving the testing layer to low-CPM markets — her passing example is Indonesia — breaks that constraint. Winners are then ported into expensive markets with the creative risk already retired.

The critical qualifier is similar conversion behavior. A test market is only valid if creative that wins there also wins in the target market. That correlation must be verified empirically, not assumed — the whole system silently fails if the test market’s audience responds to different mechanisms.

Play 6.1

Stand up a formal creative test-market program

  • Select 2–3 candidate test markets per app based on low CPM and plausible behavioral similarity to the target market.
  • Validate the correlation before trusting it. Take 10–15 creatives with known US performance, run them in each candidate market, and measure rank correlation. Only markets with strong correlation become official test beds. Budget one cycle purely for this calibration.
  • Set a weekly test-volume target that would be impossible at target-market CPMs. Track it as a core operational metric.
  • Define promotion criteria for graduating a creative from test market to primary market.
  • Re-validate correlation quarterly. Market dynamics shift and a test bed can silently stop being predictive.

Play B — Localize into overlooked revenue markets

The second play is about revenue, not testing. Her argument: teams default to the US because it has the largest cash value, but ignore the markets they actually understand or that are quietly converting well. Babbel and Blinkist built enormous businesses starting from Germany. Ewa started in its own local language before expanding. With AI translation, adding a language is now a matter of hours rather than a project.

The nuance: culturalization is much harder than translation

Her Japan bet at Replika is the cautionary case. They committed, hired a Japanese speaker, and did genuine localization — and the cultural adaptation still did not work. Her conclusion is a deliberate paradox: don’t go hard on countries you cannot understand, but also try many more countries than you currently do.

The resolution is a tiering model. Do not treat “add a language” and “enter a market” as the same decision.

TierWhat you doInvestmentDecision rule
Tier 1 Home advantage Full cultural adaptation: copy, creative, casting, paywall, pricing, references High — native team involvement Only where you genuinely have native fluency
Tier 2 Broad translation AI translation of store listing, app, paywall and ad copy. Localized creative only after signal appears. Low — hours per language Default. Try many. Cost of trying is near zero.
Tier 3 High-context markets No entry without a local partner or native team member. Japan, Korea, and similar. Very high — or zero Do not half-commit. Half-commitment is the expensive failure.

She adds a genuinely useful reframe on cultural research: look for similarities, not only differences. Her example was recognizing shared generational experience with a Korean friend and with people from Central America, despite very different surface cultures. For app positioning this means the underlying pain is often far more universal than the surface presentation, and a working angle frequently ports across markets that look unrelated.

Localization checklist

0/8

Section 07 · Doctrine V

Organic Is A Double-Edged Sword

The thing everyone wants is the thing that traps you. Run paid early even when organic is carrying you.

Both Replika and Solid Starts had enormous organic traffic. Money arrives without daily ad spend, the business is not hostage to CAC, and it feels like the ideal state. Her argument is that this is a trap with a delayed detonation, and she has watched it play out more than once.

How the trap closes

  1. Saturation. Organic reaches the boundary of its niche. Everyone who could plausibly discover you has. Growth flattens — not because anything broke, but because the addressable pool is exhausted.
  2. Pressure arrives. Investors, acquirers or internal targets require a growth story. A flat line, however profitable, is not sellable.
  3. Paid is switched on late. The reasonable assumption is that a beloved product will acquire efficiently.
  4. Cannibalization. Roughly half the time, per her estimate, paid buys users who would have arrived organically anyway. Spend rises, revenue does not. The team cannot tell the difference from the dashboard.
  5. No steering. Unlike paid, organic offers no lever. You cannot adjust it daily. You watch it.

Replika compounds the lesson with an unforecastable shock: ChatGPT commoditized the entire AI-companion category. An organic-dependent business has no dial to turn when its category collapses.

She attaches a story that makes the no-steering point sharper. The early ChatGPT-wrapper apps caught a purely organic influx and solidified top App Store positions — and when other teams copied their paywalls and monetization, nothing transferred, because the money was never coming from the paywall in the first place. In her words it was all just dumb luck: the owners could not repeat it, were not really monetizing it, and could not even sell it. Copying the visible parts of an organic winner teaches you nothing, because the part that mattered is invisible.

The prerequisite everyone skips

She is blunt that organic strategy only applies if the product is genuinely unique. If you are building a time tracker or a storage cleaner, organic will not happen, and neither will brand. Uniqueness is the precondition, not the outcome. The host’s example is Cal AI: it went viral because the mechanic was novel and visually demonstrable in a single screenshot. He also notes the decay — once every calorie app has the same feature, that same creative stops working.

ASO gets flagged as the one organic channel that keeps delivering for years, with the caveat that algorithms appear to favor established apps, making a top position harder to win now than previously. Both speakers treat serious ASO as a specialist discipline requiring dedicated daily keyword work, not something to do casually.

Play 7.1

Run an incrementality test on every organic-heavy app

For any app where organic is a large share of installs, you are almost certainly unable to state what paid actually adds. Run geo holdout tests: suppress paid in matched regions and measure the true incremental lift. Without this you may be spending real money buying users you already had. This is the highest-value analytical work available on an organic-strong app, and it should be scheduled rather than discussed.

Play 7.2

Track a niche-saturation indicator per app

Build an early-warning metric: organic installs as a share of estimated addressable audience, trended over time. Second derivative matters more than the absolute number. When organic growth decelerates for two consecutive months, that is the trigger to invest in paid capability, not after the flat line has already been reported upward.

Play 7.3

Score every app on defensible uniqueness, honestly

For each app in the portfolio, answer in writing: what can we do that a competitor cannot replicate in ninety days? If the answer is nothing, then organic, brand and PR are all off the table, and the app should be run as a pure performance-marketing business with the cost discipline that implies. This is a clarifying exercise, not a demotion — it stops you spending on channels that structurally cannot work for that product.

Organic checklist

0/6

Section 08 · Doctrine VI

Focus, Red Oceans And Portfolio Discipline

Her stated biggest failure of the year: running too many products simultaneously.

In order to not make mistakes, you need to prioritize one thing, and you need to literally treat it like a war room where every day you come in and ask: what are we doing today? Don’t let anything go like ‘oh, it’s the same, you scaled one app, you can do another.’ No, it’s not like that.
On why parallel products fail

The specific trap she names is seductive and familiar: “we already have the developer on salary, so this new idea costs nothing to build.” Development capacity is not the binding constraint. Attention is. Marginal engineering cost being near zero says nothing about the marginal cost of the leadership focus, creative iteration and market learning that the new product will consume.

Play 8.1

Classify every app by mode, and cap the scaling slot

Each app is assigned exactly one mode, reviewed monthly, and the classification is public within the team:

ModeWhat it meansAttention allocatedCap
Scaling Daily war room. Aggressive creative testing, market expansion, full leadership attention. Daily standup, senior ownership Max 1–2
Maintaining Proven economics, running on established playbooks. Optimization only. Weekly check-in Several
Validating Pre-build or early testing under the Section 05 gate Time-boxed sprint Max 1 at a time
Sunsetting Explicitly deprioritized. Decision made and communicated. Minimal

The discipline is that nothing sits in “scaling” by default. Promotion into the scaling slot requires something else to leave it.

Play 8.2

Run an actual daily war room on the scaling app

Fifteen minutes, same time daily, one standing question: what are we doing today, and what did yesterday teach us? Not a status meeting. Not a reporting ritual. If the app cannot sustain a daily decision cadence, it is not genuinely in scaling mode and should be reclassified honestly.

Red oceans and the uniqueness requirement

Her closing lightning-round answer: growth would be easier in blue markets rather than red ones. She describes re-entering the mental health category and finding it brutal — “it’s mental out there” — and says she does not know how people are surviving without a genuinely unique product.

The host supplies the counterweight: Cal AI entered a category already crowded with calorie counters and won, and he admits he made the same misjudgment about Ladder, assuming a new fitness app was walking into an impossibly brutal market. She answers with her own history. In 2017 everyone assumed there was no room for another fitness app, and companies bigger than BetterMe have been built from that market since. Her conclusion: when a market is big enough, there is room for everyone.

On execution intensity

The Higgsfield section describes a team working seventeen-hour days, six-day weeks, sleeping in the office. She is careful not to prescribe it universally — she says she would not want to work that way now — but observes it produced a genuine market lead, and that afterward she pushed harder in subsequent roles.

The host’s reframe is the more useful takeaway and the one worth adopting: intensity works when it comes from genuine passion and is chosen, not when it is imposed. Both speakers agree that cracking the whip on employees to work ten-hour days does not produce the same result. The management implication is to hire for intrinsic motivation in the categories you operate in, and not to attempt to manufacture Higgsfield-style intensity through pressure. It does not transfer.

Portfolio checklist

0/6

Section 09 · Doctrine VII

The Line We Do Not Cross

Black hat growth as a category is ending. The drift into it is gradual, which is what makes it dangerous.

The final substantive discussion covers deceptive subscription funnels: quiz flows that obscure pricing, post-purchase upsell chains that exploit sunk-cost momentum, per-day pricing that hides the real charge. Her account of how it happened is the important part, because it is not a story about bad actors.

  1. Web funnels started as a legitimate response to ATT and a way to avoid platform commission.
  2. Ordinary commercial greed applied ordinary optimization pressure.
  3. The question drifted from “how do we sell better” to, in her words, how to lie to the user so they don’t understand that they were lied to.
  4. Regulators noticed. The damage landed across the whole category, including companies that never engaged in it.

The host’s account is concrete: his wife completed a long quiz funnel, authorized a $1 charge via Apple Pay, and was then walked through a chain of upsells she clicked through while trying to reach the plan she believed she had bought. The real charge was $350–400. Support refused a full refund citing a 30-day term. He notes a chargeback is the appropriate response, and that the pattern was almost certainly extremely profitable while it lasted.

A monetization standard worth adopting

Adopt a bright-line test rather than case-by-case judgment, because case-by-case judgment is exactly the mechanism that produces gradual drift.

Required

  • Total charge amount and billing period visible on the purchase screen, without scrolling or expanding
  • Trial end date and the amount that will be charged, stated plainly
  • Cancellation path no harder to find than the subscribe path
  • Confirmation email restating price, period and cancellation method
  • Refunds honored promptly on good-faith requests

Prohibited

  • Per-day pricing shown without the total charge at equal prominence
  • Post-purchase upsell chains that exploit checkout momentum
  • Material terms disclosed only in fine print
  • Any flow where a user could reasonably not know they subscribed
  • Support processes designed to exhaust refund requests

Play 9.1

The naive user test

Before any paywall or funnel change ships, one person who has not seen the flow completes it on a real device without guidance. They are then asked three questions: What did you just buy? How much will you be charged, and when? How would you cancel? If they cannot answer all three correctly, the flow does not ship. This takes ten minutes and catches nearly everything.

Play 9.2

Monitor refund and chargeback rates as an ethics signal

Refund rate, chargeback rate and “I didn’t know I subscribed” support ticket volume are tracked per app as first-class metrics. A rise in any of them means the funnel has drifted, regardless of what revenue is doing. Revenue is a lagging indicator here and will look excellent right up until the removal notice.

Play 9.3

Quarterly funnel audit against the standard

Someone not responsible for the revenue number reviews every live paywall and web funnel against the table above. Optimization pressure is continuous and unidirectional; the audit is the only mechanism that reliably counteracts drift. Findings go to leadership, not just to the app team.

Monetization standard checklist

0/5

Section 10

The 90-Day Implementation Plan

Sequenced so that early work unlocks later work. Owners are role placeholders — assign names before circulating.

Filter by owner

Weeks 1–2 Instrument and baseline

0/6

Weeks 3–4 Build the test-market engine

0/5

Weeks 5–8 Scale creative volume

0/6

Weeks 6–10 Localization expansion

0/4

Weeks 8–12 Organic truth and validation gate

0/6

What to expect if this is working

  • 5–10×Weekly creative tests vs. baseline
  • <30dSince last step change
  • 30%+Concepts failing brand review
  • 20%+Spend on creative <21 days old

Section 11

Master Checklist & Operating Cadence

One page to print and run against. Everything below appears in expanded form earlier in this document.

On knowledge sharing

One recommendation sits outside the doctrine structure but is worth acting on. At Palta, portfolio companies openly shared test results with each other, and she credits this with materially accelerating everyone. Her position is that the industry underperforms because teams hoard findings, and that sharing costs little — results rarely transfer cleanly between products anyway, so what you actually give away is inspiration rather than advantage. Her example: someone somewhere discovered that adding a blink animation to a continue button lifted conversion. That idea does not occur to one team in isolation.

Two concrete actions follow. Internally, if you already have multiple apps under one roof with fully aligned incentives, run a standing cross-app forum where test results are shared as a matter of routine, not on request. Externally, identify three or four adjacent, non-competing studios and set up a recurring call. As the host points out, competitors can see most of your creative in Meta’s ad library regardless, so the perceived secrecy advantage is largely illusory. The genuine scarcity is having someone competent look critically at what you are doing, which no company can afford to buy twice over.

Section 12

Where I’d Push Back

Adopting advice uncritically is its own failure mode. These claims need adjustment before they fit a real business.

Everything above is written as directive because a playbook should be actionable. This section restores the necessary skepticism. Four claims do not survive contact with a real portfolio unmodified.

Pushback 1

“Run one product at a time” — conflicts with the studio model

She names parallel products as her biggest recent failure, and the reasoning about attention being the real constraint is sound. But the conclusion does not transfer directly to a portfolio studio. Portfolios exist because app outcomes are hit-driven, and a single-product strategy concentrates that risk severely. Palta — one of her own reference points — is a multi-app company.

My adjusted position: The constraint is not the number of apps but the number in active scaling. Maintaining apps on proven playbooks consumes far less of the scarce resource than launching or scaling does. Cap the scaling slot at one to two, be rigorously honest about which mode each app is in, and do not let “maintaining” quietly become “neglected.” That preserves her insight without abandoning the model the studio is built on.

Pushback 2

“Brand doesn’t exist” — overstated, and she partly retracts it herself

The claim is deliberately provocative and useful as a corrective to teams that over-index on visual consistency. But she supplies her own counter-example at Solid Starts, where ignoring brand produced real damage. The host also notes Ladder’s Hilary Duff partnership showed near-immediate measurable impact, which complicates the clean brand-versus-performance split.

My adjusted position: Brand does not justify spend at this scale — correct, and you should not run awareness campaigns. But brand constrains creative in trust-critical categories, and the constraint is real. Use the trust gate rather than either extreme. Note also that retention and word-of-mouth are brand effects that do not appear in CAC and are therefore systematically underweighted by a pure-performance lens.

Pushback 3

Survivorship bias runs through the whole conversation

The evidence base is companies that worked. Ugly ads worked at BetterMe; you do not hear from the many teams whose ugly ads simply underperformed. Higgsfield’s seventeen-hour days are presented as vindicated, but the same intensity at a company that mistimed the market produces burnout and nothing else. Being early was correct for Higgsfield and expensive for many others.

My adjusted position: Treat these as hypotheses with good priors, not as established mechanisms. This is precisely why Section 03’s instrumentation matters — it is what lets you find out whether ugly ads work for your apps rather than assuming they must. Test the doctrine the same way you test creative.

Pushback 4

The paid-first prescription assumes healthy paid economics

Her advice to run paid from day one alongside organic is sound for apps with strong LTV in high-value categories. For lower-ARPU apps in expensive auction environments, early paid can burn capital that would be better spent reaching product-market fit. The prescription is partly an artifact of the high-LTV subscription categories she has worked in.

My adjusted position: Run paid early at whatever scale keeps the capability calibrated and the learning flowing — but the purpose at that stage is capability-building and audience seeding, not growth. Do not confuse the two, and do not let “always be running paid” become an argument for unprofitable spend on an app that is not ready.

What is not in dispute

Several claims are well-supported, cheap to implement, and carry little downside risk. If bandwidth is constrained, do these first and leave the rest:

  1. Testing creative in cheap markets and scaling winners into expensive ones. The single highest-leverage tactic in the document. Low cost, large effect, mechanically sound.
  2. Validating demand with marketing before committing engineering. Cheap insurance against the most expensive category of mistake a studio can make.
  3. Broad, low-cost localization. Near-zero marginal cost now — and if you operate outside the default US-first markets, you may already hold a structural advantage in one she independently named as strong.
  4. Refusing black hat monetization. Asymmetric risk. The downside is removal from the store; the upside is incremental revenue that is not worth it.
  5. Measuring volatility rather than only averages. Costs nothing but a reporting change and reframes what the team is hunting for.
So don’t go chasing waterfalls — no, go chasing waterfalls. Don’t stick to the lakes.
On entering hard markets anyway

Credit where it belongs

None of this is my thinking.

Every doctrine, example, number and warning on this page came out of one conversation between two people who have earned the right to make these claims. I organised their work into a plan. I did not originate any of it.

  • The thinking

    Yuliya Lennox

    Roughly a decade of app growth — BetterMe, Ewa, Palta, Replika, Higgsfield and Solid Starts. All seven doctrines are hers, including the ones I argue with in Section 12, and including the failures she volunteered about herself.

  • The interview

    David Barnard

    Host of Sub Club. His pushback is not filler — the aquarium-app exchange in Section 05 and the red-ocean counterweight in Section 08 are both his, and both change the conclusion.

  • The podcast

    RevenueCat

    Makes and publishes Sub Club, free, with no paywall on any of it. Go watch the full episode — this page is a summary, and summaries lose things.

Watch the original — Sub Club Make Ugly Ads to Grow Your App — Yuliya Lennox youtube.com · the full conversation, unedited by me
Mert Demirdelen

Organised by

Mert Demirdelen

Head of Growth & Product · Ankara, Türkiye

I run growth and product for consumer mobile apps — acquisition, monetization and retention, across mobile and web. I turned this episode into a plan because I wanted my own team to act on it rather than nod at it. If you are running any of these plays and want to compare notes on what actually moved, I would genuinely like to hear about it.

Structured, written and built as a page with Claude Code (Opus 4.8).

Source material: “Make Ugly Ads to Grow Your App” on the Sub Club podcast by RevenueCatDavid Barnard in conversation with Yuliya Lennox. Quotations are short excerpts from that conversation, reproduced here for commentary and attributed throughout. The arrangement into doctrines, the plays, checklists, tables and 90-day plan are my own, and so are the places where I disagree. Any mistake in reading her argument is mine, not hers. Nothing here is affiliated with, reviewed by or endorsed by RevenueCat, the host or the guest.