Shawn Van Dyke spent years learning how to keep structures from failing.
Then the engineering firm laid him off.
That should have been the part of the story where everything became less certain. Instead, it led him to a question that would make the businesses around him uncomfortable.
Not a technical question. Not a question about load, span, soil, materials, or safety.
A much simpler question: Did the work actually make money?
The surprising part was not that some contractors did not know. The surprising part was how much they could know while still not knowing that.
He knew the hard math
Shawn studied civil engineering at the University of Tennessee, then earned a master’s degree in structural engineering.
Engineering trains you to respect consequences.
A number is not close enough because it feels close. A beam does not care whether the estimate was optimistic. A foundation does not accept confidence as a substitute for evidence.
The inputs have to support the outcome.
Then Shawn lost his job.
He could have searched for another engineering firm and returned to the same path. Instead, he moved toward the field. He worked around commercial contractors, HVAC companies, landscapers, and real estate development.
That is where he noticed a strange divide.
The people doing the work could solve difficult problems all day. They could walk onto a site, study a condition, understand the sequence, choose the right material, organize a crew, and turn a drawing into something real.
But move the conversation from the work to the business behind the work, and the certainty changed.
What did the labor really cost? How much overhead had to travel through this job? What margin was required? When would the cash arrive? What happened if the schedule moved? Did the price protect the company, or merely win the customer?
The builders knew how to build.
The business often ran on hope.
The offer
One of Shawn’s subcontractors saw what Shawn was good at.
Not swinging the hammer. Not installing the system. The paperwork. The systems. The documentation. The math most people postpone until the work is already underway.
The owner made Shawn an unusual offer.
You run the business. Let me stay in the field.
Shawn eventually agreed and took full authority over the business side as COO. The owner focused on producing the work. Shawn focused on making the company underneath the work function.
The business grew from roughly six or seven people to 18. More importantly, it moved out of debt and into profit.
That result is easy to misread.
The craftsmen did not suddenly become more talented. The market did not hand the company a magical new trade. The work did not become less complicated.
The difference was that the business around the craftsmanship stopped being an afterthought.
Shawn would later call his approach the “boring success formula.” Systems, he argued, are not exciting. But the bottom line is what matters, and healthy movement from the top line to the bottom line requires a system.
The system was boring.
The result was freedom.
The sentence that controls the estimate
Now imagine the conversation at a kitchen table.
The homeowner has a number in mind. Maybe it came from a neighbor. Maybe it came from a search result. Maybe it came from the amount of cash available. Maybe it came from nowhere at all.
“Our budget is $18,000.”
The contractor hears the number and begins solving backward.
What can we remove? Where can we sharpen the labor? Can the crew finish faster? Can the supplier move? Can we accept less margin this time?
The contractor believes the customer has supplied a pricing fact. The customer has actually supplied a preference.
Those are not the same thing.
Shawn’s writing often challenges the way contractors respond when customers want to “save money.” The customer may be expressing fear or uncertainty, not presenting an engineered limit for the project.
If the contractor treats that fear as the controlling input, the business begins designing the economics of the job around a number that was never connected to the work.
The estimate can still look professional. The proposal can still win. The schedule can still fill. The crew can still complete everything promised.
And the business can still lose.
A full schedule is persuasive
This is why pricing mistakes survive. They do not always look like mistakes at first.
The sold job enters the board. The deposit hits the bank. The crew stays busy. The owner sees trucks moving and interprets motion as health.
Then reality arrives in pieces.
Materials cost more than expected. The job takes two extra days. A change order never gets approved. The final payment arrives late. Overhead keeps running while the crew corrects the punch list.
The project produces revenue.
The company keeps almost none of it.
Nobody can point to one dramatic failure because the guess was distributed across the entire job. Five percent here. A day there. A cost omitted. A margin quietly surrendered before the customer ever signed.
The job did not go wrong. The price entered the job wrong.
That distinction changes the meeting on Monday morning.
| If leadership treats the loss as a production failure, | the crew gets another checklist. |
| If leadership treats it as a sales failure, | the salesperson gets another script. |
| If leadership treats it as bad luck, | nothing changes at all. |
But when the team traces the job back to the estimate, a different question appears:
Which assumption entered the promise without being tested?
Maybe labor came from memory instead of actual completed jobs. Maybe overhead was spread across an unrealistic number of billable hours. Maybe the payment schedule required the company to finance the customer. Maybe the desired margin existed only as a percentage added at the end.
The completed job is not merely history. It is evidence for the next estimate.
“But we have to respect the market”
Of course you do.
A contractor cannot charge any number and expect the customer to accept it. Demand matters. Competition matters. Positioning matters. Value matters.
But “the market” is not a calculator.
Calling a competitor and copying a price does not reveal that competitor’s labor efficiency, purchasing power, overhead, callbacks, debt, warranty exposure, or target profit.
Accepting the homeowner’s budget does not make the budget capable of funding the work.
Reducing the price because the salesperson feels tension does not reduce the company’s cost to produce the promise.
| The market decides whether the customer buys. | Your economics decide whether the job was worth selling. |
Both truths have to survive the estimate.
The engineer returns
This is where Shawn’s engineering background becomes more than biography.
An engineer does not begin with the answer the client would prefer and then force the structure to support it. The engineer begins with the conditions.
Load. Material. Span. Risk. Required performance.
The price of a trade job deserves the same respect.
Labor. Materials. Overhead. Risk. Cash timing. Required profit.
Only after those inputs become visible can the company decide what to change.
Maybe the scope changes. Maybe the sequence changes. Maybe the customer chooses a different option. Maybe the company walks away.
But now the decision is being made with evidence.
Not fear. Not hunger. Not the relief of getting another signature.
The lesson arrives late
It would be easy to reduce Shawn’s story to “know your numbers.” That is true, but it is too weak.
The real lesson is that a number can enter the business wearing authority it never earned.
| The customer calls it | a budget. |
| The salesperson calls it | the market. |
| The owner calls it | what we need to do to keep the crew busy. |
Then the company builds an entire job around it.
That is the hidden decision.
The contractor did not lose profit when the material cost changed or the crew ran long. The contractor exposed the profit when an unverified number became the foundation of the price.
Guessing costs money.
Not because experience has no value. Experience is what helps an owner recognize risk faster than a spreadsheet can. But experience must still meet evidence before the company makes a promise.
The customer’s budget is useful information.
It is not your selling price.
The operating move
Take one estimate your company won last month. Do not begin with the selling price.
Rebuild the job from the bottom up.
What labor did it require? What material did it consume? What overhead had to be carried? What changed after the signature? When did cash arrive? What did the company keep?
Then ask the question Shawn’s path brought into focus:
Did the work actually make money?
If the answer is unclear, the estimate was never finished. It was only sold.
The craftsman can build the job.
The business must prove it should.
That’s Moneyball for the Trades.