THE BOTTOM LINE
- Contract Wording is King: The distinction between a best efforts obligation and a guaranteed result is critical in service agreements. Vague project scopes often lead courts to classify the work as best efforts, protecting the supplier if the final outcome disappoints the client.
- Proof of Incompetence is Required: A client cannot simply withhold payment on a best efforts contract because they are unhappy with the result. They must prove the supplier failed to act with reasonable professional skill and care.
- Separate Agreements, Separate Standards: Different parts of a project can be governed by different standards. A follow-up, fixed-price task is more likely to be seen as a guaranteed result, where failure to deliver means the client does not have to pay.
THE DETAILS
In a dispute between IT service provider Evoqia and consultancy firm Team Bliss, the North Holland District Court provided a sharp reminder of how crucial contractual definitions are when a project fails to meet expectations. Team Bliss hired Evoqia to implement a custom digital platform but withheld payment on several invoices, arguing the platform was defective. Evoqia sued for payment, and the court had to determine the nature of the supplier’s obligation: was it to deliver a perfect final product, or was it to apply professional skill and effort toward that goal?
The court’s decision hinged on the distinction between an obligation of result (a promise to deliver a specific outcome) and an obligation of means (a promise to perform with due care, also known as a best efforts clause). The court found that the initial, broad agreement for the platform implementation was an obligation of means. The scope of work was described using estimates and lists of tasks rather than concrete, guaranteed deliverables. Therefore, for Team Bliss to justify non-payment, it was not enough to show the platform was flawed; they had to prove Evoqia had been professionally negligent. As Team Bliss could not sufficiently prove this, the invoices related to the initial project work were deemed valid.
However, the case had a twist. Midway through the project, the parties entered into a second, separate agreement for a fixed price of €7,500 to develop a specific feature (an inputsheet). The court classified this agreement as an obligation of result. Since Evoqia failed to deliver the fully functional and accepted inputsheet—a fact supported by emails from Team Bliss listing outstanding issues—the court ruled that the final invoice for this specific task was not due. This ruling underscores a vital lesson for businesses: even within a single client-supplier relationship, different tasks can be subject to different legal standards, and clarity in each contract or statement of work is paramount to managing risk.
SOURCE
Source: Rechtbank Noord-Holland
