6 Research Steps Before a Commercial Solar Email

A prospecting email should not be the first place a commercial solar hypothesis becomes specific. By the time a message names a facility, use type, public project, roof area, or planning event, the marketer should know which source supports that statement and which facts remain unknown.

That research is not an invitation to build a surveillance file. Its purpose is narrower: decide whether the team can send one truthful, useful message to the right starting role with a proportionate next step.

This guide supplies six steps and a send decision record. It does not authorize contact or data use, identify a decision-maker, assess a facility, design a system, determine savings, or give privacy, legal, advertising, engineering, finance, tax, utility, permitting, property, contract, or investment advice. Current qualified review remains necessary.

The facility personalization guide explains how to use a verified fact in creative. This page begins earlier, with the research and release decision that determines whether any email should leave the system.

What should commercial solar prospecting research prove?

Commercial solar prospecting research should prove that the company and facility are identified, the contact data has a documented source and permitted use, one facility question is directly relevant, the message’s facts and claims are supported, and the proposed next step fits the recipient’s likely role. It should also expose unknowns, privacy risks, corrections, exclusions, and reasons not to send.

Research is complete when it changes the release decision from an unsupported guess to send, hold, route, or stop. It is not complete because a researcher filled every field. Some fields should remain blank until the facility supplies or authorizes the evidence.

Use four source states:

The U.S. Energy Information Administration’s Commercial Buildings Energy Consumption Survey is a national sample survey about commercial-building characteristics and energy use. It can help a researcher understand which questions exist. It cannot establish the load, tariff, demand pattern, performance, or solar opportunity of one named facility.

Research should answer five release questions:

• Is this the correct entity and facility?
• Can the company use the contact and facility data for this purpose?
• Does the source support every factual sentence in the email?
• Does the offered asset help one real facility decision without pretending the project exists?
• Can the recipient correct, redirect, decline, or stop the contact cleanly?

If any material answer is no, the record should hold or stop. A marketer does not earn permission by making the email more personalized.

Which six research steps belong before the email?

The six steps are resolving company and facility identity, validating contact provenance and permitted use, researching facility and energy context without assigning private facts, finding a genuine planning question, mapping roles and alternatives, and auditing the exact email, asset, claims, follow-up, and closure controls. Complete them in order because later personalization depends on the earlier evidence boundary.

Step 1: Resolve the company, entity, and facility

Start with the operating entity, legal entity where relevant, facility name, physical address, use description, property or campus boundary, source URLs, observation date, and confidence. A headquarters mailing address, registered office, operating location, leased site, owned property, and portfolio office can refer to different decisions.

Prefer current official sources, authorized directories, or appropriately licensed records. Preserve the exact sentence or field each source supports. An official facilities page may establish that a company operates a warehouse at an address. It may not establish property ownership, roof rights, utility-account control, capital budget, or the recipient’s authority.

Check for conflicting sources. If one page uses an old facility name or address, do not pick the convenient version. Record the conflict, refresh it, or hold the message. A bounced domain, closed location, acquisition, tenant change, or stale directory can turn careful creative into an obviously wrong email.

Write a one-line identity boundary:

Entity | facility | address | stated use | property or campus boundary | source | date | verified unknowns

The email should not become more specific than that line.

Step 2: Validate the contact source and permitted use

Document where the name, role, email address, and other identifiers came from; who supplied them; applicable license or vendor terms; stated purpose; geography; consent or other lawful basis where relevant; retention; correction; suppression; and deletion route. Public visibility is not a universal permission slip.

NIST describes its Privacy Framework as a voluntary tool for helping organizations identify and manage privacy risk. It does not authorize outreach or determine applicable law. Its useful discipline is to map the data processing, affected people, purpose, risk, controls, owners, and lifecycle before launch.

Avoid role inflation. A database may label someone “facilities director,” but the current role, company relationship, and decision authority still need confirmation. The first email can ask whether the person is the correct starting role. It should not announce that they control a capital project.

Apply minimization. If the message needs a business email, facility name, and relevant role, do not collect personal interests, household details, unrelated profiles, or a long cross-platform history. More data does not automatically create more relevance.

Set precedence before sending. A prior decline, opt-out, customer record, active opportunity, legal hold, vendor restriction, or other governed state may override a new prospect record. The research process must check those systems rather than treating each new list as clean.

Step 3: Research facility and energy context without guessing

Use the facility’s stated function to select questions, not to assign consumption. A warehouse, cold-storage site, office, factory, school, hotel, retailer, and multifamily property can have different operating, roof, parking, tenancy, resilience, and decision contexts. The named facility may not resemble a sector average.

Research available and permitted public facts such as stated use, operating announcements, facility plans, sustainability reports, roof or parking visibility, and portfolio structure. For each fact, store source, date, scope, and an explicit “does not establish” field.

DOE’s PV system design basics explains that modules are part of a complete system with mounting structures, power electronics, and storage in some systems. It does not assess the prospect. Use that boundary to avoid treating an apparently open roof as a complete solar conclusion.

Unknowns commonly include meter scope, electricity use, interval pattern, tariff, export treatment, roof condition, structure, access, shading, electrical service, ownership, lease rights, planned loads, utility feasibility, budget, timeline, and decision authority. List them. Do not fill them with benchmark data.

The research output should be a question such as, “Which property, meter, usage, roof, electrical, and planning records would your team use to decide whether an early screen is worthwhile?” It should not be a fabricated system estimate.

Step 4: Find a real facility planning question

A relevant email needs a reason beyond “the roof looks large.” Look for a current, verified planning event or operational question: roof work, facility expansion, lease review, fleet electrification, parking work, efficiency program, energy benchmark, equipment replacement, capital cycle, procurement plan, portfolio target, or another source-backed event.

Verify that the event is current and applies to the facility. A corporate commitment may not assign a project to every site. A permit may be obsolete. A press release may describe a plan that changed. Ask for correction rather than turning the event into urgency.

Connect the event to an asset. A roof project may justify a coordination checklist. A portfolio review may justify a facility-screening schema. An energy benchmark may justify a data-readiness note. An unclear ownership path may justify a decision map.

Avoid manufactured scarcity. Do not imply that an incentive, equipment price, utility capacity, schedule, tax treatment, or approval will disappear unless the current source and qualified reviewers support that exact statement.

If no real question is visible, choose a modest orientation asset or stop. A generic “go solar” pitch with a company name is not evidence that research succeeded.

Step 5: Map roles, alternatives, and the next decision

Commercial solar can involve facilities, sustainability, finance, procurement, property, operations, engineering, legal, ownership, executive, lender, utility, insurer, and authority roles. The prospect may coordinate only one part. Research should identify likely roles to confirm, not declare one person the decision-maker.

NASA’s decision-analysis guidance discusses alternatives, criteria, evidence, uncertainty, and recommendations in NASA systems engineering. It does not validate prospecting. The transferable discipline is to define the decision and alternatives before presenting a seller-selected project as the only path.

Possible next decisions include:

• confirm the correct facility and role;
• accept or decline a working asset;
• identify another stakeholder;
• share a sanitized record under an agreed process;
• schedule an early screen;
• defer to a named planning event;
• state that the project or contact is not relevant;
• request no further outreach.

The message should make at least three routes easy: proceed, redirect, and stop. It should not force the recipient to book a meeting merely to correct the data.

Use the commercial consensus guide after a verified opportunity needs a deeper decision map. The multi-stakeholder proposal checklist supports the later document stage. Prospecting research only needs enough role context to avoid sending an inappropriate promise to one guessed title.

Step 6: Audit the exact email and release record

Review the subject line, opening fact, facility question, working asset, destination, call to action, sender identity, disclosures, claims, reply handling, follow-up limit, suppression rules, and expiry as one version. A compliant-looking footer does not repair an unsupported facility or savings claim in the opening.

The FTC’s advertising and marketing guidance says United States claims must be truthful, cannot be deceptive or unfair, and must be evidence-based. The page does not approve a commercial solar email. Verify public-source claims, credentials, comparisons, production, savings, prices, urgency, incentives, schedules, and outcomes against current evidence.

For United States commercial email, the FTC’s CAN-SPAM guide describes requirements including accurate routing information, nondeceptive subject lines, identification, a physical address, an opt-out method, honoring opt-outs, and vendor oversight. It is not global advice and does not itself authorize contact.

Assign reviewers by authority. Privacy reviews the intended data use. Legal and compliance review applicable requirements. Technical owners review facility and solar wording. Product reviews capability statements. Brand reviews voice. Campaign operations verify suppression and replies. No reviewer silently accepts another role’s decision.

Record evidence against sending, not just evidence for it

Prospecting research becomes biased when the record saves only facts that make outreach look promising. A facility name, visible roof, public sustainability statement, and relevant role can all be real while the correct decision is still hold, route, or stop. Require researchers to collect disconfirming evidence with the same care as supporting evidence.

Negative or limiting evidence may include a closed or sold facility, an outdated contact, a tenant without property rights, an existing customer or active opportunity, a previous decline, a roof project that removes the timing window, a public statement that applies only to another portfolio, a data-license restriction, or an unsupported claim the working asset would need. None of these facts should be interpreted beyond its source.

Add a challenge column to the research record:

Require an independent person to challenge high-risk records before release. The reviewer should be able to return the decision without rewriting the message: wrong entity, unsupported fact, excessive data, stale event, missing authority, conflicting customer state, weak destination, or inadequate stop control. Those reason codes make later process review more useful than “email did not perform.”

Research also needs a freshness policy. Facility identity and public plans can change. Contact roles, vendor permissions, platform fields, and campaign claims can change. Assign each material source an expiry or event trigger instead of treating a completed spreadsheet as permanently current.

How should the team make the final send decision?

Make the decision from one research record with four possible outcomes: send when every material field is supported and reviewed, hold when a named source or owner could resolve the gap, route when another team or existing relationship controls contact, and stop when data authority, relevance, claim support, suppression, or recipient respect cannot be established. Preserve the reason and version.

Use this release workflow:

1. Freeze the candidate email and asset. Assign a version and prevent late unreviewed substitutions.
2. Verify every factual span. Match the company, facility, event, role, product, and claim wording to the source ledger.
3. Check data authority and precedence. Confirm permitted use and search for customer, opportunity, decline, opt-out, and restricted states.
4. Test destination parity. The linked page or asset must complete the task promised in the email.
5. Run the uncomfortable-reading test. The sender can explain how each fact was obtained, why it is used, and how it is corrected or retired.
6. Approve send, hold, route, or stop. Record the owner, reason, timestamp, expiry, and next event.
7. Monitor replies and closure. Route corrections, referrals, declines, and opt-outs before any later sequence acts.

Copy-ready commercial solar email research record

Illustrative example, not a prospect, campaign, facility assessment, email result, or legal conclusion. An official company page identifies a food distribution facility at a current address. The researcher records only the name, address, stated use, source, and date. Energy use, temperature-controlled space, ownership, roof condition, meter boundary, budget, and authority remain unknown.

The team finds no current project event, so it does not send a speculative savings message. It prepares a short facility-data readiness sheet and an email asking whether the site and role are correct and whether the sheet would help a future energy or roof review. The recipient can accept, redirect, decline, or opt out.

Nothing in the example predicts response. The research earns a bounded question, not a conclusion that the facility needs solar.

SurgePV’s verified solar design platform can carry an accepted facility into 3D roof modeling, array layout, shade analysis, yield and financial models, electrical workflows, material schedules, and proposal production. Every output still depends on suitable inputs, stated assumptions, configured equipment, and responsible review.

Those functions apply after a facility accepts a governed assessment and supplies or authorizes the required inputs. SurgePV does not source contacts, authorize data use, infer intent, determine decision authority, approve email claims, or guarantee response, production, savings, conversion, revenue, or approval.

Frequently Asked Questions

How much research should happen before a commercial solar email?

Research enough to verify the company, facility, contact source, permitted use, one relevant decision question, supporting source, and safe next action. Stop when further collection does not change the message or requires data the company lacks authority to use. A shorter accurate record is better than a detailed profile built from weak or excessive inferences.

Can public facility data be used in a solar prospecting email?

Public visibility does not automatically establish unrestricted use, accuracy, ownership, decision authority, or permission for every outreach purpose. Record the source, date, permitted use, facility boundary, and exact fact supported. Keep energy use, roof condition, budget, solar suitability, and interest unknown unless suitable evidence establishes them, and obtain qualified privacy and legal review.

Should a commercial solar prospecting email include a system estimate?

Only a visibly preliminary screen should be considered, and only when suitable, lawfully used inputs support it. The email must identify the source date, assumptions, purpose, and limitations and must not present the artifact as an accepted design, engineering conclusion, price, production guarantee, savings result, utility approval, or proof that the facility should proceed.

Who should receive the first commercial solar email?

Choose the role supported by current evidence, then ask whether that person is the right starting point. Facilities, sustainability, finance, procurement, property, operations, legal, ownership, engineering, and executive roles may control different decisions. Do not assign authority from a job title alone, and make correction, forwarding, decline, and opt-out routes easy to use.

Where can SurgePV support commercial solar prospecting?

SurgePV can support roof, layout, shading, energy-yield, financial, electrical, bill-of-materials, and proposal workflows after a facility accepts a governed project review and suitable inputs are available. It does not source contacts, authorize data use, infer intent, approve email claims, replace engineering, or guarantee response, production, savings, conversion, revenue, utility approval, or another result.