After the Signature: Delivery Is the Next Sale

At the moment the contract is signed, sellers divide into two groups.

One considers the job finished and opens a new file. The other knows that what was just signed is not the end of a sale but the beginning of the next one.

We saw in the channels station that referral from an existing client is the highest-closing channel and the shortest cycle. This station is the factory that produces that channel — and there is no other factory.

The number that sets the size of the window

The 2026 ERP Report from Panorama Consulting Group, built on 170 responses collected between January 2025 and January 2026, found the median project timeline to be nine months.

Nine months in which the customer lives with his choice before he sees its effect. And throughout them he compares, every week, what he was promised against what is happening.

And you are the person who made the promise.

The most dangerous forty-eight hours

The gap that produces most disasters is not technical. It is the gap between what you sold and what the delivery team understood.

The seller knows things that are not written in the contract: that the finance director does not trust the number his system produces, that the warehouse manager is the silent loser who can sink the project without a word, and that the event driving the purchase is a due-diligence review scheduled for March.

Whoever hands over the contract alone hands over the structure and leaves the meaning behind.

The handover meeting takes no more than an hour, and has five items:

1. The event and its date — what made them buy now, and when it lands.
2. The decision voices — who signs, who can object alone, and who loses something from the change.
3. The cost figure the customer spoke himself.
4. What you promised, verbatim — including what you said needs customisation, and we saw in the demo station why this is written down rather than remembered.
5. What you saw of their data’s disorder, which is the first thing the data migration team will hit.

The three mistakes that create an angry customer in month one

The seller vanishing. On the day your contact stops after months of daily follow-up, the customer concludes — rightly — that he was a target rather than a partner. He will not say it to you; he will say it to whoever asks him about you.

A completely different team. Whoever sold on his personal presence and then handed over a team the customer had never seen has unsold what he sold with. Introduce the delivery team before signature, not after — even in one meeting.

“That’s not in scope.” The sentence is usually true, and it is fatal in month one. Whoever wanted to say it at no cost should have written what is outside the scope into the proposal — which is what the negotiation station explains.

The number that says where the market is going

In the same report, the share of buyers using a third party for organizational change management rose from 38.4% to 46.8%, and for post-implementation and benefits realization from 28.3% to 42.1% — the largest jump in the report.

And yet fewer than a quarter of companies said they had focused intensely on change management.

The gap between those two figures is your commercial opportunity: the market has begun buying the post-implementation layer, and most buyers still do not. Whoever sells “after go-live” as a line in the proposal — not as a service mentioned later — is selling something the market is asking for and nobody is offering.

Renewal is decided months before its date

The renewal decision is not made in the renewal month. It is made when somebody in an internal meeting is asked: are we actually getting value from this?

The answer is assembled from small accumulated things: is the system used or has it become a data vault? Has anything improved that somebody can name with a number? Does the finance director know what changed, or only that he paid?

So the quarterly review is not customer service. It is selling. One page every three months: what improved, with a number; what is still outstanding; what comes next. Whoever sends it builds his own renewal file; whoever does not leaves the file to whoever complains.

The story: the project that succeeded and lost the renewal

The story is composited from real events, and every identifying detail has been changed.

A project at an industrial company that went well. It went live roughly on schedule, the problem the system was bought for was solved, and the technical team was satisfied.

A month before renewal I asked the finance director a routine question about renewing. He said something I had not expected:

“Honestly, we’re paying without knowing what we’re buying. The project finished a year ago, and you haven’t called me since — until today.”

The system was working. The problem was that it was no longer visible. What had improved had become normal, the normal is not thanked, and the invoice was the only thing reminding him we existed.

He renewed that year, after a discussion. He did not renew the year after.

The lesson: the project’s success does not protect the renewal. What protects it is keeping the effect visible in numbers — and that is your work, not the system’s.

Checklist before you move on

• Does the delivery team know the event that drove the purchase, and its date?
• Is what you promised written somewhere the delivery team will read?
• When did the customer first meet the delivery team — before signature or after?
• How many existing clients received an impact page with numbers from you in the last three months?
• The last renewal you lost: was the system failing, or invisible?

Next station

Until now the discussion assumed a buyer who wants to buy. Now the two hardest cases in the market: the company with a system that works, and the one that says “we’ll build it ourselves”: the incumbent and “we’ll build it ourselves”.