How a Solo Founder Built a SaaS by Solving His Own Annoyance

**Lucas** (0:01)
If these conversations are useful for what you're building or running, this is the one to hear. We're talking about the oldest and maybe most reliable play in independent SaaS.
Building software that solves your own problem.

**Luna** (0:15)
The scratch-your-own-itch model. But we're not just rehashing the principle, we're digging into the original case study, Basecamp.

**Lucas** (0:23)
Right, before it was a company, it was a web design firm called 37 Signals. The year is 2003
Jason Fried and his team are juggling client projects, websites for small businesses, and they can't find a project management tool that isn't bloated and terrible. So they build one for themselves.

**Luna** (0:43)
And they named it Basecamp. It launched in February 2004
Within a few months, they had paying customers.

**Lucas** (0:52)
The key detail.
They didn't set out to start a SaaS company. They had a pain point. Every morning, they'd waste time with email threads and spreadsheets just to figure out who was doing what. So they built a to-do list, a message board, a file sharing thing. Basically, the minimum viable product before that term was everywhere.

**Luna** (1:11)
And they charged for it from day one.
No free tier. No freemium. Just a flat fee per project.

**Lucas** (1:19)
That's the part that stands out to me. In 2004, the conventional wisdom was that web software had to be free to attract users. But Fried and his partner, David Heinemeyer Hansen, had a different view.
If it's useful to us, it's useful to other agencies like us, and those agencies have budgets. So they priced it at $49 a month for unlimited projects.

**Luna** (1:42)
Which today sounds cheap, but back then it was a real bet. And within a year, Basecamp was generating more revenue than their web design business.

**Lucas** (1:52)
Exactly. That's the moment they pivoted.
By 2005, 37Signals stopped taking new client work and went all in on Basecamp. They had maybe 10,000 paying customers at that point. No Ventura Capital, no sales team, just a product that solved a real problem for a specific audience.

**Luna** (2:14)
But here's my question, does this still work in 2026?
The SaaS landscape is completely different. There are thousands of project management tools.
Notion, Asana, monday.com, ClickUp, all with massive marketing budgets.

**Lucas** (2:31)
It's harder, no question. But the principle still holds. The difference is that scratch your own itch today often means finding a very narrow underserved niche.
Basecamp succeeded because it was built for small creative teams, agencies, freelancers, small businesses. That's a specific persona.

**Luna** (2:51)
So, the strategy isn't built for everyone who needs project management. It's built for the version of yourself that existed in 2003

**Lucas** (3:00)
Right. And that's what a lot of first-time founders miss. They try to compete on features.
They think they need to have every integration and every view.
But Basecamp's philosophy was the opposite.

**Luna** (3:18)
I remember reading Fried's book Rework, where he talks about constraints as a feature, not a bug. They limited projects to a certain number of to-do lists, limited file sizes, limited the number of users per project.

**Lucas** (3:32)
And that forced the product to be opinionated. It wasn't trying to be everything to everyone. It was saying, this is how we think work should be organized. If that works for you, great.
If not, here's your money back.

**Luna** (3:48)
That confidence came from dogfooding. They were their own customers. Every feature they built was something they needed that week.

**Lucas** (3:56)
There's a specific example from 2006
They added a feature called WriteBoard, a collaborative document editor, because they needed it for client proposals. They didn't do market research. They didn't survey users. They just built what they needed.

**Luna** (4:14)
And then they spun that off into a separate product. WriteBoard was free, I think.

**Lucas** (4:19)
It was, but it drove people to Basecamp.
It was a marketing tool, not a revenue stream. That's another lesson. You can build small free utilities that lead people to your paid product.

**Luna** (4:32)
So the takeaway for a solo founder today, start with your own pain, build something that works for you, and don't be afraid to charge from day one.

**Lucas** (4:41)
But also, pick a niche that has budget.
Small creative agencies in 2004 were spending money on software. If your own pain is in a space where people are used to paying, like business tools, not consumer apps, that's a green flag.

**Luna** (4:56)
Yeah, that's important. A lot of first-time founders try to build for consumers, and consumers expect free. But if you're building for professionals, they're willing to pay for something that saves them time.

**Lucas** (5:09)