An email comes in. A business relation is withholding a payment. The tone is polite, the content assertive: the work isn't up to standard, that was supposedly flagged before, and until there's a solution, there'll be no payment. A photo is attached at the bottom.

The first reflex is almost always the same: reply today. Set the facts straight. Show that this won't just be let go.

That reflex feels like decisiveness. There's also a quiet fear underneath it: that silence will be read as agreement. So a reply gets written — quickly, indignantly, with the latest email open on the second screen.

And yet that is often exactly the moment you start writing away your own options.

Because what is this actually about? At first glance, it's about money, about responsibility, about who should have done what. Those are real questions, and sooner or later they need answering. But whoever looks closely at a file like this usually sees something else first: the information isn't in order.

The agreements are scattered across three email threads and one phone call nobody took notes on. The dates in the different messages don't quite line up. Several people — internally and on the other side — each know a piece of the story, but no one has the full picture. The photo at the bottom of the email shows that something was visible at a certain moment. That's all it shows. Not why it was there, not since when, not by whom. Yet in the accompanying text it's treated as the clincher of an argument.

That's often how it goes in files like this. A claim repeated three times starts to sound like an established fact — even to the person who first disputed it. A sentence from an older email, entirely innocent at the time, suddenly carries different weight once a dispute is on the table. And within the same exchange, three kinds of considerations run together: operational, commercial and legal. As long as they stay tangled, every email accidentally answers three questions at once. Usually none of them well.

Before deciding what to say, it therefore pays to first work out what you actually have in hand. What do you actually know — with a source to back it up, not just a feeling? What is being claimed, by whom, and what does it actually rest on? Then there's your own reading of the case, which for now is better treated as an interpretation, however plausible it feels. And then there's what you don't know — information that's missing and is better requested before taking a position than after.

That sounds slow. In practice, it's usually the opposite. Whoever sorts this out thoroughly once afterwards writes faster, shorter, with fewer corrections later. Part of the discussion in a file like this turns out to be about things neither side can actually prove. Better to name those than to fight over them.

There's also an economic side that easily slips out of view in the heat of the moment.

A dispute is rarely only about who is right.

Money sits idle that's needed elsewhere. Every step of escalation costs hours from people who should really be working with clients and projects. There's the question of whether the relationship is still worth anything after this file — and whether you even want that. There's the sober arithmetic between the amount at stake and what it costs to prove you're right, in euros, in time, in attention.

And there's something harder to put on an invoice: the value of options.

As long as you can still go several ways — settle, ask more questions, take a firmer position, let it rest — you're in a different position than once you've already committed yourself fully in writing.

Communication changes those options.

In both directions.

One carelessly worded email can lock in a position that's hard to walk back later. It can contain a concession that was never meant as one, but gets cited as one later anyway. It can write down a suspicion as if it were a finding, after which that suspicion takes on a life of its own. It can escalate at the exact moment a commercial solution was still within reach.

Not out of ill will.

But because the reply was written to the last email instead of to the whole file.

That's why I'll put it bluntly: before a commercial dispute becomes a legal question, it's usually already an organisational problem first.

Whoever sorts things out first — chronology, sources, what's established and what isn't — sometimes finds the dispute is smaller than it looked. Or built differently than assumed.

Sometimes your own position turns out stronger than expected.

Sometimes there's a weak spot that's better examined honestly yourself than denied in an indignant reply.

That's a gain too: you want to know the weak spot in your own story before the other side finds it.

And only then comes the question everyone wanted answered first: what do we write back?

Sometimes that's a firm, factual answer. Sometimes a short request for substantiation is enough. A conversation can make more sense when the relationship is worth more than the amount. And sometimes, more often than you'd think, the strongest answer is one you don't send just yet.

Not out of weakness.

Because you want to know first what you're actually replying to.