Skip to main content

RFP Go/No‑Go Scoring

Ingests new RFP documents, applies a custom go/no‑go rubric, and outputs a pursue/no‑bid recommendation with a scored breakdown and cited reasons.

Jake Rosenthal avatar
Written by Jake Rosenthal
Updated over a week ago

What does this mean?

Teams make faster, consistent bid decisions, focus effort on high‑probability opportunities, and avoid time spent sifting through low‑fit RFPs.

How it works?

Ingests new RFP documents, applies your company’s custom go/no‑go rubric for fit, budget, timeline, scope, and required capabilities, and outputs a pursue/no‑bid recommendation with a scored breakdown and cited reasons—no portal access required.

Workflow steps

Step 1: Ingest new RFP document

The Workflow activates when a new RFP document is uploaded or received—whether from Google Drive, SharePoint, or uploaded manually.

Step 2: Extract RFP requirements

Cassidy parses the document to pull out key details: scope of work, budget parameters, timeline expectations, required capabilities, compliance requirements, and submission deadlines.

Step 3: Score against your go/no-go rubric

The Workflow applies your company's custom evaluation criteria—assessing fit, budget alignment, timeline feasibility, scope match, and capability requirements—and assigns scores to each category.

Step 4: Generate pursue/no-bid recommendation

Based on the scored breakdown, Cassidy produces a clear recommendation with cited reasons pulled directly from the RFP, explaining why the opportunity does or doesn't meet your thresholds.

Step 5: Deliver results for review

The scored breakdown and recommendation are sent to your team—via email, Slack, or Microsoft Teams—so decision-makers can quickly review and act without needing to access any external portal.

Did this answer your question?