Almadar A company near Al Sulaimaniyah issuing an RFP that invites glossy vendor brochures instead of direct answers will get exactly that back.
The RFP is the bridge between vendor selection and contract. It turns the requirements uncovered during readiness assessment into precise, answerable questions, and it sets the commercial and legal terms on which every response is judged. A weak RFP produces incomparable proposals and a negotiation where the vendor holds most of the information.
Writing requirements vendors can't dodge
The difference between "the system must support multi-currency" and "the system must post a SAR-denominated purchase invoice against a USD purchase order, revaluing the open liability at month end using SAMA reference rates, and produce the exchange difference in a separate GL account" is the difference between a yes and a demonstrable answer. We write requirements at the second level of specificity, drawn from your real transactions, so vendors must show rather than claim.
The Saudi compliance section
Every RFP we build carries a dedicated section on Kingdom requirements: ZATCA Phase 2 integration approach and certification status, Arabic invoice and report generation, Hijri date handling, Zakat-ready financial structures, GOSI and WPS payroll connectivity, and data residency. Vendors must state whether each is met through standard configuration, partner add-on or custom development, because that distinction drives both cost and risk.
Commercial terms that protect you
The RFP also establishes how pricing must be presented: licensing separated from implementation, implementation broken down by phase, support priced for years two through five, and change request rates disclosed up front. It sets acceptance criteria, payment milestones tied to deliverables, and the reference and Saudi delivery team information every bidder must provide.
A common Saudi scenario
An Riyadh manufacturer issues an RFP built from a template downloaded online. Three vendors respond with documents ranging from thirty to two hundred pages, none directly comparable, all claiming full Saudi compliance. Only after contract signature does it emerge that one vendor's ZATCA integration is a third-party bolt-on with its own annual fee and a separate support relationship. A properly structured RFP would have surfaced that on page one of the response.
What you receive
A complete RFP package: requirements schedule with priority weighting, Saudi compliance questionnaire, scripted demo scenarios, commercial response template, evaluation scoring framework, and a timeline for issue, clarification, response and evaluation.
Running the clarification process fairly
Between issue and response, bidders will ask questions, and how those are handled shapes the quality of what comes back. Every question and answer is circulated to all bidders in writing, so no vendor gains an information advantage and every proposal is built on the same understanding of your requirements. This also creates a record that protects you if a dispute arises after contract signature.
Multi-entity groups spanning Riyadh need the RFP to specify entity-level requirements separately, since a single consolidated requirements list tends to hide the fact that one entity's needs differ materially from the others.