Someone has to ask the uncomfortable questions.

How an unexpected writing assignment became a continuing role helping enterprise pursuit teams make stronger arguments.

I didn't set out to work on major deals.

The first corporate job I was hired for after college was doing Salesforce implementation.

During one client project, I wrote extensive documentation on my own initiative—partly to make sense of the system myself, and partly so other people could use it. One of the company's co-founders saw that work and invited me to join a major enterprise proposal effort.

I was brought in to write the proposal. That was the assignment.

A room full of experts still needs a compelling argument.

The proposal team included technical specialists, delivery leaders, and executives who knew far more than I did about the solution we were proposing.

But when everyone contributes their own piece, a response can become a collection of technically correct answers without a clear argument connecting them. Someone needs to consider how the whole thing will sound to the person deciding whether to trust us with the work.

As I tried to write, I kept finding things I couldn't make sense of without asking a few more questions.

So I, an absolute corporate newbie, got big brave and asked questions.

What are we actually promising? Why should the client care? Where's the evidence? And have we answered the question they asked—or just the one we'd rather answer?

Sometimes the strongest argument was buried in technical detail. Sometimes we were making assumptions the client had no reason to share. And sometimes an impressive-sounding answer didn't answer the question at all.

I hadn't been hired to challenge the argument. I just couldn't bring myself to write around the holes in it.

One assignment became a standing role.

After that initial pursuit, I joined the company's large-deals team, working with subject-matter experts and senior leaders to shape proposals, strengthen their arguments, and prepare for client briefings.

That's where message discipline became especially important. With only so much time in front of a potential client, it was easy for a presentation to become a tour of everything the team knew or was excited to talk about.

But the goal wasn't to show off our expertise. It was to give the client what they needed to make a decision in our favor.

Not simply what they wanted to hear. And certainly not everything we wanted to say. We needed to understand what mattered most to that audience, make the relevant argument, prove it, and resist anything that distracted from it.

Sometimes that meant questioning a favorite slide or asking a confident expert to explain why a detail mattered to the person making the decision. The technical depth still mattered. It just couldn't be allowed to bury the point.

What began as a writing assignment became an ongoing role as a constructive challenger and thought partner.

The takeaway

I learned early that I didn't need to be the technical expert—or the most senior person in the room—to contribute something valuable.

Sometimes the most useful thing I could bring was the question everyone else didn't think to ask.

The point of a client briefing isn't to tell people everything we know. It's to give them a reason to choose us.