Saudi government tenders typically split evaluation into two phases: technical and financial. Understanding this split and how each is scored will fundamentally change how you prepare.
Structure: The Technical Proposal. Your technical proposal answers: "Can you deliver the scope? Do you understand the work? Have you done similar work before?" It covers your methodology, team, timeline, quality controls, compliance, and risk mitigation. It does not mention price. The technical proposal lives or dies on feasibility, clarity, and proof of prior delivery.
Structure: The Financial Proposal. Separately, you submit a financial proposal that shows your cost breakdown, pricing per deliverable or phase, payment terms, and contingency budget. The financial proposal is evaluated after—and only if—the technical proposal passes. This is crucial: you are not scored on price until your technical merit is established.
Evaluation Order. In most Etimad tenders, evaluation proceeds as follows: (1) Compliance check—are you eligible and have you submitted all required documents? (2) Technical evaluation—does your methodology, team, and timeline meet evaluation criteria? (3) Financial evaluation—of technically qualified bidders, who offers the best value? Only the technically qualified proposals move to financial evaluation.
Implication 1: Technical Fitness Comes First. Your primary goal in the technical proposal is not to win on cost, but to be in the technical winner pool. If you are disqualified or score low technically, your price is irrelevant. Focus relentlessly on addressing every evaluation criterion with evidence and detail. Generic, light technical proposals lose.
Implication 2: Price Does Not Compensate for Technical Weakness. A common misconception: "We will win on price even if our technical proposal is mediocre." False. Most tenders set a minimum technical score threshold. Proposals below that threshold are rejected even if they quote the lowest price. You must meet the technical bar first. Only then does price matter.
Implication 3: Once Technical is Approved, Price Becomes Critical. After passing technical evaluation, evaluators compare financially qualified bids using a scoring formula. The formula typically rewards lower price, but also considers value-add elements (warranty, support, timeline acceleration). If you are technically equivalent to competitors, your price will determine the winner.
Strategic Implication 1: Separate Your Writing Teams. Your technical and financial proposals serve different purposes and audiences. Your technical team (project managers, engineers) should own the methodology section. Your financial team (accountants, estimators) should own the cost breakdown. These are different skills. Do not merge them into a single document or hand them both to a single writer.
Strategic Implication 2: Use Different Evidence. In your technical proposal, lead with past projects, team credentials, and process controls. In your financial proposal, lead with cost transparency, unit rates from similar work, and contingency buffers. Technical credibility comes from depth and case studies. Financial credibility comes from structure and benchmarking.
Strategic Implication 3: Coordinate Without Confusion. Your technical methodology and financial estimate must align. If your technical proposal claims you will deliver in 12 months with a team of 6 people, your financial proposal must show costs consistent with that plan (salaries, overhead, materials for a 12-month 6-person scope). Misalignment between technical and financial sections is a red flag to evaluators.
Red Flag Check: Before submitting, read both proposals side-by-side. Do they tell the same story? Does your budget make sense for your proposed timeline and team size? Are your quoted deliverables 100% aligned between sections? Inconsistencies are costly.
Final Thought: Treat your technical and financial proposals as two halves of a single argument. The technical half says, "Here is how we will succeed." The financial half says, "Here is what it costs." Both must be compelling, consistent, and Saudi-context aware.