Q&A Landscaping Checked Its Labor Price Against Truck GPS

On October 28, 2026, RuntimeWire reported on Q&A Landscaping, a residential landscaping and hardscaping company (hardscaping is patios, walls and walkways) whose owner, Quinten O'Dea, used Claude to look at his labor costs. Claude is an AI assistant made by Anthropic. The RuntimeWire headline says Claude found the company's labor costs were 10% higher than priced.

O'Dea told RuntimeWire he matched two records. One was the stop history from the GPS trackers in his trucks, satellite location devices that log where and how long each truck stops. The other was payroll data, the hours the company paid each worker. Together they showed a gap between the company's pricing assumption and the time crews actually spent at billable sites, meaning customer jobs whose time is charged into the price.

Where we land: the useful part of this story isn't that AI made anything faster. It's that one owner found the labor number sitting under his prices didn't match what his crews were doing, and he found it with data he already had. He also says he can't tie Claude to higher sales. That honesty is why we think this story is worth a landscaping owner's time.

Claude and the check O'Dea ran

A company doing both landscaping and hardscaping prices plenty of crew time, and that crew time sits inside every quote.

In practice, that means lining up truck stops at job sites against hours paid, to see how much paid time landed on customer work.

Per O'Dea's account to RuntimeWire, the time crews spent at billable sites didn't match the time his pricing assumed.

The 10% and who reports it

The 10% figure comes from RuntimeWire's headline. The article says it was told by the owner in an email to RuntimeWire. It's self-reported. Most of the article beyond its opening is cut off on the page, so we're working from the part we could read.

In the text we could see, O'Dea describes it as a gap between the company's pricing assumption and the time crews spent at billable sites. We'll keep to that wording. The headline gives the size; the owner's own words give the shape.

There's no dollar figure in the account, and we won't make one up. Turning 10% into dollars would need his crew sizes, wages, and job mix, none of which the article gives.

A labor number sits under every quote

Job costing is the practice of tracking what each job actually cost to do, so you can compare it with what you charged. In our read, labor is the hardest part of that to pin down in landscaping. Weather, drive time, and site surprises all change how long a crew spends.

A labor assumption is the number of crew hours a company expects a job type to take, multiplied by what those hours cost. If that number is off, it's off on every quote built from it. In our read, that's the core of this story: the error wasn't on one job, it was under all of them.

Service Autopilot, which sells software to landscapers, wrote in March 2026 that labor often runs 25% to 40% of revenue for landscaping businesses, and that labor burden typically adds 20% to 35%, so a $20 an hour worker can cost $24 to $27 per hour before any work gets done. Labor burden is what an employer pays on top of wages, such as payroll taxes and insurance. That's a vendor estimate, not a study. When labor is that large a share of the price, a gap in crew time is not a rounding error.

In an undated Blue Collar Builders video interview, O'Dea says the company has about 20 guys out each day. With that many people in the field, a small miss in the hours assumption can repeat across many jobs in a season.

He can't connect it to more sales

Here's the part we'd underline. Per RuntimeWire, O'Dea says he can't tie Claude to higher sales. The story frames this as one small business finding a real pricing error with AI, not a proven sales gain.

We won't claim a sales or profit increase either. The result he reports is narrower: a labor gap found, and a plan, per RuntimeWire, to use the analysis to adjust the company's rates next year.

That's a plain result, and in our read that's what makes it believable. An owner who says what he found and what he can't prove is easier to learn from than one who credits AI with every good month.

Estimates were the other job Claude had

The labor check wasn't the only work. According to RuntimeWire, Q&A Landscaping has used Claude since April to turn dictated job scopes into estimates. A job scope is the owner's description of the work after walking the site.

Per the same article, those estimates get checked against supplier prices and the company's past jobs before a quote goes to a customer. The company has been in business since 2010, RuntimeWire reports, which means there's a long record of past jobs to check against.

We mention this only because it shows where Claude already sat in the office. The labor finding is the story.

Do your trucks and payroll line up?

What we'd watch for: the comparison itself is one a person could do, just not easily. The real question is whether the two records exist and can be lined up.

Start with the trucks. If your trucks have GPS trackers, can you export the stop history with times? If the export only shows a map, it won't help much. You need stops, arrival times, and departure times.

Then look at payroll. You need hours paid per worker per day, and a way to know which crew was on which truck. If crews switch trucks often, write that down before you start, because the match depends on it.

What a labor check needs before AI touches it

Pick a window. A few weeks of normal work is a reasonable first sample. A week of rain days or a holiday week will skew it.

Pick the question. O'Dea's was about time at billable sites versus his pricing assumption. Write your own version in one sentence before giving any AI the files. A vague question gets a vague answer.

Keep a person on the result. If Claude or any AI tool says your labor runs above your pricing, check a handful of days by hand against the raw records. You're about to change prices based on it, so you should trust it yourself.

Changing rates next season

Per RuntimeWire, O'Dea plans to use the analysis to adjust rates next year. That's the slow, careful version of acting on a finding, and we think it's the right one.

A rate change touches every customer conversation. Doing it at a season break gives the owner time to recheck the numbers and to explain new prices plainly. It also leaves time to rerun the GPS and payroll match with fresh data before the new rates go out.

For a related look at who should sign off when job cost numbers move, see our post on who may approve job cost in BuildOps Finance Hub. For the field records side, our post on Zuper Field Agent finishing job records covers what crews log from the truck.

Labor cost questions from landscaping owners

What did Claude find at Q&A Landscaping?

According to RuntimeWire, matching truck GPS stops with payroll data showed a gap between the company's labor pricing assumption and the time crews spent at billable sites. RuntimeWire's headline puts it at 10% higher than priced, a figure the owner reported himself.

Did Claude raise Q&A Landscaping's sales?

No such claim is made. Per RuntimeWire, owner Quinten O'Dea says he can't tie Claude to higher sales, and the company plans to use the labor analysis to adjust its rates next year.

What data do I need to check my own labor pricing?

You need truck GPS stop history with arrival and departure times, plus payroll hours per worker per day. You also need to know which crew rode in which truck, so the two records can be matched.

If you want the long version of how we think about readiness, Start with a FREE quiz and Get Your AI Score.