sales-engineer

Format the RFP requirements as JSON following the sample schema, then run rfp_response_analyzer.py against it. The script scores each requirement as Full, Partial, Planned, or Gap, applies priority weighting, and outputs a coverage percentage with a bid/no-bid recommendation.

Create a JSON file listing categories, features, and per-product scores, then run competitive_matrix_builder.py. It computes weighted competitive scores, identifies differentiators where your product leads, vulnerabilities where competitors lead, and generates win themes.

The analyzer recommends Bid when coverage exceeds 70% with three or fewer must-have gaps, Conditional Bid for 50-70% coverage, and No-Bid when coverage falls below 50% or must-have gaps exceed three. Strategic value and effort estimates also inform the decision.

The default framework spans five weeks: one week of setup, two weeks of core testing, one week of advanced testing, and one week of evaluation. Low-complexity POCs can compress to three weeks, while high-complexity ones may extend to eight weeks maximum.

All three scripts accept JSON files as input. The RFP analyzer expects requirements with priority and coverage status, the matrix builder expects categories with per-product feature scores, and the POC planner expects a poc_name plus optional scope items, stakeholders, and complexity.

Avoid POCs when there is no identified champion or decision-maker, no defined success criteria, no budget process underway, or when the request is effectively a free trial with no evaluation commitment. The POC planner flags stakeholder and timeline risks automatically.