B2B / project environment
A sensitive commercial file had grown into scattered emails, photos, reports and disputed invoices with no coherent overview. Simply Dom reconstructed the chronology, separated facts from claims, and built a single communication line that every next step could rest on.
The situation
The file hadn't formed all at once.
It had grown: months of email traffic between several people, photos taken at different moments, reports, earlier agreements, invoices some of which had since been disputed.
The business owner knew the matter well and remembered the events clearly.
But the file itself told no coherent story.
A recent email from the other party sounded decisive — until you placed an older email next to it that changed the context.
A photo proved that something was visible at a given moment, but not how it had gotten there.
A statement from someone involved was relevant, but not yet an established fact because of that.
And the file was growing faster than any one memory could keep carrying it.
The business question
The biggest risk lay not only in what the other party wrote, but in the reflex to respond to it immediately.
Whoever does that eventually contradicts themselves.
Makes an accidental concession that was never meant as one.
Escalates where it wasn't needed, or focuses on the wrong question while the real issue sits untouched.
And meanwhile forgets to request the information actually needed to take a position at all.
Every rushed email risked narrowing the commercial room to manoeuvre a little further.
The choices made
No universal method — but the order that made sense for this particular file.
First reconstruct the chronology: what happened when, according to which piece of evidence.
Then label each element for what it is: a fact with a source, a claim made by a party, an assumption that somewhere along the way started being treated as fact, or an interpretation.
Next, map the gaps: what's missing, what should be requested.
Alongside that, the commercial stakes: what amount weighed against what costs, time and relationship.
And marked separately: the points that need technical or legal review by a specialist, because they fall outside this work.
Only then the actual choice:
reply, ask for substantiation, clarify, reserve a position, propose a conversation — or deliberately send nothing for now, because it first had to be clear exactly what was being replied to.
And only after that choice: writing.
My role
Very concrete work.
Reading the entire email trail, from the first message to the last.
Building the timeline.
Cataloguing and dating photos and documents.
Placing statements next to earlier evidence and naming the differences.
Flagging contradictions and open questions — including the uncomfortable ones.
Because that's part of it too: the client's own account was tested as well.
Where the evidence didn't fully support the business owner's memory, that was said plainly.
Not to weaken the story, but because a line that rests on one weak spot isn't a strong line.
You want to know that spot before the other party finds it.
After that: formulating the questions that needed answering first.
Drafting correspondence in language that's firm where it needs to be, without closing doors that were better left open.
And where specialist judgment was needed, preparing the material so a technical expert or lawyer could get to work immediately — without first having to reconstruct the entire file themselves.
Execution
The result was tangible.
A reconstructed timeline with a source reference for every event.
An inventory of documents and photos.
An overview of the disputed points, showing for each one what was established, what was claimed, and what remained open.
A list of unanswered questions.
Several communication options, with their respective pros and cons.
A draft reply, with internal notes on wording and possible consequences.
And a package that, if needed, could be handed over to an external specialist in one move.
No system, no software, no file management as a service.
Simply: making the file decidable again.
What was deliberately not done
No emotional reply to the last email, however tempting the tone.
No claim presented as fact without evidence behind it.
No technical conclusions beyond what the available evidence supported.
No threats that would have produced nothing but escalation.
No legal certainty invented where none existed.
No attempt to win every single sentence.
And above all: no automatic reply, simply because the other party had written last.
"Defensible" doesn't mean here: guaranteed to win.
It means: a line that holds together, rests on evidence, and stands up to critical reading.
The goal wasn't the sharpest possible reaction.
The goal was to restore enough structure for the business owner to make the next decision deliberately — themselves.