He Dropped From 86 to 50 Hours Instantly

I was on a coaching call recently and the guy I was working with dropped something almost in passing - like it wasn't even the main point. He was telling me about a contractor he's working with. Decent developer, $15 an hour, handling some technical work for his SaaS project. Reasonable enough.

Then he mentioned the estimate.

The contractor had quoted 86 hours for a piece of work my client had looked at and figured was maybe a 10-hour task. Could be 15 if things got messy. Not 86. So he pushed back. Asked some questions. Challenged the breakdown line by line.

The contractor came back at 50 hours.

And that's the moment I want to talk about. Because that single data point - 86 dropping to 50 in one conversation, with no new information, no scope change, no renegotiation of deliverables - tells you everything you need to know about how that original quote was built.

Those 36 hours were invented. They were never real. And the fact that they evaporated instantly the moment someone asked a question proves it.

The Speed of the Concession Is the Signal

Most people, when they get a high contractor quote, focus on the number. Is 86 hours reasonable? Is 50 hours reasonable? They start Googling, asking around, trying to figure out what the "right" number is.

That's the wrong question.

The right question is: how fast did they move?

When someone has actually thought through their estimate - when they've broken down the task, considered the edge cases, mapped out the dependencies - they don't immediately drop 42% of their hours the moment you look at them sideways. They defend the number. They explain why it's 32 hours for the scraping module and not 15. They push back on your assumptions. They might come down a little. Maybe 10%, maybe 15% if there's genuine scope flexibility.

But 42%? In one conversation? Without any new information on the table?

That's not a negotiation. That's a contractor who threw a number at the wall, watched it not stick, and threw a smaller number. The original quote had no foundation. It was an aspiration dressed up as an estimate.

What Actually Happened In That Call

The specific breakdown my client described was wild. The contractor had quoted 32 hours just for a scraping component - something that, when we talked through it, was realistically a 15-hour job. And that was the line item that stood out most because it was so obviously inflated. My client had already checked it against ChatGPT and other reference points, and the numbers just didn't add up.

So when we talked through the approach - how to handle the upcoming negotiation call with this developer - the play was simple: be direct. Tell him that if the hours stay at 86, we can't keep using him. Tell him 15 hours for the scraping component is fine, we'll approve that without hesitation. But 32 hours for that same task? That's not something we can sign off on.

No drama. No long debate. Just: these are the numbers that make sense to us, here's the threshold, let us know if you can work within it.

That's it. You don't have to be aggressive. But you do have to be willing to walk. If you're not willing to walk, you're not negotiating - you're just asking permission to pay less, and they know it.

This Isn't Just a Developer Problem

I want to be clear - this isn't some indictment of developers or freelancers specifically. Padded estimates exist everywhere. I've seen it with designers, copywriters, marketing agencies, video editors, legal firms. Anywhere someone is billing hours for creative or technical work, there's an incentive to round up aggressively on the front end.

The logic from the contractor's side is understandable, even if it's bad practice. They're hedging for unknowns. They're building in buffer for client revisions. They're accounting for the fact that half their clients are disorganized and will drag the project out. All of that is real. But none of it justifies an estimate that falls apart the second you look at it - because a well-built estimate with legitimate buffer should be defensible. You should be able to explain every hour.

If you can't defend 86, you shouldn't quote 86.

The 20% Rule

Here's the framework I'd give anyone managing contractors, developers, freelancers, or vendors of any kind:

If they drop more than 20% without any new information, the entire quote is suspect.

Not just the hours they dropped. The whole thing. Because the only way someone moves that fast is if the original number wasn't built from the ground up - it was built from the top down. They picked a number that felt ambitious, put line items underneath it to make it look structured, and hoped you wouldn't look too closely.

A 10-15% adjustment in one conversation is normal. That's real negotiation - a little buffer comes out, both sides land somewhere fair. But anything beyond 20%, with no change to scope or deliverables, and you're not dealing with an estimate. You're dealing with an opening position in a game the contractor has played many times before.

The fix is simple: ask them to defend every line. Not in a hostile way. Just: walk me through why this specific task is X hours. Ask the question once. If they can answer it clearly, they probably earned those hours. If they stumble, or the number immediately shrinks, you have your answer.

The Parallel to Sales (And Why This Matters for Your Business)

Here's the part most people miss: this exact dynamic plays out in reverse when you're on the selling side.

When you quote a client and they push back and you immediately drop your price by 40%, you've just done the same thing. You've told them your original price was invented. You've trained them that your numbers aren't real, which means every future number is negotiable by default. That's a terrible position to be in - and it's one I see agencies and freelancers walk themselves into constantly.

Strong pricing, like a strong estimate, has to be defensible. Not arrogant - defensible. You should be able to explain exactly what goes into it, why the hours are what they are, why the deliverables justify the cost. If you can do that, you can hold the line when someone pushes back. And when someone pushes hard and you come down a little - 10%, 15%, because there's genuine scope flexibility - that's fine. That's negotiation.

But if the first sign of resistance causes you to drop 40%, your client knows something important about you: you don't actually believe your own numbers.

This is one of the core things I work on with people inside Galadon Gold - not just how to get meetings, but how to hold a price under pressure, how to structure an offer that you can actually defend, and how to train clients from day one that your numbers mean something. Most of the pipeline problems people think they have are actually offer and positioning problems in disguise.

How to Handle the Conversation When It Happens

So practically speaking - you get a quote that looks padded. What do you do?

First, don't make it emotional. This doesn't need to be a confrontation. You're not accusing them of anything. You're just asking them to walk you through their math.

Ask for a line-by-line breakdown if you don't already have one. If the contractor quotes a lump sum, that's already a yellow flag - anyone who's thought carefully about a project should be able to break it into components without much effort.

Once you have the breakdown, pick the one or two line items that look most inflated and ask specifically about those. Not "this seems high" - ask "help me understand the 32 hours here. What does that include?" Let them explain. Sometimes there's a legitimate reason you hadn't considered. But often, the explanation will be vague or circular, which tells you the hour count was approximate at best.

Then set your threshold clearly. My client was going into a call the next day and I told him the framing: if he comes in at 15 hours for the scraping piece, approve it on the spot, no hesitation. That's fair, that's the right number, pay it without drama. If he comes in at 32 hours, he's told them they can't use him at that level. Simple. No lengthy debate. The number either works or it doesn't.

That kind of clarity is what makes these conversations easy. The contractor knows where the line is. You know where the line is. There's no ambiguity for either side to hide behind.

On Hiring and Building a Team Around People Who Are Straight with You

The broader lesson here is about who you want in your orbit.

My client was also in the middle of searching for a full-time developer - someone in India at a budget that made sense for the business, probably around $500-$1,000 a month. He'd found a few candidates from Discord, some from Brazil, some from Nigeria, rates coming in at $2,000-$5,000 a month. Higher than the budget allowed, and he hadn't yet found someone at the right combination of skill and cost.

In the meantime, he was using the current contractor - who was fine at $15 an hour, genuinely capable - but the padding behavior was a problem. Because once you know someone inflates their numbers when they think they can get away with it, you have to watch every invoice. And that's a tax on your time and your trust that compounds over months.

The best contractors and the best hires are the ones who quote honestly even when they think they could get away with more. Those people are rare and worth paying well. When you find someone like that, you hold onto them. You don't nickel-and-dime them, you don't squeeze them on every invoice - you build a relationship that runs on trust and you pay them what they're worth. That dynamic produces better work, faster turnaround, and way less headache than constantly managing someone whose numbers you can't trust.

In the meantime, use Loom updates, keep communication tight, and stay on top of hours before they accumulate. My client's instinct to send a Loom when work was done rather than a long text thread was exactly right - that's how you keep projects moving without it becoming a full-time management job.

The Single Rule Worth Remembering

I'll leave you with this:

If a contractor drops more than 20% of their estimate the moment you push back, without any scope change, the entire quote was built backward.

They didn't start from the work and build up to the number. They started from a number they wanted and built down to something you'd accept. That's not estimating - it's anchoring. And once you see it, you can't unsee it.

Ask for the breakdown. Ask why. Watch how fast the numbers move. The speed of the concession is the only data point you need.

If you want to get better at managing contractors, pricing your own services, and building a business that doesn't leak money at every vendor relationship - check out the 7-Figure Agency Blueprint. And if you're actively building your outreach and lead pipeline alongside all of this, my Best Lead Strategy Guide is worth a read.

The fundamentals don't change. Whether you're hiring or selling, the numbers you put out should mean something - and you should be able to defend every one of them.