The sales team brings a $50,000 opportunity. Finance says no. If leadership explains the rejection only as “we don't have capacity,” the team is left wondering whether winning work still counts as success.
Show what the project would displace, when it needs money and what would make it acceptable. A project can be profitable on its own and still be the wrong commitment this month. Sales deserves the reasoning and a practical alternative.
This is a conversation for a founder whose team has found attractive work the business can't responsibly deliver now. The objective is a decision sales can explain to a customer without losing confidence in the company's growth strategy.
Rejecting profitable project capacity: explain the displaced promise
Start with the commitment already made. Identify which delivery team is booked, what it has promised and which date the new work would put at risk.
“Everyone is busy” is too vague. “The only implementation team is committed to the current client's launch through June 20” gives sales something they can test. The constraint may be specialist skills, supervisory attention or a supplier dependency rather than headcount.
Finance should describe the economics, while operations confirms whether the resource conflict is real. Leadership owns the final tradeoff. Ask sales to challenge the assumptions; their customer feedback can reveal a workable start date or a smaller first phase.
Arron's published funded-growth and scope-control posts support connecting commitments to delivery resources, cash timing and clear boundaries. The sales-facing rejection process here is a new editorial application, not a reported client result or exact Bennett policy.
The best financial decision may be to stop growing explores the broader pause. This decision is narrower: whether to accept one project now.
Hypothetical: $15,000 contribution with a $20,000 cash requirement
Assume a fictional services company expects $50,000 of project revenue and $35,000 of direct delivery costs. Contribution is $15,000, or 30% of revenue. That amount is before company overhead and other costs, so it isn't a promise of $15,000 in net profit.
The new project requires $20,000 before the customer pays. Assume the business has $30,000 of cash, of which $25,000 is already reserved for payroll and other existing commitments. That leaves $5,000 available under this fictional plan. The project creates a $15,000 timing gap: $20,000 needed minus $5,000 available.
Now assume taking the new project would displace an existing $80,000 engagement with $55,000 of direct costs. Its expected contribution is $25,000. Replacing that contribution with $15,000 reduces expected contribution by $10,000, before any additional disruption costs.
Those assumptions don't prove every similar project should be rejected. They show why “it's profitable” doesn't settle the decision. If the original engagement can move without lost contribution, the comparison changes. If funding is genuinely available, the cash constraint changes. Check both rather than treating a spreadsheet's first answer as final.
Bennett's project staffing mix and profitability analysis is the technical context for evaluating delivery economics. Use it to support this conversation without turning the rejection meeting into a capacity-model lesson.
If the project looks attractive but the commitments behind it are difficult to reconcile, use a Profit & Tax Leak Check to frame the delivery-and-cash questions before making another promise.
Communication skills matter when revenue growth meets a limit
A useful explanation has three connected parts: what the company is protecting, the specific conflict and the next acceptable path.
For this hypothetical, the founder could explain that the current launch remains the priority, the same team cannot deliver both starts and the new project needs cash before collection. Sales can then offer a later date or revised scope, subject to customer agreement and a fresh review.
Present the constraint as the organization's responsibility. Don't tell sales they should have known about an invisible booking conflict. If the team didn't have current availability or the cash assumptions, the process needs improvement.
Avoid promising that hiring, technology or extra hours will fix the issue without checking the actual bottleneck. Buying more capacity can create new costs, debt or supervision demands. Increased productivity may help, but it doesn't erase a specific deadline automatically.
Sales motivation also deserves attention. A rejection after weeks of work feels different from an early qualification decision. Recognize the value of the opportunity and make clear what the team should pursue next.
Leadership capacity includes owning the alternative
Choose a named owner and a date for the revised proposal. For example, operations checks a later start by Wednesday, finance reviews payment timing and the account lead asks whether the customer can wait.
A delayed start is useful only if the customer can accept it. A reduced scope must still solve a real problem and protect margins. A deposit may improve cash timing but won't create a second delivery team.
Where neither timing nor scope can change, a clear no is more responsible than a promise nobody can fulfill. Explain that conclusion promptly. Let sales preserve the relationship with an honest answer rather than repeated “we're still reviewing” messages.
Revenue goals need resource maps provides the larger planning connection. The immediate next step is to return a decision on this opportunity.
Make the next exception visible
Define the trigger for revisiting the rejection: a verified opening in delivery capacity, changed customer dates, acceptable funding or a genuinely different scope. Determine who can approve the exception and record its assumptions.
The final decision should reflect the new evidence. Don't let the loudest request quietly bypass the same constraint that stopped the previous deal.
Afterward, review the sales feedback. Was qualification too late? Was availability out of date? Were incentives rewarding bookings without delivery readiness? These are questions to investigate, not conclusions about your team.
When developing the next proposal, focusing on the actual constraint gives sales a better position from which to negotiate. Record which delivery investments would improve the ability to accept similar work and which would merely move the bottleneck. Efficiency means fulfilling the promise with the resources planned, not making the booking at any cost.
The foundation of sustainable growth is a decision making culture that can discuss profitability without treating rejection as personal failure. Ask sales to speak about past opportunities that were approved despite the same warning. A brief reflection can separate fear of losing a deal from evidence that the business can achieve the promised result. Put the resulting comment in the opportunity record so the next review makes sense.
Set one improvement that makes future decisions more consistent. If the money and capacity story still doesn't add up, bring the proposed commitment to Bennett's Leak Check before approving the start.
Frequently asked questions
Can a profitable project still be a poor choice?
Yes. It may displace a better committed project or require cash the business has already allocated. Review the whole commitment, not its isolated margin.
Who should explain the rejection to sales?
The leader who owns the final decision, with finance and operations supporting the assumptions. Sales shouldn't have to infer the reason from a forwarded spreadsheet.
What numbers should the explanation include?
Expected contribution, the displaced commitment and cash needed before payment. State the assumptions and avoid confusing contribution with net profit.
Should finance decide whether delivery has capacity?
Finance can test the economic effect. Operations should verify availability, dependencies and deadlines so the decision rests on an actual delivery constraint.
Does a customer deposit solve the problem?
It may reduce the cash gap. It doesn't resolve a team conflict or guarantee that the agreed scope can be delivered on time.
How can sales challenge a rejection constructively?
Bring new evidence about the customer's timing, scope or payment arrangements. Ask which verified change would reopen the decision.
What if the customer can't accept a later start?
Check whether a smaller viable scope works. If it doesn't, communicate a clear rejection rather than offering a date the company can't support.
When should the decision be reviewed again?
When a stated constraint changes and the named owner verifies it. A repeat request alone isn't a new reason to approve the work.