Here’s what happens when you manufacture rejection before the client even responds…

Quick update: Remember about five minutes ago when I announced this newsletter AND the podcast would both be called ‘Recalibrate’? Cohesive branding, professional consistency, all that good stuff? Yeah, I’m already ditching it. The podcast launches in the next couple weeks as RE: Engineered (yeah, I said that last time too, but I mean it now), and I don’t need two brand names fighting for space in my brain. So this newsletter is back to being nameless. Just a newsletter. Well done, me.

I spent an entire weekend preparing for a meltdown that never came.

Friday afternoon, I sent a quote to a client. The number had nearly doubled from what I’d casually mentioned earlier—not because I was padding numbers, but because my team’s first pass had only covered the technical work. Project management. Coordination. All the stuff that actually makes projects successful instead of trainwrecks.

When he’d asked earlier if he needed to brace himself for the price, he’d joked about being glad he was sitting down when I shared that first pass with him. So naturally, I spent the entire weekend rehearsing my defense. Planning my justifications. Imagining him questioning my competence or integrity (thinking we had the job in the bag so let’s pad our numbers), my honesty, maybe even pulling the project.

Monday morning, he scheduled a call.

Here we go, I thought.

We connected. Small talk. Project updates. Then: “Got your quote. Looks good. I’ll get the purchase order started.”

Wait, what?

No pushback. No negotiation. Not even a good-natured jab about the price increase.

I’d just burned 48 hours manufacturing a crisis that existed only in my head.

The Big Picture

As I spent a weekend wringing my hands, I realized something about this scenario: I’m not alone.

Engineers manufacture rejection constantly. We create entire disaster scenarios in the gap between stating our worth and hearing the response. That manufactured anxiety doesn’t just steal our weekends—it causes us to underprice services, throw in free work, and systematically leave money on the table.

The curse of knowledge makes it worse. Because our skills are obvious to us, we assume they’re obvious to everyone. We think “anyone could do this” when the reality is that most people absolutely cannot. Then we project that undervaluation onto our clients, convinced they’ll balk at our prices when they’re actually ready to pay for real expertise. It’s why they are hiring us!

Core Insight

The problem wasn’t the price. The problem was the story I told myself about the price.

I’d convinced myself the client would reject it because I was thinking like an engineer (“this is just technical work”) instead of like a client (“this solves my critical problem”).

This pattern shows up everywhere:

Salary negotiations: You accept the first offer because “I should be grateful” instead of recognizing you’re solving problems worth way more than their opening bid.

Scope creep: You throw in “just one more analysis” without charging because “the client will need this.” If there’s value, there should be a price.

Underpricing: You quote based on “how long it takes me” rather than “what it’s worth to them”—forgetting that your decades of experience make the 2-hour solution possible in the first place.

Over-delivering: You spend twice the budgeted hours chasing  “excellent” when the client was perfectly happy with “very good.”

Each of these starts with the same manufactured rejection: “They won’t accept this.” Meanwhile, the client is sitting there thinking: “When can we start?”

I see this with my kids sometimes. One of them will spend an hour trying to figure out if they should ask for something, manufacturing every possible rejection scenario. The other just asks. Guess which one gets more of what they want?

Why This Matters To You

The financial cost compounds fast. That \$10K you left on the table? Multiply it across projects and you’ve given away a year’s salary. Those “helpful” extra hours? That’s time you could’ve spent on another client or actually enjoying your life.

But the worst part? Doing this is a gut-punch to your confidence.

Every time you underprice and they accept, you train your brain that you weren’t worth more.

Every time you over-deliver without charging, you reinforce that your time isn’t valuable.

Every manufactured rejection makes the next one more likely.

The most successful technical professionals I know aren’t necessarily more skilled. They’ve just stopped creating rejection stories between stating their worth and hearing the response.

They quote the real number and wait. They know their value and the value they bring to the clients.

They recognize that if a client balks, that’s information—not confirmation of their fears.

They understand that clients evaluate value completely differently than engineers do.

Practical Steps

1. Today: Name the rejection story you’re manufacturing right now.

Where are you currently underpricing or over-delivering because of a disaster scenario that exists only in your head? Write it down. Then write what you actually know to be true. The gap between your fear and reality is usually massive.

2. This Week: Practice “state and wait” with something low-stakes.

Quote the number. Then shut up. Don’t justify, don’t backpedal, don’t fill the silence with “but I could probably do it for less.” Just wait for the actual response. Document what happens versus what you feared would happen. You’ll be surprised.

3. This Month: Calculate what your manufactured rejection stories
actually cost you.

Audit your last three projects. Where did you underprice? Where did you throw in free work? Add it up. That number—the one that’ll probably make you wince—use that next time you’re tempted to pre-reject yourself.

The rejection you’re bracing for? It usually exists only in your head.

Stop manufacturing disasters. State your worth, then shut up and wait for the actual response.