A dispute over the development of a bespoke software tool has culminated in a Dutch court ruling that serves as a critical reminder for any company commissioning or providing tech services. The case highlights the costly consequences of misaligned expectations and the crucial difference between paying for a guaranteed outcome versus paying for billable hours.
THE BOTTOM LINE
- Define Your Deal: Vague project scopes are a recipe for disputes. Your contract must explicitly state whether you are paying for effort (i.e., time and materials) or a guaranteed result (i.e., a fixed-price deliverable). The court will enforce what is written, not what was assumed.
- Object with Specificity: In a time-and-materials project, simply refusing to pay is a weak defense. To challenge invoices, a client must object to specific work items or hours in a timely manner. General complaints of “no progress” are unlikely to succeed in court.
- A Lien on Digital Assets Has Limits: While a developer can legally withhold digital assets like domain names for non-payment (exercising a right of lien), this power is not absolute. They cannot continue to charge for services the client has already terminated, and the assets must be released once the associated payment dispute is resolved.
THE DETAILS
The dispute arose between a commercial real estate agent and a web development agency, Visualmedia, over the creation of a sophisticated property valuation tool. The client believed he had commissioned a fully functional tool for a maximum price of around €19,000, to be delivered within 10 weeks. The project dragged on, costs escalated to over €120,000, and with no finished product in sight, the client stopped paying. Visualmedia sued for its outstanding invoices, arguing the agreement was for an agile, hourly-based development project with no fixed price or deadline.
The Northern Netherlands District Court sided heavily with the developer on the core issue. The judge scrutinized the original offer, which used terms like “estimate” for the hours and proposed an iterative, “sprint-based” working method. The contract did not contain a maximum price or a hard deadline. The court ruled that this constituted an “effort-based” agreement, not a “result-based” one. The client’s assumption of a fixed price and timeline, while perhaps understandable from a business perspective, was legally irrelevant because it wasn’t what the contract said. As the client could not prove the developer had failed to exert sufficient effort, the invoices for the development work were deemed largely valid.
However, the ruling was not a total victory for the developer. The court meticulously reviewed each invoice and rejected those for services that were not clearly ordered by the client, such as a significant technical update. More importantly, after the client terminated the hosting agreement in response to the developer taking his websites offline, the court ruled that all subsequent hosting charges were invalid. Consequently, Visualmedia was ordered to immediately transfer the client’s domain names and source codes, as its right to withhold them ended once the court dismissed the related hosting claims. This underscores that while suspending services can be a powerful collection tool, it must be wielded carefully and in line with contractual realities.
Source: Rechtbank Noord-Nederland
