[BETA] New bridge building flow

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.

​

Overview

Good searches used to require you to think like the system: the right keywords, the right filters, the right order. One missing phrase could quietly drop the signals that mattered most, and when results came back off, it wasn’t clear whether the search was wrong or the data was. Our reimagined bridge building experience flips that around. You describe what you’re looking for in your own words. Starbridge breaks your intent down into a structured search - buyer filters, bridge filters, search phrases, and match score criteria - all visible and editable. You preview scored results, iterate until the bridge surfaces exactly what you want, and only then create it. Every result that lands in the bridge comes with a relevance score, an explanation of that score, and a summary of why the signal matters - so consumers can act without clicking into every row.

​

Who can use this and which bridges it applies to

Only builders and admins can create bridges. The new flow applies to the following bridge types:

• Meetings
• RFPs
• Purchases
• Conferences

Other bridge types (Job Changes, Custom Web Signals, Contacts, Buyer) continue to use their current creation flows.

​

The three phases of bridge building

The flow is the same for every supported bridge type:

1. Describe — Enter a natural language description of what you’re trying to find.
2. Refine — Review the structured search Starbridge generated for you. Edit buyer filters, bridge filters, search phrases, and match score criteria. Preview scored results.
3. Create — When the preview looks right, create the bridge.

​

Phase 1: Describe what you’re looking for

From the bridge creation entry point (for example, Create Bridge on the Meetings, RFPs, or Purchases page), you’ll land on a single input that asks you to describe your search in natural language. The more specific you are, the better the structured search will be. A good prompt typically includes:

• Who you’re looking at — the type of buyer, geography, size, or segment
• What you’re looking for — the topic, keyword, product category, or signal type
• Timeframe you’re interested in – things like “meetings in last 3 months”, or “RFPs due in the next 6 months”
• What “good” looks like — the conditions that make a result worth acting on (e.g., “actively evaluating alternatives,” “contracts expiring within 12 months,” “budget already allocated”)

You can skip the natural language input and jump straight to manually configuring filters and search phrases if you prefer - the button to do so is on the same screen.

​

Phase 2: Refine search and match criteria

After you submit your prompt, Starbridge analyzes it and generates a structured search draft. You’ll see a short animation while we break your query into filters, phrases, and scoring criteria - then the full Search and match criteria view opens for review. The structured search has four components. Each one is visible, editable, and independently tunable.

​

Buyer filters

Defines who you’re searching over. This controls the set of buyers whose signals are eligible to appear in the bridge. You can define buyer filters in one of three ways:

• Buyer lists — Use a pre-configured list or territory
• Buyer filters — Filter by geography, buyer type, size, classification, and other structured attributes
• Select buyers — Pick individual buyers by name

When Starbridge generates buyer filters from your prompt, we use attribute-based filters rather than pre-configured lists — that way, you can see exactly which attributes we selected and modify as needed. Buyer filters apply to all supported bridge types except Conferences.

​

Bridge filters

Filters specific to the signal type you’re searching. These are the structured fields native to the document itself — for example:

• Meetings and strategic plans — meeting type, date range, meeting body
• RFPs — RFP status, due date, issuer type
• Purchases — contract type, purchase type, effective and expiration dates, total value

​

Search phrases

Defines what you’re searching for - the specific phrases used to surface candidate signals from the document corpus. You can further add, edit, or remove search phrases to refine your search intent. A few things to know:

• Starbridge generates phrases proactively to make your search comprehensive. If a generated phrase doesn’t match your intent, delete it.
• For Meetings bridges, you can add up to 30 phrases to cast a wider net and improve accuracy.
• Auto-generate additional similar search phrases by using the “Add similar search phrases and keywords” option or by hovering over a specific search phrase and clicking the “+” button to generate additional phrases similar to that specific phrase
• Cast the net wide here, filter hard in scoring. Search phrases control which signals are evaluated for your bridge; match score criteria control which signals eventually make it into the bridge.

​

Match score threshold

Set a minimum match score — any signal scoring below it is excluded from the bridge entirely. Moving the threshold up is the fastest way to tighten a noisy bridge; moving it down is how you open it up if you’re missing results you expected to see. You can also toggle the preview between All signals, Above threshold, and Below threshold to see what you’re excluding and sanity-check that the threshold is set where you want it. To adjust the logic used to produce match scores, see “Match score criteria” section below.

​

Match score criteria

Defines what counts as a strong match. This is where you translate “a result I’d actually act on” into criteria Starbridge can apply to every potential signal. Write criteria as discrete statements under two headings:

• What makes a strong match — Criteria that define a good result (e.g., “Discusses an active evaluation or pilot,” “Mentions a named vendor under consideration”)
• Red flags - penalize or exclude — Criteria that weaken or exclude a signal (e.g., “Passing mention only, not the focus of the meeting,” “Historical reference with no current activity”)

​

Previewing your bridge results

Each result in the preview includes:

• The signal itself — the meeting, RFP, or purchase that matched
• A match score — the score for that result against your criteria
• A match reasoning — why that result received the score it did, tied directly to your match score criteria
• Summarized relevance — a longer plain-language summary of why this signal matters (Meetings only in v0; expanding to other bridge types)

You can view your bridge preview results in a table format or in a feed card format, depending on your preference. Iterate until the preview looks right. Common moves:

• Seeing irrelevant results? Add a disqualifier to your scoring criteria, or raise the threshold.
• Missing results you expected? Add a search phrase, widen a buyer filter, or lower the threshold.
• Scores feel off but results are correct? Tune the scoring criteria to ensure that different factors increase / decrease match scores appropriately 

Anytime you change filters, phrases, or criteria, you’ll be prompted to refresh your preview to see the latest results.

​

Phase 3: Create the bridge

When the preview matches what you want, click Save search as bridge. Your bridge is created with every existing signal that matches your criteria (which may include more signals than the bridge preview). Starbridge will to surface and add new relevant signals automatically as they appear. You can further enrich signals by adding columns to the bridge — contacts, CRM data, AI analysis, web agents, and more. Every bridge created through this flow includes three default columns:

• Match score
• Score explanation
• Summarized relevance

These are added to the bridge by default and are visible to both builders and consumers, so anyone acting on a signal can quickly see why it was surfaced.

​

Editing a bridge after creation

You can edit any part of the structured search after the bridge is created — buyer filters, bridge filters, search phrases, and match score criteria are all editable from the bridge’s settings. What you cannot edit after creation is the original natural language prompt. If you want to start over with a fundamentally different intent, duplicate the bridge and start a new search — this is intentional, to prevent silent drift between the prompt and the structured search it generated. Edits to scoring criteria rescore existing results; edits to filters or search phrases may surface entirely new results or drop existing ones.

​

Tips for a good search

A few patterns that consistently produce better bridges:

• Start broad, tighten with scoring. Generate a wide candidate set through search phrases, then use match score criteria to filter down to what’s actionable. Resist the urge to over-constrain phrases.
• Write disqualifiers, not just strong-match criteria. Naming what shouldn’t be in the bridge is often faster than describing every nuance of what should.
• Preview before creating. The preview is there specifically so you can catch problems before they turn into a cluttered bridge.
• If you’d describe the ideal result out loud, write that down as the prompt. Don’t translate it into keyword-speak — the whole point of the new flow is that you don’t have to.

​

Giving feedback

The team is actively collecting feedback during beta. We’d especially love to hear:

• How easy it is to get to the right results
• Anything that feels confusing or missing
• How it compares to how you’ve built bridges in the past

Share feedback with your CSA or in your dedicated customer Slack channel.