Case 024
Case 024
What happened? Client accuses team of poor performance and refuses to pay for the last two months.
Why? Frustration with unresolved bugs and change in their internal dev leadership.
Client wants: To avoid payment and assign blame.
We want: To receive payment and protect reputation.
Our strengths: Documented updates, milestones, and team logs.
Weaknesses: Bugs were present, some expectations not clarified.
Client’s strengths: Can claim quality issues.
Weaknesses: Still dependent on codebase we delivered.
Compromise: Offer bug fixes in exchange for partial payment.
Tough approach: Deny access to repos until payment is cleared.
Backup plan: Let go of payment but retain portfolio rights.
Fixing bugs may restore trust. Going tough may lead to legal risk but shows backbone.
Lead with a calm explanation and solution offer. If ignored, escalate access control. Break after tough message to await response.
Think about what details are missing, what should be clarified, and what additional strengths and weaknesses each side might have.