How to price equipment costs into a construction job
Price owned equipment with an hourly rate that covers both ownership cost (depreciation, financing, insurance, storage) and operating cost (fuel, maintenance, repairs, wear), then multiply by the hours the job needs. Price rented equipment at the full delivered cost, not just the rate on the quote.
Review invoices, committed costs, and cash timing together before making project decisions. AI-generated illustration.
To price equipment into a construction job, give every owned machine an hourly rate equal to its yearly ownership cost plus its operating cost, divided by the hours it actually works in a year. Multiply that rate by the hours the estimate needs, then add mobilization, demobilization, and the operator as separate lines. For rented equipment, use the full cost: rental rate, delivery and pickup, fuel, damage waiver, and any minimum charges. Either way, the equipment cost lands on the job as a direct cost, not buried in overhead.
Many small contractors charge nothing for equipment they own outright because "it's paid for." The machine is still wearing out, still insured, still parked somewhere. When it dies, the replacement has to come from job profits that never accounted for it.
What goes into an equipment rate
Federal cost rules for construction equipment are a useful checklist even on private work. FAR 31.105(d)(2) separates ownership and operating costs, lists operating allowances such as fuel, filters, oil, grease, servicing, repairs, maintenance, and tire wear, and notes that labor, mobilization, demobilization, overhead, and profit are generally not part of the equipment rate and need separate consideration. It also names the U.S. Army Corps of Engineers equipment schedule as an example of a predetermined rate schedule a contracting agency may specify.
Equipment cost components
Category
Includes
Priced as
Ownership
Depreciation, interest or cost of capital, insurance, registration and taxes, storage
Annual cost ÷ annual working hours
Operating
Fuel, oil, filters, grease, servicing, repairs, tires or tracks
Cost per operating hour
Kept separate
Operator labor, hauling to and from the site, overhead, profit
Own estimate lines
How to build an hourly equipment rate
1. Estimate annual working hours honestly
Use hour meter readings and your equipment log, not the hours you wish the machine ran. Utilization is the biggest single driver of the rate. A machine that works half as many hours carries twice the ownership cost per hour.
2. Calculate yearly ownership cost
Depreciation is purchase price minus expected resale value, divided by years you plan to keep it. Add a cost of capital on the average investment (the interest you pay, or what the money would earn elsewhere), plus annual insurance, registration, and a share of yard or shop cost.
3. Calculate operating cost per hour
Fuel burn per hour times your fuel price, plus maintenance and repairs per hour from your service records, plus tire or track wear. If you have no history, start with the manufacturer's service intervals and parts prices and refine it after a season.
4. Add them and set the rate
Ownership per hour plus operating per hour is your cost rate. Some contractors also set a lower standby rate for days the machine sits on site but does not run, which covers ownership but not fuel or wear. FAR 31.105 uses a similar idea for suspended work on federal jobs, capping ownership allowances at a standby amount.
5. Charge it to jobs the same way you priced it
Post equipment hours to each job's equipment cost code at the internal rate, offsetting an equipment income or recovery account. At year end, compare what the rates recovered to what the fleet actually cost. If recovery runs short, the rates or the utilization assumption were wrong.
Worked example: a compact track loader
Say a sitework contractor owns a track loader. All figures are illustrative; plug in your own.
Cost of capital (7% on $44,000 average investment)
$3,080
$3.08
Insurance and registration
$1,800
$1.80
Yard and storage share
$600
$0.60
Fuel (2 gallons an hour at $4.00)
$8.00
Maintenance and repairs
$6.50
Tracks and wear parts
$2.00
Total cost rate
$31.58
A grading job needs about 120 machine hours, so equipment cost is roughly $3,790. Add two trailer hauls for mobilization and demobilization at, say, $350 each, and the operator at the burdened labor rate as its own line. Overhead and profit go on top of all of it.
Now say the loader only works 500 hours a year. Ownership cost per hour doubles from $15.08 to $30.16 and the total rate climbs to about $46.66. At that utilization, renting for the jobs that need it may cost less than owning. When to buy vs rent construction equipment walks through that decision.
Pricing rented equipment
Rental quotes look simple and rarely are. Price the equipment rental rate at the increment you will actually use (daily, weekly, or monthly), then add delivery and pickup, fuel or refueling charges, damage waiver or your own insurance, environmental or service fees on the quote, and a buffer if the schedule could slip into another rental period. Track it against the purchase order so off-rent calls happen on time. See how to manage equipment rental costs.
Where equipment rates show up after the bid
The rate is only useful if field hours get recorded against it. Have operators or foremen log machine hours by job and cost code on the daily report, the same way they log labor. Hour meter readings at the start and end of each week catch the gaps. When a machine moves between two jobs in one day, split the hours rather than charging the whole day to whichever job it ended on.
Review the rates once a year with actual fleet costs from the books. Fuel prices, insurance renewals, and a bad repair year can each move the operating side by a few dollars an hour. On change orders and T&M work, use the same internal rate plus markup so extra work recovers equipment the way base-bid work does. Keeping one rate sheet for estimating, job costing, and change orders avoids arguments later about which number was right.
Mistakes to avoid
Charging nothing for paid-off equipment. It still costs money to insure, store, repair, and eventually replace.
Using a rental company's rate for owned equipment. It includes their overhead and profit. Use your own cost and add your markup once.
Leaving mobilization out. Two hauls on a small job can cost more than the machine hours.
Rolling equipment into overhead. Then every job carries the excavator, including the interior finish jobs that never saw it.
Never checking recovery. If the fleet cost $90,000 last year and jobs were charged $60,000, $30,000 of cost hid in overhead.
Smart Business Automator tracks job costs by code, including equipment, and shows them in job costing and WIP views next to labor and materials. See job costing and WIP automation.
Frequently asked questions
Should equipment be a direct cost or overhead?+
Equipment used on a job should be charged to that job as a direct cost at an hourly or daily rate. Only equipment that supports the whole company, like a shop forklift, belongs in overhead.
Is the operator included in the equipment rate?+
Usually not. Most contractors price the operator as labor at a burdened rate on a separate line. FAR 31.105 also treats labor as separate from equipment ownership and operating costs.
What is a standby rate for equipment?+
A standby rate is a reduced rate for days a machine is on site but idle. It typically covers ownership costs but not fuel, maintenance, or wear, since the machine is not running.
Can I use a published equipment rate schedule?+
On some public contracts the agency specifies one. FAR 31.105 names the U.S. Army Corps of Engineers construction equipment schedule as an example. On private work, your own cost-based rate is usually more accurate for your fleet.
The path from $500,000 to $2 million is not simply four times more work. It is the stage where memory, text messages, owner approvals, and disconnected spreadsheets begin to fail.
This New Guard Growth Playbook maps the first five operating systems an owner-led contractor needs: lead intake and qualification, estimate-to-job handoff, crew planning and field feedback, cash and WIP visibility, and employee and compliance control. The revenue figures are illustrative milestones—not a promise, benchmark, or universal path.
Starts muted when the player comes into view.
Read the full episode transcript
Published transcript from Scaling Legends. It may contain transcription errors. View the source transcript.
overbilling combined with margin fade. Because when you put those two together, they create this highly misleading picture of financial health. It acts as a silent killer of job profitability, really, where a company looks cash rich on paper, but they're actually bleeding out. Bleeding out behind the scenes. Yeah. And that dynamic and really how to survive it is the core of what we're analyzing today. Right. So welcome to this AI -assisted scaling legends decision briefing. This is produced by Smart Business Automator using the sources linked in our show notes. And Smart Business Automator designs AI and... Before we really get into it, I just need to state that this briefing is for educational and informational purposes only. It is not legal, financial, tax, safety or professional advice. Right. Always
consult your own professionals. Yes, definitely. So our mission for this deep dive is laser -focused. We are analyzing the crucial operational gap between the illustrative revenue milestones of, say, $500 ,000 and $2 million for owner -led specialty contractors. Yeah, and that $500K to $2 million range, it is such a critical vulnerability zone. It really is. What's fascinating about this... specific jump in revenue is that scaling is not simply just doing four times more work. Right. It's the exact stage where the old ways of doing things, relying on memory or sending a quick text message to solve a problem. Oh, yeah. Requiring the owner's personal approval for just everything and using disconnected spreadsheets. All of that mathematically begins to fail. It just falls apart. And the people who own this
problem, the ones who are feeling the pain of this bottleneck most acutely right now, they're the owners, the CEOs, COOs, project executives who are tuning in. Like, if you are listening to this and you're in that revenue gap, you know this pain. Oh, for sure. Because if we look at this from a systems perspective, it makes total sense why it breaks. Relying on owner memory during rapid growth, it's kind of like trying to upgrade a computer's processor while you leave a tiny, overheating hard drive in place. I like that, yeah. Like your processor is churning through new jobs, it's fielding new crews, generating new revenue. But the hard drive, which is the owner's brain, it can only store and retrieve so much data at once. Right. Eventually, the whole system crashes from information overload.
That is a very accurate way to picture it. And when that metaphorical hard drive gets full, what breaks first is the fundamental mechanism of control within the business. Okay, so what breaks? Well, the central thesis is that revenue growth must trigger a redesign of work, information, and approval paths before it triggers uncontrolled hiring. Wait, wait, I want to pause on that for a second. Because that sounds counterintuitive to a lot of growing companies, I think. Yeah. Are you saying a company shouldn't just hire more people to handle the extra work if they're growing quickly? Not if the information pathways still run straight through the owner. Oh, I see. If an owner must approve every single price and, you know, assign every worker daily, chase down every missing document. Right. Hiring more people just creates more noise. The company does not
have a scalable system in that scenario. They just have a bottleneck and a severe control risk. So it just amplifies the problem. Yes. the manual process failures become very obvious very quickly. So what do those failures actually look like on the ground? What are the symptoms? We see a few distinct symptoms across the industry. For one, lost bids produce no reusable data. If a company loses a bid, the information just disappears instead of informing the next estimate. Right, it's just gone. Another symptom is that estimates live entirely in one person's head, or maybe they are locked away in a single spreadsheet on one laptop. Which is terrifying. Right. And that in the field, daily reports might describe the activity like someone might write, we poured concrete today. Right. Super vague. Yeah. Yeah.
But they fail to capture the installed quantities or document changed work. And because of all this, the owner only learns about lost production after payroll is run or at month end. Oh, man. I think it is crucial to reframe how we look at those symptoms because, you know, it's really easy to just blame the staff, right? Like, oh, my guys aren't communicating. But those are not people failures. Like a superintendent failing to text the owner about a material delay, that is a data handoff failure. Without established rules for how data moves, exceptions can't be flagged automatically. So this means the owner has to sift through everything. I'm talking every single email, every text message, every invoice. just to find where the problems are. Which is an impossible task for one person as the project
volume multiplies. Right. It just doesn't scale. Yeah. So because manual handoffs are failing at this revenue milestone, we need to transition into a practical automation map. Right. We have identified five operating systems required to stabilize operations and, you know, get the owner out of the bottleneck. Okay. But instead of just listing them, let's trace the actual lifecycle of a project, starting at the very beginning with system one, which is lead intake and qualification. Yeah, in the typical owner -led version, new opportunities are just a mess. A total mess, yeah. Calls come in, referrals happen out on the job site, website forms trigger emails. They all arrive in entirely different places. And the owner decides, usually just from memory, which opportunity deserves attention. And follow -up depends entirely on whether someone remembers
to make a phone call. So how does the growth stage system fix that? It shifts from that memory -based approach. to a required intake record. It applies strict go or no go rules right at the front door. Okay, so if we map the automation for that, it's actually quite straightforward. Your inputs are your calls, your digital plan rooms, your web forms. You set up rules to normalize the trade and the project size. Then the system is designed to flag exceptions. So, for instance, if a project is outside your normal service area or the client's timing is totally unrealistic, the system flags it. Instead of the owner reviewing 50 random emails to find the three good leads, the system categorizes them automatically. But just to be clear, a human still makes the final
pricing decision. And the final bid or no bid call. We are automating the routing of the information, not the strategic thinking. Right. That routing is so important. Because it leads right into the next major hurdle, which is handing the estimate over to the field. System two. In the vulnerable owner -led state. Production receives a signed contract and maybe a really short verbal explanation of the estimate from the owner. Right. Just a quick, here is what we are building kind of chat. Which is terrifying when you think about it. You're handing over a multi -hundred thousand dollar project based on a five minute conversation in a pickup truck. It creates a huge disconnect. Yeah. The problem is that verbal production handoffs lead to cost reports that just cannot explain why actual performance differs from the original
estimates. If the field does not know the specific budget assumptions, they can't possibly manage to them. Right. The growth stage system fixes this by requiring an approved estimate version and a baseline job budget that can actually be compared with committed costs. And this is where we really need to talk about cost codes. because they are the secret language of this handoff. For anyone unfamiliar, a cost code is basically just a bucket. You can't just say, we spent $5 ,000 on this job today. Right. What did you spend it on? Exactly. You need to know if that $5 ,000 went into the drywall bucket or the painting bucket so you can see which part of the estimate is failing. Yes. So the automation map here focuses on creating job records only from approved estimate
versions. It maps those... estimate items directly to your budget cost codes automatically. And this is where you need a forcing function. Yes. The system establishes automated alerts for missing sign -offs from the operations team. So if the contract language conflicts with the estimate or a scope item just doesn't have a budget, the system triggers an exception alert. This forces the pre -construction side and the operations side to look at the baseline together, accept it, and sign off before a single dollar is spent on the site. That alignment between the estimate and the field is vital for the next phase, which is system three. crew planning, time capture, and daily feedback. And to understand the philosophy behind this, we can actually look to the U .S. Occupational Safety and Health Administration,
or OSHA. How does OSHA tie into daily financial reporting? Well, it's about the principle of proactive management. Oh, okay. You don't merely wait around for a site inspection to find out you have a safety problem. Right, you'd be in a lot of trouble. Yeah, you identify hazards before they cause injuries. Yeah. We must apply this proactive necessity to daily field feedback regarding production. Oh, I see where you're going. You cannot wait for a month -end financial report to find out a crew was delayed on a Tuesday three weeks ago. That makes perfect sense. A delayed crew is essentially a financial hazard. Yes. And you need to spot it proactively. Right. So translating that OSHA philosophy into a workflow, the inputs are your job schedule, the time cards, and the daily reports. The automated rules validate
those time cards against the specific cost codes we talked about earlier, and they compare the planned hours versus the actual hours worked. And if there's a discrepancy. That is where the system works for you. If a daily report is missing, or if someone is logging time for work that is outside, the baseline scope, the system automatically routes a notification to the responsible supervisor. Okay. Supervision then has to explain the cause and choose the corrective action right there in the moment, rather than the owner having to track down a superintendent a whole month later to ask why payroll looked so high. Right. Which leads us directly back to the CFMA insights. Okay. Specifically regarding the financial side, which is system four, cash, billing, and work in progress. or WIP visibility. This is arguably
the most critical shift because revenue is not cash. A healthy bank balance is not proof that every job is profitable. I really want to emphasize that for the leaders listening. Having a lot of cash in the bank today, it does not mean you actually made a profit on the work you're doing. That's right. That is why WIP schedules must act as an early warning system. Let's go back to our opening warning about overbilling and margin fade. Right. The silent killer. Yeah. Overbilling often happens when a contractor bills ahead of the work actually completed. Just to stay cash positive. Yes, to stay cash positive. But what happens if estimated costs to complete the job keep rising? which is margin fade. Oh, wow. You have a highly misleading picture. Your
bank account looks full today because you overbilled. But because your profit margin is fading, you are actually going to run out of cash before the project is finished. That is a terrifying scenario to discover at the end of the month. Yeah, it really is. So the automation map here involves refreshing your financial forecasts on a defined cadence, maybe weekly. The system then ranks any exceptions by cash exposure or gross profit exposure. This ensures the executive team sees the issues while there's still time to actually act. Right. But I have to ask, how do we prevent alert fatigue here? That's a good question. Because if an owner gets a push notification every time a single dollar moves or a single hour goes over budget, they're just going to start ignoring the system entirely. That is a very real implementation risk. Yeah. Okay. You
set the thresholds. So the system only shouts when cash flow is directly threatened, severely overdue receivables, or when a cost to complete update is completely missing. Oh, I see. You automate the routine data flows, but you only alert the human when an exception requires executive judgment. That is a critical distinction for keeping the owner sane. And it applies just as much to our final operational area, System 5, which is employee and compliance control. Right. Because scaling your workforce is not just an operational challenge, it's a regulatory one. Definitely. Adding employees and crews creates legal obligations that cannot simply live in the owner's memory or, you know, on a sticky note. No, definitely not. For example, the Internal Revenue Service states that employers generally have withholding, depositing, reporting, and
payment duties for employment taxes. Right. Furthermore, if you rely on subcontractors, the U .S. Small Business Administration provides guidelines on distinguishing employees from contractors. And just as a quick reminder to our listeners, companies must always use appropriate CPA and legal professionals for the specific facts regarding their jurisdiction. We're just talking systems here. Yes, of course. But from a system standpoint, managing all of this compliance data is prime territory for automation. The inputs are your onboarding data, trade licenses, subcontractor insurance certificates. The automation calculates the lead times for license renewals. It restricts sensitive financial data access based on someone's role. And it automatically escalates expired credentials. It takes the burden
of remembering entirely off the owner. Right. So if a key subcontractor's insurance is going to expire in 30 days, the system sends them a reminder automatically. It sends another at 15 days. It only flags the owner if the exception remains unresolved at day zero. So we've outlined how to handle intake, estimating handoffs, field reporting, financial visibility, and compliance. Yeah, the five systems. These are essential. But having a theoretical map is useless without a starting point, which brings us to a major implementation risk that trips up a lot of companies transitioning past the $500 ,000 mark. Okay, so what usually goes wrong when they try to actually implement this? The primary danger is automating a vague process. If your cost codes, your status
definitions, and your approval thresholds are inconsistent across your company, meaning project manager A does it differently than project manager B, automation just moves bad information faster. It will not fix a broken process. That is such a good point. The golden rule here is to standardize the minimum fields first. Decide what data is required, standardize it, and only then automate the routing and the reminders. Okay, so we can translate that risk avoidance into three immediate concrete audits you can run this week to see if you are really ready to automate. I like this. First, sit down and list every single place a new opportunity can arrive at your company. Then, trace one single opportunity through its entire life cycle. From the initial estimate to the go or no -go decision. all the way to follow up. See exactly where it gets stuck in someone's
inbox. Yeah, that's a great exercise. And the second audit. Second, open the last three jobs you were awarded. Check if operations actually received the final estimate assumptions and cost codes before they started work. Did they get a baseline budget or did they get a verbal summary? Right. That's what you want to find out. Third, mark every recurring task that only the owner can currently perform. For each of those tasks, define the specific data threshold another person would need to make that decision safely without the owner in the room. That is so important. Yeah. And to build directly on those three audits, we have a specific directive for the decision makers listening today. Go through and mark each control in your business as repeatable, owner -dependent, or not measured. Okay. And once they have that categorized, what's next? Then choose
one owner -dependent handoff to formally document. Just one. Do this before you add another employee or mobilize another crew. That is fantastic advice. Just pick one and start there. We highly encourage you to share this deep dial specifically with the person who will be running operations when the owner is unavailable. Yeah, they really need to be in the loop. They need to understand the mechanics of this transition just as much as the executive team does, because they're the ones who are going to be interacting with the new systems. If you are ready to map your operating and approval workflows, you can request a growth stage workflow assessment at smartbusinessautomator .com. I will repeat that domain for you. It's smartbusinessautomator .com. It is a critical step in turning a bottlenecked business into a scalable one. To close things out today, I
want to leave you with a final thought to mull over. We talked earlier about the owner's brain being the original hard drive of the company. It holds all the relationships, all the pricing intuition, all the history. But there is a tipping point. At what point does the company's greatest historical asset, the owner's intuition, become the specific ceiling that prevents the company from scaling? Think about what you are holding on to and what you need to systematize. Thanks for joining us on this deep dive, and we'll catch you next time.
