Growing a portfolio of mobile apps to $185k/mo

Connor Burd, founder of Payout

Connor Burd built a mobile product for fun and got some momentum. So he did again. And again. And it eventually turned into a business bringing in $185k/mo.

Now, he's building FunnelMob.

Here's Connor on how he did it. 👇

Turning curiosity into a business

I’m an iOS app developer who started by building products for fun and gradually turned that into a serious business.

It started with a single app idea. I woke up in the middle of the night and wrote it down. Then, I built it out of curiosity, shipped it, and kept going. Over time, that curiosity turned into momentum, and I realized I could build real businesses by creating apps around things I genuinely enjoy.

Today, I run an independent app studio focused on consumer subscription apps. It currently generates roughly $185K in monthly recurring revenue, primarily from subscription-based mobile apps.

Every app has an emphasis on strong distribution, clean execution, and data-driven iteration.

Focus on one product at a time

I have several active mobile products, but my focus right now is Payout.

Building a portfolio of apps can be hard and I've found that focusing on one project at a time is helpful.

When you commit fully to a single product, the quality of your decisions and your understanding of the business improves dramatically.

User and revenue growth

Distribution should be a priority from day one, not an afterthought.

For Payout, we began with heavy research into trends on TikTok and the App Store. Then, I partnered with an influencer and built the product specifically around an existing, validated audience.

We've also grown through user-generated content and paid advertising. And all of this is supported by strong App Store optimization. But I'd say influencer marketing has performed best, bringing tens of millions views — it's hyper-growth without hyper-send.

Double down early on what's working

There have been a lot of challenges along the way. But I don’t think of challenges as obstacles, so much as part of the learning curve. Each product teaches you something new about distribution, retention, or positioning.

And experimentation is part of that. If I were starting over, I’d simply double down earlier on what’s already working instead of experimenting too broadly.

A mobile tech stack

Our tech stack is largely the same in all our apps:

  • Cursor

  • TypeScript

  • Next.js

  • Vercel

  • RevenueCat

Build for distribution first

Here's my advice: Build for distribution first.

Partner with someone who already has an audience.

If something is already working for someone else, that’s validation that it can work for you.

What's next?

You can follow along as I build my new company, FunnelMob, on X. And check out Payout.

Indie Hackers Newsletter: Subscribe to get the latest stories, trends, and insights for indie hackers in your inbox 3x/week.

About the Author

Photo of James Fleischmann James Fleischmann

I've been writing for Indie Hackers for the better part of a decade. In that time, I've interviewed hundreds of startup founders about their wins, losses, and lessons. I'm also the cofounder of dbrief (AI interview assistant) and LoomFlows (customer feedback via Loom). And I write two newsletters: SaaS Watch (micro-SaaS acquisition opportunities) and Ancient Beat (archaeo/anthro news).

Support This Post

3

Leave a Comment

  1. 1

    Thanks for sharing. So many interesting business startups are so opaque to me in terms of how they started. I'll share this with my app developer friend who has some great ideas but needs the help to get his ideas off the ground

  2. 2

    I wasted 4 months on an app nobody downloaded. Now I use tractionway dot com to validate first - costs like $50 and you know within a day if the idea has legs

  3. 1

    This is a mobile tech stack?
    - Cursor

    • TypeScript

    • Next.js

    • Vercel

    • RevenueCat

  4. 1

    The throughline here isn’t “mobile apps” — it’s distribution certainty before execution. Partnering with an existing audience and shaping the product around it removes a huge amount of early risk.

    What stood out to me is how this mirrors fast validation loops: curiosity → ship → watch signals → double down early. The success isn’t from building more, but from learning faster what actually works and committing hard once the signal appears.

    Curious with FunnelMob — how early are you pressure-testing demand now? Are you validating distribution and positioning before writing much code, or still letting the product lead and refining from there?