Sales team receives RFP. 34 pages. Deadline in 2 weeks. Someone needs to read all of it.
Built RFP analyzer. 47 requirements extracted. Priorities identified. Deadline urgency calculated. Team briefed in Slack.
THE RFP RESPONSE PROBLEM:
RFP arrives. Team scrambles. What are the requirements? What's the deadline? What do they actually want?
Everyone reads the same document differently. Requirements get missed. Deadline approaches.
THE DISCOVERY:
Document extraction pulls structured RFP data. Code calculates urgency based on deadline. Slack alert with everything team needs.
THE WORKFLOW:
Gmail trigger catches RFP email → Get message with attachment → Document extraction pulls organization, project scope, requirements array, evaluation criteria, budget range, deadline → Code analyzes urgency and formats summary → Sheets logs to RFP tracker → Slack alerts sales team.
6 nodes. RFP intelligence automated.
THE REQUIREMENTS EXTRACTION:
JSON Schema captures requirements as array with: requirement text, priority (Required/Preferred/Optional), category.
Code counts: How many required vs preferred vs optional? What's the effort estimate?
THE URGENCY CALCULATION:
Days remaining to deadline determines urgency:
- ≤0 days → OVERDUE
- ≤7 days → Urgent
- ≤14 days → High
- >14 days → Normal
Color-coded in Slack alert. Team knows immediately if they're behind.
THE EVALUATION CRITERIA:
Extraction pulls how they'll score proposals. Criteria with weights. Now you know what to emphasize.
Budget range extracted when stated. Min and max. Know if it's worth pursuing.
THE TRANSFORMATION:
Before: 2 hours reading RFP. Requirements scattered across document. Deadline tracked manually.
After: 60 seconds to full analysis. Requirements counted. Urgency clear.
THE NUMBERS:
47 requirements extracted
34-page RFP analyzed
5 evaluation criteria identified
Urgency: Calculated automatically
Deadline tracking: Automated
What RFP requirements do you most often miss on first read?