> ## 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.
# Account Scoring (Beta)
> Score every account in your market on ICP fit and buying signals, powered by your Market configuration, Vendor Presence bridges, and an Account Scoring bridge.
Account Scoring is currently in **beta**. If you'd like access to this feature, please reach out to your Starbridge contact or [support@starbridge.ai](mailto:support@starbridge.ai).
## Why Account Scoring
Prioritizing your accounts is harder than it should be.
You probably already have a gut sense of how you'd rank your accounts — but that logic usually lives in someone's head or a spreadsheet that goes stale the moment a new signal comes in.
Account Scoring fixes that. Every buyer in your market gets one clear, explainable **account score (1–100)**, combining how well they fit your ideal customer profile with how active their buying signals are right now.
With Account Scoring, you can work your territory with intent — pulling up the accounts that match a specific play you're running, or simply working down your list starting with your hottest account.
Getting Account Scoring up and running takes two setup steps, followed by building your scoring logic and sharing it with your team:
Your organization's Market — buyers, customers, products, competitors, and complementary vendors — is already configured by default. Review it, especially your Buyers definition, since that's the buyer pool Account Scoring runs against.
Run vendor presence searches across your Market so competitive and complementary vendor data is ready to feed into scoring.
Start from scratch, or migrate an existing buyer bridge you've already been using for scoring.
Once you're happy with your scoring quality, share it out so the rest of your team can see it too.
Once buyers are scored and shared, you'll see account scores on feed cards, on buyer pages, and throughout the new Territory and Total Market Buyers views.
***
## Step 1: Confirm your Market
Market is the org-level configuration that describes how your organization sells, so Starbridge can tailor scoring, signals, and the broader product experience to your business instead of a generic template.
Market is configured by Admins. A default Market should already exist for your organization — this step is about **reviewing and confirming it's accurate**, not building it from zero.
Your Market is made up of five parts:
* **Buyers** — the accounts you sell to, defined using buyer filters. This is the most important part to get right, since it directly defines your organization's total addressable market (TAM) — the buyer pool that both Account Scoring and Vendor Presence bridges run against.
* **Customers** — who your current customers are, what your ideal customer profile (ICP) looks like, and the target job titles you typically sell to.
* **Products** — the product categories or problems your organization solves, rather than a catalog of individual SKUs or product names.
* **Competitors** — the vendors you compete against, tied to the specific products they compete on.
* **Complementary vendors** — vendors you sell or work alongside, but don't compete with (for example, a CRM provider like Salesforce).
Before moving on, double-check each of these — particularly your **Buyers** definition. If it's too broad, too narrow, or out of date, both your Account Scoring bridge and your Territory/Total Market views will inherit that mistake.
Market isn't just an input to Account Scoring — it also tailors the Starbridge experience across the rest of the product based on the buyers, products, and vendors you've told us about.
***
## Step 2: Set up Vendor Presence bridges
With your Market confirmed, the next step is setting up **Vendor Presence bridges** at the market level.
A Vendor Presence bridge lets you run a vendor presence search across **every buyer in your Market at once**, checking each one for:
* Any **competitor** vendors defined against your products
* Any **complementary** vendors you sell or work alongside
This step is highly recommended before you build your Account Scoring bridge. Vendor presence is one of the strongest available inputs into your Fit score — knowing whether a buyer already uses a competitor or a complementary vendor materially sharpens how well Account Scoring can rank them. Vendor presence data is also surfaced elsewhere in the product, including on individual buyer pages, so it's worth setting up even beyond scoring.
Once your Vendor Presence bridges have run, that data becomes available as a column option when you build your Account Scoring bridge in the next step.
***
## Step 3: Build your Account Scoring bridge
With your Market confirmed and Vendor Presence bridges in place, you're ready to build your **Account Scoring bridge** — a single, org-level bridge that scores every buyer in your Market.
Account Scoring bridges are set up by Admins.
Building your Account Scoring bridge follows six steps:
Decide whether to build your Account Scoring bridge from scratch, or migrate an existing buyer bridge you've already been using to score accounts.
Double-check that the Buyers defined in your Market are accurate — this is the buyer pool your Account Scoring bridge will run against.
Add the buyer attributes, vendor presence, and AI Analysis columns you want to count toward Fit. If you migrated an existing bridge, confirm the Fit attributes that came over are correct — you can review everything that migrated in the scoring migration report we provide once migration is complete.
You can also pull in data directly from your CRM to use as a Fit input: choose **Configure Integration**, then **Pull data from my CRM**. Any CRM data you bring in this way is grouped under Fit alongside your other attributes. Common examples include account type and whether an account has an open opportunity.
Add the bridges you want to count as signal sources. Only include bridges that represent actionable buying signals — exclude one-off analyses or bridges that don't reflect an active buying opportunity (for example, a bridge that looks for dissatisfaction with your own product).
For each fit attribute you've included, define what value indicates a strong buyer fit. For each signal type, define what indicates a strong buying signal. For both Fit and Signals, you can optionally add a prompt describing how different attributes or signal types should be weighed against and prioritized relative to one another (for example, "an RFP is the strongest signal, even without an accompanying meeting"). If you migrated an existing account scoring bridge, your original scoring prompt is migrated in under each fit attribute for you to review and confirm.
Run scoring on the first 5 buyers in your bridge to confirm everything is set up correctly, making edits as needed. Once you're happy with the results, run scoring for every buyer in your Market.
This produces one overall **account score (1–100)** per buyer, made up of:
* A **Fit score**, shown as a band of **Weak, Moderate, Strong,** or **Ideal** — reflecting how well a buyer matches the strong-fit definition you set for each included attribute, shaped by your overall Fit prompt if you provided one.
* A **Signal score**, shown as a band of **Ice Cold, Cool, Warm,** **Hot,** or **Burning Hot** — reflecting how active and timely a buyer's included signals are, shaped by your overall Signal prompt if you provided one, along with a short explanation of the opportunity it represents.
Fit and Signals then combine into the overall score with a few consistent principles: a strong-fit account with no active signals can still score highly on fit alone; among similar-fit accounts, hotter signals move a buyer higher; and a weak-fit account can get a lift from a hot signal but can't be pushed all the way into your best-fit tier.
Scores refresh daily as underlying signals refresh, but you'll need to manually re-run scoring after changing your Fit or Signal configuration. Any column added to the bridge after initial setup is excluded from scoring by default until you opt it in.
***
## Step 4: Share your scores with your team
Sharing scores is done by Admins.
Scores stay visible only to Admins while you iterate on scoring quality. Once you're happy with the results, open the **Account Scoring Guide** and toggle **Share scores**, or use the **Share score** button in the top right of the bridge screen. Either one shares your scores with the rest of your team.
Until you share scores, everyone outside the Admins running scoring sees **To be scored** wherever an account score would otherwise appear, so you have room to get your scoring methodology right before rolling it out.
***
## Where scores show up
Once your Account Scoring bridge has run and scores are shared, scores surface throughout the product:
* **On feed cards** — each account update in your feed now shows the buyer's account score alongside the change.
* **On the buyer page** — see the overall score plus the underlying Fit and Signal explanations for any buyer.
* **In the new Territory and Total Market Buyers views** — the Buyers page now has three tabs:
* **Territory** — scoped to a rep's own territory. Sort and filter by account score and by every underlying input that feeds into it (Fit attributes, vendor presence, signal types, and more).
* **Total Market** — the same functionality as Territory, scoped to every buyer in your organization's Market.
* **All Buyers** — the existing view you have today, unchanged. No account score or score-input columns appear here.
Buyer List configuration and management has moved to **Settings**, where it's accessible to Builders and Admins. You can still apply Buyer Lists as a filter on all three Buyers view tabs.
If your organization hasn't finished confirming its Market or hasn't set up a territory yet, the Total Market and Territory tabs will prompt you to do so rather than showing an empty view.
***
## FAQ
No — a default Market already exists for your organization. This is a review-and-confirm step, especially for your Buyers definition, not a build-from-zero step.
Yes, they're optional, but strongly recommended. Vendor presence is one of the strongest Fit inputs, and the data is also useful on its own — for example, on buyer pages.
No — when you build your Account Scoring bridge, you can choose to migrate from an existing buyer bridge instead of starting from scratch. Compatible fit attributes and your existing scoring prompt are brought over for you to review, and you'll get a scoring migration report summarizing exactly what came across. AI Analysis and custom web agent columns keep their existing values so you don't spend extra credits re-running them.
Account scores range from 1–100, blending a Fit band (Weak, Moderate, Strong, or Ideal) with a Signal band (Ice Cold, Cool, Warm, Hot, or Burning Hot). A top score generally means both strong ICP fit and an active, timely signal.
Market, Vendor Presence bridges for Market, and the Account Scoring bridge are configured by Admins. Buyer List management in Settings is available to both Builders and Admins.
***
Have questions or feedback on the Account Scoring beta? Reach out to your Starbridge contact or [support@starbridge.ai](mailto:support@starbridge.ai).