Guides › Integrations
CRM Insights & Value Projections Teach LeadLogiX what a lead is worth to your business from your own closed deals — without touching the objective score or price. Find it: Settings > Scheduled Jobs. New job → “Learn from my CRM”; projections then appear on each lead Before you start: A connected CRM — this reads from it and never writes. Closed deals in that CRM with amounts filled in. Deals closed without a value still count as closed but cannot tell LeadLogiX what one is worth.
Turn it on Create the job New job → Learn from my CRM , then authorise on your CRM's own sign-in screen — there is no key to copy. (Connecting Salesforce or HubSpot creates this job for you as their Insights job.) Set a commission rate, unless your deals carry one Expected value is close probability × commission, so without either it stays blank. If you run more than one line of business, map your deals to lines On the connection: HubSpot deal pipelines or Salesforce Record Types, each to a line. Uses another field? Name it in Field to read and map its values. Enable the job It runs daily. Its run notes say how many closed deals it found, and how many were placed on a line.
What you get — expected value to you A projection grounded in your own outcomes. Each lead shows a projected close probability , expected deal value and commission , an expected value (close probability × commission), and a typical sales-cycle length — labelled with the segment it came from and a confidence level. With too few comparable deals, LeadLogiX shows nothing rather than a shaky guess.
If you run more than one line of business Two businesses, two sets of economics — never one average of both. Each line gets its own value picture, and a lead is valued against the closed deals from its own line. The map is yours to edit — nothing in your CRM moves. Until you map anything, your workspace keeps one blended picture, and a line with no closed deals of its own falls back to it. A run that says SUCCESS can still be applied to nothing Success means deals were pulled — a separate question from whether they could be used. Deals your map does not cover are left out of the per-line figures and counted. Read the run notes: they say how many deals were placed on a line, or that none were, and why. You'll know it worked: An expected-value figure appears on your leads, and the calibration job's run notes say how many closed deals it used. Thin numbers with a note explaining why are the honest outcome — that is the job telling you it needs more history, not failing. If no expected value appears 1 · No closed deals have been pulled yet Nothing has been read from a CRM. Connect one, or check the calibration job has run — its history says how many closed deals each run found. 2 · Deals were pulled, but none could be placed on a line of business Your deals are healthy; LeadLogiX cannot tell which line each belongs to, so it refuses to apply them rather than credit one business with another's revenue. The message names the field it read and what it found — usually a value missing from your map, or a field your instance does not use. Both are fixed on the calibration job in minutes. 3 · Your deals are mapped, but not to this lead's line Nothing to fix — this line has no closed deals of its own yet, and fills in as you close business in it. Close probability shows, expected value is blank No commission figure on your deals and no commission rate on the job. The card says why. The numbers look thin Deals closed without an amount are left out of the averages, and the run notes say so. The firewall: insights never change the score or price CRM insights are display-only . They are built from your private history and kept strictly separate from LeadLogiX's LQI and price, which stay identical for every buyer. That separation is enforced in the platform itself, not just by policy: the scoring engine cannot reach the code that reads your CRM history, and the only writer of that history is the scheduled job that pulls it — nothing in your browser can edit it. Disconnecting is clean: delete a CRM's Insights job and everything learned from that CRM goes with it, including the history kept. Remove them all and LeadLogiX stops showing what a lead is worth to you and says so — scores, prices and spend carry on unchanged, because none of them came from your CRM. How it calculates: closed deals — what they closed for, won or lost, how long they took — are rolled into your own baselines of close rates, deal values, commissions and sales-cycle length, broken down by segment (such as geography or lead type) with a sample size each. Every new lead is matched to its closest segment. Expected value uses commission, not deal value, because what your client pays is not what you earn. Connected to more than one CRM, each is calibrated separately and the one with the most closed-deal history is used — never an average, because a number you cannot trace to one system is not worth much. Deal-size bands follow each line's scale, so a $400 premium is an ordinary insurance deal, not a tiny one. Insights tell you what a lead is worth; profiles tell you who the customer is and which campaigns produce them — see Customer Profiles on the Product tab. What Insights adds, and what it needs Capability Needs Pipeline projection from your own closed deals, not a benchmark Closed deals with amounts. Expected value per lead, traceable to your commissions and close rates At least one calibrated CRM. Quality-to-outcome comparison: where LeadLogiX's score and your outcomes agree Won/lost outcomes recorded. Field to read : leave blank for your CRM's usual field (pipeline, Record Type), or type the name of any field whose value tells one line from another — a deal type, a product, a business unit — exactly as your CRM stores it. LeadLogiX simply reads a different column. This page pulls history in ; pushing leads out is Connect a CRM . Use either or both.