Negotiation on Delivery Schedule Conflict - B: Confidential Information for Ram, Project Manager at New Horizon INC Custom Case Solution & Analysis

1. Evidence Brief: Case Extraction

Financial Metrics

Penalty Clause: New Horizon Inc (NHI) faces a liquidated damages penalty of 5000 USD per week for every week of delay beyond the contracted October 1 deadline (Source: Paragraph 4).
Overtime Budget: Ram has a discretionary budget of 20000 USD allocated for resource crashing or overtime to expedite the schedule (Source: Paragraph 7).
Margin Target: The project was bid at a 22 percent net margin; any expenditure beyond the 20000 USD budget directly erodes this target (Source: Paragraph 8).
Contract Value: Total project value is 450000 USD (Source: Exhibit 1).

Operational Facts

Current Delay: Technical integration issues in the CRM module have resulted in a 4-week slippage against the original timeline (Source: Paragraph 2).
Resource Constraint: The lead developer, Priya, is scheduled to transition to a high-priority Project X on October 20. Her expertise is non-transferable for the final integration phase (Source: Paragraph 6).
Technical Status: 85 percent of the core functionality is stable; the remaining 15 percent involves the reporting dashboard which is currently failing (Source: Paragraph 3).
Client Milestone: The client has a critical board-level demonstration scheduled for October 15 (Source: Paragraph 5).

Stakeholder Positions

Ram (Project Manager): Seeks to minimize penalty costs while maintaining the long-term relationship with the client. Under pressure to avoid a margin dip (Source: Paragraph 1).
Mr. Sahay (VP, NHI): Has explicitly stated that NHI cannot afford a margin hit below 20 percent on this engagement (Source: Paragraph 8).
Client PM: Demanding full delivery by October 1; has hinted at excluding NHI from future RFP cycles if this deadline is missed (Source: Paragraph 5).

Information Gaps

Client Flexibility: The case does not specify if the client would accept a phased delivery where only core modules are live by the board meeting.
External Labor: Availability of third-party contractors to replace Priya after October 20 is not mentioned.
Technical Debt: The long-term cost of rushing the remaining 15 percent of code is not quantified.

2. Strategic Analysis

Core Strategic Question

How can Ram resolve the 4-week delivery delay to satisfy the client October 15 board requirement while staying within the 20000 USD budget and preventing a margin collapse below 20 percent?

Structural Analysis (ZOPA and BATNA)

The Zone of Possible Agreement (ZOPA) is narrow. The client requires a working demo by October 15, while NHI's current trajectory suggests a November 1 completion. Ram's Best Alternative to a Negotiated Agreement (BATNA) is to accept the 4-week delay, pay 20000 USD in penalties, and risk the relationship. The client's BATNA is to sue for breach or terminate, which is costly and leaves them with no system for their board meeting.

Strategic Options

Option 1: Phased Delivery (Recommended). Deliver the 85 percent stable core functionality by October 10. Use the 20000 USD budget to pay Priya for intensive focus on the demo-critical reporting features. Defer the non-essential reporting modules to November 1.
- Trade-offs: High client management effort; requires the client to waive 2 weeks of penalties in exchange for a guaranteed stable demo.
- Resource Requirements: Full commitment of Priya until October 20; 15000 USD in overtime pay.
Option 2: Total Acceleration. Use the 20000 USD to hire external contractors to work alongside Priya to hit the October 1 deadline.
- Trade-offs: High risk of integration failure due to the learning curve of new staff; zero contingency for further delays.
- Resource Requirements: Immediate procurement of 2 senior developers.
Option 3: Negotiated Extension. Offer a 5 percent discount on the next project in exchange for a 4-week extension with no penalties on the current contract.
- Trade-offs: Protects current margin but cedes future revenue; does not solve the client board meeting problem.
- Resource Requirements: Sales and executive alignment.

Preliminary Recommendation

Pursue Option 1. It addresses the client primary pain point (the board meeting) while keeping NHI costs within the 20000 USD discretionary budget. It avoids the 20000 USD penalty by trading off functionality for speed.

3. Implementation Roadmap

Critical Path

T-Minus 24 Hours: Finalize the list of critical vs. non-critical features for the October 15 demo.
T-Minus 48 Hours: Secure formal agreement from Mr. Sahay for the phased delivery approach.
Week 1: Renegotiate delivery schedule with the client PM; secure a waiver of liquidated damages for a guaranteed October 10 delivery of core modules.
Week 2-3: Execute 24/7 sprint on the reporting dashboard using the overtime budget.
October 10: Deploy Phase 1.
October 20: Final knowledge transfer from Priya to the maintenance team before her transition.

Key Constraints

Priya Transition: The hard stop on October 20 means no buffer exists for Phase 2. All knowledge transfer must be documented by Week 3.
Client Board Pressure: If the October 10 deployment fails, the client will likely trigger the maximum penalty and terminate future cooperation.

Risk-Adjusted Implementation Strategy

The plan assumes a 15 percent technical failure rate. Ram must maintain a daily 8:00 AM sync with the technical team to identify blockers immediately. If the reporting dashboard remains unstable by Week 2, the contingency is to use a static data visualization for the board meeting rather than a live integration, ensuring the demo does not crash.

4. Executive Review and BLUF

BLUF

NHI must pivot to a phased delivery strategy. The current 4-week delay creates a 20000 USD penalty exposure and threatens a critical client relationship. By delivering 85 percent functionality by October 10 and securing a penalty waiver in exchange for meeting the client board meeting deadline, NHI preserves its 22 percent margin and relationship. Attempting full delivery by October 1 is technically unfeasible; accepting a 4-week delay is financially unacceptable.

Dangerous Assumption

The analysis assumes the client values the board meeting demo more than the legal right to collect 20000 USD in penalties. If the client PM is incentivized by cost-savings rather than project success, the phased delivery proposal will fail.

Unaddressed Risks

Resource Burnout: The intensive sprint for Priya and the core team may lead to errors in the final 15 percent of the code, creating long-term warranty costs (Probability: High; Consequence: Moderate).
Project X Conflict: If Project X starts early or requires Priya for emergency planning, the Phase 2 delivery will collapse (Probability: Low; Consequence: High).

Unconsidered Alternative

NHI could propose a temporary staff augmentation where they pay for a client-side developer to assist in the integration. This would shift some technical risk to the client and potentially reduce the penalty through collaborative delay.