The Consulting Math That Lies to You: Why Engineers Get the Numbers Wrong

Every experienced engineer has done the math. You are sitting in a meeting that should have been an email, watching someone three levels above you make a decision you know is wrong, and the arithmetic starts running in the back of your head. Your employer bills your time at $250 an hour. You see maybe a third of that. The rest disappears into overhead, management layers, and office space you never asked for.

So you do the calculation. $250 an hour, 40 hours a week, 50 weeks a year. That is half a million dollars. Cut the rate in half and you are still looking at a quarter million. The gap between what you earn and what you could earn feels like slow-motion robbery, and every pointless standup meeting makes it worse.

This is the consulting fantasy. It is not entirely wrong, but it is dangerously incomplete. And the engineers who leap without understanding why end up back in employment with depleted savings and damaged confidence.

The Numbers Nobody Mentions

The fantasy math works because it leaves out everything that makes the real math harder. Start with utilization.

As a full-time employee, you bill close to 40 hours a week because someone else handles the work of finding you things to do. As an independent consultant, you are doing that yourself. Industry data consistently shows that independent consultants spend 30 to 40 percent of their working time on non-revenue activities: business development, proposals, invoicing, contract negotiations, learning, marketing.

Your billable hours are not 40 per week. They are closer to 25, and that is when things are going well. When things are not going well, your billable hours might be zero for weeks at a time.

Now recalculate. $125 an hour, 25 billable hours a week, 45 working weeks (you need time off, and you are paying for it yourself now). That comes to around $140,000. Not profit. Revenue. You have not subtracted health insurance, self-employment tax, business insurance, accounting fees, software subscriptions, or retirement contributions.

A senior engineer I know left a position paying $185,000 to start consulting at $150 an hour. He expected to earn more. After his first full year, he had billed $127,000 in revenue. After expenses, taxes, and benefits, his take-home was roughly $89,000. He was working harder than he ever had. He went back to full-time work within eighteen months.

This is not a worst-case scenario. This is a common first-year outcome.

Then there is the cost side. Health insurance is the first shock. If your employer provides a gold-level family plan, they are likely paying $12,000 to $18,000 per year. You see the $200 deducted from each paycheck and assume that is the cost. The real cost is five to ten times that. Then there is self-employment tax: you pay both halves of Social Security and Medicare, which on $150,000 of income is more than $20,000. Paid time off, retirement matches, disability insurance, equipment, software licenses -- all of these shift from your employer's balance sheet to yours when you go independent.

Here is a useful exercise before you do anything else: ask your HR department for a total compensation statement. Many companies provide them annually. The difference between your salary and your total compensation is the gap you need to fill with consulting revenue before you are even breaking even.

The Pricing Trap That Kills New Consultants

Even the engineers who get past the revenue math often fail on pricing. Not because they price too high, but because they price too low -- and the psychology of why is worth understanding.

New consultants are terrified of quoting a rate that will make a potential client laugh. So they quote a rate that makes the client say yes immediately. An immediate yes means the rate was too low. Then they are stuck billing at a rate that does not cover their costs, and they are too afraid to raise it.

Here is what experienced consultants know about pricing that new consultants do not:

Low rates do not attract clients. They repel good ones. Sophisticated buyers interpret low prices as a signal of low quality or desperation. They think, "Why is this person so cheap? What is wrong with them?" Pricing at the bottom of the market range is not competitive positioning. It is a warning flag.

The first number you say sets the anchor. Everything that follows is negotiated relative to that number. If you say $150 an hour and the client was willing to pay $200, you have left $50 per hour on the table for the entire engagement. Always quote at the upper end of your comfortable range. You can negotiate down. You cannot negotiate up without looking like you are making things up.

Silence after quoting a rate is normal. The first time I quoted my full rate, there was a long silence. I was sweating. I almost offered a discount just to break the tension. The client said, "That works. When can you start?" The silence felt like rejection. It was just processing.

When a client pushes back on price, the wrong response is to immediately drop your rate. Better responses: reduce the scope ("I can work within that budget by focusing on assessment only"), offer a different structure ("I can offer this as a fixed-price project for $15,000"), or hold firm ("My rate reflects the outcomes I deliver. If this is not the right fit now, I am happy to stay in touch."). The one response to avoid is, "Oh, okay, I can do it for less." Immediate capitulation destroys your credibility.

What Actually Separates Success from Failure

The consultants who build sustainable practices share a pattern. It is not passion or hustle. It is something more specific.

They have a specific, marketable skill. Not "software engineering" or "cloud architecture." Something a potential client immediately understands. "I help mid-size banks migrate their core systems to modern APIs" is a consulting practice. "I do software development" is a job listing.

They are comfortable selling. Not in the slick, manipulative sense. In the sense that they can describe their services and quote a price without feeling like they are begging or bragging.

They have financial cushion. The consultants who survive the first two years almost always had savings, a working spouse with benefits, or some other safety net. Starting consulting with no savings is like starting a road trip with the fuel light on.

And critically: they treat it as a business, not a series of gigs. They have systems for tracking leads, managing projects, invoicing, and taxes. They build infrastructure because they understand that the business of consulting is a business.

The failure patterns are equally predictable. They underprice themselves. They do not sell -- they wait for the phone to ring. They take bad clients out of desperation. They burn out because every unbilled hour feels like lost money. And they ignore the business side until something goes wrong.

The timing matters too. Engineers often start consulting when they are angry -- frustrated with their manager, exhausted by corporate politics. Anger is a powerful motivator but a terrible strategic advisor. The best time to start is when you are in a position of strength: employed, earning well, with savings in place. The worst time is when you have just been laid off and your savings are thin.

Some engineers will do the honest math and decide to leap. Others will decide to stay. Both are good outcomes. The only bad outcome is leaping based on fantasy math and returning to employment a year later wondering what happened.