Internal Reference

Sales Leads Inbox · RFI / RFP Triage

Fish Fry

Codename: Bite comes in → we fry it → it hits the table. Fish Fry is the structured ForgeFX pipeline for turning incoming opportunity emails into a reviewed sales package.

Input
Greg drops the lead

Email text, screenshots, RFI/RFP attachments, quote requests, deadlines, and any context already in hand.

Output
Branded sales packet

A ForgeFX-styled .docx analysis plus a short Slack summary for Greg to review before anything external happens.

Guardrail
Review before handoff

Mary/Sara handoff and Salesforce task creation happen only after Greg reviews the analysis.

What The Bot Does

Fish Fry runs the lead through nine ordered steps. Poor-fit leads stop early; strong or partial fits become response-ready material.

Analyze What It Is

Identify issuing organization, opportunity type, NAICS code, size standard, procurement pattern, and source context.

Assess ForgeFX Fit

Score Strong, Partial, or Poor based on VR/3D training, workforce development, digital twins, Unity/WebGL, and known gaps.

Map Where We Fit

For viable leads, name 2–4 ForgeFX-aligned scope tasks and flag any capability or procurement mismatch.

Extract Key Dates

Pull questions due, response deadline, RFP release, award date, and period of performance in clear calendar format.

Draft Vendor Response

Create a complete ForgeFX response with best-available estimates. Use [FILL IN] only when no reasonable estimate exists.

Draft Questions

Generate prioritized clarifying questions for the contracting officer, including due date and contact details when available.

Greg Review Gate

Deliver the branded .docx and short summary to Greg first. No external send or internal handoff before this review.

Handoff To Mary & Sara

After review, provide email-ready copy and attachments for Mary Pierce and Sara Golling to review, fill, and send.

Salesforce Follow-Up

Create at most one Salesforce Task for the single most important next action, with a real owner and deadline.

Bid / No-Bid Signals

  • Strong fit: custom VR/3D training simulator, workforce development, operator training, digital twin, or Unity/WebGL scope.
  • Partial fit: related simulation work with hardware, reseller, schedule, budget, or catalog-product constraints.
  • Poor fit: no meaningful simulation/training scope or requirements clearly outside ForgeFX delivery.
  • COTS catalog warning: single-unit OEM hardware + brochure + short quote turnaround + warranty language usually caps fit at Partial, leaning pass.
  • Reseller warning: if the sender is quoting for an end client, name both organizations and ask whether direct-to-end-client bidding is possible.

Standard Deliverables

  • Short Slack summary: issuing org, opportunity type, fit verdict, deadline.
  • Full branded .docx: analysis, fit rationale, dates, draft response, clarifying questions.
  • Original screenshots and attachments preserved with the reviewed packet.
  • Optional Salesforce Task: one owned next action, no scheduled reminder bot or cron job.
Important: Steps 7–9 wait for Greg review. The bot prepares the package; humans approve what leaves the building.

Operational Flow

1 · IntakeGreg provides the opportunity email and files in the working sales lead thread.
2 · AnalysisThe bot extracts the facts, classifies the opportunity, and identifies ForgeFX fit.
3 · PacketThe bot renders a ForgeFX-branded .docx instead of dumping long raw text into Slack.
4 · ReviewGreg checks the output and gives corrections, go/no-go, or process feedback.
5 · HandoffAfter review, the team receives email-ready response material and one Salesforce next action if needed.

Feedback Requested

Adam and Greg: use this reference as the working definition of Fish Fry. If the process should change — fit thresholds, handoff rules, document format, Salesforce ownership, or who sees what — reply with the tweak and the skill can be updated.