A legacy client wants to sign a four hundred thousand dollar contract for a project that requires us to use old technology that we are phasing out. Our cash flow is stable, but my team is afraid of looking ungrateful and losing the relationship. How do we say no?

Question

Tyler Smith · Accepted Answer

Declining a project from a legacy client that requires using outdated technology, even for a significant sum like $400,000, is a strategic decision that prioritizes your company's future and the client's long-term success. Viewing this through the lens of gratitude can be a trap that diverts valuable resources and ultimately harms the relationship.

Why Decline the Project

Accepting work on an outdated platform carries several risks:

• Resource Lock-up: Your best engineers will be tied up maintaining old systems instead of developing new, innovative solutions.
• Delayed Transition: It will slow down your company's critical transition to a new product suite and architecture.
• Future Dissatisfaction: In five years, when you can no longer support their legacy systems, the client will likely be dissatisfied, damaging the relationship anyway.
• Opportunity Cost: The $400,000 contract might prevent you from pursuing a much larger opportunity, such as launching a new product worth $2 million.

Gratitude in business does not mean accepting work that hurts your business; it means being honest about your capabilities and commitments.

How to Communicate Your Decision

The best way to decline is to frame your refusal as a commitment to the client's long-term success.

1. Schedule a Direct Call
Do not send an email. A personal call demonstrates respect for the long-standing relationship and allows for a more nuanced conversation. This direct communication is crucial for [building trust](/qa/building-vulnerability-trust-leadership-team) and maintaining a positive connection.

2. Deliver a Clear Message
Use a script similar to this:
"We value our ten-year partnership, which is precisely why we must decline this project. Our technical roadmap is shifting entirely to our new architecture so we can provide faster, more secure solutions. If we took this on, we would be building on a platform we plan to retire, which would leave you with an unsupportable system in the future."

3. Offer Alternatives and Solutions
Immediately follow your decline with constructive options:
• "We want to help you transition to our new platform."
• "Alternatively, we can introduce you to two trusted partners who still specialize in your current setup."

This approach preserves the relationship by demonstrating integrity and a genuine interest in their success, even if it's not directly through this specific project. It also aligns with a strategic vision for [setting long-term targets](/qa/setting-10-year-target-with-rapid-tech-changes).

Aligning Your Team

If your team is struggling with the decision due to fear of looking ungrateful or losing the client, you need to provide a clear business case.

• Resource Capacity Review: Use your weekly leadership alignment meeting to review your resource capacity. This can help prevent your team from [devolving into status reports](/qa/stop-weekly-leadership-meetings-devolving-into-status-reports) and instead focus on strategic allocation.
• Calculate Opportunity Cost: Quantify the opportunity cost of dedicating your top engineers to this legacy project.
• Present the Numbers: When the team sees that accepting this $400,000 contract prevents them from launching a new product worth $2 million, the emotional hesitation will likely vanish, and they will align behind the rejection. This objective data helps overcome [polite gridlock](/qa/polite-meetings-terrible-decisions) and ensures strategic alignment.