Proposals
AuraScore 83/100

Enterprise RFP Solution Architecture Compliance Matrix

Map enterprise software RFP requirements against native features, roadmap dependencies, and integration risks into a structured evaluation matrix.

Use this template when evaluating complex technical requirements during pre-sales RFP response stages. It helps solution architects assess platform compatibility, development scope, and operational risks before finalizing bid commitments.

Template

Role: Principal Pre-Sales Solution Architect specializing in enterprise B2B software proposals.

Context

  • Prospect: {{prospect_name}}
  • Proposed Software: {{software_solution}}
  • RFP Scope: {{rfp_requirements_summary}}
  • Target Deployment: {{target_deployment_model}}
  • System Integrations: {{integration_dependencies}}
  • Required Compliance: {{mandatory_compliance_standards}}

Task

Generate a comprehensive technical fit and compliance matrix evaluating the proposed software against the prospect's RFP specifications to guide bid governance, response scoring, and implementation risk mitigation.

Method

  1. Deconstruct {{rfp_requirements_summary}} into discrete functional domains: core workflows, architecture, data governance, and operational support.
  2. Evaluate each requirement category against the native capabilities of {{software_solution}}.
  3. Classify compliance status for each item using strict standards (Fully Supported, Roadmap Dependency, Custom Integration, or Not Supported).
  4. Assess technical feasibility under the specified {{target_deployment_model}}.
  5. Identify implementation friction points associated with {{integration_dependencies}}.
  6. Cross-reference platform security architecture against {{mandatory_compliance_standards}}.
  7. Formulate specific proposal narrative justifications and mitigation notes for all non-native or roadmap-dependent items.

Constraints

  • MUST use standard compliance tags: [Native], [Roadmap], [Partner/API], [Non-Compliant].
  • MUST NOT over-promise future product capabilities without specifying a delivery milestone.
  • Matrix rows must remain grouped by technical domain.
  • Delivery effort estimates must be qualified by low, medium, or high implementation risk.

Output format

  • Section 1: Executive Technical Viability Summary (100-150 words)
  • Section 2: Technical Compliance Matrix (Markdown table with columns: Requirement ID, Domain, Capability Description, Compliance Status, Effort/Risk Level, Proposal Positioning Notes)
  • Section 3: Critical Architecture Gap Analysis & Mitigations (3-5 structured bullet points)

Self-review

  • Ensure all elements from {{rfp_requirements_summary}} and {{integration_dependencies}} are explicitly addressed.
  • Confirm that compliance ratings accurately reflect {{mandatory_compliance_standards}} without unsubstantiated claims.
  • Verify table structure aligns with required column headers.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-proposals
technology-software
rfp
enterprise-software
pre-sales