Bingo Card Creator: What Patrick McKenzie's Famously Boring Teacher Software Still Teaches About Long-Tail SEO and Niche Education Products

Somewhere around 2006, a young software engineer living in Ogaki, Japan, sat down and built a desktop application that generated bingo cards. Not medical imaging software. Not a social network. Bingo cards. The kind elementary school teachers print out for vocabulary review on Friday afternoons. That engineer was Patrick McKenzie, known online as "patio11," and the product was Bingo Card Creator. Over the following years, McKenzie would document its growth, plateaus, pricing experiments, and eventual sale in extraordinary detail on his blog and across forum posts, creating one of the most studied case studies in the bootstrapper canon.

The product itself was never exciting. That was the point. And the lessons it generated remain some of the most practically useful blueprints for anyone building a niche software product, an education tool, or a side project they hope to turn into real revenue.

Spotlight

Picture a teacher in suburban Ohio, searching Google at 9 PM on a Sunday night. She types "Halloween bingo cards for second graders." She needs something printable, customizable, ready by Monday morning. She doesn't want to learn Photoshop. She doesn't want to browse Pinterest for an hour. She wants to click, type her word list, hit print, and go to bed.

That teacher was McKenzie's entire market. Not edtech VCs. Not school district procurement officers. Not curriculum designers. One specific person, with one specific problem, at one specific moment in their week.

McKenzie, who was working as a salaryman at a Japanese company at the time, built Bingo Card Creator as a side project. He wrote extensively about the experience on his personal blog and in detailed "annual review" posts that tracked revenue, traffic sources, conversion rates, and strategic decisions with a level of transparency that was rare in the mid-2000s and remains uncommon today. Those posts became required reading in communities like Hacker News, the Microconf conference circuit, and indie hacker forums. McKenzie eventually moved on to much larger projects, including co-founding Starfighter and later joining Stripe. But Bingo Card Creator remained the proof-of-concept that a single developer, working part-time on something genuinely mundane, could build a sustainable software business.

He didn't raise venture funding. He didn't have a co-founder. He had a boring product, a deep understanding of how teachers search Google, and the patience to write hundreds of pages optimized for the exact phrases those teachers typed.

The Strategy

McKenzie's strategic insight was deceptively simple, and it's worth unpacking because the simplicity is what makes it powerful.

He chose a market where the buyer had almost zero price sensitivity relative to the time saved. A teacher who needs bingo cards for tomorrow's class isn't comparison-shopping SaaS tools. She's solving an urgent, low-stakes problem. The willingness to pay even a small amount, rather than spend another 45 minutes on a manual alternative, was the entire business model.

This is a classic example of what the indie business community now calls a "boring business." Nothing more.

The positioning decision was equally deliberate. McKenzie didn't build "a party game generator" or "a classroom activity platform." He built a bingo card creator. One noun, one verb, one use case. This extreme specificity meant he could own every long-tail search query related to that activity. And there were hundreds of them. "Thanksgiving bingo cards for kindergarten." "Sight words bingo." "Baby shower bingo printable." Each one represented a landing page opportunity, and McKenzie built pages for as many of them as he could.

This is the long-tail SEO strategy that made the product viable, and it's the part of the story that gets cited most often. Rather than competing for broad, high-volume keywords where he'd be crushed by larger sites, McKenzie targeted the long, specific queries that individually attracted modest traffic but collectively added up to a real audience. Each page was crafted to match the exact intent behind the search. A teacher looking for "Christmas bingo cards" landed on a page about Christmas bingo cards, not a generic homepage. The relevance signal was strong. Google rewarded it.

What McKenzie chose not to do is just as instructive. He didn't build a mobile app. He didn't chase virality. He didn't add collaboration features, classroom management tools, or anything that would have pulled the product toward the broader edtech market. Every feature decision was filtered through one question: does this help a teacher make bingo cards faster? If not, it didn't ship.

McKenzie also wrote extensively about his pricing experiments. He started with a low price point and raised it over time, documenting what happened to conversion rates at each tier. His broader lesson, which he shared across blog posts and conference talks, was that most small software creators undercharge dramatically. Teachers, he observed, weren't evaluating his product against free alternatives on a feature-by-feature basis. They were evaluating it against their own time, and their time was worth more than the cost of a license.

McKenzie's approach mirrors what ecologists call niche construction. He didn't just discover a habitat where his product could survive. He actively built one, page by page, keyword by keyword, creating an environment so specifically tailored to his product that competitors would need to replicate not just the software but the entire content infrastructure to displace him. The bingo card generator itself was simple enough that anyone could clone it in a weekend. The hundreds of SEO-optimized landing pages, the domain authority accumulated over years, and the deep understanding of teacher search behavior were the actual moat.

He also applied direct-response copywriting principles to his landing pages and calls to action, writing about A/B testing headlines, button text, and page layouts. The discipline of measuring what actually drove conversions, rather than guessing, compounded over time. Small improvements to conversion rate on a page that receives steady organic traffic produce gains that are effectively permanent.

The Playbook

Here are concrete takeaways from McKenzie's approach that a solo founder or small team can apply right now.

1. Pick a customer, not a category. McKenzie didn't target "education." He targeted a specific person (elementary school teacher) with a specific task (making bingo cards) at a specific moment (Sunday night before class). The narrower your customer definition, the easier every downstream decision becomes: what to build, what to write, where to show up.

2. Build your SEO strategy around long-tail intent pages. Don't write five blog posts and hope for the best. Identify every variation of how your target customer searches for your product, then create a dedicated page for each one. Each page should match the searcher's intent precisely. This is labor-intensive, but it compounds. The pages keep working for years.

3. Charge more than you think you should. If your product saves someone time or solves an urgent problem, the buyer is comparing your price to the cost of their own frustration. Not to a competitor's feature list. Test higher price points. McKenzie wrote publicly about the revenue impact of raising his prices, and the results consistently surprised him.

4. Say no to feature creep. Every feature you add is a feature you maintain. McKenzie kept Bingo Card Creator narrowly focused for years, resisting the temptation to expand into adjacent use cases. The product stayed simple, which meant support costs stayed low and the core experience stayed reliable.

5. Document everything publicly. McKenzie's willingness to share revenue numbers, strategic decisions, and even mistakes built an enormous amount of credibility and goodwill in the developer community. That reputation opened doors to consulting work, speaking invitations, and eventually a role at Stripe. Your side project's most valuable output might not be revenue. It might be the story you tell about building it.

6. Plan your exit from day one. Bingo Card Creator was eventually sold. McKenzie didn't cling to it forever. He recognized when the product had plateaued and when his time was better spent elsewhere. If you're building a side project, think early about what a successful exit looks like, whether that's a sale, a graceful wind-down, or a transition to passive maintenance.

Under the Hood

Bingo Card Creator started as a desktop Java application before transitioning to a web-based product. McKenzie later rebuilt parts of the stack using Ruby on Rails, which he wrote about on his blog. The technical complexity of the product itself was genuinely low. Generating a grid of randomized words and rendering it as a printable PDF is not a hard computer science problem.

That's precisely what makes this case study interesting from a technical perspective. The defensibility was never in the code. It was in the distribution.

McKenzie's real technical investment was in the content and SEO infrastructure: the templating system for generating landing pages at scale, the analytics pipeline for tracking which pages converted, and the A/B testing setup for optimizing copy and pricing. These aren't glamorous engineering challenges, but they're the ones that actually drove revenue.

The unit economics of a product like this are favorable in ways that more complex SaaS tools can't match. There's minimal infrastructure cost (generating PDFs isn't resource-intensive), near-zero support burden for a well-designed self-service product, and the content-driven acquisition model means customer acquisition cost approaches zero once the pages are indexed.

The survivorship bias caveat. McKenzie's story is cited constantly, and it deserves to be. But it's worth asking: why did he succeed where presumably many others, building similar simple tools for niche audiences, did not?

A few factors stand out. First, McKenzie is an exceptionally clear writer and thinker. His ability to articulate strategy, write compelling landing page copy, and communicate with his audience was a genuine competitive advantage, not just a nice-to-have. Many developers can build a bingo card generator. Far fewer can write the landing page that convinces a tired teacher to pull out her credit card.

Second, timing mattered. McKenzie started building long-tail SEO content during a period when Google's algorithm was arguably more receptive to this strategy than it is in 2026. The search landscape has shifted significantly. Google's own AI-generated answers, increased competition for even niche queries, and periodic algorithm updates have all made long-tail content strategies harder to execute. The principle still works, but the execution requires more sophistication and higher content quality than it did in the mid-2000s.

Third, persistence. McKenzie worked on Bingo Card Creator for years, making incremental improvements to pages, prices, and conversion flows. Most side project builders abandon their products within months. The compounding effects of SEO and iterative optimization only kick in if you stick around long enough to see them.

There's also a counter-argument worth acknowledging. In 2026, the same long-tail content strategy McKenzie pioneered is being supercharged (and commoditized) by generative AI tools that can produce landing pages at massive scale. The underlying principle, match your content to specific search intent, remains sound. But the barrier to entry for creating that content has dropped dramatically. A founder applying this playbook today needs to think carefully about what differentiates their pages beyond just existing. Original data, genuine expertise, and community trust are harder to replicate than templated landing pages, regardless of whether a human or an AI writes them.

What This Means for Your Build

McKenzie's story is a reminder that the most valuable software products aren't always the most technically impressive ones. Sometimes the best thing you can build is something simple that solves a specific problem for a specific person, and then make sure that person can find it.

If you're a solo founder or a small team sitting on an idea for a niche tool, an education product, or a "boring" utility that solves a real problem, the playbook is available. Pick your customer. Build the minimum product that serves them. Create content that matches how they search. Price it based on the value of their time, not the complexity of your code.

At Foxxception, we help bootstrapped founders and small teams move from idea to working product fast. Whether you need a functional MVP, a web app with a landing page strategy baked in, or just a technical partner who understands that boring businesses can be great businesses, we're here to build with you. Check out our app portfolio to see what focused, practical product development looks like.

The most boring product in your idea backlog might be the one worth building first.

Sources

• Bingo Card Creator - Patrick McKenzie's original product site
• Patrick McKenzie's personal blog (kalzumeus.com) - source for his annual revenue reviews, pricing experiments, A/B testing write-ups, and strategic commentary referenced throughout this article
• McKenzie's extensive public writing and conference talks (including Microconf presentations) provided the foundational details about his SEO strategy, customer positioning, and pricing philosophy discussed here