In the quiet world of cybersecurity, trust is as vital as the code itself. For this contractor, transparency and fairness were guiding principles, yet a shadow of doubt and dispute emerged when a client questioned the very work that had been openly communicated and agreed upon. What began as a straightforward job spiraled into a confrontation that tested not just contracts, but respect and understanding.
Faced with resistance and a refusal to honor the invoice, the contractor made a hard choice—locking the client out of critical systems, a last resort born from frustration and the need to protect his livelihood. This was no act of malice, but a powerful reminder that every service rendered deserves recognition and recompense, even in the complex dance of trust and technology.
AITAH a client I did some work for refuses to pay his invoice so I locked him out of his computer systems
As renowned business ethicist Dr. Mary Gentile explains, “Integrity is doing the right thing, even when no one is looking, and especially when doing the wrong thing is tempting.” In this scenario, the OP is balancing the integrity of fulfilling a contract (getting paid for work delivered) against maintaining a positive long-term client relationship, complicated by the client’s subjective dispute over the work’s necessity.
The OP’s decision to use system lockout as leverage is a high-risk maneuver rooted in the principle of retaining control over property (the newly built system) until compensation is rendered. While the lawyer suggests no legal issue exists for withholding access to unpaid work, this tactic significantly breaches standard professional communication and trust, which are critical in service contracting. The client’s reaction likely stems from perceived control loss and the sudden disruption to operations, fueled by the part-owner’s feeling that he was not fully consulted or that the work was inefficient.
The OP’s action was an appropriate escalation within the context of payment enforcement for custom-built assets, but it was poor practice for client management. A more constructive future approach would involve immediate escalation through formal mediation or arbitration channels, rather than unilaterally cutting off system access. This preserves the relationship framework while still leveraging the existing contractual agreement for payment.
THE COMMENTS SECTION WENT WILD – REDDIT HAD *A LOT* TO SAY ABOUT THIS ONE.
The original poster (OP) is facing a payment dispute after completing cybersecurity contract work, leading them to restrict the client’s access to a newly built system until the invoice is settled. The OP feels justified because the work was completed and legally, they hold leverage over the system they created, contrasting with the client’s part-owner who questions the scope and necessity of some billed items.
Is the contractor’s action of withholding access to the client’s system until payment is received a justified response to a disputed invoice, or does this action constitute an overreach beyond standard business practice for client relations?
