Quick answer
A defined prospect-prioritization measure using fit and engagement evidence, distinct from contact eligibility, purchase probability and technical or financing approval.
Answer: Lead scoring assigns points or another defined measure to prospect records using selected fit and engagement evidence. Solar teams can use it to prioritize review and route inquiries, while keeping missing information visible. A rules-based score is not a calibrated purchase probability, a credit decision or proof of site suitability. Its criteria, data sources and resulting actions need regular outcome review.
Keep fit, engagement and contact eligibility separate
Fit asks whether the project matches the team’s service area, project type and delivery scope. Engagement asks what the prospect has actually requested or done. Contact eligibility asks whether a particular communication is permitted. Combining all three into one unexplained number makes it harder to act appropriately.
HubSpot documents separate fit, engagement and combined scores, with property/event rules, limits and configurable thresholds. Score types and availability depend on its subscription. This is an example of documented vendor functionality, not evidence that SurgePV natively scores leads or supplies a CRM.
Lead nurture automation uses follow-up rules after enrollment. Scoring can inform that process, but a person requesting a quote or asking a technical question should not be left waiting for a threshold.
Choose criteria that support a real routing decision
| Evidence | Appropriate interpretation | Review limitation |
|---|---|---|
| Service location | Relevant to the team’s actual delivery area | Verify the project address and current service scope |
| Project type and size | Match to the team’s capabilities | Unknown scope is a request for clarification |
| Decision-making role | Helps identify the appropriate conversation | Tenants, agents and commercial procurement teams may have different authority |
| Explicit consultation request | Direct reason to respond | Confirm the request and assigned owner |
| Meeting booked or completed | A concrete stage event | Booking is not a signed project |
| Proposal interaction | Possible interest in the specific proposal | Verify event identity and avoid repeated-event inflation |
Keep unknown values distinct from confirmed mismatches. A missing electricity bill does not prove low consumption. A renter may represent a building owner or commercial tenant; establish decision authority instead of automatically rejecting the record.
Roof age, geometry, shading and structural condition require appropriate project evidence. A sales score cannot approve them. Financing eligibility belongs in the applicable lender’s process; avoid using sensitive financial attributes as a casual proxy for sales interest.
A hypothetical points worksheet
For illustration only, suppose a team assigns 20 fit points for a confirmed service-area match and 10 for a confirmed decision-making role. It assigns 25 engagement points for an explicit consultation request and 10 for a booked appointment.
Fit = 20 + 10 = 30 points
Engagement = 25 + 10 = 35 points
Combined = 30 + 35 = 65 points
65 points does not mean a 65% chance of purchase. These invented weights illustrate transparent arithmetic, not validated solar sales thresholds. The request already calls for a response, regardless of the total. Do not count one event repeatedly through overlapping rules unless that accumulation is intentional and bounded.
A known service mismatch can route an inquiry for another response or referral. An opt-out should stop the relevant communication through an eligibility rule, not merely subtract points and leave the record enrolled.
Control noisy and stale signals
Mailchimp’s bot-activity guidance explains why automated interactions can inflate opens and clicks. A sequence of tracked clicks is not necessarily a person comparing equipment. Prefer explicit requests, verified conversations and documented stage changes when choosing high-priority actions.
Record source, timestamp, rule version and whether a value was customer-provided or inferred. Set limits for repeated events and define when older engagement should cease influencing priority. Review duplicate records and company/contact relationships; one commercial project can involve several people without representing several independent opportunities.
A CRM integration should preserve field meanings, update behavior and failures across systems. Do not assume every application calculates the same score or immediately receives every stage change.
Validate the decision the score is meant to improve
Compare outcomes within defined cohorts and a consistent observation period. Examine appointments, qualified opportunities and completed sales by score band alongside response times and service fit. Include unsuccessful and unresolved records rather than testing only closed customers.
High scores can appear to convert better partly because those prospects received faster attention. Track that treatment difference before interpreting the result as predictive accuracy. Adjust rules when actual evidence reveals missed useful inquiries or excessive false priorities; there is no universal hot-lead cutoff or guaranteed conversion uplift.
Maintain lead source attribution so channel mix is visible. Designers should flag unresolved technical assumptions, installers should identify delivery constraints, and sales teams should record real outcomes and reasons. The score supports accountable review rather than replacing it.
Frequently asked questions
Is a lead score a probability of purchase?
Not by default. A points system summarizes chosen criteria; a probability needs a separately validated and calibrated predictive model.
Should unknown site information reduce a score automatically?
Not necessarily. Keep unknown information visible and request clarification instead of treating it as a confirmed mismatch.
Are email opens reliable scoring evidence?
They can be noisy because of privacy features and automated activity. They should not outweigh an explicit request or verified conversation.
Does a high score approve a solar project or financing?
No. Site, engineering and financing decisions require their own evidence and applicable review processes.
Related Glossary Terms
About the Contributors
Co-Founder · SurgePV
Nirav Dhanani is identified by SurgePV as a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, conversion results, and market-expansion claims are not asserted without retained evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
