Why ERP Actually Gets Bought: The Event Before Your Call

Open any ERP vendor’s deck and you will find the same promise: we help companies grow. It sells nothing, because it describes nobody. A company growing quietly does not buy a system — it defers, because deferring is free and replacing a system is not.

Companies do not buy because they want to. They buy because something happened.

This station is about that something: how to name it, how to ask for it, and why a deal with no dated event is not a qualified deal however friendly it looks.

Your first competitor is not a competitor

In The JOLT Effect (2022), Matthew Dixon and Ted McKenna analysed more than 2.5 million recorded sales conversations and produced the number that explains most of what happens in this market: between 40% and 60% of qualified deals are lost to “no decision”, not to a rival. In roughly 56% of those losses the buyer was already sold on the need — and then froze.

Read that again. In half your pipeline you are not competing against another vendor. You are competing against things staying as they are.

And the status quo is a formidable competitor: free, familiar, and nobody gets blamed for it. Against that you offer a visible cost, a risk, and months of strain on staff who never asked for the project. In The 2026 ERP Report from Panorama Consulting Group — 170 responses collected between January 2025 and January 2026 — the median project timeline was nine months. Nine months you are asking of a man who does not wake up thinking about your software.

The event is the only thing that flips that equation, because it changes the question from “should we change?” to “what does not changing cost us?” — and the second question has a numeric answer while the first does not.

The seven events that open a budget

Across fifteen years in the Egyptian and Emirati markets, almost every deal I have closed traces back to one of seven events. This is not a statistic; it is an inventory of experience, and I say so plainly:

1. A regulatory deadline. E-invoicing is the clearest case in this region: ZATCA Phase 2 in Saudi Arabia and the UAE e-invoicing mandate. The virtue of this event is that its date was written by a third party, so nobody inside the company can postpone it by decision.

2. A discovered discrepancy. Stock count does not match the books. A customer balance shows as settled and is not. An item is being sold below cost because the cost itself is calculated on paper. A discrepancy, once found, creates in a week the decision two years of pitching could not.

3. An audit or due diligence. An investor coming in, a bank assessing a facility, a potential acquirer. Whoever asks for the statements also asks to trace them back to source documents, and a spreadsheet does not survive that request.

4. Expansion that breaks the old method. A second branch, a second warehouse, a new production line, a market in another currency. The method that ran one location does not run two, and the discovery always arrives after the opening, never before.

5. A change in who sits in the chair. A new CFO, a founder’s son entering management, an operations director arriving from a larger company. The newcomer needs a visible win in year one, and a systems project is visible.

6. The incumbent system reaching end of life. The vendor stopped supporting it, or the one person who understood it left, or the version no longer runs on current hardware. This event is distinctive because the budget is nearly guaranteed and the competition is therefore brutal — it has a full station of its own: selling against an incumbent.

7. A public operational failure. A shipment late in front of a major customer. A fine. A production stoppage because a raw material ran out and nobody knew. The event the founder can date to the day.

The story: the warehouse that was not short

The story below is composited from real events, and every detail that could identify anyone has been changed.

A food distributor in an industrial city — four warehouses, around sixty staff. I knocked on that door four times over eighteen months. The answer was the same each time, and genuinely friendly: the current system gets us by, and we have other priorities.

Then the call came. Not from me — from him.

A half-year stock count had turned up a shortfall in a single item worth roughly a warehouse clerk’s annual salary. The surprise was not the shortfall. The surprise was that the discrepancy had existed for eleven months, and that four different people had each noticed a piece of it from their own position and nobody had ever put those pieces in one place. The storekeeper saw an item running short. The accountant saw a cost rising. The salesman saw a customer complaint about a short delivery. The purchasing manager saw himself buying more than usual. Four correct signals in four separate ledgers.

What the man bought after that was not software. He bought never again taking eleven months to find out.

The lesson that matters to you: nothing in my pitch changed between visit four and that phone call. What changed is that the event happened. All four visits had done was make sure mine was the number he reached for when it did.

What this does to your method

If the event is the engine, then the first ten minutes of any first conversation have exactly one job: establish the event and its date. No capability tour, no company slides.

Three questions are enough, and they are deliberately hard to answer with nothing:

“What made you open this subject now specifically, rather than last year?”

“If things stay exactly as they are through year end, what happens?”

“Who inside the company raised it first?”

The second question is the thermometer. If the answer is nothing serious, we carry on, you are looking at curiosity rather than a project, and the honest thing is to log it that way rather than count it as a deal and miss your quarter. The third question opens the next station: the decision map — because whoever raised it is rarely whoever signs.

When there is no event

There is a third possibility salespeople rarely admit: that you are the one who creates the event.

It is possible, and it is the slowest route in this profession and the most valuable. It is not created by a presentation but by putting in front of a company a number about itself that it did not know — the share of orders shipped short, the days between invoice and collection, the cost of an item calculated in a way that hides the loss. This is not a sales trick: it is reading a real operating cycle and telling its owner what is in it.

That is exactly where the best deals in this market come from. Sell a company a number about itself before you sell it software, and you enter the competition defining the question every competitor will be measured against.

Checklist before you move on

• Do you know the event, with its date, for every deal in your pipeline?
• Are the deals with no event tracked separately, or mixed in and inflating your forecast?
• Can you write in one line what happens to the customer if they do nothing through year end?
• Do you know who raised the subject inside the company first?
• For the deals with no event: what number about themselves could you put in front of them?

Next station

You know why a budget opens. Station two is about who decides to spend it: the decision map and the five voices — and why a brilliant pitch to the wrong room is a cleaner loss than a poor one.