StudyVibes: Designing and Launching an Independent Lofi Pomodoro Timer

Starting Point

A product test built around something I actually use

The goal was specific from day one: build a passive income product, something real and live, generating revenue while I sleep, without giving up on design quality. The constraint I set for myself was that it had to be something I genuinely love and use daily.

The Pomodoro technique was the obvious starting point. I've used it for years. But most tools in this space get the environment wrong. They treat the timer as the product, when for most people the timer is just a scaffold for a whole ritual around focus.

Design Process

From "music to study" to a full environment system

I started by mapping what I actually do when I sit down to study or do deep work. The first thing I reach for is music, specifically instrumental, lofi, ambient. "Music to study" is a whole genre with its own aesthetic and emotional register.

That realization unlocked the product's core idea. If the music creates atmosphere, then each playlist is really an environment. A rainy jazz café. A night city. A cozy library. The timer lives inside a place that puts you in the right headspace.

From there, the design extended naturally into the physical. If someone is intentionally building a study environment around their screen, they're also thinking about what's on their desk. That's where the product concept clicked into a business model: the affiliate layer.

These aren't random products. They're the physical artifacts of a study environment, the things someone who cares about their focus ritual actually buys. The decision was to surface them contextually, as part of the atmosphere, not as an ad unit.

Instrumentation

Building a tracking system that could actually teach me something

The product runs three monetization streams in parallel: Amazon affiliate commissions, Google AdSense display, and a Stripe-powered premium subscription ($4.99/month or $19.99 lifetime). That complexity required deliberate instrumentation, not just Google Analytics on the page but a system I could actually read.

Each of the seven affiliate items has its own Amazon tracking ID, so I can see precisely which product drives clicks and which converts. On the GA4 side, I instrumented three key events: affiliate_click, open_premium_modal, and premium_click. The three moments where a session becomes revenue.

Setting this up end-to-end (tagging, testing, verifying events fire correctly) was one of the most satisfying parts of the whole project. It's a small system, but designed deliberately. Every data point maps to a decision I might make later.

What I Learned

Owning the full loop changes how you design

In client work, design decisions and business outcomes are separated by layers: PMs, engineers, timelines, other stakeholders. Here there were no layers. A decision about where to place the affiliate widget is a revenue decision. An event I forget to tag is data I'll never recover.

That directness sharpens your instincts fast. It also made me a better collaborator on client work, because I understood more viscerally what it feels like to own the outcome, not just the design.

Results

Early traction, growing intelligently

The product is live and generating around ~$200 USD/month on average, through a combination of affiliate commissions, AdSense, and early premium subscribers. It's early-stage and metrics are still accumulating, but the revenue is real and passive.

The next phase is data-informed: understanding which environments drive affiliate clicks, optimizing the premium modal conversion, and expanding the playlist catalog to increase session depth. The instrumentation built at launch makes all of this tractable.