Today the module measures one thing: how much of the fit score can be built for your company — how many of its 108 inputs are live. The fit score itself is not calculated yet. This page describes both, and says which is which.
What it does
The fit score is built from 108 inputs, grouped into five parts: how closely the customer matches your ideal customer, how well your product fits their problem, how likely they are to stay, whether they are profitable to serve, and how much room they have to grow. Each part is scored from 0 to 100, and the five are combined at fixed weights into one score. The inputs come from other modules — your customer records and signals first, then sales, customer, marketing and finance modules as each one starts running. So the score starts incomplete and fills up. Completeness is part of the answer, not a footnote: every score carries it, and every module that reads the score adjusts how far it relies on it. Below 30% complete the score is not used for decisions unless someone overrides that, and the override is recorded.What it produces
Its headline is two figures:
Each name links to its definition, which also says how the Data API and MCP will carry it — neither serves these two figures yet.
Behind them, the module produces:
How the score is built
These are the Balanced weights, which every company starts on. Three other weight sets exist — growth first, retention first and margin first — and changing to one is a joint decision of your CFO and CEO. Two adjustments follow: the whole score is scaled down when the data behind a customer is not reliable enough, and enterprise and small-business customers carry small weight shifts. A score of 75 or more is High fit, 45 to 74 Medium, under 45 Low.
An input that is not live yet counts as neutral, so an early score is incomplete rather than pessimistic. A customer whose records are not confidently matched across your tools is not scored at all. Fit score sets out the full rule.
How completeness is counted. The 108 inputs are counted a module at a time. When a module that feeds fit is running for you, all the inputs it feeds count as live; when it is not, none of them do. Completeness is the live inputs divided by 108.
The fit score’s definition gives typical completeness ranges for each stage of setup. Those come from the design; the counts above are the ones Beacon works from, and the two do not yet agree. Read the count.
What you see on its page
In Beacon, open Growth, then Go-to-market, and choose Customer fit. The page has six tabs:- Overview — how many of the 108 inputs are live, what the score may be used for, what switches on next and what it adds, the inputs bar by area, and the modules it reads from.
- Dashboard — where the module’s four charts will appear: customers by fit band, completeness over time, fit against net revenue retention, and recurring revenue by fit band. Each waits for a fit score.
- Signals & alerts — the seven alert rules, who each goes to and where. None is sending yet.
- Scorecard — every module that feeds fit, marked live, next step or later, the Balanced weights, and the fit bands. The other weight sets are shown, not switchable.
- Customers — where each customer’s score and its five parts will appear once scores exist.
- Setup — the four Customer fit questions, saved as you answer them.
What it needs
Customer fit starts as soon as your CRM is connected. Every other tool adds detail through the modules that read it, and none is required.
See Connect your tools for how each connection is made.
Reads from
Which modules read it
Several pages that are live today — Churn risk, Deal likelihood and Cost to serve among them — already have a place to look at customers by fit. They show Not scored there, because the fit score is not calculated yet, and none of the modules above receives a fit score today. The Modules page in The Brain shows which modules are running for you.
Alerts
No alert is sent yet. Six of the seven wait for the fit score. The completeness alert has its figure today, but Beacon does not send alerts yet.
Setup questions
- Which weight set should the fit score use? Recommended: Balanced. Another set is chosen by your CFO and CEO together.
- Keep the standard fit bands? Recommended: yes — High at 75 and over, Low under 45.
- From which deal stage should a low-fit deal raise an alert? Recommended: Proposal.
- Who reviews fit alerts? They receive the alerts and approve changes to the fit score.
What is not calculated yet
- The fit score, its five part scores and its band, for every customer.
- Completeness for each customer. The figure today is for your company as a whole.
- The four Dashboard charts, which all read the score.
- “Beacon fit” in your CRM, which waits for a score.
- The quarterly review of the weights against what actually happened to your customers.
- Alerts — none is sent yet.
Related
Modules
The ten module families and which modules are available today.
Fit score
The full rule behind the score, its weights and its bands.
Signals
The signals that feed all five parts of fit.
Connect your tools
What each connection unlocks, and which inputs switch on with it.
How confident a number is
How Beacon says how much of a figure it can see.
Boundaries
What Beacon reads, what it never changes, and what it does not decide.