GoRails: Stacking $19/Month Screencasts for Seven Years to $60,000 MRR as a One-Person Business

Online course businesses are usually talked about through big launches — six figures in the first week. GoRails sits at the opposite end. It is a learning site that methodically explains how to use Ruby on Rails through screen recordings, and in a November 2021 interview with Failory, founder Chris Oliver said GoRails was “doing $60,000 in MRR, which is very good as a single-person business.” Getting there took seven years.

At the time of the interview he was 32, based in St. Louis, Missouri. Before this he worked full-time as a consultant for startups. He had originally bought the domain GoRails.com simply as a place to publish his own Rails notes. When he noticed the site was picking up traffic, he chose a specific order of operations: rather than building a product from zero as someone nobody knew, he would “sell to an audience I already had.”

That choice decided the outcome. He quit consulting on January 1, 2014 to go full-time, but his savings only covered about nine months. Starting from zero readers, nine months would very likely not have been enough.

Numbers and timeline

Failory places the company in the $25K–$100K monthly revenue band. $60,000 MRR sits near the middle of that range.

Why “publish free, every week” worked

His first move was to package his consulting experience into paid material. It didn’t work. He explains the reason in one line: nobody knew who he was.

So he changed course and started publishing every new video for free first. The goal wasn’t revenue but accumulated trust. There is a structural reason this matters. For developer education, the buying decision comes down almost entirely to a personal fit question, does this person’s way of explaining things work for me? Fit cannot be conveyed in a sales page. You have to show the actual teaching. Free publishing wasn’t a marketing expense so much as a fitting room for the product.

And it was that fitting room that made the Hacker News day pay off. The person who submitted it wasn’t him. The developers who arrived didn’t land on a pitch page for a paid course. They landed on free explanatory videos, which is precisely why more than 600 of them converted into email signups. The list he captured that day became the foundation for what he calls “a pretty important piece of the business”: the newsletter.

Whether a spike converts into a business depends entirely on what is sitting there when the spike arrives. In GoRails’ case, what was sitting there was free video and an email field. That pattern of stocking free inventory in advance also runs through the paid-course operator who had eight misses before three hits: the inventory you build before the win is what gives the business its durability.

What was inefficient — the three-product breakdown

Oliver runs two other products besides GoRails, and his opposite assessments of them are the most practically useful part of this case.

• Hatchbox.io (Rails hosting): very high support burden, low return relative to effort
• JumpstartRails.com (a template for building SaaS): the best return relative to effort

Even when both sell to the same Rails developers, hosting means taking custody of infrastructure, and incident response and one-off support scale without limit. A code template, once built, costs almost nothing to duplicate and lets you bound the support surface. In a one-person business, you have to evaluate products by how much of your own time they eat before you evaluate gross margin, otherwise growth in revenue is the thing that stops your hands.

His biggest regret, by his own account, is not hiring sooner, along with not paying himself a salary for two years. He describes the latter as “super hard” and discouraging for anyone thinking of starting. Long stretches of unpaid work often get told as inspirational stories. The person who lived it does not tell it that way.

Seven years of run-up, and a framework that ships a new version every year

Part of why the monthly fee held is the nature of Ruby on Rails as a subject: the framework ships new versions every year, which makes existing explanations go stale. That is a production burden, but it is also what creates a reason to keep paying monthly instead of buying once. A one-time-purchase product would find that recurring revenue much harder to hold. In Japan, designs centered on one-time sales, like the operator who published nine Udemy courses, are common, and whether you can move to recurring depends heavily on how fast your subject changes.

The other part is time. A seven-year run-up is not available to most people, and the first two years were unpaid. What this case shows is not that stacking output always produces $60,000 MRR, but something closer to this: in businesses where accumulation compounds, you don’t have to force acceleration along the way. Nobody engineered the 600 Hacker News signups. They came after years of weekly videos, when someone else decided to post the link.

The figures here rest on a November 2021 interview, and MRR since then has not been disclosed. What the current pricing page tells us is the shape of the thing today: $19 a month for a personal plan, 650+ screencasts, a Discord with over 6,000 developers. If you assume the same $19 price back then, the subscriber count would land somewhere around 3,000, but the price at the time of the interview was never published, so treat that only as a rough order of magnitude.