Back to Blog
solar business18 min read

Rank Commercial Solar Opportunities by Fit and Risk

A gated method for ranking commercial solar opportunities by customer fit, site evidence, delivery risk, economics, and scarce-resource demand.

Nimesh Katariya

Written by

Nimesh Katariya

Solar-industry contributor

Rainer Neumann

Edited by

Rainer Neumann

Editorial contributor · SurgePV

Published ·Updated

Quick Answer

Rank commercial solar opportunities in two passes. First apply stop gates for scope, site control, evidence, technical feasibility, authority path, and customer decision readiness. Then compare surviving opportunities by fit, risk, information quality, commercial value, and demand on scarce roles. Keep scores as decision aids and record the evidence behind every rating.

Commercial solar pipelines become crowded with projects that are large enough to look important and uncertain enough to absorb months of attention. A headline contract value can pull designers, estimators, executives, and finance partners toward a site before anyone has confirmed who controls the roof, which meters matter, or what decision the customer can actually make.

Ranking is a resource-allocation decision. It determines which opportunities receive site diligence, modeling, specialist review, procurement effort, and leadership time. That decision needs more than optimism and deal size.

The method below uses hard gates first and comparative priority second. It helps sales and operations leaders direct scarce work while leaving technical, financial, legal, utility, authority, and customer decisions with the appropriate people.

Decide what the ranking is allowed to do

Write the action tied to rank. Is the team choosing which opportunities receive a discovery call, interval-data analysis, preliminary layout, site survey, budget estimate, engineering review, or executive pursuit support? One score should not authorize every stage.

Rank within a comparable group. A portfolio RFP, owner-occupied warehouse, ground-mount development, and small retail roof may demand different evidence and specialist resources. Segment by sales motion, project class, market, or next diligence decision before comparing.

Name the planning horizon. A weekly work-allocation list differs from a quarterly market view. An opportunity can be strategically interesting but unready for immediate design. Preserve both observations instead of forcing one rank to express them.

Use four statuses alongside any score:

Status Meaning Appropriate action
Ready Evidence supports the next work package Assign within capacity
Conditional Valuable if a named gap is resolved Pursue the gap, not full work
Deferred Timing or evidence does not support current effort Record trigger and review date
Stopped Outside scope or fails an unresolved gate Close or route elsewhere

This prevents a high score from overruling a missing prerequisite. Scores compare degrees. Gates protect boundaries.

Build the evidence card before rating

Each opportunity needs a compact record that can be checked by someone other than the account owner. Use source labels and dates.

Include:

  • Customer entity, contacts, decision roles, and procurement route.
  • Site, property control, meter and load identity.
  • Customer objective and decision timing.
  • Roof or land information, electrical evidence, and known constraints.
  • Utility, authority, landlord, insurer, lender, or other external dependencies known so far.
  • Delivery model, finance concept, and responsible parties.
  • Requested work, next action, owner, and evidence gap.

Separate customer statements, external records, company observations, and planning assumptions. “Customer expects expansion” is not the same as an approved load plan. “Roof appears clear in imagery” is not a verified available area.

EPA’s solar project development process describes a path including site screening, procurement, design, permitting, construction, and operation for contaminated-land and related development contexts. Your commercial rooftop process will differ, but the source demonstrates why an early opportunity is not one undifferentiated unit. Different stages require different evidence and decisions.

Do not score an empty field as average. Mark it unknown. Unknown information can itself create work and risk, but it is not evidence that the underlying condition is bad.

Gate 1: company scope and customer fit

Ask whether the project lies inside the company’s current market, service, project, geography, competence, and risk boundaries. A potentially large project outside current capability may be a partnership or future-market question, not a normal pipeline opportunity.

Define scope in controlled terms. Include project types, size bands if the company uses them, delivery models, locations, customer classes, technical conditions, and work the company refuses or routes to partners. Obtain professional advice for licensing, contract, employment, tax, or regulatory boundaries.

Customer fit includes the problem the buyer is trying to solve and whether the company can responsibly support that decision. A buyer asking for an indicative rooftop option is different from one demanding a guaranteed return, fixed approval date, or technical commitment without site evidence.

Possible gate outcomes are pass, conditional, route, or stop. A conditional pass should name the required management decision or partner capability. Do not let every exception become a founder-approved “strategic” deal with no operating plan.

Gate 2: site and decision control

Commercial opportunities can involve a property owner, tenant, electricity account holder, parent company, procurement team, facility operator, and finance provider. Confirm who has authority over the roof, energy decision, contract, site access, and data.

The opportunity does not need every final document before screening. It needs a credible path to site and decision control. Ask who can authorize diligence, who must consent, what term or ownership condition matters, and what evidence will confirm it.

For a third-party structure, the roles change. EPA’s description of solar power purchase agreements explains that a developer may own, operate, and maintain the system while a host buys the generated electricity under contract. Do not rank a host-owned purchase and a PPA as if their approvals, risks, and resource needs were identical.

Stop or condition an opportunity when the main contact cannot identify the decision route, property control is incompatible with the intended structure, or the requested diligence would outrun the customer’s authority. Record the next evidence rather than labeling the buyer weak.

Gate 3: usable information for the next decision

Match evidence to work. A remote screening may use bills, imagery, customer statements, and available drawings with visible limitations. A tariff-sensitive commercial model may require interval data and current tariff treatment. A final layout or technical package needs site and professional review appropriate to its purpose.

Create an evidence sufficiency test for each work package. Do not simply count documents. Check identity, period, provenance, completeness, consistency, and freshness.

Evidence area Screening question Escalation trigger
Load Do records cover the intended meters and period? Missing meter, facility change, timing-sensitive case
Roof or site Can a candidate area be modeled with stated limits? Conflicting dimensions, unknown use, planned work
Electrical Is a preliminary boundary identifiable? Missing service evidence or unusual connection need
Customer Is the decision and audience named? No authority, unclear objective, contradictory requests
External path Are jurisdiction and utility identifiable? Unknown process controlling feasibility or schedule

An evidence gap may be easy to resolve. Rank the effort and likelihood of resolution separately from the condition itself. A customer who can provide interval data tomorrow is different from a site where meter ownership remains disputed.

Gate 4: no known fatal conflict at the current stage

The screening team should identify conditions that could make the proposed route infeasible, outside scope, or misleading. Examples might involve unavailable installation area, incompatible site plans, an unresolved ownership term, an external requirement the company cannot meet, or a customer schedule that excludes necessary diligence.

Do not turn screening into final feasibility. State the evidence reviewed and the boundary. A remote model cannot confirm concealed structure, actual electrical condition, authority approval, utility response, or equipment availability.

The U.S. Department of Energy’s PV system design basics describes modules, mounting, power electronics, and site considerations as parts of the system. The ranking card should reflect those interfaces without pretending to complete their detailed review.

When a fatal conflict is suspected but unverified, choose a bounded investigation. State the question, person, cost or capacity allowance, output, and stop condition. Do not allocate a full proposal package merely to discover whether the project has a viable roof.

Compare fit after the gates

Fit measures how closely the surviving opportunity matches the company’s chosen market and operating strengths. Define dimensions with observable anchors.

Useful dimensions include customer need, project class, geography, delivery model, evidence access, decision access, timing, and relationship. Avoid circular ratings such as “good fit because sales likes it.”

Use a simple ordinal scale with written definitions. For example:

  • Strong: directly inside the chosen scope with current evidence.
  • Acceptable: inside scope with ordinary, resolvable variation.
  • Weak: near the boundary and requiring a named capability or condition.
  • Unknown: evidence absent; no rating assigned.

Do not add unknown as a midpoint. Show coverage next to the rating. An opportunity with strong ratings on two observed dimensions and six unknowns should not outrank a fully evidenced acceptable project merely because the spreadsheet averaged blanks away.

Use a Bounded Model for the Next Diligence Decision

Explore how SurgePV can support commercial roof, layout, shading, energy, financial, electrical, material, and proposal work after your pipeline gate defines the project and evidence.

Explore Commercial Solar

Compare risk by exposure and treatment

Risk is not one red score. Separate categories that have different owners and treatments. Consider customer and contract, site, technical, utility and authority, delivery, procurement, finance, data, safety, and reputation as applicable.

For each material risk, record:

  1. Condition and source evidence.
  2. Decision or outcome exposed.
  3. Current uncertainty.
  4. Proposed treatment.
  5. Owner and review date.
  6. Residual condition after treatment.

Do not multiply invented likelihood and impact numbers into fake precision. A qualitative matrix can be useful if anchors are clear. “High” might mean the condition could stop the current project route or exceeds a defined management authority. “Low” might mean it is ordinary, controlled work inside an approved process.

Keep upside separate from risk. A large contract value does not reduce uncertainty. A strong relationship does not confirm roof structure. A familiar building type does not settle utility treatment. Let each evidence class stand on its own.

Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility.

The solar project constraint register can hold treatments after an opportunity receives diligence. It preserves the condition, evidence, owner, decision, and affected output without pretending the pipeline score resolved the project risk.

Compare resource demand at the constrained role

Estimate which roles the next work package requires and for how long, using internal observations where available. Separate routine production from scarce specialist review. A project that needs uncommon engineering, executive negotiation, complex interval analysis, or a difficult site survey may consume more constrained capacity than its nominal size suggests.

Build a resource request rather than one total-hour guess:

Work package Role Evidence required to start Effort basis Queue constraint
Load analysis Analyst Accepted meter and interval files Comparable internal cases Analyst availability
Candidate layout Designer Accepted site brief Project class and complexity Design queue
Site diligence Field role Question plan and access Site and travel plan Scheduling
Specialist review Qualified role Bounded decision pack Reviewer estimate Scarce expertise
Commercial response Sales and leadership Stakeholder and bid brief Procurement path Decision calendar

Label estimates and update them after work. The purpose is comparative allocation, not a fixed fee or schedule promise.

Inspect downstream demand. A fast proposal may create procurement and delivery work the company cannot accept in the customer’s window. Capacity is a chain. Rank opportunities with awareness of the constraint likely to matter if the customer proceeds.

Compare commercial value without letting revenue dominate

Use the value measure that fits the decision: expected gross contribution under approved assumptions, strategic account value, recurring portfolio potential, entry to a chosen market, or another management-approved factor. Keep each label precise.

Avoid treating total contract price as value. Costs, risk allocation, payment timing, warranty or service obligations, partner shares, and resource use matter. Finance should define the calculation and preserve source inputs.

Do not multiply a seller’s confidence by revenue and present the result as expected value unless the probability method is validated and governed. Stage-based probabilities often become inherited folklore. If historical data exists, segment it by comparable process and project type, then test whether the classifications remain predictive.

Strategic value needs a concrete mechanism. “Logo value” is vague. “This named customer can authorize a defined multi-site assessment if the first site meets its decision criteria” is clearer, though it still requires evidence and should not be treated as guaranteed future work.

Keep financial and strategic factors beside, not inside, stop gates. A lucrative opportunity outside responsible scope remains outside scope until the company deliberately changes its capability and authority.

What should a commercial solar opportunity card contain?

A commercial solar opportunity card should contain the buyer decision, company-fit boundary, decision control, usable evidence, known fatal conflicts, commercial value basis, risk treatment, constrained-role demand, next action, owner, and review trigger. The card should expose missing information separately from poor fit so uncertainty does not quietly become a low or high score. Keep uncertainty visible during every opportunity comparison.

One card per opportunity gives the challenge meeting a common unit. A revenue field alone rewards large, vague projects. A detailed technical record alone can reward projects that are interesting to design but unlikely to reach a controlled customer decision. The card keeps commercial, evidence, risk, and resource questions beside one another without collapsing them too early.

Use these fields:

Opportunity-card field Required entry Return condition
Buyer decision Choice, stakeholder, and requested timing No actual decision is named
Company fit Service, market, project type, and prohibited work The request falls outside approved scope
Decision control Property, customer, and approval roles known so far The contact cannot progress the stated decision
Evidence status Available, requested, qualified, and missing inputs A recommendation depends on a guessed material input
Fatal-conflict check Known conflict and source, or explicitly not yet observed “No conflict” is inferred from missing review
Commercial value basis Scope and customer value mechanism Headline revenue has no defined deliverable
Risk and treatment Exposure, owner, next action, and release effect Risk is named without a treatment path
Constrained-role demand Design, estimating, finance, contract, or leadership work Resource need has no receiving owner
Next decision Action, owner, evidence, and date The opportunity can remain active without movement
Review trigger Event that changes rank or gate status Old priority survives after the basis changes

Do not fill the card with optimistic defaults. “No known conflict” is different from “conflict review complete.” “Evidence requested” is different from “evidence acceptable for this release.” Those distinctions let the team compare uncertain opportunities without presenting absence of information as favorable evidence.

How should a team challenge the opportunity ranking?

Challenge the commercial solar opportunity ranking by reviewing gate evidence first, then fit, treatable risk, constrained-role demand, and commercial value. Sales, design, delivery, finance, and leadership should identify stale inputs, hidden work, unsupported optimism, and reversible decisions before scarce capacity is assigned. Every challenge needs an owner and a defined effect on priority. It changes evidence, ownership, or allocation decisions.

The meeting should not become a negotiation in which the loudest sponsor wins. Read the card and challenge the evidence. A design lead can question whether the current site packet supports the requested release. Sales can explain the buyer decision and control path. Finance or contracts can identify a condition without pretending to approve another function’s work.

  1. Remove or return opportunities that fail a current gate.
  2. Separate missing evidence from evidence of poor fit.
  3. Confirm the constrained role and the exact work being requested from it.
  4. Test whether the proposed risk treatment is owned and feasible.
  5. Compare commercial value only among opportunities that survived the gates.
  6. Assign the next action, owner, and trigger that could change the rank.
  7. Record dissent when a leader overrides the evidence-based order.

Use this copy-ready challenge note:

Opportunity and buyer decision:
Current gate status:
Evidence challenged:
Missing information:
Fit concern:
Risk, treatment, and owner:
Constrained role and requested work:
Commercial value basis:
Priority decision: advance, hold, return, defer, or decline
Next action and owner:
Review trigger:
Override and recorded reason:

An override is sometimes legitimate. A company may accept a learning project, protect a relationship, enter a new market deliberately, or respond to a strategic customer. Record the original ranking, override owner, reason, resource allocation, and review trigger. Do not rewrite the evidence to make the exception look ordinary.

How does the scorecard change weekly allocation?

The scorecard changes weekly allocation by separating opportunities ready for constrained work from those awaiting evidence, treatment, or a customer decision. Managers can assign scarce design, estimating, finance, contract, and leadership attention to qualified next actions while parking, returning, or declining work that would otherwise occupy the queue without a reviewable purpose. This keeps priority tied to the next decision.

Illustrative example, not a company result: Opportunity A has a large headline value but unclear property control, incomplete electricity evidence, and no owner for a commercial-structure question. Opportunity B is smaller, has a named buyer decision, a usable site packet for preliminary review, and a clearly defined design request.

The scorecard does not claim that Opportunity B will close or produce more profit. It shows that B can use the constrained design role for a defined next decision. Opportunity A may remain strategically important, but its next allocation should go to evidence and decision control, not to a design queue that cannot resolve those commercial conditions.

When Opportunity A supplies the missing records and assigns the commercial owner, its gate status and resource request change. The team reviews it again using the current evidence rather than preserving the earlier low rank. Priority is a dated operating decision, not a permanent label attached to the customer.

The same record reveals when the constraint moves. If design capacity becomes available but contract review becomes the limiting role, resource-demand comparison should follow the actual queue. A fixed weighting model can hide that shift. Keep the bands and gates stable enough for comparison while allowing the constrained-role field to reflect current operations.

Use outcome review to improve definitions, not to claim prediction from a small sample. Ask whether gate failures were recognized, whether resource estimates matched observed handoffs, and whether returned work shared a cause. A lost deal does not prove the ranking was wrong, and a won deal does not prove every assumption was sound.

Translate rank into a queue instruction

A priority label is incomplete until the receiving role knows what to do. Attach a queue instruction that names the deliverable, evidence packet, acceptance rule, requested date, and release level. Use the solar rep capacity checklist to separate active customer work from parked demand and downstream waits.

Queue instruction Meaning for the receiving role Management response
Advance Evidence and ownership support the defined next action Assign capacity and confirm acceptance
Hold for evidence The opportunity may fit, but a material input is missing Keep it out of the constrained queue and assign the request
Return The handoff fails a stated acceptance rule Send the exact reason and required correction
Defer The opportunity may become useful after a named event Park it with an owner and re-entry trigger
Decline Current scope, control, or conflict makes the work unsuitable Record the reason and close the active request

This vocabulary prevents “high priority” from becoming permission to bypass intake. A strategically important opportunity may deserve rapid evidence collection or executive attention, but the constrained technical role still needs a usable assignment. Urgency changes the response time and escalation path; it does not manufacture the missing project basis.

Build the ranking model

Choose a small number of dimensions and define anchors before rating. One workable structure is:

  • Fit with chosen customer, project, market, and delivery scope.
  • Evidence coverage and confidence.
  • Customer decision access and next action.
  • Treatable risk at the current stage.
  • Commercial value under approved definitions.
  • Demand on scarce resources.
  • Timing and opportunity cost.

Weights express management priorities. They are not facts. Document who approved them, test sensitivity, and show how the order changes if a disputed weight moves. If small changes reverse the top projects, the ranking is fragile and should not be treated as a command.

Never allow a total score to override a failed gate. Show the components, evidence date, coverage, and override record. Require a reason and approver when management chooses a lower-ranked project.

Use bands instead of pretending rank 3 is meaningfully better than rank 4. A priority band can mean assign now, resolve one named gap, monitor, or defer. The portfolio owner then uses capacity and sequencing judgment inside the band.

Run a cross-functional challenge before assigning scarce work

Sales presents the customer decision and relationship evidence. Design or technical roles challenge information sufficiency and work scope. Operations challenges delivery and capacity. Finance challenges commercial assumptions. Leadership resolves tradeoffs within authority.

The meeting should focus on the highest-priority and highest-uncertainty items, not reread every CRM field. Ask:

  • What evidence would most change this priority?
  • Which assumption is carrying the largest decision?
  • What is the smallest next work package that resolves it?
  • Which constrained role will this displace?
  • What customer event makes the timing real?

Record the decision, owner, work package, due date, and condition for reranking. A rank without an action is dashboard decoration.

The commercial solar sales cycle guide helps with ongoing stakeholder and timing work after prioritization. This article stays focused on choosing which opportunity deserves the next unit of diligence.

Validate the model against outcomes

After opportunities close, defer, fail, or enter delivery, compare the original evidence and ratings with what happened. Do not rewrite the old record. Ask which dimensions were useful, where definitions failed, and whether missing information was treated appropriately.

Track outcomes relevant to the model: gate failure reasons, diligence spent before stop, returned work, decision access, signed agreements, gross contribution under finance definitions, delivery exceptions, and customer experience. Respect retention, privacy, and access requirements.

Calibration needs enough comparable cases. Until then, describe the model as a management framework, not a predictive engine. A score can still improve discussion by making assumptions visible.

Review incentives. If reps are rewarded for high pipeline value, they may resist stopping weak opportunities. If operations is rewarded only for utilization, it may reject useful exploratory work. Governance should make those tensions discussable rather than hiding them in ratings.

A practical weekly ranking sequence

  1. Update evidence cards only for material changes.
  2. Apply scope, control, information, and fatal-conflict gates.
  3. Segment surviving opportunities into comparable groups.
  4. Rate fit, evidence, decision access, risk, value, resource demand, and timing.
  5. Review coverage and sensitivity before totals.
  6. Challenge the top band across roles.
  7. Assign the smallest useful work package within capacity.
  8. Record stop, defer, override, and reranking conditions.

This sequence keeps the commercial solar pipeline connected to work the company can actually perform. It does not punish ambition. It gives ambitious opportunities a clear route for proving that they deserve more scarce attention.

A good ranking system makes one uncomfortable fact visible: the largest opportunity may not be the next opportunity. The next one is the project whose current evidence, customer decision, risk treatment, and resource demand justify the work package the team is about to assign. Open the generation and financial tool only after that package is defined.

Close the loop with customers. If an opportunity is conditional, ask for the specific document, meeting, authority, or decision that would change its status and explain why. If it is deferred, state the event that will reopen it. If it is stopped, communicate the scope or evidence reason without blaming the buyer. Clear status protects the relationship better than weeks of vague enthusiasm followed by silence.

Pipeline hygiene also protects analytical quality. Archive superseded evidence, retain the current decision record, and do not leave duplicate opportunities for the same site under different contacts. A duplicate can make demand look larger while splitting customer history and resource estimates. Define who can merge, close, or reopen records and preserve the reason.

Finally, audit the work that never reached a score. Referral requests, executive introductions, and urgent bid emails often bypass ordinary qualification. Log them with the same gates and resource demand after the immediate response. Otherwise the ranking model describes the formal pipeline while scarce staff continue to be allocated through side channels.

Bring a Qualified Commercial Opportunity to a Guided Demo

See how SurgePV can support a bounded design and proposal work package after your team has defined the decision, evidence, and review path.

Book a Guided Demo

Frequently Asked Questions

Should commercial solar opportunities be ranked by project value?

Project value can inform prioritization, but it should not dominate it. A large opportunity may have weak site control, poor evidence, a low-probability procurement path, or demands the exact specialist already constraining delivery. Compare value with fit, risk, information quality, decision access, timing, and resource demand.

What is a stop gate in commercial solar qualification?

A stop gate is a condition that prevents an opportunity from consuming the next level of effort until it is resolved. Examples can include work outside company scope, missing authority to pursue the site, unusable decision evidence, or a requirement the team cannot responsibly meet. Each gate needs an owner and route.

How often should a commercial solar pipeline be reranked?

Rerank when material evidence changes and at a regular cadence suited to the sales cycle. A new bill set, stakeholder decision, site finding, utility response, bid clarification, or resource constraint can change priority. Avoid constant score churn from minor CRM activity that does not alter fit, risk, or next action.

Can a scoring model predict which solar project will close?

A scoring model can make assumptions and evidence visible; it cannot guarantee a sale. Historical validation may show whether internal ratings relate to later outcomes, but markets and project mixes change. Use scores to allocate diligence and expose disagreement, then preserve human judgment, customer context, and clear stop conditions.

Who should own commercial solar opportunity ranking?

Sales should not own the decision alone because the ranking consumes design, estimating, engineering, procurement, and delivery capacity. Assign one accountable pipeline owner, with input from the roles whose scarce resources or risk boundaries are affected. Keep rating definitions controlled and record overrides with evidence and an approver.

Sources

Primary research and reference material used for this desk-research article.

Where this fits

This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.

About the Contributors

Author
Nimesh Katariya
Nimesh Katariya

Solar-industry contributor

Nimesh Katariya contributes to SurgePV content concerning solar project workflows. This profile intentionally does not assert certifications, project totals, seminar counts, or technical-review authority without retained verification evidence.

Editor
Rainer Neumann
Rainer Neumann

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.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime

Book Free Demo

Choose which optional technologies SurgePV may use. Essential storage remains active for security and requested features.