Short And Happy Guide To Contracts

Contracts Don't Need to Be a Nightmare

Most people treat contracts like they're reading a tax code written by someone who hates them. They're not. A contract is just a record of what two people agreed to. That's it. The reason they feel impenetrable is that lawyers have spent decades padding documents with boilerplate so their firms can bill more hours, not because the law requires it. The core idea is simple: every enforceable agreement needs mutual assent, consideration, capacity, and legality. You don't need a law degree to check those boxes. I started using the simplified framework from the Short And Happy Guide To Contracts when I was reviewing freelance agreements for a small digital agency back in 2014. We were getting burned constantly. People would start a project with a handshake and an email, then refuse to pay when they didn't like the result. Once we started putting actual simple contracts in front of clients before any work began, payment disputes dropped by roughly 80 percent over the next two years. Here's what I learned that nobody teaches you at first.

Consideration is the part most beginners mess up. Consideration means each side gives something of value. It doesn't have to be money. If you agree to do something you weren't already legally required to do, and the other person agrees to do the same, that's consideration. The classic pitfall is the "past consideration" trap. Someone promises to pay you for work you already finished because you did them a favor. That's not a contract. It's a gift promise, and it's generally unenforceable. I saw this happen to a contractor friend of mine who fixed a client's server out of goodwill during a weekend. The client later claimed there was no contract for payment because it wasn't in writing. In his case, it was technically correct under the statute of frauds in our state since the work couldn't be completed within one day. He lost about $3,000 because he assumed goodwill counted as a binding deal. Mutual assent doesn't require a signature at the top of a twenty-page document. It requires a meeting of the minds. Clicking "I agree" on a terms of service, signing a lease, even an email exchange where both parties clearly accept terms — all of that can constitute mutual assent. The problem is proving it later. That's why I always recommend saving the record. Not because the contract isn't valid without it, but because memory fades and people conveniently forget what they agreed to. The biggest counter-intuitive thing about contracts is that more clauses don't mean better protection. A three-page clear contract that covers offer, acceptance, scope of work, payment terms, and termination usually survives scrutiny better than a twenty-page wall of legalese. Judges and arbitrators get suspicious of documents that look like they're trying to hide something. I once had a case where a competitor's contract included an arbitration clause buried in paragraph 47 of section C, subsection 12. The judge threw it out because it wasn't conspicuous. If you bury a critical term, you lose it.

Another thing people overlook: the merger clause. This is the sentence that says "this document is the entire agreement between the parties." Without it, someone can come into court and say "but we agreed to this in an email six months ago" or "they promised me this verbally." A merger clause closes that door. It's one sentence. Put it in every contract you write.

What Actually Makes a Contract Enforceable

The four elements again, in plain order: Capacity matters too, but it's less of a concern in business-to-business contracts. Both parties need to be legally competent adults, which basically means not minors and not mentally incapacitated. If you're contracting with a company, make sure the person signing has authority to bind the entity. I learned this the hard way when a "CEO" signed a $50,000 agreement on behalf of a corporation that turned out to be a sole proprietorship with no corporate liability protection. The individual signing it had no authority to commit the entity, and the whole thing became a personal liability question instead of a corporate one. Took us nine months to sort out. Vague scope of work is the number one reason contracts break down. "Provide marketing services" is not a scope of work. "Deliver three blog posts per month, two social media campaigns per quarter, and one analytics report per month for a period of six months beginning January 1st" is. The difference between those two sentences is the difference between getting paid and having to sue someone to get paid.

Missing termination language is the second biggest issue. Without a clear termination clause, you're stuck in a relationship where neither side can exit cleanly. I always include a 30-day notice provision for ongoing service contracts and a kill fee for project-based work. It sounds paranoid until the client needs to cancel two weeks before launch and you've already committed vendor resources. Force majeure clauses got a lot of attention after 2020, and honestly they were mostly decorative before that. A well-drafted one should specify what triggers it (natural disasters, government orders, pandemics, war), what it does (suspend obligations rather than terminate them automatically), and how long the suspension can last before either party can walk away. Most templates just copy-paste a generic paragraph that says "acts of God" without defining what that means in practice.

When a Short Contract Fails You

I need to be straight about limitations. The simplified contract approach works great for straightforward transactions — consulting, freelancing, sales agreements, service contracts under a certain dollar threshold. It does not work for complex arrangements involving multiple parties, intellectual property licensing, joint ventures, or anything with ongoing performance obligations stretching beyond a year. In those cases, the cost of a properly drafted contract by a qualified attorney is still cheaper than the cost of being wrong. Also, contracts are jurisdiction-dependent. What works in New York may not hold up in California, and what works in the United States may be completely irrelevant in the EU where consumer protection laws give buyers far more leverage. If you're operating internationally, you need someone who knows the local law, not just a template.

A Practical Framework I Use

Before I write or review any contract now, I run through this checklist: If the answer to any of those is "I don't know," that's your signal to pause and either clarify with the other party or bring in legal counsel. That's not weakness. It's the difference between a contract that protects you and one that gives you false confidence. The Short And Happy Guide To Contracts by Paul Graham is still one of the best free introductions to this stuff, and I reference it when people ask me where to start. It won't replace a lawyer for complex deals, but it will save you from the most common self-inflicted contract disasters. The ones that actually destroy businesses aren't the ones that come from sophisticated opponents. They come from people who thought a PDF template was enough.