How a Last-Minute Pitch Built Focus Friend
A pitch meeting that had already ended in a polite no is an unlikely starting point for a chart-topping app. Yet that is roughly how Focus Friend began: one extra question asked as the call wrapped up, and a creator who could not stop thinking about the idea an hour later. The story is less about luck than about three repeatable moves — putting yourself in the room, testing design in public, and accepting that monetizing a beloved creator's audience carries a trust cost that a faceless brand never pays.
The pitch that outlived the meeting
Bria Sullivan had already shipped a successful game, Boba Story, but she wanted to test whether a creator's audience could be monetized through an app. A chance dinner with YouTuber Hank Green led to a pitch meeting aimed at building something for one of his educational channels, Crash Course. The team passed. As the call was ending, Sullivan offered one more concept: a Crash Course focus timer. Crash Course still declined, but Green personally liked it, texted an hour later that he could not stop thinking about it, and agreed to build the app for his core audience, the Nerdfighters.
The reusable lesson is not 'always ask one more question.' It is that a rejected pitch can still surface a viable product if the idea is small enough to evaluate quickly and specific enough to a real audience. Sullivan did not need the whole Crash Course team to say yes; she needed one decision-maker with an audience fit.
Validating design on a live stream
Instead of designing in isolation, Sullivan used her existing TikTok following as a real-time review panel. During long live streams she sketched art styles, displayed color palettes, and asked viewers which they preferred. She showed six versions of the app's central character — a 'bean' — and let the audience pick the direction.
Her reasoning was that for female audiences and gamified products, visual style drives organic reach and conversion. The original lo-fi 'Bee and Puppycat' look she favored was dropped entirely after that unfiltered feedback. By launch, the aesthetic already matched what the target users wanted.
A practical takeaway: a live stream is a cheap way to run preference tests before committing to production art. The cost is time on camera; the payoff is fewer redesigns after release.
When a fanbase feels betrayed by a paywall
Focus Friend launched quietly through a YouTube community post. It drew 20,000 downloads in its first week, but the reaction was not purely positive. Users objected to a subscription model rather than a one-time lifetime unlock, and they were especially sensitive to standard practices such as ad tracking. Because the app was tied to Hank Green — a public figure known for philanthropy — some users experienced the monetization as a personal betrayal rather than a business decision.
Sullivan's response was to remove advertising tracking IDs entirely. That choice effectively ended the team's ability to run paid user acquisition, but it protected Green's reputation and the audience relationship. The distinction worth holding onto: distribution reach and monetization trust are separate risks. A creator solves the first and can amplify the second.
Why the developer should steer the product
Sullivan's conclusion from the partnership is blunt: influencers rarely know what makes a good standalone app. In her experience, creators tend to propose social feeds or information streams, which she does not consider strong app ideas. Her advice to developers working with creators is to take the product manager role. Creators understand what their audience likes to watch; developers understand utility. The strongest collaborations push toward a clear functional use case — a focus timer being the example here — rather than another content feed.
A short pre-build checklist follows from this:
- Confirm the creator can name a concrete job their audience needs done, not just a content format.
- Agree in advance who owns product scope and who owns audience messaging.
- Test the core utility with the audience before investing in art or monetization.
- Decide early how visible the creator will be in pricing decisions, since trust is attached to their name.
- Model the cost of removing tracking or paid acquisition if the audience objects.
More from the episode
The full conversation also covers Sullivan's path from learning Android development in 2010 to winning an App Store Award, the realities of solo development while raising a newborn, and her view that product instinct matters more than pure engineering skill. Links to her profile and to Focus Friend and Boba Story on the App Store are available in the episode's guest links.
Frequently asked questions
What is Focus Friend?
Focus Friend is a focus timer app built by Bria Sullivan in partnership with YouTuber Hank Green, aimed at his Nerdfighter audience. It launched through a YouTube community post and reached 20,000 downloads in its first week.
Why did Focus Friend's subscription model cause backlash?
Users expected a lifetime unlock rather than a subscription, and they were uncomfortable with standard ad tracking. Because the app was associated with Hank Green, a public figure known for philanthropy, some users treated the monetization as a personal betrayal rather than a normal app business decision.
What did the team change after the negative reaction?
They removed advertising tracking IDs entirely. That decision largely eliminated their ability to run paid user acquisition, but it protected Hank Green's reputation and the trust of the audience.
What is Bria Sullivan's advice for developer–creator partnerships?
She recommends the developer act as product manager. Creators know their audience's content preferences, but developers understand utility. The best collaborations steer toward a clear functional use case, such as a focus timer, instead of building another social feed or content stream.