> ## Documentation Index
> Fetch the complete documentation index at: https://hc.starbridge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# RFP Bridge

> Build an RFP Bridge that surfaces relevant procurement opportunities from tens of thousands of active bids — and score them against your specific requirements fit.

## Overview

Starbridge continuously monitors SLED-focused RFPs, pulling from state and local government procurement portals, third-party aggregators, municipal websites, and custom web sources.

The RFP Bridge applies your search logic and scoring criteria to surface only the RFPs worth acting on - filtering out everything that's out of scope, already expired, or a poor fit before it reaches your reps.

The key insight: **not all RFPs that mention your product category are worth pursuing.** An RFP for "learning management software" could be a \$10M statewide contract or a 50-seat pilot for a single school - and the requirements inside the document determine whether you can win it. Your bridge results should reflect that.

## Building your Bridge

The bridge building flow for RFPs follows the same three-phase structure as other bridge types in Starbridge: **Describe → Refine → Create**.

<Note>
  For a full walkthrough of the bridge building flow — including how to set buyer filters, search phrases, match score criteria, and preview results — see the [Bridge Building Flow](/builders/how-to-build-a-bridge) guide.
</Note>

## Configuring good search phrases

Search phrases define the candidate pool - the set of RFPs Starbridge evaluates against your scoring criteria. Cast a wide net here; filter hard in scoring.

### Think about how agencies describe what they're buying

RFP language varies significantly across agency types, geography, and procurement staff. The same need gets written many different ways. Your phrases should capture that variation - not just the canonical product name.

<Tabs>
  <Tab title="✓ Broad requirement language (use this)">
    | Category            | Example search phrases                                                                                                          |
    | ------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
    | ERP / Finance       | "financial management system" OR "enterprise resource planning" OR "accounting and budgeting software"                          |
    | LMS                 | "learning management system" OR "online training platform" OR "eLearning courseware" OR "professional development platform"     |
    | GIS / Mapping       | "geographic information system" OR "mapping software" OR "spatial data platform" OR "land records management"                   |
    | HR Software         | "human resources information system" OR "payroll management software" OR "workforce management platform"                        |
    | Cybersecurity       | "managed security services" OR "endpoint detection and response" OR "cybersecurity assessment" OR "network monitoring services" |
    | Document Management | "document management system" OR "records management software" OR "content management platform" OR "digital archiving"           |
  </Tab>

  <Tab title="✗ Too narrow or too broad (avoid this)">
    | Issue                    | Example                                 | Problem                                     |
    | ------------------------ | --------------------------------------- | ------------------------------------------- |
    | Single product name only | "Workday"                               | Misses RFPs that don't name your competitor |
    | Generic category         | "software"                              | Returns everything                          |
    | Internal jargon          | "K–12 SIS v2.0"                         | No agency writes this in a bid              |
    | Acronym only             | "HRIS"                                  | Misses agencies that spell it out           |
    | Too narrow               | "fleet management for fire departments" | Cuts out police, public works, transit      |
  </Tab>
</Tabs>

### Cover the edges of your category

The most valuable RFPs are often ones that don't use your exact product name. Think about adjacent terms, functional descriptions, and how different buyer segments write about the same need:

* Different agency types write differently: a K–12 district's "student information system" RFP looks different from a city's "resident services platform" — even if you serve both
* Procurement staff often use outdated or non-standard terminology: "legacy system replacement" might refer to a category you modernize
* Services and software are sometimes bundled: "implementation and training services" may appear alongside the software RFP, or instead of it

## Finetuning RFP scoring criteria

This is where the RFP Bridge earns its value. Scoring criteria let you describe, in plain language, what makes an RFP actually worth pursuing - and what disqualifies one. The goal is a bridge where every high-scoring result is a real opportunity your team should evaluate.

### Structure criteria around requirements fit

Unlike the Meetings Bridge, where scoring is about buying stage, RFP scoring is about **fit** - whether the specific requirements inside the document align with what you sell, how you sell it, and who you sell to.

<Columns cols={2}>
  <Card title="Positive criteria" color="#22c55e" icon="circle-check">
    Include signals that indicate a strong fit with your offering:

    * RFP requires specific capabilities or features you provide
    * Scope (seat count, agency size, contract value) matches your target segment
    * Contract structure is one you can bid on (open RFP, cooperative purchase, sole source)
    * Timeline and implementation requirements are feasible
    * Funding source is confirmed (grant-funded, budget allocated, bond-approved)
  </Card>

  <Card title="Negative criteria" color="#ef4444" icon="circle-xmark">
    Exclude RFPs that aren't worth pursuing:

    * Scope is too small or too large for your business
    * Requirements include capabilities you don't offer
    * Incumbent vendor is named and sole-source language is present
    * Mandatory certifications or partnerships you don't have
    * Primarily a services contract, not a software or product buy
  </Card>
</Columns>

### Use criteria to describe the requirements you need to see

The most powerful use of scoring criteria in the RFP Bridge is going inside the document — telling Starbridge what to look for in the RFP's actual requirements section, not just its title or summary.

<AccordionGroup>
  <Accordion title="Scoring for specific features or product requirements" icon="list-check">
    If your product has a specific capability that differentiates you — or a hard dependency — encode that in your criteria:

    **Positive:**

    > *"The RFP specifically requires integration with existing SIS or student data systems, real-time reporting dashboards, or mobile-accessible interfaces."*

    **Negative:**

    > *"The RFP requires on-premise deployment, custom hardware, or a government-hosted private cloud — ruling out SaaS-only vendors."*

    This tells Starbridge to score higher when those requirements appear in the document, and lower (or exclude) when disqualifying requirements appear.
  </Accordion>

  <Accordion title="Scoring for scope and contract size" icon="ruler">
    Two RFPs can share identical search phrases but represent wildly different opportunities. Use criteria to filter by scope signals buried in the document:

    **Positive:**

    > *"The RFP mentions a user base of 1,000+ employees, a multi-year contract term (3–5 years), or a budget estimate above \$500,000."*

    **Negative:**

    > *"The RFP is a pilot or proof-of-concept with fewer than 100 users, or explicitly states a budget under \$50,000."*

    Note: budget ranges are often present in RFPs as estimates or funding source descriptions even when not listed explicitly.
  </Accordion>

  <Accordion title="Clarifying ambiguous product categories" icon="magnifying-glass">
    Broad category terms surface a wide range of RFPs — use criteria to narrow to the ones that actually match:

    If you sell **cybersecurity software** specifically (not managed services):

    > *"The RFP is for a software platform or SaaS product — NOT a managed security services contract, staffing augmentation, or consulting engagement."*

    If you sell **body-worn cameras** (not general surveillance):

    > *"The RFP is specifically for law enforcement body-worn camera equipment or programs — NOT in-vehicle dash cameras, fixed building surveillance, CCTV infrastructure, or drone video systems."*

    If you sell **HR software to government** (not private sector):

    > *"The issuing agency should be a government entity, school district, or public institution — NOT a private company, nonprofit, or commercial organization."*
  </Accordion>

  <Accordion title="Catching the right contract type" icon="file-contract">
    RFPs, RFIs, ITBs, and sole-source notices all look similar in search — but require very different responses. Use criteria to filter for the contract types your team pursues:

    **Positive:**

    > *"The solicitation is a competitive RFP, RFI, ITB, or cooperative purchase opportunity open to multiple vendors."*

    **Negative:**

    > *"The notice is a sole-source justification naming an incumbent vendor, a notice of intent to award already completed, or a contract extension rather than a new procurement."*
  </Accordion>
</AccordionGroup>

## Use the preview to calibrate and refine scoring criteria

Before launching your Bridge, open the **Preview** and deliberately review results across the full scoring range - not just the top results.

<Steps>
  <Step title="Review high-scoring results">
    Confirm these are RFPs your team would actually pursue. If something scores high that shouldn't:

    * Identify which requirement or phrase is triggering it
    * Add a negative criteria that captures why it's a poor fit
    * Raise the match score threshold if results are broadly noisy
  </Step>

  <Step title="Review low-scoring results">
    Look through results in the bottom half of the score range. If you find an RFP that *is* relevant but scored low:

    * Read the match reasoning - Starbridge explains why it scored the way it did
    * Identify what language in the document makes it relevant
    * Add a search phrase or positive criteria that captures that signal
  </Step>

  <Step title="Iterate until the scoring feels right">
    You're looking for a distribution where high-scoring results consistently match your ICP and win criteria, and low-scoring results are genuinely poor fits. For RFP Bridges, expect to refine criteria around scope, requirements, and contract type — these are the most common sources of noise.
  </Step>
</Steps>

## Enriching your RFP Bridge

Once your Bridge is created, add columns to make each result immediately actionable for your team.

### RFP Bridge-specific columns

RFP Bridges include structured data fields pulled directly from the procurement document:

| Column       | What it contains                                                                |
| ------------ | ------------------------------------------------------------------------------- |
| **Due Date** | The RFP submission deadline — useful for prioritization and sequencing outreach |
| **Status**   | Active, expired, awarded, or cancelled                                          |
| **Issuer**   | The name of the procuring agency                                                |

These default columns can be referenced as inputs in your AI Analysis and email outreach - for example, using `@Due Date` in an automated follow-up sequence.

### Other useful enrichment columns

<AccordionGroup>
  <Accordion title="AI Analysis" icon="sparkles">
    Use natural language to analyze the RFP document directly. Common RFP Bridge use cases:

    * *"Does this RFP include any mandatory certifications, teaming requirements, or vendor qualifications that would disqualify us? List them."*
    * *"Identify the top 3 evaluation criteria listed in this RFP and explain how a response should be weighted."*
    * *"What is the estimated contract value or budget range mentioned in this RFP?"*
    * *"Write a one-paragraph summary of this RFP for a sales rep preparing a bid/no-bid decision."*

    AI Analysis works within the document content — it doesn't search the web.
  </Accordion>

  <Accordion title="Web Agent" icon="globe">
    Use the Web Agent for context outside the RFP document itself:

    * *"Has this agency issued similar RFPs in the past 3 years? What vendors were awarded?"*
    * *"What is this buyer's current technology stack or incumbent vendor for this category?"*
    * *"Are there any news articles about this agency's budget situation, leadership changes, or strategic initiatives?"*
  </Accordion>

  <Accordion title="Vendor Presence" icon="building">
    Check whether the issuing agency has an existing contract with a competitor. Useful for estimating incumbent risk and tailoring your response — especially when the RFP mentions an "existing system" the new vendor must integrate with or replace.

    <Tip>
      See the [Vendor Presence](/vendor-presence) guide for how to set up this column type!
    </Tip>
  </Accordion>

  <Accordion title="Contact column" icon="address-book">
    Add a web-based contact to surface the procurement officer, department head, or decision-maker at the issuing agency. Useful for reaching out before the official submission deadline — or after a bid is submitted — to build the relationship.
  </Accordion>
</AccordionGroup>

## Next steps: Explore other bridge types

The RFP Bridge catches buyers who are already in procurement. Pair it with earlier-stage signal sources to build a complete pipeline.

<Columns cols={2}>
  <Card title="Meetings Bridge" icon="users" href="/builders/meetings-bridge">
    Surface buyers 6–18 months before they issue an RFP — when they're describing problems in board meetings and strategic plans. The earliest signal available.
  </Card>

  <Card title="Purchases Bridge" icon="receipt" href="/builders/purchases-bridge">
    Identify contracts with competitors that are expiring. Buyers renewing or replacing an existing solution are often the most receptive to an RFP conversation.
  </Card>

  <Card title="Conference Bridge" icon="calendar-days" href="/builders/conferences">
    Track buyers attending procurement or industry conferences. Useful for pre-submission relationship-building with agencies your team is actively bidding.
  </Card>

  <Card title="Buyers Bridge" icon="building-columns" href="/builders/buyer-bridge">
    Build a static list of target agencies to score and prioritize across all signal types — including whether they have active RFPs, expiring contracts, or recent meeting signals.
  </Card>
</Columns>