The call was a status update. Forty minutes, eleven people, one slide deck the color of a hospital wall. The project had already slipped twice. Everyone on the call knew it. Nobody on the call said it.
I was there as a technical add-on. A resource. The kind of person whose name appears on a staffing sheet, not on a contract. When my turn came, I had two minutes and a slide about data readiness that nobody was going to remember.
So I didn't use it.
“You're not going to miss this go-live because of the technology. You're going to miss it because three people on this call own decisions they aren't allowed to make.”
Then the silence. I counted it later, off the recording. Twelve seconds. On a Zoom call, twelve seconds is a geologic era. I have watched consultants panic-fill two seconds of it with credentials.
The CEO unmuted. He did not ask who I worked for. He did not ask about my SAP certifications or how many S/4HANA implementations I'd done. He asked one question:
“What would it take to fix that?”
Six weeks later I signed a $605K contract, direct, as an independent. No integrator on the paper. No recruiter taking a cut off the top of every hour. That single deal is part of the $4.52M in contracts I've now signed direct.
Here's the part that should make you angry
Nothing I said on that call required 22 years in and around SAP. Half the people in that meeting already knew it. Two of them had said it privately over Teams that same week.
They didn't say it out loud because they had been trained - by firms, by recruiters, by annual reviews - to be agreeable. To stay in scope. To be a good resource.
And that is the actual ceiling on your income. Not your module. Not your rate card. Not the market. It is the fact that every incentive in the staffing chain rewards you for being pleasant and punishes you for being necessary.
A pleasant resource is interchangeable, and interchangeable people get priced by the hour by someone else. Read the recruiter trap if you want to see exactly what that costs you in dollars per year. It is worse than you think.
Why executives buy people, not resumes
The consultant's instinct in a room with a CEO is to establish credibility. So we lead with history: years, modules, implementations, logos. It feels safe. It is the single fastest way to be categorized as staffing.
Here is what an executive is actually running in his head during your two minutes: Is this person going to make my problem smaller or my calendar longer? That's it. That's the whole evaluation.
Your resume answers a question he didn't ask. Naming his unspoken problem answers the only one he cares about. And the moment you name it accurately - specifically, without hedging - something shifts that you can feel through a screen: you stop being someone he is being sold, and become someone he is consulting.
“Credentials make you qualified. Diagnosis makes you necessary. Only one of those gets a contract written around it.”
The four-move sequence
What happened on that call was not luck and it was not charisma. It was a sequence I have now run - and taught - dozens of times. It works in a status meeting, a LinkedIn DM, a discovery call, or a hallway.
01 - Name the failure, not the task
Tasks are scoped by delivery managers. Failures are owned by executives. “Data migration readiness” is a task. “You'll miss the close in month one and finance will find out in front of the board” is a failure. Only one of those has a budget attached to it that doesn't need three approvals.
02 - Make it specific enough to be uncomfortable
Vague diagnosis sounds like consulting. Specific diagnosis sounds like someone who has already been inside the building. Name the function, the month, the meeting where it blows up. If your sentence could be said to any Fortune 500 running SAP, it is not specific enough.
03 - Stop talking
This is where 90% of consultants lose the deal they just won. You said the hard thing, the room went quiet, and your nervous system reads silence as rejection. It isn't. It's processing. Every second you let sit is a second the buyer spends convincing himself. Do not rescue him.
04 - Answer the cost question with scope, never a rate
When he asks “what would it take,” the losing answer is a number per hour. The winning answer is a shape: what you'd own, what changes, by when, and what it's worth if it holds. Rates get compared. Outcomes get funded. The full structure is in the 4-part proposal framework.
What this is really costing you right now
Run the math honestly. If you're billed out through a firm or a recruiter, the client is paying somewhere between $450 and $900 an hour for your seat. You see a fraction of it. Over one twelve-month project, the spread between what your work is worth and what you are paid is routinely $200K-$400K.
That gap is not a market condition. It is a positioning condition. It exists because the person signing the check has never heard you say a single sentence that made you necessary. Someone else spoke for you, and they got paid for the speaking.
The full numbers are broken down in salary vs contract rate. Fair warning: most consultants read it twice.
You already have the material
This is the part I want you to actually hear. You do not need a new certification. You do not need to become a salesperson, or extroverted, or comfortable with cold outreach. You do not need to quit your job this month.
You need to take the thing you already see on every project - the breakage everyone is politely not naming - and learn to say it out loud, to the right person, in language that gets a contract written instead of a task assigned.
That's the whole shift. It took me 22 years and one leap to find it. It takes two hours to hand it to you - the exact sentence structures, the diagnosis framework, the proposal that turned “what would it take” into $605K signed direct.
The next executive who goes quiet on your call should be quiet because you finally said the true thing. Not because you were waiting your turn.