
Scream to Scale: The 90-Day Blueprint for a 1M ARR Horror App
The Vertical Scream: Why Horror Microdramas Are the Next Gold Rush
The Skeleton: Building an App for Zero Friction
Sourcing the Shivers: Content Strategy and Production
Blood Money: Revenue Models for Micro-Streaming
The Midnight Viral: Organic Growth and Social Hooks
Targeting the Terror: Paid UA and Data-Driven Scares
Keeping the Ghosts Around: Retention and Community
The 90-Day Execution: Scaling to Your First Million
Most founders spend 90 days planning. Roy Oasing spent 48 hours. Oasing, who scaled a data company to one billion dollars in revenue — now worth eighteen billion — coined the Strategic Game Planning process on a single principle: execution first, plan second. Not a five-year roadmap. Not a perfect model. A 48-hour sprint to answer one question: how big do you want to be? For a horror microdrama app targeting one million in ARR, that question has a precise, non-negotiable answer — and the clock is already running. Last session established that community infrastructure — the Theory Board, Live Premiere events, behaviorally triggered notifications — must be live before Day 30, because the first cohort's habit-formation window closes fast. That insight feeds directly into Phase One: the Soft Launch. Days one through thirty are not about scale. They are about proof. Ship the Content-First app, activate the hybrid revenue model, and run horror-specific interest targeting on paid channels. Your target is the first 100 paying users. Those 100 users are not a revenue milestone. They are a data instrument. Oasing's framework sets growth targets on 24-month horizons, not five-year plans, because long-term timelines give founders permission to delay. For this sprint, Yolanda, the 24-month ambition compresses into 90 days — and the soft launch is where you validate the one marketable feature that will carry the entire scale phase. Run seven-minute customer interviews. Identify your whale profiles immediately. A single whale at five hundred dollars lifetime value subsidizes one hundred casual users, so finding them in week two is not optional — it is the unlock for everything that follows. Days 31 through 60 are the Aggressive Scale phase, and the revenue target here is 50 percent of your monthly goal — roughly forty-one thousand dollars in MRR. Lookalike Audiences seeded from your whale cohort go live at day fourteen; by day thirty, sixty to seventy percent of paid budget runs against those audiences. Brandon Dawson, who sold his company for 151 million dollars after being voted least likely to succeed, built that outcome on one principle Oasing echoes: be different or be dead. For your app, differentiation is the content moat — App-Originals no competitor can replicate, distributed through channels your organic Clip-Mining system has already primed. Rapid expansion follows proving what works. Not before. Days 61 through 90 are Optimization and Retention. Cut underperforming series. Cut underperforming ads. The math is unforgiving: at a blended average spend of five dollars per user, you need 200,000 paying users to hit one million ARR. Every dollar of CAC above your LTV ceiling and every series with low completion rates is dead weight pulling that number further away. The 20-mile approach — consistent, disciplined daily progress toward the revenue milestone — is what closes the gap. Inherent virality, Share-for-Coins, and a community that generates more than 50 percent of its own growth activity are your compounding forces in this final phase. Data-driven optimization is not a refinement step, Yolanda. It is the phase itself. The full 90-day arc is this: soft launch to validate, aggressive scale to build momentum, optimization to lock in retention and cut waste. Oasing's core rule applies at every stage — revenue goals are set by desire, not data, because ambition drives action and data only refines it. Traditional strategic planning is broken; it relies on hype and delays execution. Your plan is just about right for an imperfect world. Ship it. The 90-day blueprint is not a guarantee. It is a forcing function. Execute the 30-60-90 sequence — technical stability first, aggressive scaling second, ruthless optimization third — and the path from zero to one million ARR is not a hope. It is a system.