If you’ve ever signed a contract and seen the words “warrants that” or “covenants to” buried in a wall of text, you’ve probably done what most founders do: skimmed past it and moved to the signature line. That’s understandable. But these two words carry very different legal weight, and not knowing the difference can cost you when something goes wrong.
Here’s the plain-language version of what every founder should know before signing.
They answer two different questions
A warranty answers the question: Is this true right now?
A covenant answers the question: What will you do going forward?
That distinction sounds small. It isn’t. It determines what happens, and what you can actually do about it, when the other side breaks their promise.
Warranties: a snapshot in time
A warranty is a statement of fact, made at a specific moment, usually when the contract is signed. It’s the other party saying “this is true,” not “this will stay true.”
Some examples a founder might actually encounter:
- A supplier states they have the legal right to sell you the goods or license you the software you’re buying.
- An investor’s term sheet includes a statement from your company that there’s no pending litigation against the business.
- A landlord warrants that the commercial property has no outstanding disputes over the lease.
If that statement turns out to be false, even if it was false at signing and nobody knew it yet, that’s a warranty breach. The usual remedy is compensation for the loss caused, not necessarily the termination of the contract (though in serious cases, that’s also possible). If a supplier warranted that they owned the rights to a product they were licensing to you, and it later turns out they didn’t, you have a claim for any loss caused by that false statement.
The important detail: warranties are usually time-limited. Contracts often specify how long you have to bring a claim if a warranty turns out to be false, sometimes 12 months, sometimes longer, depending on what’s at stake. Once that window closes, you generally can’t go back and claim the warranty was wrong, even if you later discover it was.
Covenants: ongoing promises
A covenant is a promise about conduct, not a statement of fact. It’s forward-looking and governs what someone must do (or must not do) for some period, often the life of the contract or beyond.
Examples a founder is more likely to run into:
- An employee or contractor covenants not to solicit your staff or clients for a set period after leaving.
- A vendor agreement requires the supplier to maintain certain insurance coverage for the duration of the contract.
- A loan or investment agreement requires the business to keep specific financial ratios within agreed limits, sometimes called financial covenants, for as long as the loan is outstanding.
- A partnership agreement might prohibit either party from working with a direct competitor in the same territory while the deal is active.
Breaking a covenant is a breach of contract, and it’s enforced in real time. There’s no “snapshot” to dispute; the obligation was either followed or not during the relevant period. Depending on the contract, the consequences can include:
- A claim for damages caused by the breach
- An injunction (a court order forcing someone to stop doing something), which matters a lot for things like non-solicit or non-compete clauses, where money alone doesn’t undo the harm
- The right to terminate the agreement, if the covenant was important enough
- In lending arrangements, an automatic default that lets the lender call in the loan immediately
That last point is worth sitting with if you’ve ever taken on business debt with covenants attached. If your business’s financial ratios fall below the loan agreement’s requirements, the lender doesn’t need to wait for anything else to happen. The breach itself can trigger consequences the moment it occurs.
Why this distinction actually matters to you
Two practical reasons:
1. It affects how long you’re protected. If something is only a warranty, your ability to do anything about a false statement may expire after a defined period. If it’s structured as an ongoing covenant instead, the obligation and your right to enforce it continue for as long as the contract provides.
2. It affects what you can actually get. Warranty breaches usually point toward compensation for loss. Covenant breaches can point toward stopping someone from doing something altogether, which matters enormously if what you’re trying to prevent is a former employee poaching your clients, or a partner working with your direct competitor down the street.
A quick way to think about it
When you’re reading a clause and trying to figure out which one you’re looking at, ask:
- Is this describing a fact about right now (“we own this,” “there’s no pending lawsuit,” “this software has no malicious code”)? That’s a warranty.
- Is this describing something someone has to keep doing, or not doing, over time (“shall not solicit,” “shall maintain insurance,” “shall not compete”)? That’s a covenant.
Some clauses do both. A statement like “Seller currently has no outstanding tax liabilities, and shall promptly notify Buyer of any that arise before closing” is a warranty about the present, paired with a covenant to stay informed going forward. Well-drafted contracts often combine the two deliberately, precisely because a one-time fact and an ongoing obligation protect you in different ways.
The takeaway
Neither clause type is inherently “stronger” than the other; they’re built to do different jobs. The risk for founders isn’t in encountering covenants or warranties themselves. It’s in signing contracts without knowing which one you’re agreeing to, only to discover the difference after something has already gone wrong.
The next time you’re reviewing a contract, pause at the words “warrants” and “covenants.” They’re not interchangeable, and the gap between them is exactly where good legal review earns its keep.