8 Months at $0, 7 Failures, 2 Pivots: Bannerbear's Full Road to $10K MRR

(Yen figures below are approximate conversions at ¥150/USD.)

The Full MRR Timeline (Self-Published)

Period	MRR	Phase
Jan–Aug 2019	$0	The “12 startups in 12 months” challenge. Builds 7 products — none with a revenue model
Sep–Dec 2019	$400	Focuses on Previewmojo, an OG-image generation tool
Jan–Feb 2020	$472	Rebrands to Bannerbear. Traffic grows but revenue doesn’t follow
Mar–Apr 2020	$488	Launches the REST API. Some early customers churn over the change in direction
May–Oct 2020	$6,109	The “7 days code, 7 days marketing” cycle. Breaks through $1K→$2K→$3K→$6K in succession
Nov 2020–Jan 2021	$10,455 (≈¥1.57M)	Repositions around “automation” and “scale”

Bannerbear has since reportedly grown to $50K MRR and roughly $1M ARR (Starter Story).

What the Business Is

Bannerbear is a SaaS that auto-generates social media images, e-commerce banners, OG images and more via API. It integrates with Zapier, Airtable and WordPress to automate image production in marketing workflows. Founder Jon Yongfook went independent with two years of savings set aside, and spent the first year in trial and error.

Three Plateaus, and How He Escaped Each

Plateau 1: He built 7 products with no revenue model (2019). The public challenge of building 12 startups in 12 months attracted attention, but MRR stayed at $0 for 8 months. His own verdict: “none of them gave anyone a reason to pay.” Being able to build and designing something worth paying for are different skills.

Plateau 2: He had picked a problem that didn’t hurt (the $400 wall). Previewmojo (automatic OG-image generation) was handy, but it “wasn’t a hair-on-fire problem.” In a niche where nobody is desperately struggling, neither price nor customer count will grow. At the time he had also written an article arguing “don’t charge $9/month for SaaS” — he had lived through the quagmire of underpricing too.

Plateau 3: The rebrand only grew traffic ($472). Refreshing the look and brand increased site visits, but revenue barely moved. The turning point was redesigning the product itself — the shift from standalone tool to API. Early customers who came for OG images churned in the process. A correct pivot comes with the pain of losing existing customers.

Operating in the Growth Phase — “7 Days Code, 7 Days Marketing”

The way he worked during the climb from $488 to $6,109 was simple and clear.

Alternate between development and marketing week by week, structurally preventing a skew toward either
Write large volumes of content and API documentation. “The more documentation I wrote, the more conversion went up”
A weekly newsletter, Product Hunt launches, and public progress updates on Indie Hackers

The final leap ($6K→$10K) came not from features but from positioning. He sorted customers into two Jobs to Be Done — “people who want automation via Zapier” and “people who want to hit the API directly for high-volume generation” — and rebuilt pricing plans, tutorials and site structure around the words “Automate” and “Scale.” Articulating whose job the product does, rather than what to build, is what broke the $10K wall.

Lessons and Analysis

“It’s the target you should niche down, not the problem” — the biggest discovery in this case. Previewmojo narrowed the problem so far that the market disappeared. Bannerbear grew by selling a broad capability — automated image generation — to a narrow target: businesses that want to automate repetitive marketing work. It is the mirror image of the lesson from MENTA, which took off by going from “advice on anything” to “programming only”.

The 8 months at $0 weren’t wasted — they were the denominator. The 7 failures, as a public challenge, generated attention and followers that became Bannerbear’s early customers and distribution base. The same law of attempts as Levels’ “4 out of 70” and Irie’s “product number 30” — compressed here into a single year.

He used the calendar to forcibly correct the developer’s tendency to overbuild. “7 days code, 7 days marketing” is a superb way to secure marketing time through structure rather than willpower. Given that the single biggest reason indie projects fail is “building without selling,” this is the most portable practice in the whole story.

Documentation is the strongest salesperson an API SaaS can have. “The more I wrote, the more I sold” shows that for developer products, content can substitute for sales costs. As an asset that gets picked up by both search and AI search, it is even more effective today.

If You Tried This Yourself

Easy to replicate: “7 days code, 7 days marketing,” “design the reason to pay first,” and “reposition around JTBD” are all executable at an individual scale
Limits: the two years of savings, and the attention earned from the public challenge, both fueled the early acceleration. The $10K→$50K stretch also relies on secondary sources (Starter Story) and can’t be verified in detail