The Hiring Market Where Developers Are Discovered First: Joe Masilotti's RailsDevs
How RailsDevs, which began with a spreadsheet, connected developer profiles with companies' hiring fees. It examines early demand validation and building in public, the difference between recurring revenue and cumulative revenue, through to the 2025 shutdown of the service.
RailsDevs, created by Joe Masilotti, was a reverse job platform where, instead of companies posting job openings and waiting for applications, developers posted profiles and companies reached out first. It was limited to Ruby on Rails developers, and focused on reducing the hassle for developers of repeatedly searching for work. It is a case of turning a problem in his own tech community into a business, rather than targeting the entire massive hiring market.
Demand Confirmed in a Spreadsheet
The starting point was the irregular requests he experienced while working as an independent developer. When work came in waves, he couldn't handle it, but at other times it was hard to find the next project. His assessment was that existing job sites were centered on full-time roles and therefore not sufficiently helpful for finding freelance or contract work.
What came before the product was a spreadsheet. To connect requests he couldn't take on with other Rails developers, Joe shared with companies a list of acquaintances who had capacity to work. Within a few weeks, two people got work, confirming demand.
The first version was released in 15 days using familiar tools: Ruby on Rails, Tailwind UI, and Heroku. The launch cost was about $300, of which $250 was for buying the domain.
On November 5, 2021, a tweet asking about a hosting problem unexpectedly became the launch catalyst. A Rails community figure who helped with it shared the service, and about 100 people registered profiles in the first week.
About a month later, the first customer asked to subscribe, but there was still no payment screen. Joe sent an invoice himself and received $99, and less than two months passed from idea to first payment.
Gathering Developers and Charging Companies
Developers participated for free, while companies bore the cost. Joe believed that by first gathering developers he could attract hiring companies, and he focused his marketing on the developer job-seeking experience as well.
The developer-first principle was reflected in actual feature decisions. In January 2022, he announced that he had removed hourly rate and salary inputs and the related sorting and display features. He believed this could lead companies to look first for cheaper people rather than the right fit, and that compensation should be set after discussing the scope and complexity of the work. However, because some users argued that public pricing was more transparent, it is more accurate to view this as a decision revealing the platform's direction rather than a universal right answer.
The revenue model evolved toward combining a monthly subscription fee with a hiring-success fee. Under the pricing system introduced in March 2022, it charged $99 per month for hiring freelancers and contract workers and $299 per month for full-time hiring. When a full-time hire was completed, it additionally charged 10% of the developer's first-year salary, and the plan also included handpicked candidate recommendations and priority consultations.
Joe added the fee to align the platform's interests with those of its customers. With subscription fees alone, the longer a company stayed, the more revenue the operator made, but what companies wanted was to hire the right developer quickly and leave. By attaching a separate reward to a successful hire, the operator could also focus on hiring outcomes rather than subscription retention length, he explained.
$4,000 MRR and the Actual Revenue Structure
An Indie Bites interview introduction published on September 13, 2022, described RailsDevs as a business that had surpassed $4,000 in monthly recurring revenue (MRR). This figure represents monthly recurring revenue at the time, and does not mean total monthly revenue including hiring fees or Joe's personal net profit.
In a November 2022 interview, he disclosed results of more than 600 developers, more than 30 successful hires, and almost $150,000 in cumulative revenue over approximately one year after launch. Reported costs were less than $10,000, and he worked without employees, alongside some contract workers. However, these are business figures disclosed by the founder, not data showing his personal take-home income.
In the same interview, he explained that almost 90% of revenue came from hiring-success fees. Therefore, a business with a subscription feature must be distinguished from a business centered on subscription revenue. The key to understanding RailsDevs's significant revenue is not just the number of subscribers, but how many actual hires were completed.
Connecting Public Development to Community Participation
Joe did not start promoting the product after finishing it; instead, he made the development process itself a public activity. He shared work in progress on Twitter and received feedback on questions and ideas in GitHub Discussions. In September 2022, it was noted that his Hotwire Dev newsletter had also surpassed 2,000 subscribers. Seen this way, it matters that the audience for sharing technical knowledge overlapped significantly with the group of developers who needed RailsDevs.
The openness did not stop at source code. RailsDevs aimed to be an 'open startup' that also disclosed business metrics such as revenue and traffic as well as major decisions. Users did not stop at creating a profile; they could offer opinions on what direction the product should take and participate in development.
In March 2023, it also launched a program that paid monetary rewards for open-source contributions. It paid $25 or more depending on difficulty for completed issues or merged code changes. Joe described this as both giving back to the community and a means to help junior developers add real paid work experience to their résumés.
Why the 2025 Shutdown Must Also Be Considered
RailsDevs should not be presented as a success story that is still operating. Joe announced that he was shutting down the service after running it for nearly four years, and the official code repository was also archived on July 28, 2025. In the shutdown announcement, he acknowledged the achievement that dozens of people had gotten jobs, while saying it was time to make room for what came next.
The introduction to a follow-up interview published in 2025 describes RailsDevs' total revenue over its operating period as approximately $250,000, and it discusses changes in market conditions and the decision to shut down the service. This, too, is cumulative revenue, not annual revenue or sale proceeds. The shutdown announcement was not news of a sale, and even after the business ended, the source code remained public.
The lesson from this case is more specific than simply advising people to choose a small market. The key to early commercialization was that he verified demand for connections manually in a community he already knew, and separated the way he gathered developers from the way he charged companies. At the same time, looking together at the structure that depended heavily on hiring outcomes rather than subscription fees and the eventual shutdown reveals that rapid monetization and long-term revenue stability are separate challenges.