punchwireShort version
All articlesBelieve more is possible

Why pessimism sounds smarter than it is

About 6 minutes to read

You've got an idea for a client whose business is bigger than anything you've worked on before. You can see a real problem you could help solve. Mention the pitch to a colleague and the objections arrive quickly: they already have an agency, your team is too small, you won't get a meeting.

Those objections sound practical. They may even be right. But they haven't established whether the client needs help, whether your idea is relevant, or whether anyone would consider a short conversation.

Pessimism gets mistaken for judgment when it states a possible failure as though the matter has been settled. You can take the concerns seriously without letting them make the decision for you.

It's easier to find a problem than to find out what's possible

You spot a weakness in a large company's customer experience. Its public instructions are confusing, and customers have to call for answers that ought to be easy to find. Your small team has solved a similar problem for a different kind of business. You want to pitch a focused improvement, not claim you can transform the whole company.

Someone points out that the company already works with major suppliers. Its procurement process may be demanding. Your team doesn't have dozens of references in that industry. Those are real issues to investigate, especially if the work would require capabilities you don't have.

But nobody has checked whether the company is satisfied with the current experience, whether there's a narrow opening for a specialist, or who is responsible for the problem. The conversation has jumped from a list of obstacles to a decision not to try.

It's easy to sound considered by listing reasons a proposal could fail. The more useful work is finding out which reasons are facts. If the company requires qualifications you lack, you'll know. If you simply assume nobody will talk to you, you've rejected yourself on their behalf.

I would rather have a well-supported no than a clever prediction that prevents any attempt. One gives you information. The other leaves the possibility untouched.

Good criticism tells you what to investigate

Criticism becomes valuable when it tells you what to check. 'They use an incumbent provider' describes a likely obstacle; it doesn't prove they have no interest in outside ideas. 'We can't meet their data-security requirements' is more consequential, and you should verify it before promising anything.

There may be a real procurement barrier, a conflict of interest, or a scale of work your team couldn't responsibly deliver. If so, the pitch needs to change or stop. Wanting the opportunity badly doesn't make you qualified for it.

Other objections are predictions dressed as facts: 'They'll never reply,' 'We're too small to be heard,' or 'They only hire famous firms.' Ask where those conclusions came from. Was there a specific rejection? A published policy? Or is everyone repeating a story that sounds plausible?

A strong critic helps you examine the proposal. They might identify the missing security certification, question the business case, or ask whether the team could deliver within the client's timeframe. Those objections improve the decision even when the answer turns out to be no.

Blanket cynicism doesn't get that far. It closes the subject before the relevant questions have been asked.

Turn the objection into a question someone can answer

Start with the problem you think you understand. Is it genuinely costly or frustrating for customers? Can you describe the experience without exaggeration? Is there public evidence that it exists?

Then consider where you could learn more without making promises. You might ask a former colleague familiar with that sector how such problems are usually handled. You could research the company's published supplier requirements or speak with someone who understands the buying process. Don't seek private information or pretend you have a relationship you don't.

The most useful question is often smaller than 'Would you hire us?' It may be 'Is the customer-support experience an area your team is working on?' or 'Do you consider focused pilots with specialist suppliers?'

The answers may show that there's a real issue but no route for your team to address it. They may show that a narrowly scoped proposal is welcome. Either way, you've replaced part of your speculation with a fact.

Belief is valuable here because it moves you to investigate a possibility others dismissed. It stops being valuable if you listen only for encouraging answers.

Make a request that deserves consideration

If the opportunity still looks credible, make a request someone can consider. Explain the customer problem you've observed, describe the specific improvement you could test, and state what your team has actually delivered elsewhere. Ask for a short conversation with the appropriate person.

Avoid declaring that your approach will revolutionize their business. You don't know enough to make that claim. A focused observation, a relevant example, and a reasonable request demonstrate more judgment than a grand pitch.

Suppose the buyer asks whether you can handle a nationwide rollout. If you can't, say so. You may be able to support a limited trial, or partner with someone who has the necessary capacity. Only propose arrangements you could responsibly deliver.

A reply isn't guaranteed. A clear refusal ends that request. But sending a credible pitch lets the client evaluate an idea that would otherwise have stayed in your notebook.

That's the practical point of optimism: you make the approach rather than spending months debating whether someone would listen.

Don't mistake confidence for being right

Once you've made the approach, keep testing the idea itself. What if the customer problem is less important than you thought? What if the company has already fixed it? What if delivery would require expertise or cost you can't support?

Those aren't reasons to defend your first theory harder. They're reasons to revise the proposal. You might find a smaller problem to address or a different kind of client better suited to your work.

Confidence doesn't improve a weak offer. Talking to a real buyer might. An honest rejection can sharpen your understanding faster than another month of rehearsing the perfect pitch.

You can believe that your team has something worthwhile to contribute while accepting that this specific client, timing, or proposal may not be right. That's an ambitious position, not a timid one.

Give a good idea the chance to become real

The next time an idea is dismissed, ask which objection could actually settle the question. Check it. If it holds, adapt or stop. If it doesn't, take the next credible step.

For the client pitch, that means verifying the practical requirements, identifying a relevant problem, and making a concise request rather than waiting for permission to believe you're allowed to compete.

You might get the meeting. You might discover a genuine barrier. Either result moves you further than a room full of smart-sounding reasons not to bother.

Don't make pessimism the final authority when it hasn't done the work of finding out.