How do I grow my engineering firm without adding overhead and headcount?
You grow an engineering firm by testing how little it takes to deliver the work, not by adding people and overhead every time the backlog grows.

You grow it by running experiments on how little it takes to deliver the work, not by adding people, software and space every time the backlog grows. The question is a design question, and most engineering firm owners have never asked it out loud.
Why does hiring feel like the only answer?
When the backlog grows, the first reflex is a job posting. The second is more space or another software seat. Both are the same move: solve the problem by adding money.
That reflex is not foolish. Under Grandfather Engineering the product is hours, so more hours reads as more capacity, and capacity is how you say yes to the next client. The firm grows by stacking people. Modern delivery is the other way: it measures value and output instead of hours billed, so capacity can grow without another fixed salary.
What that costs you is structure. Every hire becomes a fixed line that has to be fed whether or not the backlog holds. Add enough of them and overhead, not judgment, starts deciding which projects you can afford to chase.
What does asking how little it takes actually mean?
It is a design question aimed at your own delivery: what is the least overhead, the fewest hands and the smallest amount of coordination that still produces a set a client accepts and an operator can run?
That is a design mentality, not a poverty mentality. A poverty mentality cuts blindly and hands the difference to the client as a thinner drawing set. A design mentality tests one limit, checks whether quality holds, and keeps the answer when it does.
Most leadership teams have never run that test. They have solved every problem by adding money or headcount for so long that nobody knows where the real floor sits. A firm that has never measured its floor will always guess high, and then budget against the guess.
How do I run the experiment?
Keep it small enough that nobody has to approve a reorganization, and real enough that the result tells you something. In my firm we keep the trial to one deliverable and one owner, so the answer arrives in a week instead of a quarter.
- Pick one deliverable, not the whole firm. A single plan set, a single permit package, a single recurring report to a client.
- Write down what it costs today, in hours and in dollars, before you touch anything. Without that number you have an opinion at the end, not a result.
- Set a hard cap on the resources for one run: who touches it, how many review passes it gets, what tooling carries the drafting and the formatting.
- Hold the quality bar fixed. The client should not be able to tell that you changed anything, except that it arrived sooner.
- Run it on real work with a real deadline. A trial on a practice project teaches you nothing about how your firm behaves under pressure.
- Compare against the number you wrote down, then keep it or revert. Both are valid answers, and reverting costs you one week, not one headcount.
Then measure it against these, not against how busy everyone looked:
- Hours per deliverable, not hours per person. Per-person hours tells you who was busy, which is not the question.
- Rework passes and review cycles. Count how many times the same sheet came back.
- Elapsed days from start to issue, which is usually the number the client actually cares about.
- Where the licensed engineer's time went, sorted into judgment and everything else.
- What changed for the client, in their words, on the next call.
Where does the experiment go wrong?
The usual mistake is cutting judgment instead of cutting coordination. Judgment is what the client is buying, and a licensed engineer's read on a site, a permit condition or a set of numbers is not overhead. It is the product.
The savings live in the middle of the process: the status meeting nobody needed, the third review pass that found nothing, the model rebuilt because nobody froze the scope, the same report formatted twice, the approval chain that exists because it always has.
The second mistake is running it once and calling it a conclusion. One run gives you a number. Three runs on three different deliverables tell you whether the floor you found is real or was a good week.
The third is running it without an owner. Someone has to be allowed to say the experiment is over and the result stands, or it quietly becomes another meeting that reports upward and changes nothing. In my firm we name that person before the trial starts, and that person's answer ends it.
What has it looked like in my own firm?
I have run my firm this way since 2017. We have delivered $2M+ a year of work and 525+ projects across 9 states with a production group I keep deliberately lean and a set of tools that carry the parts a licensed engineer does not need to touch.
That is not a claim that small is always right. It is a claim that the question has an answer, and the answer is usually lower than the owner assumes before they test it.
In my experience the constraint is rarely the number of engineers on the org chart. It is the number of handoffs, approvals and rebuilds between the engineer and the deliverable. That number is a design choice, and design choices can be changed on a Tuesday.
What to do next week
Ask one question in your next leadership meeting: when did we last run an experiment on how little it takes to deliver this work? Not how little we could pay people, and not how thin we could run the team. How little structure the work actually needs. Write the answer down exactly as it is given.
If the answer is never, you have found your next project, and it costs less than the hire you were about to make. If the answer is a date and a number, ask what changed because of it. An experiment that changed nothing was a measurement, not a decision.
- Write down what one recurring deliverable costs you today, in hours and dollars. Do it from the records, not from memory.
- Pick the one deliverable you will cap, and set the cap before anyone starts working on it.
- Name the person who is allowed to call the experiment over.
- Run it on a live project, keep the quality bar, and put a date on when you will compare.
Then run it again on something else. The firms that win the next decade will not be the ones with the most people. They will be the ones that asked how much they can produce for how little overhead, and kept asking.
From the book Engineer Your Freedom
Michael Groselle, P.E., is the founder of Modern Engineering Solutions, a multi-state water and wastewater engineering firm. He left salaried engineering in 2017 and built the firm from one resignation letter and zero clients to more than $2M in annual revenue, with a team of 37 and 525+ completed projects.
Sold on Amazon. Prefer the Kindle edition? Buy it on Amazon ($9.99).