There is something wonderfully unimpressive about $2,000.
In Silicon Valley terms, $2,000 in monthly recurring revenue will not get you invited onto a stage. Venture capitalists aren't fighting to get into the round. Tech publications aren't sending reporters. There are no breathless headlines about a company disrupting a trillion-dollar industry. But imagine you are a student. You have already started two businesses that failed. You build another piece of software by yourself, and four months later, 28 strangers are collectively sending you approximately $2,000 every month for permission to use it. Suddenly, $2,000 becomes very interesting.
In June 2026, a solo founder shared essentially this story with Reddit's r/SaaS community. He said his SaaS had reached roughly $2,000 in monthly recurring revenue four months after launch, with 28 paying subscribers. He was still studying and had two failed businesses behind him. The obvious question was how he did it. His answer is interesting because it looks almost nothing like the automated growth machines founders are constantly encouraged to build.
The Launch That Worked — and Failed
The story begins with a sensible decision. Before launching publicly, the founder recruited a small number of beta testers and gave them two weeks to try to break the product. They obliged. Their feedback, according to his account, was brutal, and he spent weeks fixing what they found. By the time the first version was publicly released, many of the problems that might have caused early customers to leave had already been discovered.
Then something encouraging happened. People started showing up. There were signups. There was traffic. People shared the product. For an early-stage founder, this is the moment that feels like validation. You have spent months pushing a boulder uphill and suddenly, however briefly, the boulder seems capable of moving on its own.
There was only one problem: he hadn't built a waitlist. The attention arrived, and there was no effective mechanism for capturing it. People became interested and disappeared. The product had generated something every early startup desperately wants—momentum—but the business hadn't built the infrastructure necessary to preserve that momentum. Instead of simply pushing harder, he rebuilt the launch around a waitlist.
That decision contains the first interesting distribution lesson.
Attention Has a Half-Life
Founders tend to treat attention as an asset. It isn't. Attention is closer to a perishable good. Someone sees your LinkedIn post today and thinks, "That's interesting." Tomorrow they are dealing with a customer complaint. The next day their child is sick. By Friday, they couldn't tell you the name of your company if you offered them money.
The founder's first launch generated attention but didn't adequately convert that attention into an identifiable group of people he could contact again. His waitlist changed that. Interest could now become an email address, an email address could become a conversation, a conversation could become a demonstration, and a demonstration could eventually become a customer.
This is a subtle but important distinction. Traffic isn't distribution. Followers aren't distribution. Impressions aren't distribution. They are raw materials. Distribution requires a mechanism that moves someone from one stage to another. The founder now had the beginnings of one.
He Didn't Start by Selling the Software
For the second version, he began posting on LinkedIn every day. But the interesting part wasn't simply the frequency. Lots of founders post every day and acquire almost no customers.
His content increasingly revolved around useful resources—checklists, templates, guides, and other lead magnets related to the problem his prospective customers were trying to solve. People were asked to comment if they wanted the resource. When someone commented, the founder had something enormously valuable: a signal. The person had raised a hand.
This transformed the psychology of the next interaction. A cold message says, in effect, "I have decided that you might want something from me." A lead magnet reverses the sequence. The prospect first says, "I am interested in this problem." The founder then begins the conversation.
In the Reddit discussion, the founder later described this distinction explicitly. His content was largely about the problem rather than the software itself. If you write about your product, the people who respond may simply be curious about the product. If you write specifically about a painful problem, the people who respond are more likely to be experiencing it.
This is one of those observations that seems obvious after someone says it, yet enormous amounts of startup marketing do precisely the opposite.
The Difference Between an Audience and a Market
Consider the typical founder's LinkedIn post: "We're excited to announce..." You can almost finish the sentence without reading it. We're excited to announce our new platform. We're excited to announce our latest feature. We're excited to announce our integration. We're excited to announce that we've redesigned the dashboard.
The company is speaking about what happened inside the company. But the customer lives outside the company.
The founder in this Reddit case gradually centered his content on the problems his prospective customers were experiencing: frustrations, mistakes, approaches that worked, and useful resources. According to his comments, he began with roughly 500 LinkedIn connections and eventually grew beyond 5,000 organically.
The number itself isn't particularly important. The composition of the audience is. Ten thousand followers who enjoy your opinions are an audience. Five hundred people who repeatedly experience the problem your product solves may be a market. Distribution improves when you learn the difference.
Then He Picked Up the Phone
This is where the story becomes especially interesting.
The internet has spent the last decade making it possible to remove humans from transactions. We have automated email sequences, automated demos, automated onboarding, automated customer support, automated scheduling, and increasingly automated sales conversations. This founder went in the opposite direction.
When a prospect entered the funnel and he could arrange a conversation, he offered a roughly fifteen-minute demonstration. But it wasn't simply a generic tour of the software. He applied the product to the prospect's actual situation. The customer didn't merely watch the founder use the software; the customer effectively began using it with him.
That difference matters. A normal software demo asks the customer to perform a mental translation. Here is Feature A. Here is Feature B. Here is Feature C. Now imagine how these features might somehow improve your life. A personalized demonstration eliminates much of that translation. Here is your problem. Here is your situation. Now let's use the software on it.
By the end of the conversation, the prospect had not merely seen the product. In a sense, they had already begun onboarding.
Then came the offer.
The Funnel Was a Conversation
The founder offered prospects a pre-launch deal at the end of these calls, and he reported that many accepted. His Reddit post says this process eventually produced 28 paying subscribers and roughly $2,000 in monthly recurring revenue.
Think about how strange this funnel looks compared with the traditional SaaS model. There wasn't a clean boundary between marketing, sales, onboarding, and customer success. The LinkedIn post created attention. The lead magnet identified interest. The direct message began qualification. The call served as the sales presentation. The personalized demonstration became onboarding. The onboarding generated product feedback. The conversation revealed objections. The sale validated the offer.
One human interaction was doing the work of half a dozen departments.
For a large company, this would be inefficient. For a company with 28 customers, that may be exactly the point.
The Most Expensive Thing You Can Automate
Startup founders are taught to fear work that doesn't scale. The logic is understandable. If acquiring every customer requires a personal fifteen-minute conversation, what happens when you need 10,000 customers?
But this question contains an assumption: that the process you use to acquire customer number 10,000 should resemble the process you use to acquire customer number ten. It probably shouldn't.
When you have ten customers, your greatest shortage isn't automation. It's information. You don't completely understand why people buy. You don't know which objections occur repeatedly. You don't know which features create the "aha" moment. You may not even know whether you're targeting the right customer.
A live conversation produces all of this information. In the comments, the founder explained that these calls became a kind of sales education. Over time, he became better at tailoring the demonstration to the prospect's exact use case rather than showing every feature. He learned how to pitch the product, how to respond to objections, and which parts of the software actually mattered to the person sitting across from him.
Automating that process too early would not merely automate sales. It would automate away learning.
Then Something Even Stranger Happened
After someone became a customer, the founder added them to a private group. Again, this sounds inefficient. Customers could ask questions directly. The founder could answer in real time. He could see who was actually using the software. Instead of building a sophisticated customer-success system, he effectively placed himself in the middle of the customer experience.
He credited this private group as one of the most effective things he had done for retention.
There is an important caveat here. We have the founder's account, not a controlled experiment. When another Reddit user challenged the neatness of the story—pointing out that after four months it is difficult to know exactly which activities caused the results—the founder acknowledged that he had tried many things and was interpreting the results retrospectively.
That admission makes the story more useful, not less.
Early-stage distribution rarely resembles a laboratory experiment. Twenty-eight customers do not give you enough data to scientifically isolate every variable. You try things. You observe. You notice patterns. Then you put more effort behind the patterns that appear promising. The mistake is not operating with imperfect evidence. The mistake is pretending the evidence is perfect.
Automation at the Edge, Humans at the Center
There is one final detail in the Reddit discussion that makes this case particularly useful. The founder eventually automated some of the LinkedIn direct-message workflow. When someone engaged with the appropriate content, the initial movement into the funnel didn't always require him to manually type every message.
But he kept the calls manual. He kept the onboarding personal.
That gives us a much more sophisticated lesson than "don't automate." Automate the repetitive edges of the system while preserving the human interactions that are still producing valuable information. A lead entering a spreadsheet doesn't necessarily teach you much, so automate it. A prospect explaining why they don't understand your pricing teaches you something, so listen. A calendar invitation doesn't teach you much, so automate it. Watching a customer struggle to use the feature you thought was obvious teaches you something, so watch.
The challenge isn't deciding whether automation is good or bad. The challenge is understanding where learning is occurring.
The Real Distribution System
If we strip away the details, the founder's reported distribution system looked something like this: LinkedIn content attracted people experiencing the problem. Lead magnets encouraged those people to identify themselves. Direct messages converted anonymous engagement into conversations. Personalized demonstrations showed the product solving the prospect's actual problem. Pre-launch offers turned some of those prospects into paying customers. Live onboarding helped customers experience value. A private group maintained a direct relationship after the sale.
It wasn't one channel. It was a chain.
This distinction is critical because founders often ask, "Which channel should I use?" LinkedIn wasn't the strategy. LinkedIn was where the strategy began. The real strategy was the sequence connecting attention to payment and payment to retention.
What $2,000 Can Teach Us
It would be easy to look at this case and conclude that every SaaS founder should start posting lead magnets on LinkedIn. That would be the wrong lesson.
LinkedIn happened to make sense for this founder and his audience. For another company, the equivalent watering hole might be Reddit, YouTube, Google, an industry conference, a Discord server, a trade association, cold email, or a surprisingly obscure online forum.
The deeper lesson is about proximity.
At the beginning, this founder kept himself remarkably close to the customer. He saw who engaged with his content. He talked to prospects. He demonstrated the software himself. He watched people use it. He heard their objections. He helped onboard them. He remained accessible after they paid.
Modern technology encourages founders to construct distance from customers because distance scales beautifully. But distance also hides things. A conversion-rate dashboard can tell you that 8 percent of visitors signed up. It cannot tell you why a particular person hesitated before entering their credit card. Analytics can tell you that someone stopped using your software after three days. They cannot necessarily tell you what disappointed them.
Sometimes the primitive system contains more information than the sophisticated one.
The Distribution Lesson
The founder ended his original account with 28 paying customers and approximately $2,000 in monthly recurring revenue. That is still a tiny company. Whether it ultimately becomes a much larger one is an entirely different question.
But that's precisely what makes the story useful.
Most distribution advice is written from the perspective of companies after they have discovered distribution. We study their SEO engines, sales organizations, affiliate programs, paid acquisition funnels, and viral loops after the machinery is already running. What we rarely see is the awkward period before the machine exists.
Here, the machine began with something almost embarrassingly manual: write something useful, see who responds, talk to them, show them how the product solves their problem, help them use it, and pay close attention to what happens next. Only then do you begin deciding what should be automated.
Perhaps that's the paradox of early-stage distribution. Founders want a machine that acquires customers while they sleep. Eventually, that may be exactly what they should build. But first, they have to stay awake long enough to understand how the machine should work.
Source
This case study is based on a June 2026 post and subsequent discussion in the r/SaaS community titled "My SaaS hit $2k MRR in 4 months. Here's the full breakdown: system, mistakes, and what I'd do again." Revenue, subscriber counts, conversion figures, and descriptions of the founder's strategy are self-reported by the Reddit poster and have not been independently verified.
Original Reddit post:
https://www.reddit.com/r/SaaS/comments/1ujq0ww/my_saas_hit_2k_mrr_in_4_months_heres_the_full/
Go Deeper Into Distribution
Mastering Distribution: How to Get Customers in the AI Era examines the larger question behind stories like this one: how do you systematically discover a repeatable way to get customers?
The book covers finding markets that hurt, positioning, offers, messaging, founder-led sales, content, partnerships, conversion, retention, and eventually turning the distribution methods that work into a competitive advantage.