Video summary
How to Build an App Studio by Buying Apps [The Wall Street Playbook]
Main summary
Key takeaways
Summary: Building an App Studio by Buying Apps (“Wall Street Playbook”)
What BlueThrone is (strategy + positioning)
- BlueThrone is an app portfolio company aiming to become the “#1 app portfolio in the world.”
- Their operating thesis:
- It’s easy to scale apps from 0 → ~$1–3M ARR via simple distribution + a “good enough” product.
- It’s harder to scale from ~$2–3M → ~$15–20M+ ARR because of:
- need for robust testing
- multiple distribution channels
- infrastructure cost optimization
- deep expertise across app business levers
- They buy apps that have already achieved “zero to one / product-market fit”, then scale them using team + playbook.
Who this is for (audience-fit)
- Target listeners:
- Own an app doing ~$2–5k/month (possibly $2–3k/month) and are debating buy vs build
- Have capital (starting around $5k+) to acquire app assets/projects
- Not for:
- First-time builders without experience or cash
- Recommendation for them: play/build with modern tooling (AI, no-code assistance, monetization + marketing stacks)
Core frameworks / playbooks (explicit)
1) Buy vs Build: decision signals (“Wall Street brain”)
Strong signals to BUY
- Unique domain knowledge you can apply that the current founder hasn’t
- Proven appreciation potential, e.g. converting weekly subscriptions to monthly at higher price
- At least 1 year of app history to observe seasonality + trends
- Founder alignment/motivation to sell, reducing deal friction and post-close risk
Strong reasons NOT to BUY
- Founder dependency: the founder is the “engine” (e.g., driving downloads via TikTok)
- No/insufficient data (e.g., only ~2 months live)
- Low defensibility (no durable acquisition channel, rankings, or moat)
Strong signals to BUILD
- You have unique product insight not currently executed well (e.g., a vaping cessation app with “run a 5K” sporty motivation)
- Your studio already has distribution capabilities (UA machine, TikTok UGC launch workflows)
- You can build moat/defensibility despite low-friction tools (e.g., Roark/Lovable)
Reasons NOT to BUILD
- Flooded categories with well-funded competitors (won’t win paid UA)
- Hardware/B2B/API-complex products that overcomplicate the app business model
2) “Don’t buy what’s broken” red-flag audit checklist
- Revenue quality / metric inflation
- Watch for lifetime purchases being labeled as ARR (non-recurring)
- Prefer recurring revenue: subscriptions (weekly/monthly/annual) or stable ad/organic revenue
- Integration risk
- App depends on founder personal brand, undocumented systems, or unique undocumented insights
- Churn bomb / hidden churn
- Total churn may look fine while recent cohorts deteriorate
- Require cohort-by-cohort analysis (month 1, month 2, etc.)
- Market timing risk
- Don’t buy at the category peak (analogy: buying crypto at the boom)
3) Deal execution “process” playbook (operational steps)
- Source apps
- Screen apps (reject ~90%)
- Talk to founder (motivation, relationship/trust)
- Pull data: revenue, cohorts, downloads, ASO
- Model valuation/offers (use 3-scenario model, optionally with Claude)
- LOI (non-binding): intended purchase price + required founder stay period
- Due diligence (often bring accountant/FP&A support)
- Close
- Transition period: typically 1–3 months
- Major failure point: founder assumes it’s “their app” before the buyer fully has it
- Tip: be extra on top during transition
Key metrics & KPIs mentioned (and how they’re used)
Revenue and scaling benchmarks
- App acquisition targets:
- ~$200k/year to $10M/year revenue range
- Scaling targets (post-acquisition):
- Move acquired apps toward $10–15M+ ARR
- BlueThrone brag metric:
- ~$23M deployed into “killer apps” (also referenced 150M+ at a prior gaming M&A role; “UA” context)
- Case study acquisition profile:
- App had ~200K monthly active users (MAU) and was organic
Monetization + retention
- Conversion optimization examples:
- subscription redesign
- A/B testing
- pricing experiments
- Retention KPI example
- Day-7 retention increased from 18% → 34% after gamification/streaks and retention mechanics
- Techniques: daily login rewards, subscription retention mechanics, gamification
Acquisition defensibility metrics
- ASO rankings / keyword performance and durability
- App store review scores (impacting ASO)
- Example: ~3.1 stars and ~1.8 in another store context (implied negative effect on ASO)
- Organic discovery channels:
- ASO + Apple Search Ads used as defensibility in a prior acquisition example
- Risk management: avoid relying on a single keyword (diversify across keywords/long-tail)
Cohorts / churn analysis (required due diligence)
- Cohort definition:
- “April cohort” = users acquired during April (e.g., 100 users)
- Track revenue generation at 1 month, 2 months, 3 months, etc.
- Purpose:
- Prevent a “churn bomb” where aggregate churn hides recent cohort deterioration
Multiples / valuation inputs
- Rule of thumb for EBITDA multiple range:
- 3x to 8x
- Valuation depends on:
- EBITDA margin
- revenue stickiness (subscriptions/resub vs one-time/lifetime/ad)
- product retention/core retention
Concrete examples / case studies & actionable recommendations
Example: Buying vs building a “simple app” with no founder know-how
- Hypothetical: buy a $10k/month habit tracking app
- If new buyer can’t run:
- A/B tests
- market expansion
- distribution channel operations
- UA and UGC/TikTok/Reddit execution
- Then the buyer risks owning an asset they can’t grow
Recommendation
- Only buy if you have a plan + capability to increase acquisition and monetization levers after close.
Example: Health & fitness category caution
- Health/fitness issues:
- many well-funded competitors
- high CPIs
- aggressive UA (incumbents outbid with major budget)
- Smart workaround:
- Focus on organic traffic via ASO keywords instead of competing on paid UA
Recommendation
- In competitive categories, buy/build only if you have non-paid defensible acquisition (ASO/organic/ASA where relevant).
Example: App audit improvements that directly affect ASO + conversion
- ASO checklist suggestions:
- keep screenshot identity consistent (avoid mid-listing color identity shifts)
- address low review ratings
- prompt reviews at the “aha moment” in onboarding
- build custom store listings targeting specific keywords (including iOS vs Android differences)
- Conversion/onboarding best practice:
- show paywall before registration/forced sign-up to increase sales
- reported result: +52% sales after flipping onboarding/paywall order
- don’t ask for notifications permission immediately; warm up first
Case study (BlueThrone): scaling an organic app with retention + monetization expansion
- Starting state:
- 200K MAU, organic
- Actions described:
- subscription redesign + aggressive A/B testing
- increased conversion (free → paying)
- ASO overhaul to grow downloads and reach 5M MAU
- expansion into additional markets
- added gamification + streaks to improve retention:
- Day-7 retention 18% → 34%
- daily login rewards and retention mechanics
- Outcome:
- still performing 4+ years later, with continued growth especially in monetization
Operating principle
- Distribution first → then retention → then monetization (avoid tackling everything at once early).
Deal structures (how payment risk is allocated)
- Full cash exit
- simple, but higher buyer risk (buyer pays immediately)
- Earnout / deferred payment
- Earnout: later payment tied to KPI(s) (e.g., downloads)
- Deferred payment: guaranteed second payment after a time period regardless of KPI (BlueThrone reportedly uses this often for fairness and to reduce buyer performance risk)
- Equity + cash
- Revenue share
- founder receives ongoing payments based on app-generated revenue (helps align founder to stay long-term)
Example from Steve
- combination of:
- some cash
- earn-out on revenue milestones
- seller’s note/deferred payment
- framed as balancing risk across multiple components
Buyer ROI / purchase math example (illustrative)
- Example:
- App makes $10,000/month (~$120k ARR)
- purchase price ~3x ARR → ~$360k (Steve mentions paying ~$350k)
- loan payments: ~$5,000/month
- repay loan in ~3 years (he “priced in” ~3 years of revenue), then remaining time becomes profit if performance holds
Josh’s caveats
- hedge assumptions that revenue stays stable
- 10-year app lifespan in current rankings can be optimistic
- buyer should expect immediate uplift post-acquisition via A/B tests, product-led growth, and pricing experiments (example: MRR 10k → 15k → 20k over time)
- consider opportunity cost of capital
- rule of thumb:
- ensure current revenue covers loan payments (safe baseline)
- appreciation improves payback speed and adds profit
Mentioned company operations / organization tactics
- BlueThrone team:
- ~80 people
- role mix: product experts, growth experts, CTO, CFO, etc.
- Their “platform” value:
- not just buying—providing operational capability (testing, monetization, ASO, market expansion, retention mechanics)
Presenters / sources
- Steve P. Young (host / “App Nation”)
- Josh (VP of M&A and business development at BlueThrone)
- Referenced people/brands:
- Cody Sanchez (via “Main Street Millionaire” referenced by Steve)
- Appic (run by Charlie Ryan, referenced as a marketplace for buying apps)
- Acquisition.com (listing/source site)
- AppsFlyer, ironSource (industry context for BlueThrone’s team)
- Down (future guest mentioned; dating app co-owner, top-10 with millions in revenues)
- Tools/platforms mentioned:
- Rock, Lovable, Claude, screendesign.com, RevenueCat, TikTok
- mobile tooling/ads: Apple Search Ads, App Store Connect, cohort analysis references
- Adaptly (Funnel Flux subsidiary)
- Paddle (monetization/funnel solutions)
- Starter Story Build (video link referenced by Josh)