In a Dispute with Your Vendor – What Applies, What Pays Off?

By Weapp · Updated

In a dispute with an IT vendor, much is governed by the contract: liability caps, penalty clauses, and how disputes get resolved. Every claim rests on giving timely formal notice of the defect and being able to document it. Even when you're right on the merits, a settlement usually beats litigation – it's faster, cheaper, and less uncertain.

When an IT project goes sideways and the vendor doesn’t deliver as promised, the temptation is to go straight for conflict. But a dispute is rarely as simple as “we’re right, they’re wrong,” and rushing to a lawyer first risks losing both money and time. Here’s a sober rundown of what actually applies to consulting services – and which paths tend to pay off.

For consulting services, there’s no consumer-protection law as clear-cut as when an individual buys a physical product. Much of what applies between businesses is instead governed by the contract you signed. That means your starting point is almost always the contract, not a general sense of what should apply.

Just as important is the evidence. Even if you’re right on the merits, it matters little if you can’t prove it. Who said what, what was actually agreed, and what was actually delivered? Without documentation, a dispute becomes he-said-she-said, and the outcome becomes a gamble regardless of who’s actually right.

The conclusion from both points is the same: your strength in a dispute is built long before the dispute arises, through a clear contract and organized documentation.

Formal notice and documentation as the foundation

Every claim rests on two things: that you’ve given formal notice of the defect, and that you can substantiate it.

Giving formal notice means telling the vendor in writing about the defect within a reasonable time after you discover it. It’s often a prerequisite for being able to assert your rights at all later on – wait too long and the opportunity can be lost. A formal notice should be specific: what is the defect, and which part of the agreement does it breach?

Documentation is the foundation under the formal notice. Keep track of:

  • The contract and its appendices – the requirements specification, timeline, and what was promised.
  • Written communication – emails and decisions where commitments were made.
  • What was actually delivered – and where it deviates from what was agreed.
  • The formal notices themselves – when you raised what, and the vendor’s responses.

The better organized this is, the stronger your position – and the more likely the other party is to make things right without a fight.

What the contract governs

Before you decide how far to push an issue, read what the contract says. Three things matter most.

Liability cap. Most contracts limit how much the vendor can be required to pay, often tied to the contract’s value. That means even a legitimate loss can be capped, which affects how much it’s worth fighting over.

Penalty clauses. Sometimes there are predetermined amounts for specific failures, like delays. A penalty clause applies without you having to prove your actual loss – but only if it was actually written in. If it’s there, it’s a powerful and simple tool.

Dispute resolution clause. The contract often specifies how a dispute should be handled – for example through negotiation, mediation, or a specific court. That clause sets the playing field, so read it before you choose a path.

Why settling usually beats litigation

Say a delivery is badly delayed and a feature doesn’t work as agreed. You’ve given formal notice, you have the documentation, and the contract is on your side. Should you sue?

Almost never as a first move. Litigation is expensive, takes a long time, and is uncertain even with strong arguments, while in practice it burns the relationship completely. A structured dialogue or mediation usually gets a better outcome faster: you can agree on a price adjustment, supplementary work, or a wind-down plan without spending hundreds of thousands of kronor and a year on legal proceedings.

The point isn’t to be a pushover. A well-documented, factually presented claim is itself a strong negotiating position – often stronger than a threat of litigation, because the other party can see you have grounds. Save the courtroom for a genuine last resort.

At Weapp we believe the best dispute is the one that never happens, and that the foundation is laid through clear contracts and open dialogue. Want a partner who works that way? Read about our services or get in touch with a short description of your situation.

Frequently asked questions

What is formal notice of a defect, and why does it matter?

Giving formal notice means telling the vendor in writing about a defect within a reasonable time after you discover it. It's often a prerequisite for asserting a claim later – wait too long and you can lose that right. The notice should be specific about what the defect is and, ideally, reference what was agreed.

What does a liability cap in the contract mean?

A liability cap is an agreed upper limit on how much the vendor can be required to pay if something goes wrong, often tied to the contract's value. That means even a legitimate loss can be capped. That's why the liability cap is one of the most important clauses to read carefully before you sign a contract.

Should I take the dispute to court?

Rarely as a first step. Litigation is expensive, slow, and uncertain even when you have strong arguments, and it typically destroys the relationship entirely. Settlement or mediation usually gets you a better outcome faster. Court is a last resort once dialogue is truly exhausted, not the opening move of a negotiation.

What's the difference between penalty clauses and damages?

Penalty clauses are predetermined amounts agreed for specific failures, such as delays, and they apply automatically without you having to prove your actual loss. Damages require you to show what loss you actually suffered. Penalty clauses are therefore easier to claim, but only if they were actually written into the contract from the start.

What should I do first when a conflict arises?

Give written formal notice of the defect, gather your documentation, and read what the contract says about liability and dispute resolution. Then have a structured conversation with the vendor before bringing in lawyers. Most disputes get resolved in that conversation, provided your case is well documented and you're clear about what you want to achieve.