MENA organisations spend weeks writing RFPs and hours deciding. The request for proposal is written by committee, weighted toward whoever can write the best marketing document, and evaluated on price more than on capability. Then the same organisations complain that their vendors underdeliver, that scope grows, and that the "partnership" feels like a transaction with delays. There is a better way—and it starts with understanding that a vendor is not a contract; it is an operating partner you are about to trust with a piece of your business. Selecting that partner deserves the same rigour you would give a key hire.

Why RFPs Fail

Most RFPs fail before any proposal arrives, for four reasons. They are written around a preferred solution rather than a problem, so innovation is invisible. They describe activities instead of outcomes, so vendors promise effort and deliver little to measure. They are evaluated by a committee that disagrees on criteria, so the winner is the best presenter, not the best fit. And they are priced against the first invoice instead of the total cost of ownership. The most expensive RFP mistake is asking vendors to solve a problem the organisation has not defined for itself.

Write the Outcome, Not the Solution

A good RFP states what success looks like, what the constraints are, and where the organisation is honestly unsure. Say "reduce average resolution time by half in six months" rather than "build a ticket system with these fields". Say "launch an Arabic checkout that lifts conversion" rather than "integrate this payment gateway". Name the assumptions you are unsure about and ask vendors to challenge them; the best vendors will, and that honesty is a signal. An outcome-based RFP is shorter to write and easier to evaluate, because it gives every proposal the same yardstick.

The Evaluation Scorecard

Agree the scorecard before the RFP goes out, and weight it before you see any proposal. Capability and track record, approach and methodology, team quality, commercial terms, risk and exit conditions, and cultural fit all deserve weight; price alone never does. Weight the scorecard against your stated priorities, share it with the evaluation committee, and score every vendor against the same questions. When the scorecard is agreed first, the discussion after demos is about evidence, not about who made the best impression. Use the scorecard to stay disciplined:

  • Capability: evidence they have done this before, not promises they will.
  • Approach: how they would run your project, not their generic process.
  • Team: who actually works on your account, not who presents.
  • Commercial: total cost of ownership, including change and exit.
  • Risk: dependencies, security, compliance, and continuity.
  • Fit: whether you can disagree with each other productively.

A Six-Stage Selection Process

Run selection like a funnel. Stage one defines the need in writing, including the decisions the vendor will inform. Stage two screens a long-list on hard criteria—capability, sector experience, scale, and solvency. Stage three asks shortlisted vendors for written proposals against your outcomes, not against your spec. Stage four runs a structured demo around one of your real scenarios, with the same scenario for every vendor. Stage five checks references and interviews the actual team. Stage six negotiates the commercial and legal terms with a clear scope, SLAs, and exit clauses. Moving through all six stages takes weeks, not months, and it catches the vendors that are excellent on paper and weak in reality.

Negotiating for Partnership, Not Price

The cheapest vendor is the one whose change requests you will fight about for two years. Price the total cost of ownership, not the first invoice: what happens to pricing after the first year, what counts as a change request, who owns the intellectual property, how handover works if the relationship ends. A healthy agreement has service levels that are measured and reviewed, a change control that is fast without being loose, and an exit clause that protects your data and your continuity. Negotiate the partnership terms with the same care as the price, because the terms decide whether this vendor behaves like a partner or like a supplier.

Managing the Relationship After Selection

The contract is where the partnership is tested, and most relationships fail in the first ninety days. Set up a joint kickoff with the actual team, agree the first deliverable and its definition of done, and put a cadence in place that surfaces problems early rather than at the milestone. Track the relationship with the same metrics as the delivery—response time, change-request cycle, and quality—and review them monthly. When problems appear, discuss them against the contract before they grow into blame. A well-managed vendor becomes an asset; an unmanaged one becomes a liability, whatever the contract says.

Smart Logic supports MENA organisations on both sides of the selection table—writing outcome-based RFPs, running evaluations, or being the delivery partner that treats your outcomes as the contract. Start with a vendor-selection playbook tailored to your portfolio.