كتابة العروض والتسعيرات

المتطلبات تصف قدرات يحتاجها النمط في بيئتك، مو الموردين اللي لازم تشتريهم. أي نظام يملأ متطلباً يحقّقه — وهذا اللي يخلّي الكتالوج قابلاً للنقل عبر الذيل الطويل من أدوات الشركات الصغيرة والمتوسطة.

1. deal_record

   مطلوبقراءةطلب

   The deal or opportunity the proposal is being written for. Source of customer, scope, stage, and any notes the rep has accumulated.

   شكل البيانات

   Deal record with customer association, current scope description, stage, expected value, products/services discussed, attached notes and call summaries.
   يُملأ عادةً بواسطة

   • opportunity record in the CRM
   • deal in a sales pipeline tool
   • structured project intake form
2. pricing_source

   مطلوبقراءةطلب

   Authoritative pricing the pattern uses for the quote. Critical: the pattern must never invent prices.

   شكل البيانات

   Rate card, product catalog, or pricing rules with SKUs, descriptions, list prices, and any standard discounting logic.
   يُملأ عادةً بواسطة

   • pricing module in the CRM or CPQ tool
   • rate card document the finance team maintains
   • product catalog in the e-commerce or billing system
   • spreadsheet maintained by RevOps
3. proposal_template_library

   مطلوبقراءةمجموعة

   Approved language, terms, and structural conventions the proposal follows. Keeps drafts on-brand and legally compliant.

   شكل البيانات

   Document templates with variable placeholders, modular sections (statement of work, terms, assumptions, exclusions), approved language blocks.
   يُملأ عادةً بواسطة

   • template folder in a document store with named templates
   • structured templates inside a proposal tool
   • approved boilerplate maintained by legal or operations
4. draft_output_destination

   مطلوبكتابةطلب

   Where the finished draft lands for the sales rep to edit and send.

   شكل البيانات

   Editable document tied to the deal: native format (Google Doc, Word) or proposal-tool format. Linked from the deal record.
   يُملأ عادةً بواسطة

   • Google Doc or Word document created and shared with the rep
   • draft inside a proposal-management tool
   • PDF generated and stored against the deal record
5. approval_routing

   موصى بهكتابةحدث

   Where drafts go for internal approval when they cross discount or scope thresholds.

   شكل البيانات

   Approval request with draft, deal context, what triggered the threshold, and routing to the approver.
   إذا مفقود

   Without explicit routing, threshold-crossing drafts either get sent without approval (bad) or get stuck on rep desks (also bad). Strongly recommend defining at least one approval gate.
   يُملأ عادةً بواسطة

   • approval flow inside the CRM
   • Slack notification to the approving manager
   • task created on the approver's queue
6. competitive_intelligence_corpus

   اختياريقراءةمجموعة

   Notes on how to position against likely competitors. Lets the proposal pre-empt comparisons and frame the offer correctly.

   شكل البيانات

   Per-competitor notes: positioning, common objections, our differentiators against them.
   إذا مفقود

   Proposals stay generic on positioning. Reps still add competitive framing manually when relevant.
   يُملأ عادةً بواسطة

   • competitive battle cards in the sales enablement tool
   • internal wiki section on competitors
   • structured notes maintained by sales operations