Skip to content

Insights··5 min

Whale deals: what the long ones taught me

Enterprise deals take months of stakeholder alignment before anything is signed. How to run one without starving the deals that take a week.

Ghassan Nawfal, Director of Sales, GPOS at Geidea UAE · Updated

A whale deal is the one that would change the year. It is also the one that takes a year. In payments and restaurant technology those deals look like a fifty-outlet group or a national franchise, and they arrive with procurement, IT, finance, operations and an owner who has heard every pitch already. I have closed some and lost some. Here is what the long ones taught me.

The map matters more than the pitch

Every whale has a stakeholder map, and it is never the org chart. It is who signs, who blocks, who has been burned by the last vendor, and who will be running the rollout on a Tuesday night when it goes wrong. Draw it in week one. Redraw it every month, because on a twelve-month cycle somebody on that map will change jobs, and if you found out from LinkedIn you are already behind.

Months where nothing moves

There will be two or three of them. Budget cycles, Ramadan, a merger, an audit. The mistake is to fill the silence with follow-ups that ask for nothing and say nothing. The better move is to bring something the client did not ask for: a number from a comparable rollout, an introduction to an operator who has done it, a one-page answer to the objection their IT lead raised in the last meeting. Silence is where relationships are built, because it is the only time you are not asking for anything.

Do not let the whale eat the boats

The quiet danger of a whale deal is what it does to the rest of the pipeline. A team that is waiting on one signature stops hunting, and if the whale swims away you have a quarter with nothing in it. The rule I hold to is simple: the long deal never gets more than a fixed share of the week, and the small deals keep closing on their own rhythm. Ironically, closing the small ones is also what gives you the references that finish the big one.

Pricing the first one

  • Price the first enterprise deal so the second one is easier, not so the first one is impossible to lose. A concession you cannot repeat is a concession you will have to explain.
  • Separate the commercial decision from the technical one. Get the integration questions answered in writing before the price is on the table, or the price will be blamed for the integration.
  • Ask how the last vendor was thrown out. The answer is your contract.

The deals that took the longest are the ones I still get calls about years later. That is the actual return on a whale: not the number, the relationship with the people on the map.

Working on something like this?