Snappa: From 10 Landing Pages for “Twitter Header Maker” to $0 → $62K MRR — a Blueprint for Use-Case SEO

(Yen conversions in this article use an approximate rate of ¥150/$1.)

The growth numbers

Snappa is an online image-creation tool for non-designers, based in Ottawa, Canada. At the time of a MicroConf talk about the business, the co-founders had set $1M ARR (annual recurring revenue of $1 million, about ¥150M) as their next target. What makes this case worth reading isn’t the $62K figure itself, but the path to get there (a pile of failed prior ventures, an audience carried over from a previous project, and the discovery of a keyword strategy out of a stall) nearly all of it laid out in the founder’s own talk.

Three prior ventures — from a $323 app to a traffic asset pulling tens of thousands of visits a day

Co-founder Christopher Gimmer’s account at MicroConf explains why the “fourth” venture, Snappa, sold from its very first week.

The first, ClassmateCatch, was a college dating app. It gathered 1,000 local signups but stalled out due to its geographic constraints. Its lifetime earnings from AdSense: $323.04. The second, BootstrapBay, was a marketplace for Bootstrap themes; it’s where he learned the SEO pattern of targeting search terms like “bootstrap navbar,” “bootstrap modal,” and “bootstrap carousel” for acquisition, and he later sold it to a friend. The third, StockSnap, was a free stock-photo site. A post on Reddit went viral (a real-world application of the so-called Skyscraper Technique), and it grew into a traffic asset pulling tens of thousands of visits a day.

The $2–3K in recurring revenue that showed up in Snappa’s very first week traces back to that StockSnap audience, early on, 90% of Snappa’s new signups came via StockSnap. As for motivation, Gimmer says he “was just looking for a way to quit my job and make a living” (paraphrased), and the idea itself was simple: he “wanted to know whether other people had the same problem I did, not being able to create professional-quality images” (paraphrased). At launch, they started with a simple landing page and signup form built on LeadPages, and also ran promotions through channels like AppSumo and Product Hunt.

A year of stagnation, then finding the winning formula

What’s easy to overlook is that Snappa’s SEO didn’t work from day one. For roughly the first year after launch, they kept up generic content marketing, general-purpose blog posts, and growth flatlined. The turning point came from keyword research in Ahrefs, which uncovered specific use-case searches like “twitter header template” and “facebook header maker.”

That’s what established Snappa’s core strategy. Instead of generic feature-oriented terms like “image creation tool,” they built roughly 10 dedicated landing pages targeting the search terms for specific uses. A page like “The Perfect Twitter Header Size & Best Practices,” for example, answers the searcher’s question head-on while also presenting the product as “the tool built specifically for this task.” Then they built backlinks through guest posting to push these landing pages up the rankings. Users don’t search “I want a design tool”. They search “I want to make a Twitter header.” Exploiting that asymmetry was the engine behind Snappa’s marketing flywheel.

Reading behind the numbers

Use-case landing pages are one of the highest-ROI SEO tactics for small SaaS companies. Searchers for a specific use case have a clear, well-defined problem and convert at a high rate, while difficulty stays low because competitors are all clustered around generic terms. Ten landing pages driving $45K MRR stands alongside Bannerbear’s “the more documentation we wrote, the more we sold” as a textbook example of content-led SaaS growth.

Defining the customer as “anyone but a designer” simplified everything about pricing and features. By dropping pro-level features and focusing on instant, template-driven creation, the amount of development, support, and learning curve stayed small enough for a small team to handle. It’s the same “cut it down” design as Carrd’s feature-restriction strategy.

Dependence on the inbound traffic source was deliberately diluted, then let go of once it no longer mattered. The 90% of signups initially coming via StockSnap fell to 10–15% as the use-case SEO built up, and it was at that point that they sold StockSnap itself under an NDA. Rather than leaving the growth lifeline permanently parked on a single external asset, they shifted it over to their own owned search asset, then cashed it out, resolving the dependency and monetizing the asset in a single move.

How the team evolved

The company was founded by two friends, Gimmer and co-founder Mark. Pushed by feature requests, they hired their first developer 4–5 months after launch, then added a marketing hire. At the time of the talk, the full-time team was four people plus a freelance template designer. Running $62K MRR on that headcount is the direct result of the “cut it down” design.

What didn’t work

This case tends to get cited as a straightforward success story, but the first half of the talk is a litany of failures. ClassmateCatch misread a structural constraint (geography) and topped out at $323. Snappa itself stagnated for its first year on generic content. The use-case SEO strategy that became the winning formula wasn’t part of the original design but surfaced from digging back through keyword data during that stall. And the strategy itself has limits: given how much weight rests on a single channel, search, it’s directly exposed to algorithm updates, and the use-case-landing-page approach is imitable by competitors, with the main moat being the backlinks and domain trust built up early.

Conditions for replication

The procedure is the part anyone can borrow: (1) enumerate use cases (Twitter header, Facebook cover, YouTube thumbnail…), (2) check the search volume and competitive weakness for each use case, (3) build a landing page for each use case designed to read as “the tool built specifically for this task,” and (4) drive backlinks to those pages through guest posts on relevant outlets. No special budget or name recognition is required. What’s needed is just execution. This case is cited repeatedly in English-language circles as a teaching example that the value of a strategy lies not in its originality, but in how completely it’s executed.

There’s also plenty of room to transplant this into Japanese. Use-case searches like “how to make an X header” or “create a YouTube thumbnail” exist in massive volume in Japanese too, but few domestic SaaS companies are seriously running a full lineup of use-case landing pages. The language barrier has, if anything, extended the shelf life of this playbook in Japan.

The initial velocity, on the other hand, travels far less well. The $2–4K that materialized from the first month rests on the email list and traffic asset from the previous project, StockSnap. Snappa wasn’t launched from zero. Build the audience with the first project, monetize with the second. This sequencing shows up as a common, replicable pattern in individual founders’ work, echoed in both Ben Stokes’s portfolio strategy and Levels’s volume approach. Copy the numbers without this “prior step,” and you’ll badly misjudge how fast the initial traction should be.

Related cases

• Bannerbear — a contrasting API-based approach in the same image space
• Carrd — the same “cutting things down” approach that made solo operation possible