AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

sales-engineer

Use for pre-sales work: RFP coverage gaps, competitive feature matrices or planning and scoring a proof of concept. Runs rfp_response_analyzer.py, competitive_matrix_builder.py and poc_planner.py.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--sales-engineer at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 7

references/rfp-response-guide.md

RFP/RFI Response Guide

A comprehensive reference for Sales Engineers responding to Requests for Proposal (RFP) and Requests for Information (RFI).

RFP Response Best Practices

1. Pre-Response Assessment

Before investing time in a response, conduct a thorough bid/no-bid assessment:

Bid Criteria Checklist:

  • Do we have a pre-existing relationship with the customer?
  • Is there an identified champion or sponsor?
  • Do our capabilities align with >70% of requirements?
  • Is the deal size justified against the response effort?
  • Do we understand the competitive landscape?
  • Is the timeline realistic for our solution?

Red Flags for No-Bid:

  • No prior customer engagement (blind RFP)
  • Requirement language mirrors a competitor's product
  • Timeline is unrealistically short
  • Must-have requirements fall outside our platform
  • Budget is undefined or misaligned with our pricing

2. Response Organization

Executive Summary (1-2 pages):

  • Lead with business outcomes, not features
  • Reference the customer's specific challenges
  • Quantify value proposition with relevant metrics
  • State confidence level and key differentiators

Solution Overview:

  • Map directly to the customer's stated requirements
  • Use the customer's language and terminology
  • Include architecture diagrams for technical sections
  • Address integration with existing systems

Compliance Matrix:

  • Mirror the RFP's requirement numbering exactly
  • Use consistent coverage categories: Full, Partial, Planned, Gap
  • Provide clear explanations for each response
  • Include roadmap dates for "Planned" items

3. Coverage Classification

| Status | Score | Definition | Response Approach | |--------|-------|------------|-------------------| | Full | 100% | Current product fully meets requirement | Describe capability with evidence | | Partial | 50% | Met with configuration or workaround | Explain approach and any limitations | | Planned | 25% | On product roadmap | Provide timeline and interim solution | | Gap | 0% | Not currently supported | Acknowledge gap and propose alternatives |

4. Priority-Weighted Scoring

Not all requirements are equal. Weight them by business impact:

  • Must-Have (3x weight): Core requirements that are deal-breakers. Gaps here typically result in disqualification.
  • Should-Have (2x weight): Important requirements that influence the decision significantly.
  • Nice-to-Have (1x weight): Desirable but not critical. Often used as tie-breakers.

5. Response Writing Tips

Do:

  • Answer the question directly before elaborating
  • Use the customer's terminology, not internal jargon
  • Provide specific examples, case studies, and metrics
  • Include screenshots or architecture diagrams where relevant
  • Cross-reference related answers to avoid redundancy
  • Proofread for consistency across sections (multiple authors)

Avoid:

  • Marketing fluff or vague language ("best-in-class", "world-class")
  • Answering a question you were not asked
  • Contradictions between sections
  • Overselling capabilities you do not have
  • Ignoring the question format (tables vs. narrative)

Bid/No-Bid Decision Framework

Decision Matrix

| Factor | Weight | Score (1-5) | Weighted | |--------|--------|-------------|----------| | Technical fit | 25% | | | | Relationship strength | 20% | | | | Competitive position | 20% | | | | Deal value vs effort | 15% | | | | Strategic importance | 10% | | | | Win probability | 10% | | | | Total | 100% | | |

Scoring Guide:

  • 5: Strong advantage
  • 4: Slight advantage
  • 3: Neutral / competitive parity
  • 2: Slight disadvantage
  • 1: Significant disadvantage

Decision Thresholds:

  • Score >= 3.5: Bid - proceed with full response
  • Score 2.5 - 3.4: Conditional Bid - proceed with executive approval
  • Score < 2.5: No-Bid - decline or submit information-only response

Effort Estimation

Estimate the total effort required and compare against deal value:

| Response Component | Typical Effort (hours) | |-------------------|----------------------| | Requirements analysis | 4-8 | | Technical writing | 16-40 | | Architecture diagrams | 4-8 | | Demo preparation | 8-16 | | Internal review | 4-8 | | Final formatting | 2-4 | | Total | 38-84 hours |

Rule of thumb: The response effort should not exceed 2% of the deal value.

Compliance Matrix Structure

Standard Format

| Req ID | Requirement Description | Priority | Compliance | Response | Evidence |
|--------|------------------------|----------|------------|----------|----------|
| R-001  | SSO via SAML 2.0       | Must     | Full       | Native SAML 2.0 support... | Config guide |
| R-002  | Custom reporting        | Should   | Partial    | Standard reports + API... | API docs |

Section Organization

Organize requirements by category for clarity:

  1. Functional Requirements - Core features and capabilities
  2. Technical Requirements - Architecture, APIs, performance
  3. Security & Compliance - Authentication, encryption, certifications
  4. Integration Requirements - Third-party systems, data flows
  5. Support & SLA - Support tiers, response times, uptime
  6. Vendor Qualifications - Company size, financials, references

Common Pitfalls

1. The Wired RFP

Symptom: Requirements language matches a competitor's product feature list. Response: Focus on outcomes over features. Highlight areas of differentiation. Ask clarifying questions that expose broader needs.

2. Feature Checklist Syndrome

Symptom: RFP is a massive feature checklist with no context about business problems. Response: Group features by business outcome. Add context in your response that demonstrates understanding of the underlying need.

3. Scope Creep in Response

Symptom: Team keeps adding content that was not requested. Response: Assign a response manager to enforce scope. Answer what was asked, provide references for additional information.

4. Inconsistent Messaging

Symptom: Multiple authors provide contradictory information. Response: Assign a single editor for final review. Create a response style guide. Use consistent terminology throughout.

5. Overcommitting on Gaps

Symptom: Marking "Planned" items as "Full" to improve scores. Response: Never misrepresent coverage. Planned items with firm timelines and interim workarounds are better than lies discovered during POC.

RFP Response Timeline Management

Typical Response Timeline

| Day | Activity | |-----|----------| | Day 1 | Receive RFP, conduct initial review, assign team | | Day 2-3 | Bid/no-bid decision, questions submission | | Day 4-7 | Requirements analysis, coverage assessment | | Day 8-14 | Draft responses, architecture diagrams | | Day 15-17 | Internal review, quality check | | Day 18-19 | Final edits, formatting, executive review | | Day 20 | Submission |

Time-Saving Strategies

  1. Maintain a response library - Reusable answers for common requirements
  2. Pre-built architecture diagrams - Template diagrams for common integration patterns
  3. Standardized compliance language - Pre-approved language for security and compliance sections
  4. Question templates - Standard clarifying questions for common ambiguities

Last Updated: February 2026