Entries by Best Bid Electrical Estimating Software Team

The First Time I Felt Like a Leader — One Hundred Dollars I Ever Saw

The Most Expensive One Hundred Dollars I Ever Saw. Steve Griffin electrical contractor business lesson

Everybody Has A First · Chapter 10

Sometimes the smallest decisions produce the biggest consequences.

I’ve learned that lesson many times during more than 50 years in the electrical contracting business, but one particular experience has stayed with me because of how simple it was. It wasn’t about losing thousands of dollars. It wasn’t about a major estimating mistake or a failed project.

It was about one hundred dollars.

For years, our company performed nearly all of the electrical work for a particular general contractor. We had a great relationship. They trusted us, and we trusted them. Whenever they had a project, we expected to receive an invitation to bid.

Relationships like that don’t happen overnight. They are built through years of doing what you say you’re going to do, showing up when you say you’ll show up, and taking care of problems when they arise.

The Phone Call Before Bid Day

Then one day, another contractor invited us to bid on a unique industrial project at a steel mill.

This wasn’t an ordinary estimate. It required multiple site visits, careful planning, and detailed discussions. We invested a tremendous amount of time understanding exactly what the owner wanted before we finally submitted our price.

We weren’t just throwing a number together. We were doing real Electrical Estimating based on information we had gathered firsthand.

A few hours before bids were due, the general contractor we normally worked for called.

“We’ve decided to bid that project.”

Then they asked me a question.

“Can you give us your MEP numbers?”

They hadn’t attended the site meetings. They hadn’t invested the time we had. Without our numbers, however, they couldn’t submit a competitive proposal.

We wanted to help a longtime customer, so we shared the information. They won the project.

At the time, I didn’t think much more about it. Business continued as usual, and I assumed the relationship would continue just as it had before.

A few days later, the owner of that general contracting company stopped by our office. He and our owner, Charles, had been friends for years. After a few minutes of casual conversation, he smiled and said, “I came by to pick up my one hundred dollars.”

Charles looked puzzled. “What one hundred dollars?”

The contractor explained that our plumbing manager had supposedly promised him one hundred dollars if they used our numbers on the steel mill project.

I happened to know that wasn’t true. Nobody had promised him one hundred dollars. Our plumbing manager hadn’t even spoken to him. He had simply provided the pricing we had already developed for the other contractor.

Charles didn’t argue. He smiled and said, “I’ve got to run get a haircut. Stop back by tomorrow and we’ll straighten it out.” The truth was, Charles didn’t need a haircut. He needed the facts.

Find the Truth Before You React

After the visitor left, Charles immediately started asking questions. He spoke with the plumbing manager.

“Did you promise him one hundred dollars?”

The answer was exactly what I expected. “No. I never said anything about paying him. I simply gave Steve’s pricing that we had already prepared.”

Charles nodded. That’s all he needed to hear.

He didn’t jump to conclusions. He didn’t make a decision while he was angry. He found out what actually happened first.

I’ve learned that this is one of the most important habits any business owner, Electrical Contractor, project manager, or estimator can develop: find the facts before you react.

The Most Expensive Decision

The next day, the contractor returned. “You got my money?”

Charles answered calmly. “No. We never promised you one hundred dollars. And I’m not paying something we don’t owe.”

That was the end of the conversation. At least, that’s what we thought.

The contractor left. And we never received another invitation to bid from them.

Think about that. A relationship that had generated millions of dollars’ worth of work over many years ended over one hundred dollars.

Now, let me be perfectly clear. This chapter isn’t about whether Charles should have paid the money. Personally, I think he made the right decision. If you start paying people for promises that were never made, where does it stop?

The lesson is much bigger than that.

Pride Can Be Expensive

Business is built on relationships. Relationships require trust. Trust requires communication.

Sometimes both parties become so focused on being right that they forget what’s really at stake.

I’ve seen companies lose customers over issues far smaller than the value of the relationship. I’ve also seen people swallow their pride, have an honest conversation, and preserve a partnership that lasted another twenty years.

Every disagreement deserves perspective.

I’ve learned to ask myself a simple question: What is this relationship actually worth?

That doesn’t mean compromising my integrity. It means understanding the difference between protecting my principles and allowing my pride to make a business decision for me. There is a big difference.

Every Decision Has a Price

One lesson business has taught me is that every decision has a cost. Sometimes it’s measured in dollars. Sometimes it’s measured in opportunities. Sometimes it’s measured in relationships.

The difficult part is that you don’t always know the true cost until years later.

Whether I’m dealing with an Electrical Estimating issue, a customer disagreement, a Bid Day problem, or a business decision, I try to think about what happens next.

What does this decision do to the relationship? What does it do to my reputation? What does it teach the people working with me? And, perhaps most importantly, would I make the same decision if I had to live with the consequences for the next twenty years?

Looking back, I still think Charles made the correct decision. But I’ve never forgotten how expensive one hundred dollars became. It was one of the most valuable business lessons I ever witnessed.

What I Learned

Not every decision should be measured by the amount of money involved.

Sometimes the smallest disagreements reveal much larger issues.

I learned to protect my integrity, keep my word, and tell the truth. At the same time, I learned not to lose sight of the long-term value of a good relationship.

I’ve carried many of these lessons into my work with electrical contractors and into the philosophy behind Best Bid Electrical Estimating Software.

Good estimating isn’t only about getting a number on paper. It’s about creating reliable systems, making sound decisions, and understanding the consequences of the numbers we put in front of customers.

The Electrical Estimating Online School is another resource I recommend for contractors and estimators who want to strengthen their skills.

I also come back to the ideas in The Art of Balance in Electrical Estimating when thinking about the bigger picture behind estimating decisions.

My Best Bid Rules

✓ Never make decisions without knowing the facts.

✓ Protect your integrity above your profit.

✓ Value relationships — but never compromise your honesty.

✓ Ask what the long-term cost might be.

✓ Don’t allow pride to make business decisions for you.

✓ Remember that today’s small decision can become tomorrow’s big consequence.

Frequently Asked Questions

What is the main lesson from the one hundred dollar story?

I learned that a small financial disagreement can have consequences far greater than the amount of money involved. The long-term value of a business relationship can be much greater than the immediate issue.

Why should business owners gather facts before reacting?

I believe facts should come before conclusions. Asking questions and confirming what actually happened prevents emotion, assumptions, and misunderstandings from controlling an important business decision.

Should an Electrical Contractor always protect a customer relationship?

Relationships are extremely valuable, but protecting a relationship should never require dishonesty or abandoning your principles. Good relationships are built on trust and honesty.

How does this lesson apply to Electrical Estimating?

Estimating involves more than calculating labor and material. An estimator’s numbers affect customers, contractors, suppliers, and project decisions. Accuracy, honesty, and communication are essential.

Why is reputation important for an Electrical Contractor?

A reputation takes years to build and can be damaged by one poor decision. Keeping my word and dealing honestly with people is more valuable than winning one argument.

How can estimating software help contractors make better decisions?

Good estimating software can organize information, improve consistency, and help contractors understand their numbers. But software doesn’t replace judgment.

Where can contractors learn more about Best Bid?

Contractors can explore Best Bid Electrical Estimating Software to learn more about the estimating system, resources, and tools I have developed.

My Final Reflection

When I think about that one hundred dollars today, I don’t think about the money. I think about the relationship.

I think about how many projects had been completed before that day and how many more might have been completed afterward.

Most importantly, I think about how easily a small disagreement can become something much larger when people stop communicating.

I still believe Charles made the right decision. We shouldn’t pay money that we didn’t owe and shouldn’t accept responsibility for a promise that was never made.

But the experience taught me something I have never forgotten.

Every decision has a price.

Sometimes you pay that price in money. Sometimes you pay it in opportunity. And sometimes you pay it in a relationship.

That’s a lesson I carry with me today.

I also included stories like this in my book Everybody Has A First because my career wasn’t built only on estimating formulas and software. It was built on people, mistakes, decisions, relationships, and lessons learned the hard way.

Everybody has a first. This was one of mine.

Let’s Talk

If you are an electrical contractor, estimator, project manager, or business owner looking for practical ways to improve your estimating process, I would be happy to hear from you.

You can call me at 800-941-7028 to discuss your electrical estimating needs and learn more about Best Bid.

You can also visit my Steve Griffin page to learn more about my background, experience, and work in electrical estimating.

About Steve Griffin

Steve Griffin

Founder of Best Bid Electrical Estimating Software

Electrician • Estimator • Contractor • Author • Software Developer

From digging ditches in 1973 to creating one of the industry’s longest-running electrical estimating software systems, Steve Griffin has spent more than 50 years helping contractors win more work and make more mone

The Philosophy Behind Electrical Estimating: What Contractors Must Understand

The philosophy behind electrical estimating with an estimator reviewing electrical plans and bid calculations





The Philosophy Behind Electrical Estimating: What Contractors Must Understand | Steve Griffin


















Estimating Philosophy  ·  Series Part 10 of 30

The Philosophy Behind Electrical Estimating: What Every Contractor Must Understand

Electrical estimating is more than math — it is a discipline with its own philosophy. Steve
Griffin explains the principles that separate profitable estimators from struggling ones.

By Steve Griffin  ·  Founder, Best Bid Electrical Estimating Software
 ·  July 23, 2026  ·  8 min read

📖 Part of the Complete Series
This article is Series Part 10 of 30 in The Art of Balance in Electrical
Estimating Software
— the complete 30-section philosophy guide by Steve Griffin. Read all sections in one
place.

Section 10: The Philosophy of Estimating

Estimating is not just counting. Estimating is not just math. Estimating is not just software.

Estimating is a
discipline. A craft. A skill.

A mindset. A way of thinking. A way of seeing a project before it exists.

A way of
understanding labor, materials, risk, and opportunity.

Estimating is decision making. Estimating is risk management. Estimating is pattern recognition.

Estimating is
experience. Estimating is judgment. Estimating is balance.

Estimating is the art of predicting the future using the information available in the present. It is the art of
turning drawings into dollars. It is the art of turning lines on paper into labor hours.

It is the art of
turning symbols into materials. It is the art of turning complexity into clarity.

Estimating is not about perfection. Estimating is about reliability.

Estimating is not about exactness. Estimating is about consistency.

Estimating is not about detail. Estimating is about understanding.

Estimating is not about speed. Estimating is about efficiency.

Estimating is not about guessing. Estimating is about informed judgment.

Estimating is not about software. Estimating is about the estimator.

Software is a tool. The estimator is the craftsman.

Software should not replace the estimator — it should empower the estimator. Software should not take over
thinking — it should reduce thinking. Software should not force decisions — it should simplify decisions.
Software should not create complexity — it should eliminate complexity.

Balance is designing software that works with the estimator — not against them.

Estimating is also about understanding human behavior. Contractors behave in predictable ways. Suppliers behave
in predictable ways.

Labor behaves in predictable ways. Competition behaves in predictable ways. Markets behave
in predictable ways.

Estimators must understand these patterns. Estimators must anticipate these patterns. Estimators must adapt to
these patterns.

Balance is designing software that reflects real world behavior — not theoretical behavior.

Estimating is also about understanding risk. Every project has risk. Every decision has risk.

Every assumption
has risk. Every shortcut has risk. Every detail has risk.

Every omission has risk.

Estimators must manage risk. Estimators must minimize risk. Estimators must anticipate risk. Estimators must
balance risk.

Balance is designing software that reduces risk — not software that increases risk.

Estimating is also about understanding opportunity. Every project has opportunity. Every decision has
opportunity.

Every assumption has opportunity. Every shortcut has opportunity. Every detail has opportunity.

Every inclusion has opportunity.

Estimators must identify opportunity. Estimators must maximize opportunity. Estimators must leverage
opportunity. Estimators must balance opportunity.

Balance is designing software that reveals opportunity — not software that hides opportunity.

Estimating is also about understanding labor. Labor is the most expensive part of most electrical projects.
Labor is the most variable part of most electrical projects. Labor is the most unpredictable part of most
electrical projects.

Estimators must understand labor deeply. Estimators must understand labor productivity. Estimators must
understand labor conditions.

Estimators must understand labor limitations. Estimators must understand labor
efficiency.

Balance is designing software that reflects real labor — not ideal labor.

Estimating is also about understanding materials. Materials fluctuate. Materials vary.

Materials change. Materials have lead times. Materials have availability issues.

Materials have substitutions. Materials have
alternatives.

Estimators must understand materials. Estimators must understand material cost. Estimators must understand
material availability.

Estimators must understand material risk. Estimators must understand material
opportunity.

Balance is designing software that reflects real materials — not theoretical materials.

Estimating is also about understanding the field. The field is where the work happens. The field is where the
drawings meet reality.

The field is where the estimate becomes installation. The field is where labor meets
materials. The field is where mistakes become expensive.

The field is where assumptions become consequences.

Estimators must understand the field. Estimators must understand field conditions. Estimators must understand
field limitations.

Estimators must understand field challenges. Estimators must understand field workflow.

Balance is designing software that reflects field reality — not office theory.

Estimating is also about understanding the customer. Customers behave in predictable ways. Customers have
expectations.

Customers have budgets. Customers have priorities. Customers have preferences.

Customers have
patterns.

Estimators must understand customers. Estimators must understand customer behavior. Estimators must understand
customer expectations.

Estimators must understand customer priorities. Estimators must understand customer
patterns.

Balance is designing software that supports customer expectations — not software that complicates them.

Estimating is also about understanding competition. Competition is fierce. Competition is unpredictable.

Competition is aggressive. Competition is strategic. Competition is opportunistic.

Estimators must understand competition. Estimators must understand competitive behavior. Estimators must
understand competitive pricing.

Estimators must understand competitive strategy. Estimators must understand
competitive patterns.

Balance is designing software that supports competitive bidding — not software that slows it down.

Estimating is also about understanding profit. Profit is the goal. Profit is the purpose.

Profit is the reason
contractors estimate. Profit is the reason contractors bid. Profit is the reason contractors work.

Estimators must understand profit. Estimators must understand profit margins. Estimators must understand profit
risk.

Estimators must understand profit opportunity. Estimators must understand profit strategy.

Balance is designing software that protects profit — not software that threatens it.

Estimating is also about understanding time. Time is limited. Time is valuable.

Time is expensive. Time is
unforgiving. Time is competitive.

Estimators must understand time. Estimators must understand deadlines. Estimators must understand workflow.

Estimators must understand efficiency. Estimators must understand productivity.

Balance is designing software that saves time — not software that wastes it.

Estimating is also about understanding clarity. Clarity is essential. Clarity is powerful.

Clarity is
efficient. Clarity is profitable. Clarity is competitive.

Estimators must understand clarity. Estimators must understand clear workflow. Estimators must understand clear
structure.

Estimators must understand clear decisions. Estimators must understand clear assumptions.

Balance is designing software that increases clarity — not software that creates confusion.

Estimating is also about understanding simplicity. Simplicity is powerful. Simplicity is efficient.

Simplicity
is profitable. Simplicity is competitive.

Estimators must understand simplicity. Estimators must understand simple workflow. Estimators must understand
simple decisions.

Estimators must understand simple structure. Estimators must understand simple assumptions.

Balance is designing software that simplifies — not software that complicates.

Estimating is also about understanding complexity. Complexity is unavoidable. Complexity is inherent.

Complexity is real. Complexity is part of the job.

Estimators must understand complexity. Estimators must understand complex drawings. Estimators must understand
complex installations.

Estimators must understand complex materials. Estimators must understand complex labor.

Balance is designing software that manages complexity — not software that increases it.

Estimating is also about understanding judgment. Judgment is experience. Judgment is intuition.

Judgment is
pattern recognition. Judgment is understanding. Judgment is wisdom.

Estimators must understand judgment. Estimators must understand when to trust the software. Estimators must
understand when to override the software.

Estimators must understand when to adjust. Estimators must understand
when to simplify. Estimators must understand when to dig deeper.

Balance is designing software that supports judgment — not software that replaces it.

Estimating is also about understanding confidence. Confidence is essential. Confidence is powerful.

Confidence
is profitable. Confidence is competitive.

Estimators must understand confidence. Estimators must understand confident numbers. Estimators must understand
confident workflow.

Estimators must understand confident decisions. Estimators must understand confident
assumptions.

Balance is designing software that builds confidence — not software that undermines it.

Estimating is also about understanding trust. Trust is essential. Trust is powerful.

Trust is profitable. Trust
is competitive.

Estimators must trust their software. Estimators must trust their workflow. Estimators must trust their
numbers.

Estimators must trust their decisions. Estimators must trust their assumptions.

Balance is designing software that earns trust — not software that demands it.

Estimating is also about understanding the future. The future is uncertain. The future is unpredictable.

The
future is competitive. The future is opportunity.

Estimators must understand the future. Estimators must understand future risk. Estimators must understand
future opportunity.

Estimators must understand future strategy. Estimators must understand future patterns.

Balance is designing software that adapts to the future — not software that becomes obsolete.

Estimating is also about understanding balance itself. Balance is the foundation. Balance is the anchor.

Balance is the compass. Balance is the guide. Balance is the philosophy.

Balance is the difference between:

  • A tool and a burden
  • A solution and a problem
  • A system and a mess
  • A win and a loss

Balance is the core principle that guides every other principle.

Balance is everything.

Key Principle

The principle in this section is one of 30 that together form a complete philosophy of electrical estimating
— built from 50 years of real-world experience bidding and winning electrical work. Every principle connects
to every other. Master them together.

Frequently Asked Questions

Questions electrical contractors ask about
electrical estimating philosophy.

What does this principle mean for my daily estimating practice?
Every principle in this series translates directly to daily estimating decisions. The
concepts covered here affect how you set up assemblies, calibrate labor units, price materials, calculate
markup, and present your final number. Applying even one principle consistently improves the quality and
reliability of every estimate you produce.

How does electrical estimating philosophy affect bid competitiveness?
Getting this right directly affects your ability to submit bids that are both accurate and
competitive. Contractors who understand and apply this principle consistently win more profitable work because
their numbers reflect reality — not guesswork, not padding, and not systematic error. Bid competitiveness is
ultimately a function of estimating discipline.

Does Best Bid Electrical Estimating Software support this approach?
Yes. Best Bid Next Generation was designed with all 30 principles in this series in mind.
Every feature, every assembly structure, every reporting tool reflects the philosophy Steve Griffin developed
over 50 years of real-world estimating. The software is the philosophy made practical.

How do I apply this to a real electrical project estimate?
Start by evaluating your current estimating process against the principle described in this
article. Identify where your workflow drifts away from the principle — whether in assembly calibration, labor
unit selection, overhead allocation, or markup calculation. Each gap is an opportunity to tighten your process
and protect your margin on the next bid.

Where can I read all 30 principles together?
All 30 sections are published together in the complete guide: The Art of Balance in Electrical Estimating Software. Reading
the full guide gives you the complete picture of how each principle connects to the others and why the whole
is greater than the sum of its parts.


The Computer That Changed Everything | Steve Griffin

The Computer That Changed Everything | Steve Griffin

Everybody Has A First · Chapter 9

I didn’t set out to become a software developer. I was trying to become a better electrical estimator. That distinction is important because most of the major changes in my career didn’t begin with a grand business plan. They began with a question I couldn’t get out of my head.

One of the biggest lessons I share in my book, Everybody Has A First, is that curiosity can take you places you never planned to go.

If the biggest electrical contractor in town was estimating with assemblies, I wanted to know what assemblies were and why they worked. I wasn’t interested in copying somebody else’s system. I wanted to understand it.

At the time, finding information wasn’t easy. This was before Google, YouTube, online forums, and instant answers. If I wanted to learn something, I had to hunt for it. I asked questions, read manuals and books, talked to people, and worked through problems myself.

Eventually, I understood the basic idea behind assemblies. Instead of estimating every nut, bolt, connector, fitting, strap, screw, and coupling separately, I could group the materials and labor that normally belonged together into one complete installation.

One receptacle. One light fixture. One hundred feet of conduit.

One feeder. Each assembly could represent the labor and incidental material required to install it.

The concept was simple, but it changed the way I thought about Electrical Estimating.

It Still Didn’t Fit

Understanding what an assembly was didn’t mean I immediately knew how to use one effectively. I knew assemblies made sense. I knew they could make estimating faster. I knew successful electrical contractors were using systems like this.

But I couldn’t make everything fit the way I had been estimating. So I continued doing estimates the way I always had. Piece by piece. Project by project.

Yet the idea stayed with me. Every estimate seemed to bring me back to the same question: There has to be a better way.

The more electrical projects I estimated, the more I realized that estimating wasn’t really about counting things. It was about systems.

A good Electrical Estimator doesn’t simply know electrical work. A good estimator develops repeatable methods that produce consistent results. The better the system, the more consistent the estimate becomes.

I didn’t fully understand it at the time, but I was beginning to think differently. Most people were trying to estimate faster. I was trying to estimate better.

Timing Is Everything

Some time later, something happened that changed my life again. Our company hired a secretary, and she convinced the owner to buy a computer.

This was a long time ago, when computers weren’t sitting on every desk in every electrical contractor’s office. They were expensive, complicated, and, to me, a little intimidating.

The only software installed on that computer was WordPerfect. She used it for typing letters and documents. Then she left the company.

The computer stayed. Nobody knew what to do with it, and nobody particularly wanted it. So they pushed it into my office.

Not because I knew anything about computers. Because nobody else wanted it.

To be honest, I kept it partly because I thought having a computer in my office made me look important. I had absolutely no idea what I was doing.

Becoming a Computer Expert in One Hour

One day, curiosity got the better of me. I turned the computer on. That alone felt like an accomplishment.

After fumbling around for about an hour, I managed to type a paragraph and print it. I was unbelievably proud.

I had typed something on a computer. Today, a five-year-old could probably do the same thing. Back then, I felt like I had joined NASA. I was officially a computer expert — at least in my own mind.

The truth was that I knew almost nothing. But something important happened that day. The computer stopped being intimidating.

It became interesting. Then it became fascinating.

The more I learned, the more possibilities I started seeing.

The Collision

For a while, assemblies had been sitting in the back of my mind. Now I had a computer sitting in my office. One represented a better estimating system. The other represented a better tool.

Eventually, those two ideas collided.

I started asking questions. Could labor be automatically attached to material? Could assemblies be stored?

Could calculations happen instantly? Could historical information be saved and reused? Could I stop starting every estimate from scratch?

Those questions eventually changed the direction of my career.

At the time, I wasn’t trying to build software. I wasn’t trying to revolutionize electrical estimating. I wasn’t trying to create a technology company. I was simply trying to become a better estimator.

That has been true for most of my career. I wasn’t chasing success. I was chasing improvement. Success usually showed up later.

Looking Back

I’ve often wondered what would have happened if that estimator had answered my original question differently.

What if he had spent an hour explaining assemblies? What if he had shown me everything? What if he had never spoken to me at all?

The funny thing is that his lack of an answer may have helped me more than a complete explanation ever could have. He didn’t teach me everything. He challenged me.

And throughout my life, challenges have motivated me more than easy answers.

That one word — assemblies — eventually led me to spreadsheets, databases, and estimating software.

Those ideas eventually became part of Best Bid Electrical Estimating Software. Looking back, it is amazing to think about: one question, one word, one old computer, and an entirely different future.

What I Learned

Technology alone isn’t the solution. A computer without a good system is simply an expensive typewriter.

The real breakthrough for me was combining a better estimating process with a better tool.

Technology should help an Electrical Contractor organize information, reduce repetitive work, learn from historical data, and make better decisions. It should support experience, not replace it.

I’ve carried that philosophy into the development of Best Bid and into the way I approach Electrical Estimating Reports, databases, assemblies, and estimating workflows.

For contractors who want to improve their estimating knowledge, I also recommend continuing to learn through practical training such as the Electrical Estimating Online School.

I also discuss the relationship between estimating systems and technology in The Art of Balance in Electrical Estimating.

My Best Bid Rules

Always ask why, not just how.

Learn the system before you learn the software.

Stay curious longer than everyone else.

Use technology to improve your thinking, not replace it.

Never stop looking for a better way.

Frequently Asked Questions

How did computers change my approach to Electrical Estimating? A computer showed me that repetitive estimating tasks could be organized and automated.

Why are assemblies important in electrical estimating? Assemblies allow me to group the materials and labor required for a complete installation rather than repeatedly estimating every individual component.

Does estimating software replace an experienced Electrical Estimator? No. I believe software should support the estimator. Experience, judgment, project knowledge, and field understanding still matter.

What should an Electrical Contractor learn before using estimating software? I believe the contractor should first understand the estimating process. Software works best when it supports a sound system.

Why is historical data important? Historical data lets me compare estimates with actual project results and improve future labor and material assumptions.

What is the biggest lesson I learned from technology? Technology is most valuable when it solves a real problem. I became interested because I could see how computers might improve estimating.

Where can contractors learn more about Best Bid? I encourage contractors to explore Best Bid Electrical Estimating Software and its estimating resources.

My Final Reflection

When I look back at that old computer sitting in my office, I don’t see a piece of technology. I see an opportunity I almost didn’t recognize.

I didn’t know where that computer would lead me. I didn’t know that assemblies would eventually become connected to databases, spreadsheets, and estimating software. I certainly didn’t know that those ideas would eventually contribute to Best Bid.

I was simply curious.

That’s why I included this story in Everybody Has A First. Major changes don’t always begin with a plan. Sometimes they begin because you refuse to stop asking questions.

If someone won’t give you the answer, don’t quit. Go find it.

You might discover something much bigger than the answer you were originally looking for.

Everybody has a first. This was one of mine.

If you would like to discuss your electrical estimating needs, estimating software, or ways to improve your estimating process, please call me at 800-941-7028. I welcome conversations with electrical contractors, estimators, project managers, and business owners.

You can also visit my Steve Griffin page to learn more about my background and experience.

About Steve Griffin

Steve Griffin

Founder of Best Bid Electrical Estimating Software

Electrician • Estimator • Contractor • Author • Software Developer

From digging ditches in 1973 to creating one of the industry’s longest-running electrical estimating software systems, Steve Griffin has spent more than 50 years helping contractors win more work and make more money.

Real-World Electrical Estimating: 50 Years of Hard-Won Lessons | Steve Griffin

Steve Griffin electrical estimating software and contracting experience





Real-World Electrical Estimating: 50 Years of Hard-Won Lessons | Steve Griffin


















Estimating Philosophy  ·  Series Part 9 of 30

Real-World Electrical Estimating: 50 Years of Hard-Won Lessons

What 50 years of electrical estimating actually teaches you. Steve Griffin shares the hard
lessons that classroom training and software manuals never cover.

By Steve Griffin  ·  Founder, Best Bid Electrical Estimating Software
 ·  July 23, 2026  ·  8 min read

📖 Part of the Complete Series
This article is Series Part 9 of 30 in The Art of Balance in Electrical
Estimating Software
— the complete 30-section philosophy guide by Steve Griffin. Read all sections in one
place.

Section 9: Real World Lessons Learned Over Decades

This section expands into deep, practical insights — the kind you only learn after decades of estimating and
decades of designing estimating software.

Estimators fail when they rely too heavily on manual thinking. Software fails when it relies too heavily on
user thinking.

Estimators fail when they chase detail instead of accuracy. Software fails when it chases features instead of
usability.

Estimators fail when they overthink small items. Software fails when it underthinks big items.

Balance is the difference between success and failure.

One of the biggest lessons learned is that estimators don’t want more control — they want better control. They
don’t want more options — they want smarter options. They don’t want more features — they want better features.
They don’t want more assemblies — they want better assemblies.

Balance is designing software that helps the estimator think less — not more.

Another lesson is that estimators don’t want perfection — they want reliability. They don’t want exactness —
they want consistency. They don’t want complexity — they want clarity.

Balance is designing software that produces reliable numbers — not perfect numbers.

Another lesson is that estimators don’t want to be impressed — they want to be supported. They don’t want
flashy features — they want practical features. They don’t want marketing — they want workflow.

Balance is designing software that supports real world estimating — not theoretical estimating.

Another lesson is that software should not replace the estimator — it should empower the estimator. It should
not take over thinking — it should reduce thinking. It should not force decisions — it should simplify
decisions.

Balance is designing software that works with the estimator — not against them.

Another lesson is that the best software is invisible. It disappears into the workflow. It feels natural.

It
feels intuitive. It feels obvious. It feels like part of the job.

Balance is designing software that feels like a tool — not a task.

Key Principle

The principle in this section is one of 30 that together form a complete philosophy of electrical estimating
— built from 50 years of real-world experience bidding and winning electrical work. Every principle connects
to every other. Master them together.

Professional electrical estimator preparing a project estimate

Frequently Asked Questions

Questions electrical contractors ask about
electrical estimating lessons learned.

What does this principle mean for my daily estimating practice?
Every principle in this series translates directly to daily estimating decisions. The
concepts covered here affect how you set up assemblies, calibrate labor units, price materials, calculate
markup, and present your final number. Applying even one principle consistently improves the quality and
reliability of every estimate you produce.

How does electrical estimating lessons learned affect bid competitiveness?
Getting this right directly affects your ability to submit bids that are both accurate and
competitive. Contractors who understand and apply this principle consistently win more profitable work because
their numbers reflect reality — not guesswork, not padding, and not systematic error. Bid competitiveness is
ultimately a function of estimating discipline.

Does Best Bid Electrical Estimating Software support this approach?
Yes. Best Bid Next Generation was designed with all 30 principles in this series in mind.
Every feature, every assembly structure, every reporting tool reflects the philosophy Steve Griffin developed
over 50 years of real-world estimating. The software is the philosophy made practical.

How do I apply this to a real electrical project estimate?
Start by evaluating your current estimating process against the principle described in this
article. Identify where your workflow drifts away from the principle — whether in assembly calibration, labor
unit selection, overhead allocation, or markup calculation. Each gap is an opportunity to tighten your process
and protect your margin on the next bid.

Where can I read all 30 principles together?
All 30 sections are published together in the complete guide: The Art of Balance in Electrical Estimating Software. Reading
the full guide gives you the complete picture of how each principle connects to the others and why the whole
is greater than the sum of its parts.


How Electrical Estimating Assemblies Changed My Approach | Steve Griffin

Electrical estimator using assemblies to improve the estimating process

Everybody Has A First · Chapter 8

One of the biggest lessons I share in my book, Everybody Has A First is that some of the most important changes in my career started with something that seemed simple at the time. For me, assemblies were one of those turning points. Learning about assemblies was one thing. Learning how to actually use them was another.

When I first discovered assemblies, I thought I had simply found a faster way to put an estimate together. I didn’t realize I was about to change the way I looked at electrical work. Once I started using assemblies in my Electrical Estimating, I had to rethink the way I counted, organized estimates, and visualized a project before the first electrician ever stepped onto the jobsite.

For years, I had estimated from the bottom up. I looked at the drawings and worked through the project piece by piece. Conduit was conduit.

Wire was wire. Boxes were boxes. Fittings were fittings.

I counted what I could see and built the estimate from those individual components.

Assemblies made me step back and think about the installation itself.

From Parts to Complete Installations

Once I understood the concept, I began creating my own assemblies. I would take a particular electrical installation and think through everything it actually required. What materials were involved?

How much labor would it take? What would an electrician actually have to do to complete the installation?

Then I tested those assemblies against real work.

I didn’t expect my first version to be perfect. If an assembly didn’t produce a realistic labor allowance, I changed it. If the material wasn’t right, I adjusted it. If something happened on the job that I hadn’t considered, I used that experience to improve the assembly.

Every completed project gave me another opportunity to test what I had created. A successful estimate gave me confidence that an assembly was working. A mistake gave me information about what needed to change.

I started realizing that an assembly wasn’t something I created once and forgot about. A good assembly should get better with experience.

Every Project Became Research

This was one of the biggest changes in my approach to Electrical Estimating. I started looking at completed electrical projects as a source of information.

Before that, it was easy to finish a job and move on to the next one. There was always another estimate waiting and another Bid Day coming. But I began asking myself what the last project could teach me.

If I estimated a certain amount of labor and the electricians needed more time, I wanted to know why. Maybe the installation was more difficult than I expected. Maybe access was a problem. Maybe the original labor allowance didn’t account for something I hadn’t considered.

If I consistently estimated too little of something, I wanted to understand why. If I was consistently carrying too much, that was worth knowing as well.

The more I paid attention to those differences, the more useful my estimating process became. I wasn’t simply preparing estimates anymore. I was building knowledge.

Memory Is Useful, But Data Is Better

I’ve relied on my memory for a lot of things throughout my career. After more than 50 years in the electrical industry, experience becomes part of how I look at a project.

But I’ve also learned that memory has limitations. I might remember that a particular installation took about a certain amount of time on an earlier job. But “about” isn’t the same as having actual production information.

Historical data gave me something much better. It gave me evidence.

If I could look back at completed projects and see what I had estimated compared with what actually happened, I could make better decisions on future estimates.

That doesn’t mean I blindly use an old number on a new project. Every electrical project is different. Conditions change, crews change, and installations can have different levels of difficulty.

But historical information gives me a starting point. It gives me something to compare against. It helps me recognize when a number looks unusual. Most importantly, it reduces the amount of guessing I have to do.

The Problem With Not Learning From Your Projects

I’ve seen contractors work on project after project and still make the same estimating mistakes. The information was there. The lessons were there.

The actual production results were there. But nobody captured them or studied them.

That’s a missed opportunity.

If I consistently underestimate a particular installation, I want to know about it. If a certain assembly repeatedly requires more labor than I originally allowed, I want to correct it.

The goal isn’t to prove that my original estimate was right. The goal is to make the next estimate better.

Assemblies Became More Than an Estimating Tool

As I continued working with assemblies, I realized the idea went beyond Electrical Estimating. It affected the way I thought about management, operations, training, and eventually software development.

I started seeing more of the business as a collection of processes that could be measured, reviewed, and improved.

The question became simple: How can I do this better the next time?

The Goal Isn’t Just to Estimate Faster

Speed is valuable in Electrical Estimating, especially when Bid Day is approaching. Nobody wants to spend unnecessary hours doing repetitive work.

But I don’t believe speed should be the only goal. The real goal is to estimate better.

A faster estimate isn’t necessarily a better estimate if important information has been missed.

That’s why I believe an estimator needs to balance efficiency with accuracy and practical judgment.

How Assemblies Influenced Best Bid

Years later, when I was developing Best Bid Electrical Estimating Software, those early lessons were still influencing my thinking.

I wanted the software to reflect the way an experienced estimator thinks about a project.

An Electrical Estimator needs to deal with quantities, labor, materials, assemblies, pricing, and reports. Those things need to work together rather than exist as disconnected pieces.

That’s why I’ve always viewed estimating software as a tool for the estimator rather than a replacement for the estimator.

The software can help organize information. It can reduce repetitive work. It can improve consistency. But the experience still has to come from the person preparing the estimate.

What Assemblies Taught Me

The biggest lesson assemblies taught me wasn’t actually about assemblies. It was about continuous improvement.

I learned that I don’t have to create a perfect system on the first attempt. I need to create something useful, use it, see what happens, and improve it.

That same philosophy works whether I’m building an assembly, reviewing an Electrical Estimating Report, training an estimator, or developing software.

Do the work. Measure the result. Learn from it.

Improve the process. Then do it again.

My Best Bid Rules

Build systems that can improve. Don’t create an estimating process that depends entirely on memory.

Track your results. Your completed projects contain information that can make future bids better.

Study historical data. Actual results are more useful than assumptions alone.

Learn from mistakes. A mistake becomes valuable when it changes what you do next time.

Don’t confuse speed with quality. The objective isn’t simply to finish the estimate faster. It’s to produce a better estimate efficiently.

Keep improving. Even a good estimating system can become better with better information.

For contractors and estimators who want to strengthen their fundamentals, I also believe education has an important place in the process. The Electrical Estimating Online School provides another resource for developing practical estimating knowledge and applying it to real work.

Electrical estimator organizing labor and materials into complete electrical assemblies for more consistent estimates.

Frequently Asked Questions

What is an assembly in Electrical Estimating?

I use an assembly to represent a complete electrical installation by combining the materials and labor associated with that installation.

Why are assemblies useful to an Electrical Estimator?

Assemblies help me improve consistency and reduce repetitive estimating work while keeping the focus on how an installation will actually be performed.

How can historical data improve electrical estimates?

I can compare previous estimates with actual project results and use those lessons when preparing future bids.

Should I use old assembly information on every new project?

No. I use historical information as a starting point, not as an automatic answer. Every project has different conditions.

How can an Electrical Contractor learn from completed projects?

I recommend reviewing what was estimated against what actually happened. Labor, material usage, production, and unexpected conditions can all provide useful information.

Can Estimating Software help manage assemblies?

Yes. Estimating Software can help organize, reuse, and maintain assemblies along with their associated labor and material information.

What is the biggest lesson I learned from using assemblies?

For me, the biggest lesson is that Electrical Estimating should be a continuous improvement process. Every project gives me information that can help make the next estimate better.

My Final Reflection

When I first learned about assemblies, I thought I had discovered a better way to estimate. What I really discovered was a better way to learn.

Assemblies made me stop looking only at individual pieces and start thinking about complete installations. They encouraged me to capture information from completed projects instead of allowing those lessons to disappear. They showed me that historical data could strengthen experience and that mistakes could become useful feedback.

Those lessons eventually influenced much more than the way I prepared an estimate. They influenced how I thought about systems, management, training, operations, and software development.

After more than 50 years in the electrical industry, I still believe the best estimators are students of their own work. Don’t just finish a project and move on. Look at what happened.

Ask why it happened. Capture the lesson and use it.

The goal isn’t simply to estimate faster.

The goal is to estimate better.

That’s what assemblies taught me, and it’s a lesson I still use today.

If you’d like to discuss your Electrical Estimating process or learn how Best Bid can help you organize your estimating work, please call me at 800-941-7028. I’m always interested in hearing from electrical contractors, estimators, and project managers about the practical challenges they face when preparing bids.

You can also learn more about Steve Griffin and my experience in the electrical estimating industry.

About Steve Griffin

Steve Griffin

Founder of Best Bid Electrical Estimating Software

Electrician • Estimator • Contractor • Author • Software Developer

From digging ditches in 1973 to creating one of the industry’s longest-running electrical estimating software systems, Steve Griffin has spent more than 50 years helping contractors win more work and make more money.

Electrical Estimating Assemblies: The Ultimate Balancing Act Between Speed and Accuracy

Electrical estimator using assemblies to improve the estimating process





Electrical Estimating Assemblies: The Ultimate Balancing Act Between Speed and Accuracy | Steve Griffin


















Estimating Philosophy  ·  Series Part 8 of 30

Electrical Estimating Assemblies: The Ultimate Balancing Act Between Speed and Accuracy

Assemblies are the most powerful tool in electrical estimating — and the most misunderstood.
Steve Griffin explains how to build and use them to win more profitable work.

By Steve Griffin  ·  Founder, Best Bid Electrical Estimating Software
 ·  July 23, 2026  ·  8 min read

📖 Part of the Complete Series
This article is Series Part 8 of 30 in The Art of Balance in Electrical
Estimating Software
— the complete 30-section philosophy guide by Steve Griffin. Read all
sections in one
place.

Section 8: Assemblies: The Ultimate Balancing Act

Assemblies are one of the most powerful tools in electrical estimating. They are also one of the biggest
sources of imbalance. Assemblies can save enormous amounts of time.

They can increase accuracy. They can reduce
thinking. They can eliminate mistakes.

They can simplify workflow.

But assemblies can also create confusion. Assemblies can create clutter. Assemblies can create complexity.
Assemblies can create frustration.

Some companies brag about having 50,000 assemblies.

That sounds impressive — until you try to find the one you need.

Imagine searching through 50,000 assemblies just to find:

1/2" EMT with 3 #12 THHN conductors

It’s not helpful. It’s not efficient. It’s not practical. It’s not balanced.

More assemblies are not always better.

Balance is having:

  • Enough assemblies to cover real world work
  • Not so many that the user gets lost
  • Assemblies that are practical
  • Assemblies that are realistic
  • Assemblies that are actually used
  • Assemblies that reflect real installations
  • Assemblies that match field conditions

Quality matters more than quantity.

An assembly should be:

  • Accurate
  • Practical
  • Useful
  • Realistic
  • Efficient
  • Easy to find
  • Easy to understand
  • Easy to modify

An assembly should not be:

  • Overly detailed
  • Overly complex
  • Overly specific
  • Overly theoretical
  • Overly rigid
  • Overly rare
  • Overly niche

Balance is designing assemblies that reflect real world electrical work — not theoretical electrical work.

Another mistake companies make is creating assemblies that are too detailed. They include every screw. Every
staple.

Every connector. Every strap. Every washer.

Every tiny part. Every tiny detail.

But does that help the estimator? Usually not.

It slows down the software. It slows down the workflow. It slows down the estimate. It slows down the user.

Balance is choosing the right level of detail — not maximum detail.

Assemblies should be detailed enough to be accurate — but simple enough to be fast.

Assemblies should be flexible enough to adapt — but structured enough to be reliable.

Assemblies should be powerful enough to save time — but simple enough to understand.

Balance is designing assemblies that help the estimator — not assemblies that impress the developer.

Another important point: assemblies should not require constant modification. They should not require constant
adjustment. They should not require constant correction. They should not require constant thinking.

Assemblies should work out of the box. Assemblies should reflect common installations. Assemblies should
reflect common materials.

Assemblies should reflect common labor. Assemblies should reflect common field
conditions.

Balance is designing assemblies that feel natural — not assemblies that feel forced.

The best assemblies are the ones the estimator never has to think about. The best assemblies are the ones that
feel automatic. The best assemblies are the ones that feel obvious. The best assemblies are the ones that feel
right.

Balance is the difference between an assembly library that helps the estimator — and an assembly library that
overwhelms them.

Key Principle

The principle in this section is one of 30 that together form a complete philosophy of electrical estimating
— built from 50 years of real-world experience bidding and winning electrical work. Every principle connects
to every other. Master them together.

Frequently Asked Questions

Questions electrical contractors ask about
electrical estimating assemblies.

What does this principle mean for my daily estimating practice?
Every principle in this series translates directly to daily estimating decisions. The
concepts covered here affect how you set up assemblies, calibrate labor units, price materials, calculate
markup, and present your final number. Applying even one principle consistently improves the quality and
reliability of every estimate you produce.

How does electrical estimating assemblies affect bid competitiveness?
Getting this right directly affects your ability to submit bids that are both accurate and
competitive. Contractors who understand and apply this principle consistently win more profitable work because
their numbers reflect reality — not guesswork, not padding, and not systematic error. Bid competitiveness is
ultimately a function of estimating discipline.

Does Best Bid Electrical Estimating Software support this approach?
Yes. Best Bid Next Generation was designed with all 30 principles in this series in mind.
Every feature, every assembly structure, every reporting tool reflects the philosophy Steve Griffin developed
over 50 years of real-world estimating. The software is the philosophy made practical.

How do I apply this to a real electrical project estimate?
Start by evaluating your current estimating process against the principle described in this
article. Identify where your workflow drifts away from the principle — whether in assembly calibration, labor
unit selection, overhead allocation, or markup calculation. Each gap is an opportunity to tighten your process
and protect your margin on the next bid.

Where can I read all 30 principles together?
All 30 sections are published together in the complete guide: The Art of Balance in Electrical Estimating Software. Reading
the full guide gives you the complete picture of how each principle connects to the others and why the whole
is greater than the sum of its parts.


The First Time I Won a Big Job — The Breakthrough Every Estimator Remembers

Electrical estimator preparing to win a major electrical construction project

Electrical Estimating Philosophy · Series Part 7 of 56

I remember sitting with my estimate in front of me and looking at the number one more time before Bid Day was over. I had already checked it, then checked it again. The drawings had been studied, quantities reviewed, labor considered, and materials worked through. At that point, there wasn’t much left to do except trust the work I had put into the estimate.

This wasn’t a small electrical project. It was the first big job where I really felt the weight of the number I was submitting. I knew that if I won, the estimate would eventually become a real project with real electricians, real materials, real labor, and real costs.

If I was wrong, I wasn’t going to discover that mistake on a piece of paper. I was going to discover it on the jobsite.

When I found out I had won, I was excited. But I also remember thinking, “Now I have to build it for that number.”

That thought probably taught me more about Electrical Estimating than the actual moment of winning.

A Big Job Changes the Pressure

Before that project, I had already estimated plenty of electrical work. I understood how to read drawings, count quantities, calculate material, estimate labor, and put together a bid. But a large project brings a different kind of pressure because every mistake gets bigger along with the job.

I took that estimate seriously. I went through the drawings carefully and tried to think beyond what I was seeing on the page. How difficult would the installation be?

How much labor would the work really require? Were there areas where access could slow the crew down? Were my material quantities realistic?

I’ve always believed an Electrical Estimator needs to understand where the numbers come from. A final total doesn’t mean much if you can’t explain how you arrived at it.

Bid Day Can Make You Second-Guess Yourself

Anyone who has worked on Bid Day knows the feeling. You’ve spent days working on an estimate, the deadline is getting close, and suddenly you start questioning everything.

Did I miss something? Is my labor too low? Did I carry enough wire? What if another contractor is lower?

I’ve felt that pressure many times.

The lesson I learned was that preparation gives you something to fall back on. Confidence doesn’t mean believing you’re never going to make a mistake. I’ve made plenty of them over more than 50 years in this business. Confidence means knowing you’ve done your homework and understanding why your number is what it is.

If I found a real error, I corrected it. But I didn’t want to change a sound estimate just because I was nervous.

Winning the Job Is Only the Beginning

The moment I learned I’d won that first big job was exciting, but the real test came afterward.

The estimate had to become a project.

The conduit had to be installed. The wire had to be pulled. Boxes, fixtures, panels, devices, and equipment had to be installed. The labor hours I had allowed had to be enough to get the work done.

That’s when you find out what your estimate is really worth.

My years working in the field helped me understand this. When you’ve actually installed electrical work, you look at drawings differently. You start thinking about access, material handling, installation difficulty, coordination, sequencing, and productivity.

Those details can make a major difference between an estimate that looks good on paper and one that works in the field.

I Learned From What Happened After the Bid

I’ve never believed that an estimator should simply submit a bid and move on.

A completed project gives you valuable information.

If the labor took longer than expected, I wanted to know why. If material usage was higher than I estimated, I wanted to understand what caused it. If something went exactly as planned, I wanted to remember that as well.

Every project became another lesson.

That’s how estimating judgment develops. You begin recognizing patterns and understanding which assumptions are reasonable and which ones deserve another look.

I’ve made mistakes throughout my career, but I’ve tried not to make the same mistake twice.

The Lowest Number Isn’t Always the Best Number

Winning a big job can make you feel successful, but I’ve learned that winning isn’t simply about being the lowest bidder.

A contractor can win a project and still lose money.

I’ve seen what happens when an estimate doesn’t properly account for labor, materials, or project risks. Getting the contract doesn’t help much if the number doesn’t give you a reasonable opportunity to make a profit.

That’s why I always ask myself two questions: Can I win this job, and can I build it profitably for the number I’m submitting?

Both questions matter.

Where Estimating Software Helps

When I started in the electrical industry in 1973, much of my estimating work was manual. I’ve watched technology completely change the way contractors prepare bids.

Today, Best Bid Electrical Estimating Software can help organize quantities, assemblies, labor, materials, and pricing while reducing repetitive work.

But I’ve never believed software replaces an experienced Electrical Estimator.

Software can help organize the information, but somebody still has to understand the project. You still need to recognize unusual conditions, question questionable quantities, and understand whether the labor makes sense.

That’s why I see technology as a tool that supports experience rather than replacing it.

The Lesson That Stayed With Me

That first big job changed the way I looked at myself.

Before I won it, I wondered whether I was ready for a project of that size. Afterward, I knew I could handle something bigger than I had handled before.

That didn’t mean I stopped learning. In fact, it made me realize how much more there was to learn.

That’s also part of the reason I wrote The Electrical Estimator’s Guide to Winning More Bids and Making More Money. I wanted to put practical lessons from my years as an electrician, estimator, and contractor into something other people in the industry could use.

I’ve learned that experience isn’t simply the number of years you’ve been doing something. It’s what you learn from those years.

What I Would Tell a New Estimator

If you’re a new Electrical Estimator and you’re waiting for your first big win, don’t worry about trying to feel completely confident before you submit the bid.

Instead, prepare.

Study the drawings. Check your quantities. Understand your labor.

Review your material. Think about how the work will actually happen on the jobsite. Question your assumptions, and learn from every project you complete.

Then, when you’ve done the work, trust your preparation.

My first big job taught me that confidence doesn’t come from guessing. It comes from knowing you’ve done everything you reasonably can to understand the project.

I’ve won many jobs since then, and I’ve lost plenty, too. That’s part of being an Electrical Contractor. But that first big win remains special because it was the moment I realized I could compete for bigger work and stand behind my estimate.

If you’d like to improve your Electrical Estimating process, prepare more confidently for Bid Day, or learn more about Best Bid, contact me at 800-941-7028. I’m always glad to hear from electrical contractors and estimators who are looking for practical ways to improve their estimating process and win more profitable work.

Frequently Asked Questionsre

1. What makes winning a first big electrical job so important?

For me, it was important because it proved that my preparation and estimating process could handle a larger project. It gave me confidence based on experience rather than simply hope.

2. How can an Electrical Estimator prepare for Bid Day?

I recommend carefully reviewing drawings, quantities, labor, materials, project conditions, and assumptions before the deadline. Good preparation makes it easier to trust your final number.

3. Should an Electrical Contractor always try to be the lowest bidder?

No. I believe the goal is to submit a competitive bid that can also be completed profitably. The lowest number isn’t necessarily the best business decision.

4. Why is jobsite experience valuable in Electrical Estimating?

Jobsite experience helps an estimator understand how drawings translate into actual work. Installation difficulty, access, productivity, coordination, and material handling can all affect project costs.

5. Can Estimating Software replace an Electrical Estimator?

I don’t believe it can. Software can organize information and reduce repetitive work, but an experienced estimator still needs to understand the project and make sound judgments.

6. How can estimators learn from completed projects?

I compare estimated labor and material with what actually happened. Understanding where the estimate differed from reality helps me make better decisions on future projects.

7. What is the biggest lesson from winning a first big job?

For me, the biggest lesson was that confidence comes from preparation. You don’t need to know everything, but you need to understand your estimate well enough to stand behind it.

My Final Takeaway

When I think about that first big job, I don’t just remember winning the contract. I remember the responsibility that came with it.

Winning gave me confidence, but building the project taught me even more.

After more than 50 years in this industry, I still believe the best estimators never stop learning. Every bid teaches you something. Every jobsite teaches you something. Every mistake can teach you something.

My advice is simple: do the work, know your numbers, learn from your projects, and trust your preparation.

That’s what turned my first big bid from a moment of uncertainty into one of the most important breakthroughs of my estimating career.

About Steve Griffin

Steve Griffin
Founder of Best Bid Electrical Estimating Software
Electrician • Estimator • Contractor • Author • Software Developer

From digging ditches in 1973 to creating one of the industry’s longest-running electrical estimating software systems, Steve Griffin has spent more than 50 years helping contractors win more work and make more money.

Electrical Estimating Software Features: Power vs. Bloat | Steve Griffin

Electrical estimating software features for contractors





Electrical Estimating Software Features: Power vs. Bloat | Steve Griffin



















Estimating Philosophy  ·  Series Part 7 of 30

Electrical Estimating Software Features: Power vs. Bloat — What You Actually Need

More features are not always better. Steve Griffin identifies which electrical estimating
software features actually win jobs — and which ones just bloat the price.

By Steve Griffin  ·  Founder, Best Bid Electrical Estimating Software
 ·  July 23, 2026  ·  8 min read

📖 Part of the Complete Series
This article is Series Part 7 of 30 in The Art of Balance in Electrical
Estimating Software
— the complete 30-section philosophy guide by Steve Griffin. Read all sections in one
place.

Section 7: Features: Power vs. Bloat

Features are one of the biggest balancing points in electrical estimating software. They are also one of the
most misunderstood. Many people assume that more features automatically make software better.

They assume that
more features equal more power. They assume that more features equal more capability. They assume that more
features equal more value.

But features are not free. Features have cost. Features have weight. Features have consequences.

The more features you add:

  • The higher the price
  • The harder the learning curve
  • The slower the software becomes
  • The more overwhelming the interface becomes
  • The more confusing the workflow becomes
  • The more training the user needs
  • The more support the company must provide

Some features are essential. Some features are helpful. Some features are fluff. Some features are harmful.

Unused features:

  • Look great in advertising
  • Add cost
  • Slow down the software
  • Increase training time
  • Confuse users
  • Create clutter
  • Distract from core functionality

Balance means including features that estimators actually use — not features added just to impress.

One of the biggest mistakes software companies make is designing features for marketing instead of designing
features for users. They want big numbers. They want long lists.

They want flashy demos. They want impressive
screenshots. They want features that sound good, even if they don’t help the estimator.

But estimators don’t care about marketing. Estimators care about workflow.

They care about speed. They care about accuracy. They care about simplicity.

They care about reliability. They
care about trust.

A feature that slows down the estimator is not a feature — it is a liability.

A feature that adds complexity without adding value is not a feature — it is a burden.

A feature that looks good in a demo but never gets used in real life is not a feature — it is noise.

Balance is choosing features that matter.

Features that save time. Features that increase accuracy. Features that reduce thinking.

Features that
eliminate mistakes. Features that simplify decisions. Features that improve workflow.

Features that support real
world estimating.

Everything else is clutter.

Another mistake is assuming that advanced features equal advanced users. In reality, advanced users often
prefer simplicity. They prefer speed.

They prefer clarity. They prefer tools that help them think less, not
more.

Balance is designing features that help both beginners and experts.

A feature should not require training to understand. A feature should not require documentation to use. A
feature should not require support to troubleshoot. A feature should not require memorization to operate.

A feature should feel natural. A feature should feel intuitive. A feature should feel obvious. A feature should
feel helpful.

Balance is designing features that feel like part of the workflow — not interruptions to the workflow.

Another important point: features should not compete with each other. They should not overlap. They should not
conflict.

They should not create redundancy. They should not create confusion.

Balance is designing features that work together — not against each other.

The best software has fewer features — but better features. The best software has simpler features — but
smarter features. The best software has cleaner features — but more powerful features.

Balance is the difference between power and bloat.

Key Principle

The principle in this section is one of 30 that together form a complete philosophy of electrical estimating
— built from 50 years of real-world experience bidding and winning electrical work. Every principle connects
to every other. Master them together.

Frequently Asked Questions

Questions electrical contractors ask about
electrical estimating software features.

What does this principle mean for my daily estimating practice?
Every principle in this series translates directly to daily estimating decisions. The
concepts covered here affect how you set up assemblies, calibrate labor units, price materials, calculate
markup, and present your final number. Applying even one principle consistently improves the quality and
reliability of every estimate you produce.

How does electrical estimating software features affect bid competitiveness?
Getting this right directly affects your ability to submit bids that are both accurate and
competitive. Contractors who understand and apply this principle consistently win more profitable work because
their numbers reflect reality — not guesswork, not padding, and not systematic error. Bid competitiveness is
ultimately a function of estimating discipline.

Does Best Bid Electrical Estimating Software support this approach?
Yes. Best Bid Next Generation was designed with all 30 principles in this series in mind.
Every feature, every assembly structure, every reporting tool reflects the philosophy Steve Griffin developed
over 50 years of real-world estimating. The software is the philosophy made practical.

How do I apply this to a real electrical project estimate?
Start by evaluating your current estimating process against the principle described in this
article. Identify where your workflow drifts away from the principle — whether in assembly calibration, labor
unit selection, overhead allocation, or markup calculation. Each gap is an opportunity to tighten your process
and protect your margin on the next bid.

Where can I read all 30 principles together?
All 30 sections are published together in the complete guide: The Art of Balance in Electrical Estimating Software. Reading
the full guide gives you the complete picture of how each principle connects to the others and why the whole
is greater than the sum of its parts.


The Electrical Estimating Mistake That Cost Me Everything

electrical estimating software, electrical estimator, electrical estimating, electrical bid mistakes, electrical bidding software, electrical estimate accuracy

Rushing an electrical estimate without verifying labor and material costs is one of the most common—and costly—mistakes a contractor can make. Underbidding a job means every missed dollar comes directly out of your profit margin, not the client’s pocket. The fix: break estimates into smaller components, double-check your numbers, and use a reliable system before bid day.

I lost real money on a job early in my career. Not a rounding error. Not a small miscalculation I could absorb.

A genuine financial hit that came straight out of my pocket. And I’ve thought about it for 50 years.

That’s the kind of lesson that sticks.

What Went Wrong on That First Big Mistake

I underbid the job. Plain and simple. I didn’t account for all the labor.

I missed materials. I rushed through the estimate because I was eager to win the bid, and I let confidence override careful attention to detail.

There was no one else to blame. I moved too fast, didn’t double-check my numbers, and paid the price for it.

Here’s what made it worse: I didn’t even realize the full extent of the mistake until I was already on the job. By then, it was too late. You can’t go back to a client and renegotiate after you’ve signed the contract.

Why Estimating Mistakes Hit Your Bottom Line Directly

Every dollar you miss in an electrical estimate comes out of your profit margin—not overhead, not contingency. Your profit.

That realization changed everything for me. I had been treating estimating like a formality, something you did to get to the work. That first loss taught me it was the work.

Getting the estimate right is the whole game. You can run a flawless installation and still lose money if the numbers going in were wrong.

Winning the bid only matters if you win it profitably. That’s a lesson I cover extensively in my book, Everybody Has A First: “Lessons from a Lifetime in Electrical Contracting and Business” — because it’s one of the truths that took me years and real dollars to fully understand.

How That Loss Changed the Way I Estimate

After that job, I started tracking everything. Every line item. Every labor hour.

Every spool of wire. I reviewed completed jobs to find exactly where I was losing money, and I started breaking estimates down into smaller, verifiable components instead of working from rough mental totals.

That discipline is exactly why I eventually built Best Bid Electrical Estimating Software. I wanted a system that would catch the kinds of calculation errors that cost me that job—something organized, accurate, and built by an electrical contractor who had actually sat through bid day and felt the sting of getting it wrong.

Key Lessons for Every Electrical Estimator

If you take nothing else from this, take these four things:

  • Never rush an estimate. The eagerness to win a bid is understandable. Letting that eagerness override accuracy is how you lose money.
  • Break your estimate into components. A single lump-sum guess is not an estimate. Verify labor and materials at every phase.
  • Use software that keeps you organized. Electrical estimating software like Best Bid exists to catch the errors your eyes miss after hours of working through a bid.
  • Review every finished job. The numbers you track after the job are the education you use on the next one.

That Mistake Made Me a Better Estimator

I’m not grateful it happened, but I’m glad I paid attention when it did. That one job gave me a discipline I’ve carried for over 50 years. It taught me that estimating is a skill—one you build deliberately, with systems, with humility, and with a commitment to getting the numbers right before bid day, not after.

Your estimating mistakes don’t have to be expensive. They just have to teach you something.

Electrical estimator reviewing labor and material costs to prevent missed expenses from reducing project profit.

Ready to tighten up your electrical estimates? At Best Bid, we work directly with electrical contractors and estimators to help them price work with confidence and win jobs profitably. Call us at 800-941-7028 or visit bestbidestimating.com to schedule a walkthrough—no sales pressure, just straight answers.

Frequently Asked Questions

Rushing through an estimate without fully accounting for labor and material costs. Speed and confidence are valuable, but not at the expense of accuracy. Every missed dollar reduces your profit margin directly.

Electrical estimating software like Best Bid Electrical Estimating Software organizes your estimate into structured components, flags calculation errors, and tracks labor and material costs systematically—reducing the chance that a critical line item gets missed before bid day.

Because when you underbid, the shortfall comes out of your profit, not your overhead recovery. Overhead is already built into your pricing structure. A missed labor or material cost has nowhere to go except your bottom line.

Steve Griffin
Founder of Best Bid Electrical Estimating Software
Electrician • Estimator • Contractor • Author • Software Developer

From digging ditches in 1973 to creating one of the industry’s longest-running electrical estimating software systems, Steve Griffin has spent more than 50 years helping contractors win more work and make more money.

Accuracy vs. Practicality in Electrical Estimating: What Level of Detail Actually Matters

Electrical estimator reviewing quantities for an electrical project





Accuracy vs. Practicality in Electrical Quantities: What Level of Detail Actually Matters | Steve Griffin<br />


















Estimating Philosophy  ·  Series Part 6 of 30

Accuracy vs. Practicality in Electrical Quantities: What Level of Detail Actually Matters

False precision wastes time and rarely improves your bid. Steve Griffin explains the right level of
quantity detail for competitive, profitable electrical estimating.

By Steve Griffin  ·  Founder, Best Bid Electrical Estimating Software
 ·  July 23, 2026  ·  8 min read

Part of the Complete Series
This article is Series Part 6 of 30 in The
Art of Balance in Electrical Estimating Software
— the complete 30-section philosophy guide by Steve
Griffin. Read all sections in one place.

Section 6: Accuracy vs. Practicality in Quantities

Quantity accuracy is another balancing act.

Take lighting assemblies:

  • If each light gets a box and cover, you will always have enough.
  • In some cases, you may have more than enough.
  • In rare cases, two lights share one box.

Is it worth the time to enter the exact number of boxes and covers?

Or is it better to enter one per light and move on?

Balance is choosing the method that saves time without risking the final number.

Manual thinking should be spent on expensive items — not low cost materials.

Estimators often chase perfect quantities. They want exact numbers. They want exact counts.

They want exact
materials. They want exact assemblies. They want exact labor.

But exactness is not always accuracy. Exactness is time.

Accuracy is reliability. Accuracy is practicality. Accuracy is consistency. Accuracy is profitability.

Balance is knowing when “close enough” is actually better than “perfect.”

If you spend time entering exact quantities for low cost materials, you slow down the estimate. You increase
thinking. You increase decisions. You increase complexity.

But does it change the final number? Usually not.

Balance is choosing the right level of detail — not maximum detail.

Key Principle

This principle is one of 30 that together form a complete philosophy of electrical estimating built from 50
years of real-world experience. Every principle connects to every other. Read the full
guide
to
see how they work together.

Frequently Asked Questions

How accurate do electrical quantities need to be in an estimate?
Practical accuracy is the goal — not mathematical precision. Quantities need to be accurate
enough that the final number protects your profit margin and is competitive in the market. Counting individual
wire nuts on a commercial project produces false precision that consumes time without improving bid quality.

What is the difference between precision and accuracy in electrical estimating?
Precision is how many decimal places you calculate. Accuracy is whether your final number
reflects reality. An estimate can be precise but inaccurate — calculated to the penny but missing a major cost
category. And it can be accurate but imprecise — rounded numbers that still land within the real cost range.
Accuracy is what matters; precision is just a tool.

How do assemblies improve electrical quantity accuracy?
Assemblies package material quantities with labor, eliminating the need to separately count
every component. A well-calibrated assembly reflects real-world installation conditions including waste
factors, connection hardware, and typical layout patterns. That built-in reality is more accurate than manual
counting because it reflects how the work is actually performed.

What are the most commonly missed quantities in electrical estimating?
Commonly missed quantities include wire terminations, junction boxes, support hardware, conduit
fittings, device covers, wire management accessories, and startup and testing labor. These items are easy to
overlook during takeoff but add up to meaningful cost on larger projects. Good assemblies capture them
automatically as part of standard scope.

When is extra quantity detail worth the time investment?
Extra detail is worth it when the scope is unusual, when the bid is very large, when competition
is known to be tight, or when the project involves significant material cost exposure such as copper-heavy
feeder runs. On standard commercial work with well-calibrated assemblies, additional counting time rarely
improves the final number enough to justify the investment.