From 5 Projects to 51 Per Year: How an Architecture Practice Grows

In 2010, F9 Productions’ project database records five projects. In 2024, it records 51.

Architecture firms do not usually grow in straight lines, and ours certainly did not. Looking across 16 years of project history has given us a useful way to think about what growing an architecture practice actually means.

Spoiler: it is not simply getting more projects.

Growth Is Lumpy

That is not a hockey stick. It is a mountain range.

There were periods of growth followed by contraction, and years that looked like breakthroughs were followed by quieter years. Eventually a new baseline emerged, but not before plenty of volatility.

That matters because firms often mistake a great year for permanent growth. They are not the same thing. Growth becomes real when the practice develops the capacity to perform at the new level repeatedly.

Lesson 1: Five Projects Can Be Managed With Memory. Fifty-One Cannot.

Five projects can be managed largely through memory. Fifty-one require something stronger.

As F9 grew, the firm also grew in the way it works. Long-term employees developed deep knowledge of our projects, standards, clients, and expectations. At the same time, our systems continued to evolve around that experience, giving the team better ways to organize information, coordinate decisions, and maintain consistency across a much larger number of projects.

Communication became just as important. Regular team coordination, clear handoffs, shared standards, and open discussion allow information to move through the office instead of staying with one person.

The result is that growth has not simply meant taking on more projects. It has meant building a more experienced team, better systems, and stronger communication so the firm can handle more work without losing the knowledge and attention that made the smaller practice successful.

Lesson 2: Systems Are Not the Enemy of Creativity

Architects can be suspicious of standardization, and understandably so. Nobody wants architecture to become an assembly line.

But there is an enormous difference between standardizing the architecture and standardizing the process around the architecture. File organization, quality-control procedures, drawing conventions, project setup, and communication expectations can all be standardized without making every building the same.

The point of those systems is not to limit creativity. It is to stop wasting creative energy solving administrative problems that have already been solved.

Fifty-one unique projects require more system, not less.

Lesson 3: Growth Requires a Broader Practice

During F9’s first nine years represented in the database, from 2010 through 2018, the firm recorded 68 projects. Of those, 52 were single-family residential, making residential architecture overwhelmingly the center of gravity.

From 2019 through 2025, the database records 251 projects. Single-family residential remained the largest category with 139 projects, but the overall portfolio became significantly broader. The later period includes 56 commercial projects, along with ADUs, accessory structures, multifamily buildings, mixed-use work, industrial projects, and other specialized building types.

That diversification matters because a practice becomes more resilient when one kind of project is not responsible for carrying the entire firm. It also becomes more intellectually interesting. Different building types force different kinds of thinking.

Lesson 4: More Projects Change the Kind of Problems You Solve

Early growth is often about getting work. Later growth becomes about controlling work.

Can the firm maintain quality and coordinate deadlines? Can people make decisions without everything bottlenecking at the top? Can knowledge transfer from one person to another? Can clients still feel like their project matters when there are dozens of other projects active?

These are design-business problems. The architecture profession sometimes treats them as secondary because they are not visible in the finished building, but they are not secondary. They determine whether the finished building gets there intact.

Lesson 5: Growth Changes the Firm’s Relationship With Existing Buildings

There is another shift hidden in the project history.

During the 2010 through 2018 period, the database skews toward new construction. During the much larger 2019 through 2025 period, existing-building projects become the majority.

That suggests something deeper than simply “we got busier.” The practice became more useful in more situations.

The work expanded into tenant improvements, additions, remodels, conversions, repairs, commercial interiors, and other projects where the architect is solving within an existing framework. That kind of diversification usually comes from accumulating confidence.

The firm becomes less dependent on one idealized version of what an architecture project should look like.

Lesson 6: Growth Creates a Knowledge Problem

Across 51 projects in a single year, a firm learns an enormous amount: permit comments, structural details, client decisions, contractor questions, budget lessons, code interpretations, scheduling lessons, and which products and details perform well in the field.

At F9, we have worked to make sure that knowledge does not stay with only the person who experienced it. One of the most important ways we do that is through our daily all-hands meeting. Employees take turns leading the discussion and sharing a project they are working on, a problem they are trying to solve, or a process improvement they have made.

That daily exchange keeps the entire team up to date on what is happening across the office and gives everyone a chance to contribute. A lesson learned on one project can quickly influence another. A difficult permit comment, construction issue, or better way of doing something does not have to stay isolated within one project team.

Combined with long-term employees, shared standards, and systems that continue to evolve, that communication helps turn individual experience into firm-wide knowledge. Each project adds more than another building to the portfolio. It adds to the experience of the entire practice.

Lesson 7: The Goal Is Not Maximum Volume

The number 51 sounds impressive, and it would be easy to assume the objective should be 60, then 75, then 100. We do not think that is the right lesson.

Project count is only one measure. Fifty excellent projects are better than seventy chaotic ones, and a larger backlog is not automatically a healthier firm. More revenue does not matter if quality, culture, client experience, or profitability deteriorate underneath it.

The real question is whether the practice is getting better at handling the opportunities it chooses to accept. Growth for its own sake eventually becomes a burden. Capability is the better goal.

Lesson 8: Every New Baseline Once Felt Impossible

Five projects felt like a practice at one point. Then fifteen did. Then thirty. Eventually, a year with more than fifty projects became part of the firm’s history.

That progression is useful because the next stage of growth almost always looks unrealistic from the perspective of the current one. The answer is rarely to suddenly work twice as hard. The answer is to change the system.

That means delegating differently, documenting differently, communicating differently, training differently, and choosing differently. The firm that can handle the next level cannot operate exactly like the firm that handled the previous one.

What the Numbers Actually Mean

We are glad F9 grew from five recorded projects in 2010 to 51 in 2024, but the number itself is not the achievement. The achievement is everything the practice had to become capable of doing between those two numbers.

That meant more project types, more coordination, more decisions, more clients, more jurisdictions, and more opportunities for something to go wrong. Ideally, it also meant more knowledge about how to prevent those problems the next time.

That is how an architecture practice grows. Not in a straight line, not without difficult years, and definitely not by simply doing more of what worked when there were only five projects.