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

assets/technical_proposal_template.md

Technical Proposal Template

Document Information

| Field | Value | |-------|-------| | Customer | [Customer Name] | | Opportunity | [Opportunity Name / RFP Reference] | | Prepared By | [Sales Engineer Name] | | Date | [Date] | | Version | [Version Number] | | Classification | [Confidential / Internal] |


1. Executive Summary

Business Context

[2-3 paragraphs summarizing the customer's business challenges and strategic objectives that this solution addresses. Focus on business outcomes, not technical features.]

Proposed Solution

[1-2 paragraphs describing the solution at a high level, emphasizing how it addresses the specific challenges identified above.]

Key Value Propositions

  1. [Value 1]: [Quantified benefit, e.g., "Reduce reporting time by 60%"]
  2. [Value 2]: [Quantified benefit]
  3. [Value 3]: [Quantified benefit]

Recommended Approach

[Brief overview of the implementation approach, timeline, and key milestones.]


2. Requirements Summary

Coverage Overview

| Category | Requirements | Full | Partial | Planned | Gap | Coverage | |----------|-------------|------|---------|---------|-----|----------| | [Category 1] | [N] | [N] | [N] | [N] | [N] | [X%] | | [Category 2] | [N] | [N] | [N] | [N] | [N] | [X%] | | Total | [N] | [N] | [N] | [N] | [N] | [X%] |

Key Differentiators

  1. [Differentiator 1 with brief explanation]
  2. [Differentiator 2 with brief explanation]
  3. [Differentiator 3 with brief explanation]

Gap Mitigation Plan

| Gap | Priority | Mitigation Strategy | Timeline | |-----|----------|-------------------|----------| | [Gap 1] | [Must/Should/Nice] | [Strategy] | [Date] | | [Gap 2] | [Must/Should/Nice] | [Strategy] | [Date] |


3. Solution Architecture

Architecture Overview

[High-level architecture description. Include or reference an architecture diagram.]

[ASCII architecture diagram or reference to attached diagram]

Example:
+------------------+     +------------------+     +------------------+
|   Data Sources   | --> |   Our Platform   | --> |   Delivery       |
|  - System A      |     |  - Ingestion     |     |  - Dashboards    |
|  - System B      |     |  - Processing    |     |  - API           |
|  - System C      |     |  - Analytics     |     |  - Exports       |
+------------------+     +------------------+     +------------------+
                                  |
                          +------------------+
                          |   Management     |
                          |  - Security      |
                          |  - Monitoring    |
                          |  - Admin         |
                          +------------------+

Component Details

[Component 1]

  • Purpose: [What this component does]
  • Technology: [Underlying technology]
  • Scaling: [How it scales]
  • Availability: [HA/DR approach]

[Component 2]

  • Purpose: [What this component does]
  • Technology: [Underlying technology]
  • Scaling: [How it scales]
  • Availability: [HA/DR approach]

Integration Architecture

| Integration Point | Protocol | Direction | Frequency | Authentication | |-------------------|----------|-----------|-----------|---------------| | [System A] | REST API | Inbound | Real-time | OAuth 2.0 | | [System B] | JDBC | Inbound | Batch (hourly) | Service Account | | [System C] | Webhook | Outbound | Event-driven | API Key |

Security Architecture

  • Authentication: [SSO, SAML, OAuth, etc.]
  • Authorization: [RBAC, row-level security, etc.]
  • Encryption: [At rest, in transit, key management]
  • Compliance: [SOC 2, GDPR, HIPAA, etc.]
  • Network: [VPC, firewall, IP restrictions]

4. Implementation Plan

Phase Overview

| Phase | Duration | Focus | Deliverables | |-------|----------|-------|-------------| | Phase 1: Foundation | [X weeks] | Environment setup, core configuration | Working environment, admin access | | Phase 2: Core Implementation | [X weeks] | Primary use cases, integrations | [Deliverables] | | Phase 3: Advanced Features | [X weeks] | Advanced scenarios, optimization | [Deliverables] | | Phase 4: Go-Live | [X weeks] | Testing, training, cutover | Production deployment |

Detailed Timeline

Week 1-2:   [Phase 1 - Foundation]
  - Environment provisioning
  - Security configuration
  - Data source connectivity

Week 3-6:   [Phase 2 - Core Implementation]
  - Use case 1 implementation
  - Use case 2 implementation
  - Integration testing

Week 7-8:   [Phase 3 - Advanced Features]
  - Advanced analytics
  - Custom workflows
  - Performance optimization

Week 9-10:  [Phase 4 - Go-Live]
  - User acceptance testing
  - Training sessions
  - Production cutover
  - Post-launch support

Resource Requirements

| Role | Hours | Phase(s) | Provider | |------|-------|----------|----------| | Solutions Architect | [X] | All | [Vendor] | | Implementation Engineer | [X] | 1-3 | [Vendor] | | Project Manager | [X] | All | [Vendor] | | Customer IT Admin | [X] | 1, 4 | [Customer] | | Customer Business Lead | [X] | 2-4 | [Customer] |

Training Plan

| Audience | Format | Duration | Content | |----------|--------|----------|---------| | Administrators | Workshop | [X hours] | Configuration, security, monitoring | | Power Users | Workshop | [X hours] | Advanced features, reporting, automation | | End Users | Webinar | [X hours] | Core workflows, self-service analytics |


5. Risk Mitigation

| Risk | Probability | Impact | Mitigation | |------|------------|--------|------------| | [Risk 1] | [H/M/L] | [H/M/L] | [Strategy] | | [Risk 2] | [H/M/L] | [H/M/L] | [Strategy] | | [Risk 3] | [H/M/L] | [H/M/L] | [Strategy] |


6. Commercial Summary

Pricing Overview

| Component | Annual Cost | |-----------|------------| | Platform License | $[X] | | Implementation Services | $[X] | | Training | $[X] | | Premium Support | $[X] | | Total Year 1 | $[X] | | Annual Renewal | $[X] |

ROI Projection

| Metric | Current State | With Solution | Improvement | |--------|--------------|---------------|-------------| | [Metric 1] | [Value] | [Value] | [%] | | [Metric 2] | [Value] | [Value] | [%] | | [Metric 3] | [Value] | [Value] | [%] |

Estimated payback period: [X months]


7. Next Steps

  1. [Next step 1 with owner and date]
  2. [Next step 2 with owner and date]
  3. [Next step 3 with owner and date]

Appendices

A. Detailed Compliance Matrix

[Reference to full requirement-by-requirement response]

B. Reference Customers

[2-3 relevant customer references with industry, use case, and outcomes]

C. Architecture Diagrams

[Detailed architecture diagrams]

D. Product Roadmap (Relevant Items)

[Roadmap items relevant to this proposal with estimated delivery dates]