Use case

Powering account scores in a sales platform with licensed signals

For product teams that put a score beside each account: what a weekly row carries, the three states a score can be in, how to survive a version change and what to settle in the licence.

Updated 9 October 20266 min read

A score beside an account is only as useful as the reason you can give for it and as stable as its definition. This guide is for the product and data team of a sales platform that wants to embed company-level account scores with their evidence. It covers what a weekly row carries, how to map it to your accounts, how to show it, how to keep the numbers stable through a change of version, and what the licence has to settle before you build.

What a weekly score carries

The intent dataset delivers Intent Scores (company_intent_weekly): a score from 0 to 100 for each company, topic and closed week in which the company scores on the topic. Weeks run from Monday to Sunday, UTC. Once a week has closed its rows are written, and they are not revised afterwards.

ColumnUse in your product
week_startThe Monday of the week scored. Label every score with it.
topic, topic_labelOne of 69 topics. Map them to your own vocabulary.
scoreRank accounts within a topic. Show it as a band you choose.
surgeTrue when the score has risen sharply against the company's own normal for the topic.
signalsHow many dated signals sit behind the score.
evidenceThe dated evidence behind the score. This is the reason to show.
intent_versionThe version the row was written under. Store it with every score you show.

Behind the score sit Company Signals (company_signals): every dated signal with its observed_at, topics and detail. The evidence on the row is enough for a first explanation. Query company_signals for the same company and topic when a user asks for more.

Every score is open to review through its evidence. The data is company-level, and routing to a person comes from the contacts you already hold.

Mapping scores to your accounts

Give every account in your platform a company_id. The domain of the account's website is the first key: match it to the domain column of the Technology Stack (company_technologies) or Web Traffic (traffic_ranks), both of which carry company_id. For a listed company, match on isin, figi or ticker with mic. Keep the basis of each match on the link, because a wrong match shows a user someone else's score. The guide to enriching company records in a data product covers matching in more detail.

A match run tells you what share of your accounts resolve to a company ID, and that share differs by account list. Your interface needs three states, not two.

StateHow you recognise itWhat to show
UnmatchedThe account has no company_id after matchingNo data. Never a zero.
Covered, no scoreThe company is in the files but has no company_intent_weekly row for the topic that weekNo score for the topic this week.
ScoredA row existsThe score, the surge flag, the evidence and the week.

A left join from your accounts, through your map to company_id, to the weekly table gives the three states in one pass.

select
  a.account_id,
  case
    when m.company_id is null then 'unmatched'
    when w.score is null then 'no_signal'
    else 'scored'
  end as state,
  w.score, w.surge, w.signals, w.evidence
from accounts a
left join account_company_map m on m.account_id = a.account_id
left join company_intent_weekly w
  on  w.company_id = m.company_id
  and w.topic      = :topic
  and w.week_start = :week_start;

A new weekly row arrives once a week. The signals behind it arrive daily, so an activity feed in your product can show evidence that is newer than the score.

Showing the score and the reason

An illustrative example for Acme Robotics shows the pattern: CRM, 68, week of 21 September, followed by one dated line for each entry of evidence, with the link from its detail where there is one.

Four rules keep the display honest.

  • Show a band, not a decimal. A user acts on a band, and a few points between two accounts do not change the call. Choose bands, and show the surge flag separately.
  • Show the number of signals. A high score resting on one signal is a thinner basis than the same score resting on eight.
  • Show the week. A score is as of the Sunday that closed its week, not as of today.
  • Carry the evidence. Every score comes with the dated evidence behind it. Put the signal count, the week and the top evidence line in the tooltip.

Fit and timing are separate questions. Keep this score as a timing input beside your own fit model and show both, so that a user can see whether an account ranks high because it fits, because the timing signals are strong, or both. The guide to prioritising accounts with intent scores shows how a revenue operations team combines them.

Versions and the change notice

Every weekly score is written under a version, recorded in intent_version, and a version does not change once released. A breaking change to the scores or the topics means a new version, announced at least 90 days ahead. For a platform whose customers learn to read a number, this is the property that matters most: the meaning of a 60 does not move under them.

Work to this routine from the first day.

  1. Store intent_version with every score you keep and show.
  2. On notice of a new version, read what the notice says has changed and list the tables and columns your product uses.
  3. Ask for an overlap in which both versions are delivered. Whether that happens, and for how long, is a matter for the agreement, not something the notice period guarantees.
  4. During the overlap, compare the same weeks. Take the rank correlation of old and new scores over your accounts for each topic, the share of your top 100 accounts that stay in, and the number of accounts that cross the surge flag in one version only. Read the accounts with the largest rank change together with their evidence.
  5. Set your own cut-over inside the 90 days and tell your customers. Do not promise them more notice than you receive: with 90 days from Fokals and 30 days to test and release, 60 days is the most you can promise.
  6. Keep old scores in your history under their version. Past weeks are never rewritten, so there is nothing to restate.

What to settle in the licence before you build

Fokals licenses data by written agreement for internal use, embedding in a product or redistribution. A sales platform that shows scores to its customers is embedding the data in a product, and is redistributing it if customers can export the rows. The data licence guide treats the three uses side by side. For this use, settle these points in the agreement.

  • The datasets: Intent Scores and Company Signals only, or the datasets behind the evidence as well.
  • Whether your customers may see the evidence and its detail, and whether they may export them.
  • Whether any attribution must travel with a value.
  • The overlap period for new versions, and the notice for changes that need no new version, such as additions to the technology catalogue, which the changelog lists.
  • What you may keep after the agreement ends, including past scores shown in your customers' reports.
  • The number of end customers or accounts covered.
  • Who answers a customer who disputes a score, and which public documents you may cite when you do.

How to read the scores

  • A score describes a company. It is evidence-backed: every score comes with the dated evidence behind it.
  • A row is as of the Sunday that closed its week, written once and never revised, so a score can be reproduced for any past week.
  • A surge flag marks a sharp rise against the company's own normal for the topic, and the evidence says what changed.
  • A version does not change once released, so a score means the same thing from one week to the next.

How Fokals delivers it

The weekly rows and the signals reach you by REST API or as bulk exports in JSON, JSON Lines or CSV, with scores refreshed weekly and signals daily. Every export comes with a manifest that lists its datasets, period and licence. The data platforms page describes licensing for embedding and redistribution.

Frequently asked questions

What is an account score in a sales platform?

An account score ranks or rates a company inside the platform, usually for fit with the product, for timing or for both. The score described here is a company-level intent score: a value from 0 to 100 for each company, topic and closed week. It describes a company, and every score comes with the dated evidence behind it.

Can I show my customers the evidence behind an intent score?

Each weekly row carries the dated evidence behind the score, so the data supports showing the reason beside the number. Whether your customers may see it, and whether they may export it, is a term of the licence. Settle it in the agreement before you design the screen.

How often do company intent scores update?

Weekly. A week runs Monday to Sunday UTC, and its scores are written when the week closes and are not revised later. The signals behind the scores are refreshed daily, so a feed of evidence can run ahead of the score. Label each score with the week it describes.

What happens to scores when a new version is released?

Every score is written under a version, and a breaking change arrives as a new version announced at least 90 days ahead. Store the version with every score you keep, plan a side-by-side comparison, and ask in the agreement for both versions to be delivered during an overlap.

What does an intent score tell a sales team?

It tells the team which accounts are active on a topic in a given week, and whether that is a change from the company's own normal. Each score is dated to its week and comes with the evidence behind it. Use the score to choose which accounts to approach and when, and use your own data to choose whom.

The queries and code on this page are examples to adapt. Test them in your own environment before you rely on them.