Weighing the Deal Internally
Grace and Jack review a lucrative proposal from a major client and weigh its revenue against demanding deadlines and serious delivery risks. They consider what accepting the deal could mean for the rest of the business.
Dialogue11

The proposal is hard to ignore: it would be our largest contract this year, and the client wants a decision by Friday. But the delivery schedule is unusually compressed.
The revenue would be welcome, but they’re asking us to launch across three regions in ten weeks. We’d have to pull people off existing projects almost immediately.
And those projects are already committed. If we divert the team, we risk missing milestones for clients who are counting on us—not to mention the strain on the staff.
I reviewed the assumptions behind their timeline. It depends on getting approvals within forty-eight hours and receiving clean data from the outset. Neither is something we can guarantee.
Exactly. The proposal treats those dependencies as givens, not risks. If either slips, we’d be pressed to make up time by cutting corners or expanding the team at short notice.
We could negotiate a higher fee for the accelerated schedule, but that wouldn’t create more capacity. It might cover overtime; it wouldn’t make the deadline any less fragile.
There’s also the concentration risk. A contract this large would absorb a disproportionate share of our resources, while leaving little room to respond if another major commitment shifts.
And if we miss the launch, the damage wouldn’t be limited to this contract. A visible failure could undermine the trust we’ve built across the market.
Still, I don’t want us to dismiss it simply because it’s demanding. The client’s priorities may be flexible, even if the proposal presents the schedule as fixed.
That’s worth testing. We could map out what’s genuinely essential, what can be phased, and which dependencies need to be owned by the client before we decide.
Good. I’ll ask for a working session, not a promise of delivery. We need to understand whether a realistic scope exists before we put the rest of the business at risk.
Vocabulary8
- hard to ignore
Difficult to dismiss or overlook. Here, the proposal is attractive because of its size and potential revenue.
- compressed
Made shorter or more tightly scheduled than usual. A compressed delivery schedule leaves little time to complete the work.
- divert the team
Move employees away from their current work to focus on something else. It can suggest that other projects may be disrupted.
- make up time
Work faster or take other steps to recover time lost after a delay. In this context, doing so could put quality at risk.
- concentration risk
The danger of relying too heavily on one client, project, or source of income. A very large contract could consume resources needed elsewhere.
- disproportionate share
A much larger portion than would be balanced or appropriate. The contract could take up too much of the company’s capacity.
- worth testing
Worthy of investigating before making a decision. Here, it means checking whether the client’s requirements might be flexible.
- owned by the client
The client is responsible for managing or delivering something. This phrase helps clarify who must meet key conditions for the project to succeed.
Key Sentences8
- 1
But the delivery schedule is unusually compressed.
A concise way to flag that a timeline is tighter than normal. You can reuse “The schedule is unusually [adjective]” to raise a concern professionally.
- 2
We’d have to pull people off existing projects almost immediately.
This explains a practical consequence of accepting a new commitment. Use “We’d have to [action]” to describe what a proposal would require.
- 3
Neither is something we can guarantee.
A tactful way to state that two conditions are outside your control. Replace “Neither” with the relevant items when explaining limits or uncertainty.
- 4
The proposal treats those dependencies as givens, not risks.
This contrasts assumptions presented as certain with factors that could cause problems. It is useful for challenging a plan’s assumptions without dismissing the whole proposal.
- 5
It might cover overtime; it wouldn’t make the deadline any less fragile.
This distinguishes between solving a cost problem and solving an underlying scheduling risk. The structure “It might [benefit]; it wouldn’t [solve the issue]” is useful for evaluating trade-offs.
- 6
A visible failure could undermine the trust we’ve built across the market.
A polished way to explain how one project could damage broader business relationships. You can reuse “could undermine the trust we’ve built” when discussing reputational risks.
- 7
We could map out what’s genuinely essential, what can be phased, and which dependencies need to be owned by the client before we decide.
This proposes a constructive next step while postponing commitment until key details are clear. The list structure helps organize questions about priorities, sequencing, and responsibility.
- 8
We need to understand whether a realistic scope exists before we put the rest of the business at risk.
A firm but diplomatic way to make due diligence a condition of proceeding. Reuse “We need to understand whether…” to identify what must be clarified before a decision.