Three companies repositioned. No product rebuilt.

The situation. A US-based enterprise AI scaleup had been selling into MENA without traction. The positioning was “enterprise AI”, which put every conversation in the same evaluation set as Microsoft and Google. Market coverage was broad, the persona was broad, the motion was partner-dependent, and the visible regional activity was events in Egypt.

Which killer was killing the deal. Choice Overload first. “Enterprise AI” is a category the buyer already associates with the two largest software companies on earth. A regional CIO hearing that pitch files the scaleup against a Microsoft roadmap they are already committed to and moves on. The internal champion has nothing to carry into the budget conversation.

Then “will this work HERE”. A broad persona across a broad market means no reference account looks like the buyer in front of you. Partner-dependence made that worse, because it put an intermediary between the vendor and the only proof that matters: a named result with a comparable customer in a comparable market. Events in Egypt produced visibility in a market where the buying committee had no budget authority for the deals being chased.

The result. Traction in a market that had produced nothing for three years. The scaleup stopped being evaluated against Microsoft and Google and started being evaluated against contact centre specialists, a set it could win. Pipeline concentrated in two markets with one repeatable buyer conversation.

The situation. A Gulf-based autonomous sales-conversion vendor was selling to CIOs, being treated as a vendor, and living with long procurement cycles. The customer base was concentrated in low-margin ecommerce, where a conversion lift is real and the budget to pay for it is not. Pipeline leaked at every stage, and the commercial model did not match how the buyer bought.

Which killer was killing the deal. The Expectations Gap. Selling autonomous sales conversion to a CIO means the proof being asked for is technical, integration, and security proof. The vendor’s real proof was commercial: conversion and revenue outcomes the CIO neither owned nor was measured on. The vendor kept presenting evidence the buyer had no use for, and the buyer kept asking for evidence the vendor was not built to produce. That mismatch reads as risk, and risk in a technical evaluation means “wait”.

Then the Valuation Problem. In low-margin ecommerce the buyer’s arithmetic never got there. Integration work, process change, and internal training sat against a margin pool too thin to fund them. The buyer’s message was that the effort exceeded the value, which produces the same outcome as a rejection.

The result. Longer contract value per client and a shorter path to yes, because the buyer holding the budget was also the buyer holding the pain. Procurement cycles shortened once the deal stopped routing through IT governance. The margin structure changed because the same delivery effort now applied to a market where a conversion is worth multiples of an ecommerce cart.

The situation. A KSA-based contact-centre technology vendor was selling cloud contact centre with positioning indistinguishable from every other vendor in the market. Competition was on price, the market treated the product as a commodity, and deal shape had settled at 10 seats in commercial accounts.

Which killer was killing the deal. Choice Overload came from sameness. When six vendors present the same category, the same architecture, and the same benefits, the buyer decides on price. That caps deal size permanently, because nothing in the pitch justifies a larger commitment.

“Will this work HERE” was the deeper one, and the whole category was answering it badly. Saudi government entities and large regulated enterprises carry data residency obligations, sovereignty requirements, and internal security postures that a generic cloud pitch does not survive. Every vendor arriving with a cloud-first deck was telling the highest-value buyers in the market that their constraints were an inconvenience to be worked around. Those buyers stayed out of the pipeline in silence. The only segment where the cloud pitch met no resistance was also the segment with the least money.

The result. Exit from commodity price competition into a segment where the differentiator is architectural. Deal shape moved from 10 seats to government and enterprise scope. The competitive set shrank from every cloud vendor in the market to the small number able to deliver and support on-premise and hybrid in KSA.

• Cisco, Avaya, Uniphore. Twenty years of B2B enterprise technology sales across MENA, ending in conversational AI.
• VP Sales, US SaaS scaleup. Owned the revenue number for the company’s growth phase.
• BCX, on-premise contact centre. Delivered on-premise contact-centre solution, the CXMfast lineage, and the credential behind Case 3’s architecture argument.
• BPO in KSA. Contact-centre and BPO delivery inside Saudi Arabia.
• BPO in UAE. Contact-centre and BPO delivery inside the UAE, the local reference for Dubai buyers.
• RAKEZ Founder Webinar. The full trust-engineering methodology, delivered live to a founder audience through a government free-zone partnership. The Trust Equation, the Trust Map, and the four Silent Killers on this page all come from that material.

Three decision rules a different business can run

From Case 1. If your category name is one a hyperscaler owns, you have volunteered for a comparison you cannot win, and feature differentiation will not rescue you, because the buyer stops reading at the category. Choose a category where your proof is the strongest proof available, then narrow the persona and the geography until “have you done this with someone like me, here” has a name as its answer. Narrowing shrinks the evaluation set you are scored against, and that set decides whether you close. The addressable market stays where it was.

From Case 2. Map who owns the outcome your product creates, who is measured on it, and who holds budget for it. If those three are different people, every deal stalls in an evaluation with no owner. Then check the margin structure of your market, because it sets a ceiling on what your product can be worth. A conversion lift in a 4% margin business and the same lift in a 40% margin business are different products commercially. When level of effort is the blocker, take the work onto your side of the line and charge for the outcome. Buyers resist effort with an uncertain payoff more than they resist price.

From Case 3. Every category has an orthodoxy that travels badly across borders. In MENA the cloud-first default collides with sovereignty and residency requirements at exactly the accounts with the largest budgets. A vendor who names that collision gives the highest-value buyer segment permission to buy. Note what happened to deal size: it grew because the vendor changed which buyer they were in front of. Deal size is a property of the segment. The negotiation moves it by a few points.

Who these cases will not help

Companies whose problem is delivery capacity rather than positioning. Companies below $500,000 in annual revenue, who get more from the 12-week cohort at $6,500 than from a repositioning engagement. Companies with a product that has never closed a deal at full price, because repositioning moves a working product to a better market and cannot manufacture the first proof point.