Apple me paga 82.393,36 para criar aplicativos e você pode fazer o mesmo

What the creator claims they did (business outcome)

• Claimed Apple paid them R$84k+ (and ~R$85,332 in a provided example) for app work in a given month.
• The amounts vary month to month.
• The video frames this as a repeatable system to:
  • generate app ideas
  • validate market demand
  • build with a “core feature” approach
  • monetize via iOS subscriptions
  • minimize platform/transaction fees
  • run marketing (mostly paid ads) and track unit economics

Idea generation & validation playbook (what to do before building)

• Rule of thumb: the “first idea” (e.g., “build a finance tracking app”) is often bad because it’s common and already saturated.
• Validation process:
  1. Talk to people who would use the app (informal customer discovery).
  2. Research the market’s existence: check whether others already sell/make money in that niche.
  3. Logic: entering an existing profitable niche is easier than creating a new market from scratch.
• Example positioning (market-creating innovation):
  • Mentions a creatine gummies brand that “created a market” (Brazil context).
  • Mentions a calorie tracker app that differentiated using a photo-to-calories mechanic.
• Idea volume metric:
  • Creator claims 10+ business/app ideas per week, with ~99% discarded.

Product strategy: “single core feature” architecture

• Design principle / framework: launch with one main feature that is:
  • highly valuable to the user
  • easy to market
• Marketing fit example:
  • A calorie tracker app with a single central action (photo + calories) supports simple ad creative:
    • show the plate in a video/ad
    • display calories on screen
    • run influencer campaigns / organic content (“record the food”)
• Avoid overengineering:
  • Don’t spend months building complex systems nobody will use.
  • Even with AI, large/complex implementations may not be worth it if demand is weak.
• Expansion rule:
  • Start with the core feature.
  • Add additional features only later if user demand and market demand justify it.

Monetization strategy (iOS-first + subscriptions)

• Platform choice / go-to-market:
  • Recommends launching on iOS first.
  • Claims Android is harder to monetize (most Android users don’t pay).
• Recommended monetization:
  • Subscriptions are positioned as “best” because they provide:
    • recurring revenue
    • user familiarity with monthly payments (Netflix/Prime analogy)
• Key subscription risks / metrics to manage:
  • Churn / cancellations (“number of users who cancel”)
  • Refunds
  • Other metrics determining long-term viability
• What they don’t recommend:
  • In-app ads: says it tends to work mainly for game apps.
  • One-time fixed-price app sales: described as outdated.

Paywall / billing tooling (experiments)

• Tools mentioned for subscriptions and paywalls:
  • RevenueCat
  • Superwall (preferred by the creator)
• Experimentation capability:
  • Superwall is used for A/B paywall tests and “tracking metrics very accurately.”

Apple fees optimization (business setup + Small Business Program)

• Baseline fee structure:
  • Apple developer program: $99/year
  • Apple automatically takes 30% of subscription revenue
• Execution steps to reduce fees:
  1. Create the Apple developer account as a business/legal entity (PJ), not as an individual.
  2. Apply for Apple’s Small Business Program:
     • eligibility: company earns < $1M annual revenue
     • claimed result: Apple rate reduced from 30% → 15%
• Operational note (process persistence):
  • They claim approval requires chasing Apple weekly/daily until approved.

Cashflow timing (Apple payout calendar as a budgeting constraint)

• Dependency/KPI: Apple pays with delay, tied to Apple’s fiscal schedule.
• Claimed rule of thumb: first payment occurs about ~60 days later (D+60).
• Example schedule:
  • Sold in January → payment around March 5
  • Earned in April → paid on the 5th of June
  • Earned in May → paid July 2
  • Earned in June → paid end of July (July 30)
• Budget implication: plan marketing/operating budgets around this cashflow lag.

Payments operations: reducing FX/transfer costs (execution partner)

• Recommends a partner for international currency transfers:
  • Tech Effectex
• Cost benchmark (claimed rates):
  • Tech Effectex: ~0.5% receiving fee
  • Other platforms: described as higher total costs (ranges given for total estimated cost, including IOF/taxes/spread)
  • PayPal: described as worst
• Quantified rationale:
  • “Every percentage point matters”; saving commission can be substantial at R$100k–R$1M/month scale.
• Operational workflow:
  • Sign up with email → confirmation link
  • Provide company details (CNPJ if applicable)
  • Link payment destination (“bank details” in dollars)
  • Add receiving payment details inside App Store Connect → finance section
  • Mentions dedicated onboarding for solo developers and app-store payout collection

Example payment conversion & operational numbers (high-level unit economics)

• Example stated:
  • Apple paid $16,590 on June 5
  • Converted to ~R$85,332 using exchange rate R$5.15 (as shown in the demo)
• Emphasis: fees reduce net, so consider:
  • transfer fees (claimed: first transfers at 0.1% for first two transfers)
  • then subtract operating costs

Operating costs & cost structure (what consumes revenue)

• Reinvestment strategy: reinvests 100% into the business.
• Largest expense: marketing (paid ads)
  • Example claim: spending ~R$60-something thousand on Meta ads to generate ~R$85,000 that month.
• Other “lean” operating costs mentioned:
  • taxes
  • accounting
  • backend service: Supas (claimed $50/month with limits/trials)
  • AI API costs for generating images/animations:
    • mentions tools like Cloud Code, Codex, Free Pack
    • states AI/creation costs are small relative to marketing (subtitle value appears corrupted, but the claim is that they’re minor)
• Planned optimization:
  • Start more organic acquisition strategies to reduce CAC so the same spend performs better next month.

Marketing operating model (roles + management)

• Creator describes internal responsibilities:
  • one person builds/strengthens product robustness
  • partner handles marketing with extensive digital product marketing experience
• Recommendation: if you can’t market, find a marketing partner or learn marketing yourself.

Concrete actionable takeaways (condensed)

Before building

• Generate many ideas (discard most).
• Validate via user conversations and confirm market profitability exists.

During build

• Launch with one main feature designed for usability and ad-friendly demonstration.
• Keep scope tight; avoid “revolutionary but expensive” features that won’t be adopted.

After launch

• Monetize via iOS subscriptions.
• Use paywall tooling (Superwall/RevenueCat) to run A/B tests.
• Reduce Apple’s take rate using Small Business Program and correct business account setup.

Operational budgeting

• Plan cashflow around Apple’s ~D+60 payout delay.
• Optimize FX/transfer costs through a lower-fee receiving partner (Tech Effectex claimed).

Presenters / sources mentioned

• Video creator/presenter (unnamed in subtitles)
• Business partner (unnamed; described as marketing lead)

Tools/companies mentioned

• Apple (App Store Connect, Apple Small Business Program, developer program)
• RevenueCat
• Superwall
• Supas
• Tech Effectex
• Husk
• Remessa Online
• Pioneer
• PayPal
• Meta Ads (Metaads)