“The lawyers did that — I have no idea what’s in it.” You’ve probably heard someone say this. Maybe you’ve said it yourself. It tends to land as a self-deprecating joke. But not knowing what your contract says — or what it can do for you — means you can’t use it. And a contract you can’t use is costing you more than you think.
There’s a version of a services contract that sits in a drawer. You used it because you needed something, it seemed fine, and you crossed your fingers. When a client pushes back on scope, or payment terms get murky, or something unexpected happens mid-engagement — you’re not sure what it says, you’re not sure it covers this, and you’re not confident enough in it to call on it clearly. So you negotiate from a position of uncertainty, or you let things slide to avoid conflict, or you spend hours in email exchanges that go nowhere. Or you end up back on the phone to your lawyer every time something minor comes up — paying for guidance on a document that should have been working for you all along.
Then there’s a contract that is aligned with how your business actually works — your services, your client relationships, how you price and deliver your work. One you understand well enough to use in everyday conversations, not just emergencies. One that sets expectations so clearly that a lot of those friction points never arise. One that signals to the people you work with exactly what kind of operator you are — before a word of negotiation has been spoken.
The difference between those two contracts isn’t luck. It’s process. Here’s what that process looks like.
Start with the business, not the template
When independent contractors and small business operators come to me for a services contract, most of them are hoping to do this once — get it right, understand it, and then be able to use it confidently without coming back to a lawyer every time circumstances shift slightly. That’s exactly the right goal. And it’s why the first conversation matters so much.
Before I look at any precedent document, I ask questions. What does your business actually do? What do these services look like in practice — walk me through a typical engagement? Are you already providing any of these services informally? When you imagine this contract, what are you focused on — getting paid, or protecting yourself from specific risks you already have in mind?
That last question is important. If a client has specific risks in mind, I want to know what they are — because they’ll often identify something industry-specific that no generic template would anticipate. And if a client doesn’t have specific risks in mind, that tells me something too: it usually means we need a conversation about what can actually go wrong in this type of work before we get anywhere near a draft.
This is the part of the process most people don’t expect. Your lawyer should be asking you these questions. If they’re not — if the conversation is short and a draft appears quickly — what you’re probably getting is a document built on assumptions about your situation rather than your actual situation.
Why taking the time to understand your contract is worth every minute
The questions above aren’t just about getting the drafting right. They’re about making sure you come away from the process with something you can actually use — and that you understand well enough to use it properly.
Take something as straightforward-sounding as describing your services. Get it too narrow, and the contract gets in the way of you doing your work — every variation becomes a potential breach, every informal conversation a liability. Get it too broad, and you lose the protection you need when scope creep or a dispute arises. The right framing requires understanding how the work actually runs day to day. That’s something only you can tell your lawyer — and once you understand why it matters, you’ll be able to make that call yourself when circumstances change.
The same goes for understanding who you’re contracting with versus who you’re actually working with — they’re not always the same. Or knowing what happens if your client sends you their contract at the same time you send yours. Whose terms govern the relationship? Most people quietly ignore this and hope it never becomes relevant. Sometimes it doesn’t. But when it does, and a dispute arises, the answer matters enormously — and by then it’s too late to sort out cleanly. None of this is complicated. These are practical, concrete things that take a short conversation to get across — and that conversation can save you hours of stress and money down the track.
Understanding what your contract can and can’t do
A contract can only protect you if you operate consistently with it. This sounds obvious. In practice it catches people out constantly.
A client came to me recently — a contractor moving into a new service area adjacent to his existing work. One of the protections we built into his contract was a clause making clear he was not acting as an agent for the people he was consulting with. That clause was important for his specific situation — but he needed to understand that if he then went ahead and acted as an agent in practice — signing things on their behalf, making commitments in their name — the protective value of that clause would be significantly compromised. The contract says one thing; his conduct says another. In a dispute, his conduct is what a court will look at.
People sometimes assume that understanding how a contract works is the lawyer’s job — that the legal complexity is best left to specialists. And there’s truth in that: there are matters that genuinely require specialist assessment and ongoing legal carriage. But there’s a real difference between that and being equipped with the practical knowledge to operate a business tool you’ve already invested time and money in. Knowing what your contract does, where it has limits, and how your own conduct affects its protective value — that’s not advanced legal knowledge. It’s the basic operational literacy that lets you use what you have.
This is the kind of thing that doesn’t take long to explain. But it’s the difference between a protection that holds and one that doesn’t. And it’s exactly the kind of thing you should leave the drafting process knowing.
The goal is to come away understanding what your contract is doing, where the variables are in your particular type of work, and where the limits of your protection lie. Not the legal technicalities — but enough to use it confidently, adapt it to different clients and circumstances without creating gaps, and know when something has come up that actually does warrant a call to your lawyer.
That knowledge pays for itself.
What you end up with
A contract that works isn’t just protection against worst-case scenarios. It’s there in every negotiation, every scope conversation, every moment a client tests your terms — setting expectations before anyone misreads a situation, reducing the friction that eats up your time, letting you show up with confidence.
That’s the contract worth having.
That’s why, when I scope a services contract engagement, I consider not only the document to be prepared, but the advice and explanation needed to help the client use it properly. The aim is to give you a contract you understand, can rely on in ordinary business conversations, and can manage with confidence unless something genuinely new or significant arises.
If you’re an independent contractor or small business operator setting up or refreshing a services contract, get in touch for a free consultation.
