How a Solo SaaS Founder Built a Business by Selling to Architects

**Lucas** (0:01)
So, there's this story I've been digging into about a solo founder named David who built a project management tool specifically for architecture firms. Not architects in the sense of software architects, I mean actual building architects, the people designing hospitals and office towers.

**Luna** (0:17)
Okay, that's a very specific vertical. How did he even land on that?

**Lucas** (0:23)
David was working as a freelance developer, and one of his clients was a small architecture practice in Austin, maybe 10 people. He kept hearing them complain about how generic project management tools like Asana or Trello didn't fit how they worked.

**Luna** (0:38)
What was different about their workflow?

**Lucas** (0:40)
For one, they think in phases, schematic design, design development, construction documents, bidding, administration. Each phase has its own timeline, deliverables, and approval chains. Off-the-shelf tools treat every project as a linear to-do list, but architecture projects have parallel streams that loop back on each other.
David built a prototype that mirrored their actual process. He showed it to the client, they loved it, and three other firms in Austin heard about it and asked for access. That was his validation.

**Luna** (1:14)
So he fell into it by accident, but then he had to decide, stay broad or go all in on architects.

**Lucas** (1:21)
Exactly, and he made a very deliberate choice to go vertical. He looked at the market size.
There are roughly 110,000 architecture firms in the US, the vast majority with fewer than 10 employees. Most of them are underserved by existing software. He figured if he could capture even half a percent of that market at 50 bucks a month per seat, that's a sustainable business.

**Luna** (1:46)
Half a percent of 110,000 firms is 550 firms. At $50 per seat, let's say five seats average, that's about 1.65 million in annual recurring revenue.

**Lucas** (2:00)
You did the math quickly, and that's before upselling larger firms. But the real insight was distribution. Because these firms cluster, they share industry forums, they go to the same AIA conferences, they recommend tools to each other.
One happy firm can bring in five more.

**Luna** (2:19)
Right? That network effect within a niche is powerful. But selling to architects isn't like selling to engineers or marketers.
How did he get his first paying customers?

**Lucas** (2:30)
He did something that sounds almost too simple.
He went to the American Institute of Architects' local chapter meetings in Austin. Just showed up, talked to people, asked about their pain points. He didn't pitch his tool initially. He just listened.

**Luna** (2:45)
That's the classic sell what they need, not what you built approach.

**Lucas** (2:50)
Exactly. After a few meetings, he had a list of features he'd never thought of.
The ability to attach large CAD files directly to tasks, a timeline view that maps to the phases I mentioned, and automatic reminders for permit deadlines. He built those into version 2 and then asked three firms to beta test it for free.

**Luna** (3:10)
And those beta testers became his first evangelists?

**Lucas** (3:14)
They did. After three months, he had 12 firms on board, each paying $50 per seat. His monthly recurring revenue hit about $3,000.
Not huge, but it was growing month over month without any paid ads.

**Luna** (3:30)
So he's at the stage where he has product market fit in a very narrow niche. What does he do next?

**Lucas** (3:37)
That's the interesting tension.
He could try to expand into adjacent verticals, engineering firms, construction managers, or double down on architects and try to become the default tool for the entire industry. He chose the latter.

**Luna** (3:51)
And that feels risky because you're betting your entire business on one niche.

**Lucas** (3:57)
It is risky, but there's a counter argument. By being the specialist, he can charge more and face less competition.
A general project management tool can't afford to tailor its product to architecture firms because the market is too small for them. For David, it's the whole market.

**Luna** (4:15)
What has he done to solidify that position?

**Lucas** (4:18)
He started publishing content specifically for architects, blog posts about improving project profitability, a podcast interviewing firm owners about their workflows. He also integrated with software architects already used like Revit and AutoCAD.
That integration alone became a moat.

**Luna** (4:37)
So, he's not just a tool. He's becoming part of their ecosystem.

**Lucas** (4:42)
Right. And now, about 18 months in, he's at 53 firms and roughly $15,000 in monthly recurring revenue. He's still solo, still bootstrapped, and he's profitable.

**Luna** (4:54)
That's impressive. But there's a ceiling. 110,000 firms is the total addressable market, and he'll eventually saturate that niche.

**Lucas** (5:04)