Communication beats negotiation — Murali on enterprise procurement
Why the surprise top trait for a procurement leader is communication, and how the RFI gate prevents 90% of the post-award problems people associate with the function.
Murali Sundararajan ran procurement at Wipro for the back half of a 30-year career — a global function spanning India, the US, Germany, France, China, and Japan, vendor base around 8,000-9,000, strategic team of fifty, transactional team of thirty-five, supplier code-of-conduct translated into every language a country registrar required. He started as a mechanical engineer in Delhi, joined Schneider Electric and TVS because they were the rare companies hiring engineers into procurement, and never left the function. Buying, in his framing, is not just buying.
The spine of the conversation is that procurement is a multi-party coordination function, not a haggling-on-price function. Everything that goes wrong in the function — the gatekeeper reputation, the late-stage involvement, the integrity slips, the post-award supplier failures — flows from teams that hire and structure procurement for the wrong job. Murali’s mental model is consistent across his hiring order, his RFX discipline, his risk framework, and his AI bet. The leader who reorganises around coordination wins the function.
The four traits — and the surprise top one
The shape of the hiring discipline lands hardest in the order of the traits.
One is that the communication should be good. The guy should be a go-getter. When I say communication good, not like talking great English — it's clarity in speaking, what he's speaking, how he speaks, and he's able to convey what he wants.
Murali’s four-trait ranking — communication, passion, technical expertise, negotiation — inverts the order most teams hire in. The reasoning is structural. A senior procurement leader spends the day translating: business team to supplier, finance to legal, governance to operations, central policy to country-specific registration rules. Negotiation is one transaction inside that day; the rest is coordination. The leader who arrives as a pure negotiator without the clarity to brief the business team six weeks before the customer contract closes is the leader who gets called at the last minute and asked to “just close it.” That is the dynamic that makes procurement get routed around. The communication-first hire — the one who places team members on the business floors rather than the procurement floor, who circulates monthly approval-time analytics to every business leader in the chain — flips the function from blocker to partner.
The RFI is the gate
The most operationally useful section is the RFX walkthrough.
The RFI is the gate. You filter out, then you get the RFP. Then RFQ, you can do a reverse auction if it's a very standard work.
The discipline is mechanical and the missteps predictable. The RFI (request for information) qualifies the supplier set — financial stability, customer base, country, regulatory posture. The RFP (request for proposal) scopes the work and contractual terms, with budgetary pricing where appropriate. The RFQ (request for quotation) finalises pricing, often through a reverse auction visible to internal stakeholders so the process is provably arms-length. Skipping the RFI is the #1 mistake because it pushes risk to the back of the chain: by the time a vendor’s financial-health issue surfaces, the team has already invested in evaluating their RFP. Murali’s claim — 90% of post-award problems are RFI-surface-able problems — is the discipline behind the process. With early procurement involvement (a person on the business floor before the customer contract lands), the full RFP-to-RFQ cycle can compress to two to three days; the month-long cycle is an artifact of involving procurement late.
Risk is three dimensions, not one
The vendor-selection framework is the cleanest piece of structure in the conversation.
It's not always price. The business guy will say that you got a good price for me, but the customer is not happy because the delivery has not happened.
The three dimensions are geopolitical, financial, and delivery. Geopolitical risk — single-source exposure in unstable regions — gets mitigated by ensuring two or three sources for any critical input. Financial risk — supplier balance-sheet fragility — gets vetted through filings, bank certificates, and third-party studies on private suppliers where the contract size justifies it. Delivery risk is the one most teams underweight: Murali’s rule is that the customer should not represent more than 30-40% of a supplier’s order book, because above that the supplier doesn’t have the bandwidth to absorb the new commitment cleanly, regardless of price. The L1 (lowest price) bid is therefore not the default winner. Going to L2 with a documented justification — bandwidth, geopolitical concentration, financial signal — is the correct decision more often than teams admit. Weekly cross-functional risk reviews with corporate risk in the room keep the framework from collapsing into theory.
Where AI lands first — and what the leader hires for
The closing thread is procurement under generative AI and RPA.
The procurement leader who hires AI-fluent team members today is the one who scales tomorrow.
The shared-service layer goes first — vendor registration, PO conversion, contract review, recurring approvals. RPA already ate the routine cycles; generative AI accelerates the rest. The strategic-sourcing layer comes second: the pre-RFP risk research, the supplier-blacklisting checks, the cross-supplier benchmarking that previously took days collapse into a query. The implication for hiring is sharp. The procurement leader who staffs for haggle-and-paperwork is staffing for a job that won’t exist in three years. The leader who staffs for technical fluency, business-team coordination, and AI-tool literacy is staffing for the function as it actually scales. Murali’s regret line is the tell — he wishes he had learned more software himself; your nose should be in, your hands off. The next generation doesn’t have the option not to.
What to listen for
The full episode covers the path from Delhi engineering to Schneider Electric and TVS, the supply-chain ⊃ procurement ⊃ strategic-sourcing taxonomy, the case for centralised global procurement, the four KPI buckets (cost-reduction, process-improvement, team-development, business-unit alignment), the right-price methodology (clean-sheet costing for products, partner-comparison for software, published-rate benchmarks for services), and the eight-thousand-to-three-thousand vendor consolidation target. His three-word descriptor is Straight forward. Easy to Reach. Flexible. Listen at /podcast/ep-025-murali-sundararajan; for the other procurement essays in the SoF catalogue, see Reba Cox and Michiel de Bruijn, or /topics/procurement-spend.
Related questions
- Why does Murali rank communication above negotiation when hiring procurement?
- Because procurement is a multi-party coordination function, not a haggling-on-price function. The procurement leader's day is spent translating business-team requirements into supplier-facing terms, walking finance through a risk-adjusted vendor recommendation, briefing legal on a clause that needs to move, and convincing internal customers to involve procurement early rather than at the last moment. Negotiation is one act inside that day. A negotiator who cannot communicate clearly across functions creates more friction than they remove. Murali's hiring frame goes communication, passion, technical expertise, negotiation — in that order — and his read is that most procurement teams hire in the reverse order and wonder why they get treated as gatekeepers.
- What is the RFI → RFP → RFQ process and why does Murali say skipping the RFI is the #1 mistake?
- The RFX process unfolds in three stages. The RFI (request for information) qualifies suppliers — financial stability, country of origin, customer base, regulatory posture, scale. It is the gate where you separate viable vendors from time-wasters. The RFP (request for proposal) scopes the work, the contractual terms, and budgetary pricing. The RFQ (request for quotation) finalises pricing, often through a reverse auction. Skipping the RFI is the most common mistake because it pushes risk to the back of the process — by the time you discover a vendor has financial-health issues or geopolitical concentration risk, you've already invested in their RFP response. Murali's frame: 90% of post-award problems are problems the RFI would have surfaced.
- What three dimensions does Murali use to screen vendor risk?
- Geopolitical, financial, and delivery. Geopolitical risk is country-and-region concentration — sourcing a critical component from a single supplier in a politically unstable region is a vulnerability regardless of price. Financial risk is whether the supplier's balance sheet can carry the work — published filings, bank certificates, and third-party studies where the contract value justifies the work. Delivery risk is whether the supplier has the capacity headroom to take the order — Murali's rule is that the customer should not account for more than 30 to 40% of a supplier's order book; above that, the supplier doesn't have the bandwidth to deliver reliably even if the price looks good. The three are non-negotiable; price comes after they pass.
- Where does Murali see AI landing first in procurement?
- In two places, in this order. First, the shared-service / transactional layer — vendor registration, PO conversion, contract review, recurring activity automation. RPA was already eating this work; generative AI accelerates it. Second, the strategic-sourcing layer — pre-RFP risk research, financial-health screening, regulatory and blacklisting checks, cross-supplier benchmarking. The work that previously required a senior team member spending days on data collection becomes a query. Murali's read: the procurement leader who hires AI-fluent team members today is the one who scales tomorrow; the leader who hires for haggle-and-paperwork is staffing for a job that's about to disappear.
Updates
- Editorial pass under the v2 podcast-summary guideline.