"Don't worry, we'll work it out between us."
You've lost count of how many times you've heard (or said) this sentence at the start of a project. Because every new collaboration begins with the same optimism. Both the service provider and the client want the same thing: for the work to be completed on time, at the agreed quality, and on the agreed terms.
That's the most natural right of both parties. So what actually protects that right?
Words Are Powerful, But They Don't Draw a Line
A promise made in a meeting is real. The intention behind it, in that moment, is real too. But intention is something that changes over time: budgets shrink, priorities shift, people forget, or act like they have.
A handshake builds trust. It's really both sides telling each other, "I want to work with you." But it carries no formality. When a dispute arises, you're left with nothing: no date, no clause, no signature. Just "that's what we said," and even that usually means something different to each side.
What a Project Without a Contract Puts at Risk
Without a contract, questions multiply and most go unanswered. When was the delivery date actually confirmed? What was in scope, and what wasn't? How many rounds of revision were included?
The client may not receive the project on the agreed date or at the agreed quality, with nothing to point to when demanding it. The service provider stands on even shakier ground: a project they've poured months of work into can be dropped without explanation, and they might not even get paid for it. There's no document to fall back on to claim what's owed for their labor.
None of this requires bad intent. Most of the time it comes from miscommunication, from expectations that were never made explicit. But the outcome is the same: trust breaks, time is lost, and sometimes the work simply goes unpaid.
A Contract Isn't a Sign of Distrust
There's a common misunderstanding here: asking for a contract doesn't mean you don't trust the other side.
It's the opposite. A contract is an agreement on clarity, signed by two parties who know their rights, their boundaries, and what they want. It means discussing upfront who delivers what and when, how much will be paid, and what happens in case of revisions or cancellation. It protects both sides equally.
A good contract actually strengthens the relationship. Because once ambiguity is gone, energy goes into the work, not into arguing about who's right.
When Should It Be Signed?
The answer is simple: before the work begins. Sitting down to negotiate terms after a problem has already surfaced is far harder: by then there's tension, sometimes resentment, in the room. At the start of a project, while everyone is still optimistic, terms get set far more calmly and fairly.
That's why putting the contract on the table right after the first meeting (at the most exciting moment of the work) is an act of courtesy, both to yourself and to the other party.
So What Should Be in the Contract?
The answer varies from project to project, but there are a few questions worth asking yourself: Is the scope clearly written, or left open with an "etc."? Are delivery dates specified, along with what happens in case of delay? Is the payment plan (deposit, milestone payments, final payment) spelled out explicitly?
(A clearly defined scope is really its own topic; we have a separate "Why?" post on that. The contract is simply the document that makes that clarity official.)
A few pages written upfront prevent every uncertainty that would otherwise surface later.
This post is for everyone who knows their worth, sets their boundaries, loves their work, and loves themselves just as much. The Why? series continues. 🐾
