10 Pre-Sales Questions for a C&I Solar Project

The commercial prospect has a recognizable logo, several facilities, and a deadline. A sales leader asks design for “something preliminary” before the next call. Estimating wants equipment direction. Finance needs a commercial structure. An executive joins because the possible contract looks large. Nobody has yet defined what the customer will decide from the work.

That is how pre-sales effort becomes a fog instead of an investment. Each person does a reasonable task, but the tasks do not form a named package with an entry condition, owner, output, decision, or stop line. After another round of questions, the project is considered too important to pause because the company has already spent so much attention on it.

The practical unit of approval is not the whole opportunity. It is the next pre-sales work package. That package might be stakeholder discovery, evidence screening, a remote concept, a site-diligence plan, a budget offer, an RFP response, or a specialist review. Executives should know what question the package resolves before scarce people begin it.

This guide is for EPC executives, commercial leaders, sales directors, design managers, and operations owners deciding whether a C&I solar pursuit deserves deeper work. It does not provide an engineering conclusion, customer credit decision, contract interpretation, tax or accounting advice, utility approval, site-safety plan, financial recommendation, or guarantee of award, savings, production, margin, or timing.

The commercial pipeline gate guide owns the full progression from qualified need to contract-ready handoff. The commercial opportunity ranking method compares surviving projects across a portfolio. This guide stays narrower: it gives executives ten questions for authorizing one more package of pre-sales work on one project.

What decision does a pre-sales resource gate protect?

A pre-sales resource gate protects the decision to spend the next unit of scarce pursuit capacity on a defined commercial solar question. It identifies the requested output, required evidence, participating roles, allowed use, unresolved conditions, decision date, and exit routes before estimating, design, engineering, finance, procurement, legal, or executive work begins.

The gate is not a confidence score dressed as governance. It is a resource warrant. A good warrant answers: what work begins, what work does not begin, who owns it, what the customer receives, what internal decision follows, and when the authorization expires.

Possible contract value belongs in the conversation, but it cannot answer those questions. The revenue-only commercial project filter explains why headline value does not reveal contribution, customer authority, site viability, risk allocation, cash timing, or demand on constrained roles.

Define pre-sales capacity widely enough to see the real constraint. The work can include customer discovery, bill and interval-data review, site-record review, remote modeling, candidate layout, yield analysis, electrical screening, structural coordination, estimating, equipment and supplier input, commercial modeling, RFP compliance, contract review, executive negotiation, and package production. Not every pursuit uses every role.

The U.S. Environmental Protection Agency’s on-site renewable project development process, in its stated customer-side context, separates activities such as goal setting, site and utility-data assessment, procurement, design, permitting, construction, and commissioning. It is not a mandatory EPC sales sequence. It supports a useful distinction: an early pursuit package cannot silently imply that later project decisions are complete.

Set the work package to the next decision, not the largest possible deliverable. If the customer needs to decide whether to share interval data and arrange a site visit, a detailed contract proposal is premature. If procurement has issued a controlled RFP, a loose concept may be inadequate. The customer decision and source set determine the package.

Do not promote an opportunity merely because several people are already working on it. Prior effort is history, not evidence that the next package deserves approval. Preserve what the team learned, then make the current decision from current facts and capacity.

Which ten questions should EPC executives ask first?

EPC executives should ask ten questions before deeper C&I pre-sales work: what decision the customer will make, who sponsors it, whether the evidence fits the requested output, which commercial path applies, what can reverse the concept, what the next package will learn, where work stops, which scarce roles it consumes, which risks need early authority, and when pursuit ends.

1. What decision will the customer make from the next deliverable?

“Send a proposal” is a request, not a decision. Ask what happens after the customer receives it. Will facilities authorize a site survey? Will finance compare ownership structures? Will procurement shortlist bidders? Will a property owner consider access? Will an executive committee approve development spending?

Record the decision, criteria, intended date, audience, and required format. If the customer cannot name the decision, the right package may be discovery rather than design. A useful discovery package should still have a finish line: a confirmed decision path, a specific information request, or an explicit reason to defer.

Match the release language to that purpose. A document suitable for discussing data gaps is not a price commitment. A remotely modeled candidate is not a construction instruction. A budget scenario is not an approved financial outcome. The package becomes more trustworthy when it says what the reader may decide and what remains unresolved.

2. Who is the sponsor, and can that person reach the decision owners?

A helpful contact does not need final authority, but the pursuit needs a credible route to it. Map the people who shape technical requirements, property access, energy data, finance, procurement, contracting, operations, and final approval. Identify who can introduce the next step and who can stop it.

Ask the sponsor to describe internal process in their own terms. Avoid imposing a generic “economic buyer” label on a public tender, landlord-tenant arrangement, facilities-led capital request, or developer-host structure. Different paths create different evidence and communication needs.

Access is observable through actions: the correct people join, requested records arrive, questions receive authoritative answers, or a procurement event opens. Do not convert friendliness or fast replies into a close probability. Use the evidence to decide the next package, not to predict an award.

3. Does the evidence support the output being requested?

Build a short source index before allocating design or estimating work. Identify the site and contracting entity, installation area, property relationship, electricity accounts and meters, billing coverage, interval data where relevant, tariff sources, roof or land records, imagery, site photos, electrical information, operating constraints, and customer statements.

Mark each item confirmed, supplied but unverified, planning assumption, conflicting, missing, or required before release. The same evidence can be sufficient for one package and inadequate for another. Aerial imagery may support a remote discussion while field or record gaps prevent a technical or contractual release.

The Department of Energy describes PV systems through connected choices involving arrays, mounting, power electronics, and other elements. That general overview does not validate a private project. It explains why a single roof image or annual bill cannot settle every interface in a C&I concept.

4. Which commercial and ownership path is actually under discussion?

Do not let “solar project” conceal the transaction. Is the customer considering ownership, a third-party arrangement, a lease-related path, an RFP, a budget study, or another structure? Who owns the site, equipment, energy attributes, operational responsibilities, and contract decisions under the proposed path? Responsible specialists must review the live terms.

EPA describes a solar power purchase agreement, in general U.S. information, as an arrangement where a third-party developer owns, operates, and maintains the system while a host customer purchases its output for a predetermined period. The page also describes participant roles and trade-offs. It does not recommend a structure or supply project terms.

A concept and financial model built for the wrong transaction answer the wrong question. Identify the path before deep analysis, or approve a package whose only job is to compare structures with qualified finance, tax, accounting, contract, and legal input.

5. Which technical or external unknown could reverse the concept?

Executives do not need to solve engineering during qualification. They do need a stop-and-escalate map. Ask design, engineering, interconnection, structural, site, procurement, and delivery owners which unknowns could materially change the proposed work, prevent the requested output, or require outside authority.

Examples can include conflicting site geometry, uncertain roof condition, unavailable structural records, unclear service information, load changes, unusual operating requirements, restricted access, equipment outside current methods, utility or authority uncertainty, environmental or land questions, or a customer request outside company competence. Each company needs a project-specific list.

Record the unknown, why it matters, who can resolve it, what evidence is required, and what work may proceed meanwhile. “Engineering to confirm later” is not a disposition. A bounded concept can carry open conditions, but the release should not pretend those conditions are solved.

6. What information will the next work package buy?

Pre-sales effort should reduce a named uncertainty or produce a named decision. Ask what the company will know after the package that it does not know now. If the team can name only “a more detailed proposal,” ask which decision becomes possible because of that detail.

Useful information gain might include a credible stakeholder path, reconciled load record, screened site boundary, candidate technical scenario, external question list, equipment availability signal, risk-owned estimate basis, commercial-structure choice, or compliant response matrix. None guarantees the project will proceed.

The package may also discover that the opportunity should stop. That is a valid result when it prevents uncontrolled later work. Define success as resolving the question, not only advancing the deal.

7. What exactly is included, and where does pre-sales work stop?

Write a work boundary before people begin. Name included inputs, tasks, reviewers, deliverables, revisions, customer meetings, external questions, and decision date. Name exclusions and change triggers. State whether the output is internal, customer-facing, budgetary, procurement-ready, or suitable for another stated purpose.

Avoid “support as needed.” That phrase turns every new question into an implied commitment. A request outside the boundary should return to the resource gate with its reason, expected learning, role demand, and deadline.

For a first commercial rooftop, the eight questions before quoting provide a deeper project-specific readiness check. This guide stops earlier, at authorization to fund that work.

8. Which scarce roles will the package consume, and what waits?

Identify the roles at the company’s current constraint. The title may be designer, estimator, engineer, finance lead, procurement specialist, project executive, or another function. Record the requested capacity, timing, dependency, and work that may wait if the package begins.

Do not infer resource demand from project size alone. A large standard project with clean records may consume less pre-sales attention than a smaller project with unclear ownership, novel equipment, multiple meters, a complex procurement, or a difficult deadline. Ask the role owners for the work breakdown.

The solar rep capacity method applies a similar principle to sales work: count the activities and constraints rather than relying on raw opportunity volume. For C&I pursuits, extend that view across every scarce pre-sales role.

9. Which risk questions need authority before detailed work begins?

Some questions should reach finance, legal, tax, accounting, insurance, safety, engineering, procurement, utility, or executive owners early because their answer changes whether the company should pursue, how it should structure the offer, or what it may say.

Examples include unusual payment or security terms, performance or availability commitments, liquidated-damage language, long price validity, supply exposure, customer-provided data rights, site-access obligations, schedule responsibility, operating guarantees, unbounded design revisions, or a request to rely on preliminary information. This list is not legal or commercial advice.

The Department of Energy’s FEMP building life-cycle cost program provides methods and tools for economic evaluation in federal investment analysis. That context does not select a private EPC method. Its useful discipline here is visible assumptions and an analysis method chosen by the responsible finance team, rather than a sales-created number with hidden treatment of cost and timing.

10. What event advances, narrows, defers, or stops the pursuit?

Every work package needs a decision date and exit routes. Define the evidence that allows another package, the conditions that narrow scope, the missing event that causes defer, and the conditions that stop pursuit. Assign an owner who will make and record the decision.

Avoid permanent “management exception” status. If leaders fund a pursuit despite weak evidence or poor fit, preserve the original result and write the hypothesis, authorized work, capacity ceiling, learning objective, decision date, and stop condition. An exception is a bounded experiment, not a blank cheque.

The U.S. Small Business Administration says market research can help a business find customers and understand opportunities and limitations, while competitive analysis examines competing businesses by product or service and segment. That general planning guidance supplies no solar demand or win-probability conclusion. It supports stating what a targeted pursuit is meant to learn.

What evidence belongs in a C&I pursuit brief?

A C&I pursuit brief should identify the customer, site, sponsor, decision path, requested output, current source set, commercial structure, technical stop questions, external dependencies, next work package, participating roles, displaced work, risk owners, release purpose, deadline, and exit rules. Separate confirmed facts, supplied records, planning assumptions, conflicts, unknowns, and management exceptions.

Keep the brief short enough for an executive decision and deep enough to expose the resource request. It is an index, not a substitute for bills, drawings, models, RFP documents, contracts, or technical files. Link controlled sources with revision and date.

Use a two-layer record. The first layer is the decision card: why this package, why now, who works, what it produces, and what happens next. The second layer is the evidence index: where each source sits, who owns it, and whether it is suitable for the proposed output.

Do not erase disagreement. If sales sees a strong sponsor while delivery sees weak evidence, preserve both observations and decide the next package that can test them. A gate that forces consensus before recording evidence will produce cheerful but useless briefs.

NIST says value stream mapping can visualize process and information flows through current-state mapping, diagnosis, future-state definition, and implementation in its manufacturing process-improvement context. It does not validate a solar workflow or outcome. The analogy is useful: map how a pursuit actually consumes information and roles before designing a cleaner gate.

Map returned work and invisible loops. Which team rebuilds the same estimate? Who re-requests missing bills? Where do customer comments cause another model? Which executive reviews a package after the decision date has moved? Those observations help define the real pre-sales work package.

How should a team approve the next pre-sales work package?

Approve the next pre-sales work package through a seven-step record: log the request, classify the customer decision, review source fitness, define the smallest useful package, obtain scarce-role and risk-owner approval, set release and exit rules, then record the outcome and learning. Return any expanded request to the same gate instead of allowing silent scope growth.

1. Log the request. Identify the opportunity, requestor, source, date, urgency, desired customer action, and current package state. Preserve the exact RFP, email, meeting note, or internal request rather than translating it into a vague CRM task.

2. Classify the customer decision. Name what the customer or internal team will decide from the output. Confirm the audience, criteria, sponsor, procurement path, and intended date. If those items are unknown, authorize discovery instead of pretending the final package is defined.

3. Review source fitness. Build or refresh the evidence index. Match each source to the requested task and label conflicts, assumptions, and missing items. Decide which gaps can remain visible and which prevent release.

4. Define the smallest useful package. State included work, roles, outputs, revisions, customer interactions, exclusions, allowed use, and the material question the package resolves. Avoid funding final-detail work when a narrower screen can settle whether deeper work is warranted.

5. Obtain role and risk approval. Ask scarce-role owners whether they can perform the work and what waits. Route early technical, finance, contract, procurement, legal, tax, safety, utility, or executive questions to people with the authority to answer them.

6. Set release and exit rules. Record who reviews and releases the output, what the recipient may rely on, which conditions stay open, and which events advance, narrow, defer, partner, or stop the pursuit. Give the authorization an expiry or decision date.

7. Close the package and retain learning. Record the output, evidence gained, questions resolved, new risks, resource used, customer action, and next decision. If another package is proposed, begin a new warrant. Do not retroactively stretch the old one.

Copy-ready C&I pre-sales resource warrant

Copy this operating record into a controlled CRM object, ticket, or pursuit form. Use “unknown” and an owner instead of leaving gaps to be interpreted as approval.

Pursuit and site identity:
Request source, date, and requestor:
Current customer or procurement source set:
Customer decision this package supports:
Sponsor and path to decision owners:
Decision criteria and intended date:

Confirmed evidence:
Supplied but unverified evidence:
Planning assumptions:
Conflicts and missing evidence:
Technical or external stop questions:

Commercial or ownership path under discussion:
Early finance, legal, tax, contract, procurement, or risk questions:

Next work package:
Material question it should resolve:
Included tasks, roles, deliverables, meetings, and revisions:
Explicit exclusions and change triggers:
Scarce roles requested:
Work delayed or displaced:
Partner or external support required:

Allowed internal use:
Allowed customer use:
Prohibited claims or release purposes:
Reviewer and release owner:
Open conditions:

Advance evidence:
Narrow condition:
Defer event:
Stop condition:
Decision owner and expiry date:

Outcome and information gained:
Next package proposed, if any:
Management exception and reason, if any:

For formal procurement, connect the warrant to a controlled response process. The solar RFP response guide shows how source documents, atomic requirements, questions, owners, evidence, review authority, deviations, and submission identity belong in a compliance matrix. The resource warrant decides whether and how deeply the company enters that work.

How should missing information and exceptions be handled?

Handle missing information by tying each gap to the decision it prevents, assigning an owner, and choosing a bounded route: request evidence, narrow the output, commission discovery, obtain specialist review, defer to a named event, use a qualified partner, or stop. Management exceptions should preserve the original gate result, authorized capacity, hypothesis, expiry, and stop condition.

“Customer will provide later” is not a complete exception. State what is missing, who requested it, who can supply it, why it matters, what work is permitted meanwhile, what output remains prohibited, and when the pursuit returns for decision.

Do not use disclaimers to carry a package whose central input is absent. A caveat can explain a bounded assumption. It cannot turn an unknown site, load, ownership, connection, procurement, or contracting basis into a supported proposal.

Illustrative example, not a customer case

A facilities contact asks an EPC for a multi-site budget proposal before an internal capital-planning meeting. The opportunity appears attractive because several buildings are involved. Sales requests layouts, yield estimates, commercial scenarios, and executive pricing review.

The resource gate finds that the contact can explain the meeting but has not identified who controls the properties, which meters belong to each building, whether interval data is available, or which ownership structure finance wants to consider. The deadline is real. The requested package still lacks a stable decision basis.

Instead of approving the full proposal, the executive authorizes a stakeholder-and-evidence screening package. Sales maps the decision roles. The customer provides a site and meter index. Design checks whether available records support a candidate-area discussion. Finance supplies questions that distinguish the commercial paths. The package ends with a source register, open-condition list, and decision on which sites deserve bounded concepts.

The example states no project size, price, savings, production, close probability, resource saving, engineering result, financing outcome, or award. Its lesson is about sequence: a smaller package can buy the information needed to decide whether a larger package is responsible.

Track the gate with events your company can define. Examples include packages requested, narrowed, approved, deferred, partnered, or stopped; roles assigned; evidence gaps closed; expansions returned for authorization; exceptions expired; and outcomes recorded. Do not turn those event counts into a benchmark or causal claim without stable definitions and comparable observations.

Review exceptions as a group. If the same evidence gap repeatedly receives management overrides, the intake process may be asking the wrong question or the company may be pursuing a segment with a different evidence path. Change the rule from observed cases, then retain its effective date.

Where can SurgePV support a C&I pre-sales workflow?

SurgePV can support connected 3D roof modeling, solar array layout, shading analysis, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation. It does not qualify sponsors, approve resource spending, verify missing records, choose transaction structures, replace specialists, interpret contracts or codes, control external recipients, or guarantee project, sales, financial, or delivery outcomes.

A connected project record can make it easier to see which site evidence, layout, analysis, electrical work, materials, and proposal output belong to the active scenario. Teams may use Solar Designing during an approved work package. The resource gate still belongs to the company.

The repository product source of truth says results depend on source data, assumptions, equipment models, configuration, and review. It also states that outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility. Carry those limits into every customer-facing package.

Software cannot decide the opportunity cost of assigning the lead estimator or engineering manager. It cannot prove that the customer sponsor has authority. It cannot accept legal terms, make a credit decision, confirm site facts that were never observed, or notify every person holding an exported file unless the surrounding company process does that work.

Use a product walkthrough to test a real pre-sales package. Bring the source index, active assumptions, desired output, reviewer, and release purpose. Ask how the workflow preserves scenario identity and propagates accepted changes. Avoid asking for a generic promise that the platform makes every commercial opportunity faster or more likely to close.

Fund the next answer, not the imagined contract

Commercial opportunities deserve ambition, but ambition should buy information in controlled steps. The executive question is not “do we like this deal?” It is “which question deserves scarce company capacity now, and what evidence will tell us what to do next?”

Make the next work package visible. Give it a customer decision, source set, role roster, work boundary, allowed use, review owner, expiry, and exit routes. Preserve unknowns instead of smoothing them into a polished proposal. Return every expansion to the same gate.

This discipline gives stop and defer decisions a constructive meaning. The team can protect a customer relationship by requesting the right evidence, offering a narrower package, or naming the event that will justify deeper work. It also keeps a promising project from consuming unlimited attention merely because nobody wants to be the person who pauses it.

Frequently Asked Questions

What counts as a pre-sales resource on a C&I solar project?

Pre-sales resources include the people, data access, software work, external support, and management attention used before contract. Depending on the requested package, that may involve sales, estimating, design, engineering, finance, procurement, legal, interconnection, site, and executive roles. Define the included roles rather than treating pre-sales as sales labor alone.

Should a large C&I solar opportunity receive more pre-sales effort?

Possible contract value can justify attention, but it does not establish customer authority, project fit, evidence quality, technical viability, commercial structure, decision timing, risk allocation, or delivery capacity. Approve the smallest work package that can resolve the next material question, then reconsider deeper commitment using what that package actually learned.

Who should approve pre-sales resources for commercial solar?

Approval should sit with the people accountable for the scarce roles, pursuit risk, and release purpose. Sales can sponsor the request, but design, estimating, engineering, finance, legal, procurement, and executives should authorize work within their own responsibilities. One person may hold several roles, while the decisions still remain distinct.

What happens when the customer cannot provide enough information?

Convert the gap into a bounded evidence request, paid or unpaid discovery package, narrower output, defer condition, partner route, or stop decision. State which decision the missing information prevents. Do not hide the gap inside a detailed-looking concept, unsupported price, savings claim, or open-ended promise that the team will solve it later.

Can SurgePV decide whether a C&I pursuit is worth funding?

No. SurgePV can support connected roof modeling, array layout, shading, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation. Executives and qualified specialists must still judge customer access, evidence, resource demand, engineering, code, utility, finance, contract, procurement, safety, delivery, and opportunity-cost questions.