Supplier's honesty on overcharging: a lesson in integrity and trust.

This title was summarized by AI from the post below.

A supplier once came to me and said, “We’ve been overcharging — and we want to correct it.” No negotiation. No prompting. Just honesty. That moment stuck with me. Not because of the savings, but because of what it signaled: integrity over margin, and a long-term mindset over short-term gain. In procurement, we often talk about cost, value, and performance. But the real moat — the defensible advantage — is trust. When a supplier chooses transparency, they’re not just protecting their reputation; they’re building a relationship that competitors can’t easily replicate. Greed might win a quarter. Fairness wins a decade. The truth always finds its way to the surface. And when it does, those who built their business on fairness and credibility are the ones still standing. #Procurement #SupplierTrust #BusinessMoats #Integrity #Leadership #LongTermThinking

Thanks for sharing, Adam. Curious to know from a procurement perspective. If a buyer suspects that they are being overcharged, what kind of data points should they present to initiate a conversation with the supplier? Especially with unique cases such as professional services, with limited market data.

Like
Reply

Such moments prove that ethics isn’t just good practice—it’s good business. When a supplier chooses transparency over margin, it builds a level of trust that no contract or negotiation can replace.

Like
Reply

Adam Paul, PMP ، This story perfectly reflects what sustainable procurement truly means — integrity as the ultimate currency. In our field, numbers can change, but ethics define endurance. Suppliers who choose transparency aren’t just fixing figures — they’re building trust equity that compounds over time. Greed may close a deal; integrity sustains a legacy. #ProcurementLeadership #EthicalSourcing #TrustInBusiness #IntegrityInAction

A quick practice tip: document integrity moments like that in supplier reviews; it reinforces trust-based behavior.

See more comments

To view or add a comment, sign in

Explore content categories