Do You Actually Know If You're Making Money?
Your firm is busy. Projects are coming in, your team is billing hours, invoices are going out, and revenue may even be higher than it was last year. From the outside, that can feel like success. But does higher revenue actually mean your firm is making more money? Not necessarily. One of the most important lessons in firm leadership is also one of the simplest: revenue does not equal profit.
Revenue ≠ Profit
Revenue tells you how much money is coming into the business. Profit tells you how much is left after paying for everything required to generate that revenue. Those are two very different measures of business health. An architecture or engineering firm can have record revenue and still struggle financially. In fact, growth can sometimes make the problem worse. More projects often require more people, and more people bring additional salaries, benefits, software licenses, computers, office space, insurance, administrative support, and other overhead. More projects can also create more overtime, more coordination, more write-offs, and more opportunities for scope creep. It is entirely possible for a firm to become busier while also becoming less profitable.
Start With the Basic Math
Consider a simple example. Imagine a firm generates $5 million in annual net service revenue. That sounds like a strong year. But if it takes $4.8 million in labor, benefits, rent, software, insurance, marketing, professional services, and other expenses to produce that revenue, the firm has generated only $200,000 in profit, or a 4% profit margin.
Now compare that with a smaller firm generating $4 million in revenue but managing its fees, staffing, projects, and overhead well enough to achieve a 15% profit margin. That firm generates $600,000 in profit. The smaller firm produces three times as much profit despite generating $1 million less in revenue.
That is why chasing revenue alone can be dangerous.
The Question Isn't Just "How Much Work Do We Have?"
Firm leaders need to ask better questions than simply whether the backlog is full or whether everyone is busy. We need to know whether our projects are actually profitable, whether our fees adequately reflect the work we are delivering, whether our billing rates cover our true labor and overhead costs, and whether project teams are working within the hours originally budgeted.
We should understand where scope creep is occurring, whether staffing is appropriate for the work, how much time is being written off, whether utilization is where it needs to be, and ultimately how much money remains after everyone—including the owners—has been paid.
These are not questions that should only be answered by an accountant at the end of the year. Firm leaders should understand them every month, and project managers should understand many of them every week.
Profit Is Created at the Project Level
Profitability is not something that suddenly appears or disappears when the annual financial statements are prepared. In most cases, it is created—or lost—one project decision at a time.
A project may have been under-fee'd from the beginning. The scope may not have been clearly defined. Additional services may have been performed but never requested or billed. A project phase may have exceeded its labor budget. Senior staff may have spent too many hours performing work that could have been delegated. A six-month schedule may have stretched into twelve months without an adjustment to the fee. A client may have fallen behind on payments. Or the project team may simply have had no idea how many hours remained in the budget.
None of these problems by themselves may seem catastrophic, but when they are repeated across 20 or 30 projects, they can quietly erase an entire year of profit.
This is why project management and financial management cannot be treated as separate conversations. Every project manager should have a basic understanding of the project fee, labor budget, hours spent, hours remaining, percent complete, billing status, accounts receivable, and projected financial outcome. You do not need an MBA to understand these numbers, but you do need to pay attention to them.
Financial Literacy Is a Leadership Skill
For many architects and engineers, financial literacy becomes a leadership responsibility long before anyone teaches us how the business actually works. Architecture school taught us how to design buildings, solve complicated problems, communicate ideas, coordinate disciplines, and navigate increasingly complex projects. What most of us were not taught was how to read a profit-and-loss statement, calculate an overhead rate, establish appropriate billing rates, build a labor budget, or understand why a project that was creatively successful might have been a financial failure.
Then one day we become project managers, principals, or firm owners and are suddenly expected to know how to do all of it.
That learning curve is one of the reasons I created Architects Operating System. Financial literacy is not about turning architects into accountants. It is about giving architects and engineers the information they need to make better decisions and build healthier firms.
Profitable firms can invest in better technology, develop their people, pay competitive salaries, pursue better opportunities, withstand economic downturns, and give their leaders the freedom to think strategically instead of constantly worrying about cash flow and the next invoice.
So the next time someone tells you the firm had a great year because revenue increased, ask one more question:
How much of it did we actually keep?
That answer will tell you far more about the health of the business.
Architects Operating System (AOS) was created to help architects and engineers better understand the business side of practice, including financial management, project management, firm leadership, and the systems required to build healthier and more profitable firms.
Because it shouldn’t take 25 years in this profession to learn how the business actually works.
#Architecture #ArchitectureBusiness #FirmLeadership #PracticeManagement #ProjectManagement #ArchitectsOperatingSystem #AEIndustry #BusinessOfArchitecture