Taking the customer's request to your leadership team

How do I get my leadership team to take a customer's emissions request seriously?

Present it as what it is: a request from a customer, with a commercial consequence, that needs a decision and a small budget. Not as a sustainability initiative. Leadership teams at small companies say no to initiatives and yes to customer requirements, so the case is built from the request in your hand: who asked, what they asked for, what it takes to answer well, and what answering well does for the relationship. One page, five sections, written in the company's own language about customers and cost.

What goes on the page?

1. The ask. Which customer, what they asked for, by when, and what it is tied to (a tender, a scorecard, a contract review, their own published target). Quote the request.
2. Why they are asking. Two sentences: their footprint includes us, their targets and reporting now depend on supplier data. The guide on what's behind your customer's emissions request has the detail.
3. What it takes to answer. The first steps and their cost: a first footprint (an afternoon with free tools), a published statement (a page on the website), a target (a short document), a renewable tariff at contract renewal (often cost-neutral). Be specific and small.
4. What it does for us. Three things, each true for most suppliers: we stay easy to buy from as customers weigh carbon in sourcing; we replace the industry average our customer holds for us with our own figure, so our improvements show; and we answer once and reuse it for every customer who asks next.
5. The recommendation. Who owns it, what gets done in the next ninety days, and what it costs. Ask for a decision, not a discussion.

Your customer will accept: a reply that says the request has been taken to leadership and a plan is being agreed. Tell them the date of the meeting; it buys you the time and it signals that the request landed.

What about cost?

Lead with the cheap version, because it is real. The first answer to most requests costs time, not money: free calculators, a page on the website, a signed commitment. The items that cost money (solar, heat pumps, electric vehicles) come later and most of them pay back through the energy bill; the paying-for-it guide covers grants and finance. Separate the two in the case so the decision in front of leadership is the small one. Asking for the capital programme and the first footprint in the same meeting is how both get deferred.

What is the risk of not answering?

State it once, plainly, without drama. A supplier that does not answer stays on an industry average in the customer's accounts and cannot be told apart from one that has chosen not to engage; as carbon becomes one of the things procurement weighs, that is a quiet disadvantage at the next review. Customers have told suppliers this directly. It is not a threat and the case should not read as one; it is the commercial reason the request exists.

Who should present it?

Whoever owns the customer. The case lands better from the sales or account lead than from an operations or quality person, because it is about the customer. If that is not you, write the page and give it to them.

What if leadership says no?

Ask for the smallest yes: permission to send the first reply with dates, and an afternoon to produce the first footprint. Both cost nothing and both can be reported back to the customer. Most leadership teams that refuse a programme will agree to a reply, and the reply creates the next conversation when the customer follows up.

Do this week: write the five-section page from the request you have received. Put it on the agenda of the next management meeting as a customer item, not a sustainability item.

What should I do next?

With a decision made, a one-page reduction plan with owners and dates turns it into actions. If your customer uses DitchCarbon, claim your profile; it is a free first action you can report back the same week.