Considered Needs Fill the Pipeline. Unconsidered Needs Build the Relationship.

Considered needs keep the seller responsive. Unconsidered needs are where consultative selling, thought leadership, and trusted-advisor value begin to shape what the customer sees next.

Considered Needs Fill the Pipeline. Unconsidered Needs Build the Relationship.

The difference between responding to demand and creating value before the customer asks.

For a large part of my career, a healthy portion of the pipeline came from customers telling us what they wanted.

Desktops. A service desk solution. Infrastructure. Cloud. Assessments.

Those are considered needs.

The customer knows what they want. They have a roadmap, a budget, a business case, or at least enough clarity to come to you and ask for something.

There is absolutely nothing wrong with that.

You listen. You respond. You deliver.

But if that's all you do, your revenue footprint is largely at the mercy of what the customer already knows they need.

The more interesting part of sales, at least for me, has always been the unconsidered need.

Not something the customer doesn't want.

Something they haven't thought about yet.

Or something they haven't revisited because their roadmap was built six or twelve months ago and the world has moved since then.

That's why I used to spend time with service-line leaders asking what they were seeing elsewhere.

What were other clients doing? What was changing in the market? What was emerging in cloud, infrastructure, digital workplace, security?

Then, in conversations with the client, I could bring some of that forward.

Not as a pitch.

More like: “You may not need to act on this today, but this is starting to matter elsewhere. We should probably begin talking about it.”

That is a very different sales conversation.

A customer might ask for a series of cloud assessments. Licensing. Sizing. Migration planning.

You can respond to each request one by one.

Or you can step back and ask whether they have considered the operating model around it.

FinOps. DevSecOps. Governance. The broader strategy that keeps all those individual pieces from becoming disconnected work.

That isn't about manufacturing a problem so you can sell more.

It's about seeing something the customer may be too busy, too close to the day-to-day, or simply too early in the journey to see yet.

To me, that's one of the clearest differences between an order taker and a trusted advisor.

One responds to demand.

The other helps the customer see what may be coming next.

And sometimes, the most valuable thing you sell is not a product at all.

It's foresight.

Read more...

Loved it? Follow me.

About the Author

Imad Lodhi

Founder IMADLODHI.COM | Partner | Global Sales & Delivery Executive | Strategy & Innovation Leader | Delivery Excellence/Analytics Leader | DWS Leader | Author

ABOUT IMAD

Imad Lodhi

Sales & Delivery Transformation Executive focused on the management systems, mindsets and behaviours that turn strategy into measurable outcomes.

Continue the conversation

Stay in the conversation.

Awesome sauce!

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form :(