The indie hacker playbook is simple: ship fast, see what sticks, move on if it doesn’t.
A dozen projects in a year is a badge of honor in these circles. Validate quickly, kill quickly, keep moving.
Jon Yongfook followed that playbook.
He committed publicly to launching twelve startups in twelve months.
He hit the pace. He shipped product after product.
By project six though, he was burned out. By project seven, he knew something was broken.
The next five years looked nothing like that first one, and what he figured out during that period reshaped every decision that followed.
He now operates a startup that generates over $900,000 a year, built on top of a single question that most creators never think to ask until they’ve already spent years chasing the wrong thing.
Twelve Startups, Zero Traction
Before the startups, Yongfook spent his days at an ecommerce company making product banners.
Hundreds of them. Social graphics, promotional images, the same layouts with different text, over and over.
Every new product meant another round of the same tedious process.
He would have killed for a way to automate it at the time, but the tools just didn’t exist yet.
That frustration stayed with him.
Years later, when he committed to the twelve startups challenge, he didn’t start with automation. He chased whatever seemed interesting that week.
A movie recommendation app, a habit tracker, ideas that looked good on paper but were more about what he thought could be profitable rather than what moved him personally.
Most made nothing. A few pulled in a couple hundred dollars a month.
He kept shipping, but the traction never came.
By project six, the energy was gone.
He could handle the pace, that wasn’t the issue.
What drained him was waking up every day to work on things he’d picked at random. Problems he had no real connection to. Businesses he couldn’t imagine running for another six months, let alone six years.
He was building fast and going nowhere.
That’s when the question changed.
Instead of asking what he could ship this month, he asked what he could commit to for years.
What problem had he actually lived, that he himself had felt the pain of? Something strong enough to push him forward even when things got tough?
His time at the ecommerce business kept surfacing. The drudgery of creating banner visuals day in and day out.
He left his job and started building something he called Bannerbear.
Months passed. His savings drained, but he maintained his conviction, and decided he would document the journey publicly.
He was in his early thirties, working from his childhood bedroom, watching his runway shrink while the product crawled toward something resembling traction.
The numbers, the experiments, the weeks where nothing moved. Building in public meant there was nowhere to hide when progress stalled.
Two years of this.
Two years of waking up, shipping, watching the metrics, and wondering if he’d made the right call walking away from a steady paycheck to bet everything on a tool that automated the kind of work most people didn’t even know was a problem.
What Finally Made The Numbers Move
It took two years to hit $10,000 a month. Barely enough for a wage after expenses.
Then something shifted.
The next $10,000 took six months.
The product hadn’t changed.
Bannerbear still did the same thing it always had. Generate images and videos automatically through an API. Feed it data, get back finished visuals. The automation he wished he’d had back in those ecommerce days.
What changed was how the front-end and back-end of his business started working together.
Yongfook developed a rhythm he called the 50/50 rule.
One week building, one week marketing.
Every feature shipped with content that showed someone exactly how to use it.
On the surface, this looked like content marketing. Tutorials, documentation, how-to guides. Standard front-end activity for building awareness.
The content also converted visitors into customers.
Each tutorial walked potential customers through exactly how Bannerbear fit into their workflow.
By the time someone finished reading, they understood the product well enough to implement it.
The documentation did the selling.
The back-end mechanics reinforced this.
He’d tried pricing at $9 a month early on.
The math was brutal.
At that price, he’d need over 5,000 paying customers to hit serious revenue. With typical conversion rates, that meant hundreds of thousands of free users.
The support load alone would bury him.
So he raised prices. $49 a month at the entry level, scaling up to $299 for heavier usage.
The higher price filtered for customers who had a real problem to solve. Teams and businesses who needed automation infrastructure.
Trial users got thirty free credits. Enough to build something real.
By the time those credits ran out, Bannerbear was already wired into their workflow.
That’s where the back-end created staying power.
Bannerbear integrates with Zapier, Airtable, Make, and dozens of other tools.
Once a team connects it to their automations, removing it means breaking systems that are already running.
When credits run out, the integrations stop working. Customers upgrade to keep their workflows running.
The front-end brings people in through search and tutorials. The back-end makes them expensive to leave.
The system compounds. Every tutorial he writes ranks in search and keeps bringing in new customers months later. Every new integration adds another layer of staying power for existing ones.
The question is how one person keeps all of this running.
How One Person Runs A $900,000 Business
Most software businesses at this level rely on teams of people.
Engineers, support staff, account managers, operations people. The demands grow alongside the revenue.
Yongfook runs Bannerbear with two customer support specialists. Everything else is him.
That sounds impressive until you realize he engineered it that way.
Start with the technology.
He built Bannerbear on Rails and jQuery. Software that’s been around for years. Stable, predictable, and boring, but dependable.
There’s no cutting-edge framework to keep up with. No complex architecture that requires a team to maintain.
He can ship new features in hours because he knows every line of the codebase.
The image and video processing runs on AWS Serverless. When demand spikes, it scales automatically. When things are quiet, it scales back. He doesn’t manage servers.
After a DDoS attack nearly took the service down, he added Cloudflare for security and edge protection. Another layer that handles itself.
Then look at how customers experience the product.
There’s no sales team, phone support, or enterprise contracts with custom terms.
Customers sign up, read the documentation, connect the API to their tools, and start generating images.
If they get stuck, the tutorials and knowledge base handle most questions before anyone sends an email.
The two support hires deal with what gets through.
He’s also deliberate about what Bannerbear doesn’t offer.
There’s no custom development. The API is the API. Feature requests become public features that benefit everyone.
There’s no design services tacked on. Customers create their own templates or use the library.
There’s no consulting, coaching, or done-for-you packages.
These would all generate revenue. Each of them would also require his time, his calendar, and eventually more people.
Every decision points in the same direction. Reduce what the business needs from him day to day.
That’s how one person operates a business generating over $900,000 a year. And it’s what makes year five feel like the system is gaining momentum rather than grinding him down.
The Question Worth Asking In Year One
Yongfook built a software product for developers and media teams. His world probably looks different from yours.
The principles behind how he built it are worth paying attention to though.
The first is about sustainability as a strategy.
Yongfook picked a problem he could commit to for years.
The 50/50 cadence, the simple technology, the refusal to add services that would eat his calendar.
All of it was designed around one question: can I still be doing this in year five?
If you’re burning out after three months on a project, the problem probably isn’t discipline. It might be alignment.
The work has to matter enough to carry you through the long stretch where nothing seems to be moving, but also not take so much from you that success inevitably leads to burnout.
The second is about how your content connects to how people buy.
Yongfook’s tutorials look like content marketing.
They function as a sales team. Every piece shows a potential customer exactly how the product fits into their daily work.
By the time someone finishes reading, they’ve already started using it.
If your content builds awareness but doesn’t lead people toward a purchase, that’s the gap worth closing.
The front-end of your business brings people in. The back-end is what turns them into paying customers.
Yongfook’s content does both at the same time.
The third is about reducing what the business needs from you.
Every decision Yongfook made shrank what the business required of him day to day.
Customers onboard themselves. Documentation answers questions before they’re asked. The technology is simple enough for one person to maintain.
As your business grows, does it need more of your time or less?
If the answer is more, something in the system needs to change.
Yongfook spent two years burning through his savings on a product nobody was sure about, including him.
What carried him through was the conviction that he’d picked the right problem, and a system built to let one person keep solving it for as long as it took.