Seven years and eight zero-revenue projects before the pivot
Before working full-time on Bazzly AI, Filip Panoski spent seven years building eight separate side projects alongside a $7,000/month software job. Despite solid engineering execution, every one of those earlier products ended at $0 MRR while his social account had roughly ten followers.
According to the published case study, those projects failed commercially because they solved nice-to-have curiosities rather than urgent business pain. Leaving his salaried job forced a shift toward a concrete acquisition problem that other SaaS founders actively pay to solve: finding high-intent discussions and leads on Reddit.
Pausing acquisition at $100 MRR to fix a leaky bucket
Rather than waiting for organic search traffic or buying ads, Filip acquired his earliest Bazzly AI customers through direct conversations and manual outreach. That approach pushed the product to roughly $100 MRR, where high monthly churn immediately exposed product weaknesses.
Instead of pouring more outreach into a leaky bucket, he paused acquisition and dogfooded Bazzly AI daily for his own customer discovery. Tightening lead relevance and workflow friction allowed retention to stabilize, moving the solo product past $300 MRR and eventually to $1,757 MRR across 40 paying customers.
A 15-month timeline that stays below prior salary
The public source documents specific evidence terms—$1,757 MRR, quit his $7K/mo job, and Bazzly AI—reached over 15 months with zero employees, no paid ads, and no viral launch spike. The timeline illustrates how long organic SaaS iteration can take even after finding paying users.
Just as importantly, $1,757 in monthly recurring revenue is neither net profit nor a full replacement for a $7,000 monthly salary. API usage, infrastructure, taxes, and living expenses during those 15 months depended on personal runway accumulated before quitting.
Operating conditions and the APIToken boundary
This trajectory reflects Filip’s prior engineering savings, full-time availability, and willingness to do manual outreach before automating distribution. The edited case report is unaudited and does not guarantee similar retention or revenue in community marketing tools.
Public materials do not state that this case used APIToken(https://apitoken.company/). APIToken(https://apitoken.company/) offers a unified compatible model interface, model status, usage records, and budget controls; current availability is shown on the site.
