KEY TAKEAWAYS
- ✓APIs are excellent solo founder products. Once built, they require minimal customer support because developers are self-sufficient users.
- ✓Build in public creates accountability and attracts the right customers. Developers respect transparency.
- ✓Don't underestimate the value of patience. Bannerbear took 4+ years to reach $50K MRR, but the growth compounded steadily.
Hello! Who are you and what are you working on?
Jon Yongfook has built companies on three continents. He's Malaysian-Japanese, grew up between countries, and has founded startups in both Southeast Asia and Japan. Before Bannerbear, he ran a social analytics startup and worked on various projects across the tech ecosystem. By the time he started Bannerbear in 2019, he had a clear framework for what kind of business he wanted: bootstrapped, solo-friendly, and built on recurring revenue.
The idea for Bannerbear came from a recurring pain point Jon encountered across multiple projects. Whenever a company needed to generate images dynamically, such as social media banners, event tickets, open graph images, or personalized marketing materials, the process was painful. Either you hired a designer to create each variation manually, or you wrote custom code to generate images programmatically using libraries like ImageMagick, which was complex and fragile.
Jon built Bannerbear as an API that lets developers auto-generate images and videos from templates. You create a design template once, specifying where the text, images, and dynamic elements go, and then use the API to generate unlimited variations by passing in different data. The use cases were broad: e-commerce stores generating product images at scale, media companies creating social sharing images for articles, event platforms producing personalized ticket graphics, and marketing teams generating localized ad creatives.
The first version took a few weeks to build. Jon launched on Product Hunt in 2019 and received a modest but encouraging response. The initial customers were developers at small companies who had been dealing with the image generation problem manually. They immediately saw the value of an API that handled it automatically.
Growth in the first year was slow by most SaaS standards. Jon was building the product, handling support, writing documentation, and creating content all by himself. Monthly revenue crawled from a few hundred dollars to a few thousand. But the retention numbers were strong. Once developers integrated Bannerbear into their workflow, they rarely churned. The API became infrastructure, and switching costs were high because it would mean rewriting the integration code and redesigning all the templates.
Jon's growth strategy centered on two channels: SEO and developer community engagement. He wrote detailed blog posts about image generation use cases, API comparisons, and technical tutorials. These posts ranked well for searches from developers looking for image generation solutions. He also engaged actively in developer communities on Twitter, Reddit, and Hacker News, sharing progress updates and answering questions about Bannerbear's capabilities.
The build-in-public approach on Twitter was particularly effective. Jon posted monthly revenue updates, shared feature releases, and discussed strategic decisions openly. His transparency attracted other developers who respected the genuine, no-hype approach. Many of his early customers first discovered Bannerbear through Jon's Twitter account rather than through search or Product Hunt.
Revenue grew steadily but not dramatically. It took over two years to reach $20K MRR, then another two years to reach $50K MRR. This patience is unusual in the startup world, where founders often panic if they're not growing at 20 percent month over month. But Jon understood that API products in a niche market follow a different growth curve. Each new customer represents a permanent integration, and revenue compounds through a combination of new customers and existing customers increasing their usage as their businesses grow.
The solo operation is sustainable because API products are uniquely suited to one-person companies. Developers are self-sufficient users who read documentation, debug their own integrations, and rarely need hand-holding. The support volume is a fraction of what a consumer app or a less technical B2B product would generate. Jon handles most support through documentation improvements and occasional email responses, keeping his weekly support time under 5 hours.
Jon expanded the product over time to include video generation, which opened up new use cases like auto-generating social media video content, personalized video messages, and dynamic video ads. Each new capability attracted a slightly different customer segment and increased the average revenue per account.
The biggest mistake Jon made was not investing in paid acquisition earlier. For the first three years, all growth was organic through SEO, social media, and word of mouth. While these channels are efficient and sustainable, they're slow. When Jon eventually experimented with Google Ads targeting specific developer search terms, the ROI was strong. Developers searching for "auto-generate images API" had high intent and converted well. Paid acquisition could have accelerated the early growth curve significantly.
Bannerbear continues to grow at around $50K MRR with Jon as the sole full-time team member. He occasionally works with freelance developers for specific features but has no full-time employees. The business generates enough profit for Jon to live comfortably in Japan and work on his own terms. He's in no rush to sell, raise money, or hire a team. The goal was always to build a sustainable, profitable business that provides freedom and independence, and by that measure, Bannerbear is a complete success.