The quiet failures

Deals don't die. They go quiet.

Almost nothing in a B2B pipeline fails loudly. There is no rejection email, no lost notification, no moment you could point at afterwards. There is a thread that was moving, and then a Tuesday where it wasn't, and nobody was assigned to notice the difference.

Updated

Silence is not an event, and that is the whole problem

Every system you use is built to record things that happen. A stage changes, a document is signed, an invoice is raised, a payment clears. Each one is an event: something occurred, someone recorded it, and the record is now different from how it was.

Going quiet is the absence of an event. Nothing occurred, so nothing was recorded, so nothing changed — and a system that only reacts to changes has no way to react at all. This is why the deal that has been untouched for six weeks looks, in almost every tool, exactly like the deal you spoke to yesterday. Both say Proposal. Neither one has a flag on it. The difference between them exists only in the head of the person who happens to remember.

“I sent the quote three weeks ago. Then nothing.” The deal did not die. It stopped being anybody's job.

Which means the fix is not discipline, and it is not a better memory. It is deciding, in advance, what counts as too long — and having something that measures the gap for you, because measuring an absence is the one thing a person genuinely cannot do by feel across thirty open threads.

The four silences, in the order they cost you

Most advice about follow-up stops at the quote. In a business where you also deliver something and get paid for it, that is the first of four places the thread can go quiet, and it is not the most expensive one.

1

After the quote: the deal that stopped being anybody's job

You sent it. They said they would come back. There was no next date, because the next move was theirs — and an open thread with no date on it is a thread nobody owns. Three weeks later the champion has moved on to something else, and re-opening the conversation now costs you the price: you will be asked to re-quote against a number that has since been shopped around.

What it costs: the margin you gave away to restart a conversation that never needed to stop.

2

After the win: delivered, and never invoiced

Winning feels like the finish line, so attention moves to the next deal. But between Won and paid there are five or six steps that belong to nobody in particular: the contract, the deposit, the shipment, the delivery confirmation, the invoice. Each one is somebody assuming somebody else is on it.

The gap between what you have delivered and what you have invoiced is the purest form of this. It is work you have already done, cost you have already paid, and revenue you have not asked for. In most businesses nobody looks at that gap as a number, because the sales tool stops at Won and the accounting tool starts at the invoice.

What it costs: your own cash, sitting in the gap between two systems.

3

After the invoice: money that is late and nobody said so

The payment terms were agreed at quote time — 30 days, 50% with the order, whatever it was. Then they were written on a PDF and never turned into a date anybody watches. So “late” becomes something you discover during a cash squeeze rather than something you were told on the day it happened.

The terms are already the answer here. If a term exists, the due date is arithmetic; if you know the due date, aging is arithmetic too. Nothing about collection requires new data entry — it requires that the term written at the start is carried forward instead of retyped.

What it costs: weeks of float on money you already earned.

4

Before the review: the answer you knew in June and cannot find

Your manager asks why the deal slipped. You knew in June: procurement wanted a lead-time guarantee, the economic buyer changed, the reference call never got booked. But the record has a stage and an amount, and the reasoning lived in an email thread you would now have to reconstruct.

So the review gets answered from memory, which means it gets answered vaguely, which means the forecast gets discounted — not because the deal is weak, but because the evidence for it was never written down at the time it was free to write.

What it costs: credibility, which is priced into every number you give afterwards.

Three structural reasons, none of them about effort

It is worth being precise that none of these are personal failings. People who lose deals to silence are not lazier than people who do not; they are usually carrying more threads. The causes are structural.

Your system of record stores outcomes, not evidence. A CRM is designed to answer the company's question — what stage, how much, when. It is not designed to answer yours: what did they actually say, what did I promise, what has to be true for this to close. Those go in a notes field nobody reads, or nowhere.

Ownership ends at Won. Pipeline tools are built for the part of the business that ends with a signature. Everything after it belongs to operations, or finance, or nobody — and “nobody” is not a person you can ask.

Nothing fires when nothing happens. Reminders are set by the person who would have remembered anyway. The threads that go quiet are precisely the ones you did not think to set a reminder on, because at the time there was nothing to remind yourself about.

What to do about it, with or without software

These four work on a spreadsheet, a notebook or a paid tool. They are ordered by how much they return for the effort.

1. Give every open thread a dated next action. Not “follow up” — a date, and a specific move. An undated intention is not being watched by anything, including you. If you cannot name the next move, that is itself the finding: the deal has no next step and should be treated as at risk today rather than in a month.

2. Decide what “quiet” means, as a number. Fourteen days in a transactional cycle, forty-five in a long procurement one. The number matters less than having one, because a threshold turns a feeling into a filter you can run every week. Without it, “which deals have gone quiet” is a question you can only answer by re-reading everything.

3. Keep watching past the win. Track the same thread through contract, deposit, delivery, invoice and payment. The two numbers worth having in front of you every week are delivered but not invoiced and invoiced and overdue. Both are money you have already earned, and both are invisible in the tool that stopped at Won.

4. Write the evidence at the time, not at review time. Two lines after a call — what they said, what you promised, what has to be true — cost almost nothing on the day and cannot be reconstructed three months later at any price. This is the habit with the widest gap between how cheap it is and how much it is worth.

How Memoire does this

Memoire is built around exactly the argument above. You capture what happened with a customer once, in whatever mess it arrived in — a pasted email, a call note, a voice-to-text dump. It is parsed on your own device into an account, an amount, an objection and a dated next action, and filed against the right deal.

From then on the silence is measured for you. Today opens on the deals that have gone quiet, the promises you have not kept and the money that is late — ranked, capped at five, each one carrying a “Why am I seeing this?” you can open. The watch-list does not stop at Won: the same thread is followed through delivery and invoicing to the payment landing, with due dates derived from the terms already written on the quote.

There is no AI service behind any of it, and no writeback to your CRM. Your customer names, prices and notes stay yours.

Keep reading

Free while in preview

Memoire is one way to do all of this without remembering any of it.

You write down what happened with a customer once. It becomes that account's memory, the next commitment you owe, and the warning when that commitment is about to be forgotten — through the quote, the delivery and the invoice, all the way to the money landing.