Why does a quotation template matter more than a price list?
A price list tells your team what things cost. A quotation template tells your team, your customer, and your auditor what was promised, on what basis, and who approved it. In Saudi B2B sales, the quote is often the first formal document a buyer forwards internally — to procurement, finance, and sometimes to a technical committee. If the template is loose, every reviewer fills the gaps differently, and the deal slows down.
A controlled template does three jobs. First, it makes the offer comparable: the buyer can line up your quote against two others because the fields are predictable. Second, it protects margin: pricing rules, validity windows, and exclusions are stated once and not renegotiated by accident in an email thread. Third, it creates a record: the version that was approved is the version that was sent, which matters when a dispute or a PDPL-related data request arrives months later.
This guide is written for Saudi enterprises and is reusable across GCC markets where the same commercial logic applies. It covers the fields, a worked example, an approval checklist, and where a governed AI agent such as SmartQuote, LeenAI's AI Quotation System, fits without taking the decision away from your team.
What fields must a quotation template contain?
Start with identity and traceability. Every quote should carry a unique quotation number, the customer's RFQ reference, the date of issue, the sales owner, and the version number. Without an RFQ reference, you cannot prove later that you quoted what was asked. Without a version number, you cannot tell whether the customer is holding the current offer or an outdated one.
Then the commercial core: line items with description, quantity, unit of measure, unit price, and line total. State the price basis explicitly — ex works, delivered, installed, or subscription — because the same number means different things under each. Add currency, tax treatment as advised by your finance team, payment terms, delivery lead time, and quotation validity. Finally, terms and exclusions: what is included, what is not, warranty scope, and the conditions that void the price (for example, quantity changes or site access delays).
A short approval block belongs on the document itself: approver name, role, date, and any conditions attached to the approval. This single block is what turns a template into a governed artifact.
Worked example: a supply-and-installation quote
Consider a Saudi facilities contractor responding to an RFQ for a small installation. The customer asks for supply and install of equipment across two sites, with a delivery window and a commissioning requirement. A weak quote lists one lump sum. A strong quote separates supply, installation, commissioning, and delivery, because each has a different cost driver and a different exclusion.
The line items might read: equipment supply (quantity, unit, unit price), installation labour (estimated days, rate basis), commissioning (fixed scope), and delivery to two sites (per-site basis). Exclusions state that civil works, power provision beyond the agreed point, and permits are the customer's responsibility unless quoted separately. Validity is stated, and payment stages are tied to delivery, installation, and acceptance rather than to a single date.
Nothing in that example requires a real customer or an invented result. The point is structural: the template forces the salesperson to expose assumptions, and the approver can see exactly what is being committed. For contracting and supply-and-installation sectors, this separation is often the difference between a profitable job and a dispute.
How do you write a professional quotation step by step?
Begin with the request, not the template. Read the RFQ, list every requested item, and mark anything ambiguous — an unclear unit, a missing specification, or a delivery condition that changes cost. Ambiguity should trigger a clarification to the customer, not a silent assumption in the quote.
Next, match each requested item to your catalogue or approved price source. Where the item is non-standard, record the basis for the price so the approver can review the reasoning, not just the number. Calculate totals, then check terms: validity, payment, delivery, warranty, and exclusions. Before sending, run a pre-send review: does the quote reference the correct RFQ, are quantities and units consistent, is the price basis stated, and has the right person approved it?
This is also where a governed drafting agent helps. SmartQuote reads the RFQ, matches items to your catalogue, applies your pricing rules, and produces a draft. The draft is not the quote — a human reviews it, edits where needed, and approves. The value is in the first pass, not in removing the reviewer.
Where does AI drafting fit without taking over the decision?
AI drafting fits best where the work is repetitive and the rules are explicit: reading RFQs, extracting line items, matching to catalogue, and applying approved pricing. It fits poorly where the request is genuinely novel or where a commercial judgment call is required. A well-scoped agent should stop and flag exceptions rather than guess.
Governance is what makes this safe. LeenAI's default integration is read-only through an API or scheduled exports, and write actions require UAT and explicit change control. In practice, that means the agent can read the RFQ and your catalogue, but it cannot send a quote or change a price without a human approving it. Every change is recorded, so the approved version is traceable.
LeenAI presents a PDPL-aware posture: data minimisation, role-based access, audit logs, and retention rules documented before code. For quotation workflows, that matters because RFQs often contain customer contact details and commercial terms. If you want to see how a pilot is scoped around one workflow, see how we scope pilots or talk to us.
What does a pre-send approval checklist look like?
A checklist should be short enough to be used and specific enough to catch real errors. A practical version covers five areas: request traceability (RFQ reference, customer name, version), commercial accuracy (quantities, units, price basis, totals), terms (validity, payment, delivery, exclusions, warranty), compliance (data handling, required disclosures), and approval (named approver, date, conditions).
Each item should have an owner. The salesperson owns traceability and accuracy; finance or commercial owns terms; the approver owns the final sign-off. When an item fails, the quote returns to draft with a recorded reason. That record is useful later: it shows what was corrected and why, which is exactly the kind of evidence an auditor or a customer dispute may require.
A checklist also makes automation safer. If the agent prepares the draft and the checklist is applied consistently, the reviewer's attention goes to exceptions rather than to routine fields.
Common mistakes and how to avoid them
The most common mistake is a quote that cannot be traced to the request. It happens when the salesperson works from memory or from an old template. The fix is a mandatory RFQ reference and a version number on every quote.
The second is inconsistent price basis: one line delivered, another ex works, with no note. The fix is a single stated basis per quote, or an explicit per-line basis. The third is silent assumptions about exclusions — civil works, permits, or site access — which surface later as change orders. The fix is to list exclusions explicitly, even when they feel obvious.
The fourth is approval by email thread. It feels fast, but it leaves no reliable record of who approved what. A named approval block on the document, with a date and any conditions, is a small habit with a large governance payoff. Finally, avoid treating a quotation as an invoice: they serve different purposes, and your finance team should confirm the tax treatment that applies.
If you are evaluating whether to build this as a governed pilot, start here or book a diagnostic. LeenAI aims to deliver a working system with handover logic in a 6–8 week operating-model timeline, scoped around one named decision.




