Why “We Draft Contracts” Was Never the Point

When I first started paying closer attention to how I described the work, I realised it usually came out in a very simple way: “we draft contracts.”

It’s not incorrect. In fact, it’s probably how most people in this space would naturally describe it. It’s clean, factual, and easy to say. But over time, I started noticing that it didn’t really connect with how clients think about their situation at all.

Because no one is actually waking up thinking they need a contract. That’s not the starting point. The starting point is usually something more uncertain and more uncomfortable.

It’s the thought that a deal might fall apart after they’ve already committed to it, or that a client might refuse to pay once the work is delivered, or that a partnership that looked straightforward at the beginning could turn into something messy later when expectations don’t match what was originally assumed.

That’s the real space people are operating in. Not documents. Not clauses. But uncertainty about outcomes.

What I thought people would respond to most, when we spoke about what we do, was clarity. I assumed that if we explained our services properly and precisely enough, it would be enough for people to immediately understand the value.

But what actually happened was slightly different. The clearer we got about what we do, the more I noticed that it still didn’t necessarily reflect what people were actually looking for.

The response was always stronger when the conversation moved away from the work itself and closer to what someone was trying to avoid. That was the part that seemed to land.

That observation changed how I started approaching client conversations. I stopped thinking first about the document or the output, and instead started trying to understand the situation behind it. What was actually worrying them in commercial terms.

Where they felt things could break if expectations weren’t properly aligned. What kind of outcome they were trying to protect, even if they hadn’t articulated it in those exact words.

Over time, that shifted the way I understood the work itself. Because once you start seeing the underlying concern properly, the description of what you do becomes less about the task and more about the effect.

It stops being “we draft contracts” and becomes something closer to helping people avoid disputes when deals don’t unfold the way everyone expects them to, or reducing the risk of ambiguity turning into conflict later on.

And that feels like a much more honest way of describing what is actually happening in practice.

There’s also something I keep coming back to, which is how easy it is for professional services to sound interchangeable when they only describe their output.

Whether it’s legal work, SaaS, fintech, IT, or consulting, the language often stays at the level of activity. What is being done. What is being delivered. What is being produced.

But clients aren’t really evaluating at that level. They are evaluating based on what changes for them if something goes wrong. Or what becomes safer. Or what becomes more predictable. That’s the part that actually drives decisions, even if it’s not always explicitly stated.

So when the description of the work doesn’t connect to that layer, it tends to blur into everything else. Not because the work itself is the same, but because the way it is communicated never leaves the surface of it.

The shift I keep noticing is that clarity doesn’t come from explaining the work better. It comes from stepping one level deeper into what the work is actually responding to in the client’s world. Once that happens, the way you describe things starts to change almost without forcing it.

And the interesting part is that it also makes everything simpler. Not more complex.

Because you stop trying to justify what you do, and you start describing what changes because of it.

If I can only describe my work in terms of what I produce, then I’m still staying inside my own process. The real shift is when I can describe what my work prevents, what it protects against, or what it makes less likely to go wrong in the situations my clients are already quietly worried about.

Because people rarely make decisions based on the existence of a service. They make decisions based on what they believe will stop going wrong if they choose it.