Proposals

Proposal Prompt 

• Federal: 

  1. Case Example (FBI: AWS to AWS-G Migration) -- Act like a 50 year experienced Proposal writer within the federal sector having a 99% success rate.  This is the FBI AWS to AWS Graviton Migration Proposal. Develop this comprehensive proposal, aligning with the Roadmap (attached), the 3x3 Matrix (to reduce cost, meet and exceed quality, and deliver as fast as possible), and select the best possible Progress platform here [https://www.progress.com/products] that would be highly useful in delivering maximum value and maximum impact benefitting the FBI. Important, be definitive! Most important, no AI hallucinations whatsoever! Also, attached is a PDF titled "TSC-MarkLogic-Cost-Reduction-Management" (Attached). Use this document's context as less or as much as you need, only if it is important, and highly useful in delivering maximum value and maximum impact benefitting the FBI. Otherwise, do not use it. Do you understand? Go! 

     • Add in initial prompt -- Assure actual evaluation factors GAO's Bid guide documents and federal source-selection boards use to judge proposals — Technical/Mission Suitability approach, Past Performance, Cost/Price realism, and compliance with the solicitation's stated evaluation criteria.

     • Missing context -- When information is missing, lacking, and not available, note a placeholder comment in BOLD text in brackets then providing a description of what is needed in bullet format and what team(s) or department(s) needs to fulfill the missing part(s) to meet maximum value and impact, and to meet or exceed a 99% success rate.

Federal Proposal (Standard)

• Federal Proposal 101: 

  1. One written in response to a government solicitation (RFP, RFQ, RFI, or grant NOFO) — follows a fairly standardized structure, largely because federal buyers evaluate against very specific compliance and scoring criteria. 

  2. Good federal proposal writers build the outline directly from Sections L and M — L dictates structure, M dictates emphasis and what wins points. Ignoring either is the fastest way to get an "unacceptable" rating regardless of technical quality.

• Regulations & Prompts:

  1. FAR (Federal Acquisition Regulation): The primary, government-wide rulebook that dictates how all civilian and defense federal agencies buy goods and services. It ensures fair competition, transparency, and consistency.

     • RAG -- Feed the RAG with the FAR document.

     • Prompt -- Must align with and address FAR rules. How (and Where) to Address FAR Compliance in Your Proposal Contracting Officers (COs) and technical evaluators are looking for risk mitigation. Handling FAR correctly depends on the section of your proposal: Compliance Matrix: If the RFP includes a section listing specific FAR clauses, you should include a compliance matrix cross-referencing how your solution meets those requirements. Avoid "Spamming" FAR Clauses: Do not copy-paste random FAR paragraphs into the technical narrative to sound smart. Evaluators want to read about your solution, your architecture, and your value proposition. Keep the technical volume focused on execution, and reserve FAR discussions for the administrative, pricing, and contract terms volumes. Subcontracting and Small Business Goals: The FBI cares heavily about socioeconomic goals and subcontracting plans governed by the FAR (e.g., FAR Part 19). If your proposal requires a small business subcontracting plan, explicitly highlight how you meet these regulations.

  2. DFARS (Defense Federal Acquisition Regulation Supplement): An additional layer of rules that applies specifically to the Department of Defense (DoD). It tacks on extra mandates regarding national security, strict cybersecurity standards (like CMMC / safeguarding controlled unclassified information), and domestic supply chain/manufacturing restrictions (such as specialty metal sourcing).

  3. Plus other Regulations that may apply...

• Core sections:

  1. Cover letter / Transmittal letter

     • Brief, formal letter identifying the solicitation number, your company, and confirming submission requirements are met.

  2. Executive Summary

     • High-level pitch: understanding of the requirement, your solution, and why you're the best-qualified offeror. Written to persuade a non-technical reader (often a contracting officer) as much as the technical evaluators.

  3. Technical Approach / Volume

     • The heart of the proposal — how you'll do the work. Typically organized around the government's Statement of Work (SOW) or Performance Work Statement (PWS), mirrored section-by-section so evaluators can easily cross-check compliance.

  4. Management Approach

     • Org chart, staffing plan, key personnel resumes, program management methodology, risk management, quality control plan, communication/reporting cadence with the government.

  5. Past Performance

     • References (often via CPARS — Contractor Performance Assessment Reporting System) demonstrating relevant, recent, similar-scope work, usually with points of contact the government can call.

  6. Cost/Price Volume

     • Often submitted as a separate volume so it doesn't bias technical evaluators. Includes labor categories/rates, ODCs (other direct costs), basis of estimate, and compliance with cost/pricing data requirements if applicable.

  7. Small Business / Subcontracting Plan (if applicable)

     • Required for larger contracts; outlines subcontracting goals for small, disadvantaged, veteran-owned, etc. businesses.

  8. Compliance Matrix

     • A cross-reference table mapping each Section L (Instructions) and Section M (Evaluation Criteria) requirement to where it's addressed in your proposal. Missing this is a common reason proposals get thrown out.

  9. Key structural drivers (for RFPs under FAR Part 15).

     • Section A – Solicitation/contract form

     • Section B – Supplies/services and prices

     • Section C – Description/specs/SOW

     • Section L – Instructions, conditions, and notices to offerors (tells you how to format/submit)

     • Section M – Evaluation factors for award (tells you how you'll be scored)