I used to be a vendor. I sold services. I pitched projects. I negotiated rates. And I was good at it.

But "good" keeps you in the game. It doesn't let you change the game.

I made a mistake several years ago that almost cost me a multi-million dollar account at a high-growth FinTech client, and it taught me the single most valuable lesson of my career. The lesson wasn't about budgets or tech stacks. It was about human nature.

I learned that in any enterprise deal, there are two projects happening at the same time:

  1. The Official Project: The one on the Statement of Work.

  2. The Secret SOW: The unwritten project that determines your stakeholder's next promotion.

If you are only selling to Project #1, you are a commodity. You are a line item. You are a cost to be managed.

If you sell to Project #2, you are no longer a vendor. You are a career ally. You are a strategic partner. You are an indispensable operator.

This is the story of how I learned that, and how you can use it to stop being a "vendor" and start being the only person they trust.

The Failure: The "Brilliant Yoda" Who Became a Threat

I was working for a tech consultancy, placing a team of engineers. I found a phenomenal candidate. A senior, Yoda-like engineer. He was brilliant, deeply experienced, and eager to contribute beyond just writing code. He wanted to consult on team-building, improve processes, and make a real impact. I thought I'd hit a home run.

I placed him on a team run by a Director of Engineering and it backfired.

What I didn't take the time to understand was that the Director also saw himself as the team-builder. He saw managing the "human being aspects" of his team as his critical path to the Senior Director title he felt was overdue.

My "brilliant Yoda" wasn't seen as a gift. He was seen as a threat.

I wasn't solving my client's real problem. I was his problem. I had inadvertently put a competitor on his team, someone who was now challenging his authority and his personal promotion aspirations.

The "A-ha!" Moment: Uncovering the Secret SOW

The unlock came when I finally sat down with the Director and stopped talking about code. I started asking about his world, his frustrations, the machinations of the business.

I realized the official project—"find me a senior engineer"—was just a fraction of the story. The real project was "I need to prove I am a strategic leader who can build and retain a world-class team, so I can finally get my promotion."

He didn't need another Yoda. He needed an engineer who would execute flawlessly and make him look like a brilliant leader.

I realized then that people in corporations care a hell of a lot more about their next promotion than they do about your specific project. Loyalty to companies is low. Loyalty to one's own career path is absolute.

I pivoted. I stopped being a "body shop" and became his partner in achieving his goal. I had a perspective he didn't; I was talking to people across the business. I could help him understand what the company really wanted, not just what was in the all-hands deck.

The relationship changed. We became comrades in arms. And yes, we ended up placing more of the right engineers on his teams and built a long-term, multi-million dollar relationship.

The Master Key: "What's Your Next Promotion?"

This is the core of my operating system. In a discovery meeting with a new enterprise stakeholder, after we've built rapport, I look them in the eye and I ask a question that is unorthodox and disarmingly direct:

"What's your next promotion, and how, exactly, is it measured?"

This question does three things instantly:

  1. It Shatters the "Vendor" Frame: No vendor asks this. They ask about budgets and timelines. This question signals that you are not there for a simple transaction.

  2. It's Disarming: It's so direct and unexpected that you get a real, unscripted answer. You cut through the corporate rhythm and get to the truth.

  3. It Re-Frames You as a "Comrade in Arms": You are immediately conveying, "I am not here to sell you something. I am here to help you win."

They'll tell you the real stuff. The stuff that frustrates them. The metrics that move their career, not the vanity metrics on the project brief.

The "After": Arming Your Champion

Once you have the answer, your job is clear. You are no longer just delivering a service. You are building the case study for your champion's next performance review.

This is a two-part process:

1. Identify the Real Metrics: Your champion's promotion isn't measured by "launching the new feature." It's measured by what that feature does.

  • Does it reduce customer churn by 5%?

  • Does it increase developer efficiency?

  • Does it ladder up to a C-suite goal like "improving time-to-market"? You find those numbers, and you make them the North Star of your project.

2. Arm Your Champion for the Meetings You're Not In: This is the most critical part. The final decision is never made when you are in the room. Your champion will have to fight for your project in leadership meetings you will never be invited to.

Your job is to give them the bullets for their gun.

You help them develop the pitch. You help them frame the victory. You build the slides that show exactly how your work is smashing the KPIs that their boss's boss cares about. You are consciously helping them build the narrative that makes them look like a hero.

This Is the System

This is the difference between a $50k project and a multi-million dollar partnership.

Your competitors are pitching "what we do." You are pitching "how I will help you get your next title."

This is especially true for the brilliant, introverted technical experts who so often fail at this. They are myopic. They think their brilliant code or perfect design should speak for itself. They get frustrated when the "sales guy" gets all the credit.

They're right to be frustrated. But they're wrong about the solution.

The solution isn't to be a better engineer or designer. The solution is to be a better operator. To translate your technical brilliance into the language of the business. And to be "soft on the emotions" of the non-technical people who control your budget.

This is more than a sales tactic. It's an operating system for how to think like an independent person who gets things done, with empathy, strategy, and gusto.

This is the kind of framework we discuss every Tuesday in the Suit & Artist newsletter.

If you're a technical or creative professional who is tired of being undervalued, this is where you learn to translate your talent into executive-level power.

Reply

or to participate

Keep Reading

No posts found