Account-Based Solar Campaign Checklist for EPCs

Account-based marketing becomes useful for a solar EPC when it narrows attention to organizations the team can understand and serve. A spreadsheet of company names with generic advertising, email, and savings promises does not provide that research or coordination.

The distinction is evidence. A credible campaign records why an account entered the list, which facilities are in scope, what is known, what remains assumed, who influences the decision, and what the next conversation should accomplish. Marketing, sales, and technical teams work from the same record instead of handing one another disconnected engagement signals.

This checklist is for EPC leaders and commercial-solar teams planning a named-account campaign. It is desk-researched operational guidance. Local privacy, marketing, contracting, engineering, utility, and authority requirements still need appropriate review.

Define a campaign around a decision, not a slogan

Write one decision the campaign should help a prospect make. Examples include deciding whether to share interval data for an initial screen, whether to include selected sites in a portfolio review, or whether to schedule a roof and electrical evidence call. “Generate enterprise leads” is an internal aspiration, not a useful customer decision.

The decision determines the offer. A facilities leader may value a site-data checklist. An energy manager may value a load-data readiness review. A finance stakeholder may need a transparent assumption register before discussing scenarios. These assets invite a bounded next step without claiming that a project is already feasible.

State exclusions. A campaign might focus on owner-occupied distribution facilities in a defined region and exclude leased sites, properties under known roof replacement, or accounts outside the team’s service capacity. Exclusions protect research time and reduce the temptation to stretch product, geography, or delivery claims.

Record the campaign observation date. Facility ownership, contacts, tariffs, roof conditions, corporate targets, and public plans change. A claim that was defensible when the list was built may not remain current throughout a long sales cycle.

Define where qualified evidence enters the solar design workflow before the campaign begins, so engagement cannot bypass intake and review.

Check account fit before buying attention

Use observable, lawful information to establish a fit hypothesis. Useful categories can include facility type, portfolio concentration, roof or land context visible in public records, operating profile stated by the organization, location within service coverage, and an announced capital or energy program. Each item needs a source and a date.

Do not turn surface signals into project facts. A large roof does not prove structural capacity, usable area, interconnection availability, consumption fit, ownership control, procurement timing, or financial value. Public satellite imagery can support a research question. It cannot support a promise.

The National Laboratory of the Rockies (NLR, formerly the National Renewable Energy Laboratory/NREL) provides broader context through its solar market research. It does not qualify a named facility. Use national or sector data to frame research, then keep the account hypothesis tied to account-specific evidence.

Score only for routing if scoring helps. A score can prioritize research, but it should show its inputs rather than conceal judgment. Use categories such as confirmed fit, plausible fit, open condition, and disqualifier. Avoid false precision from a 100-point score built mostly from missing fields.

How should an EPC decide which accounts enter a campaign?

An EPC should admit an account only when a dated, source-backed fit hypothesis connects a named organization and facility to the campaign’s market, project scope, service capacity, and next customer decision. The record should distinguish verified facts, inferences, open conditions, disqualifiers, and contact permissions. A large roof, corporate target, or database title alone does not reliably establish fit or authority.

Begin with campaign exclusions so reviewers can identify out-of-scope accounts before detailed scoring. Name the service boundary, facility and project types, delivery constraints, minimum evidence, and circumstances the team will not pursue. A researcher should be able to reject a clearly out-of-scope account without turning every missing fact into a sales task.

Then write a fit hypothesis in a form another reviewer can challenge: “This named facility may fit this campaign because these dated sources support these conditions; these decision-changing facts remain unknown.” The sentence should point to a customer decision the campaign can support, such as whether to share an energy-data package or schedule a facility-evidence discussion. It should not jump to feasibility, production, savings, or schedule.

Use a routing matrix rather than hiding uncertainty in one score:

Treat every state as time-bound. An account admitted from a public facilities plan can become stale. A facility can change ownership, a contact can leave, and a campaign can exceed delivery capacity. Record the observation date and the event that triggers review. Never preserve a high-priority label after the evidence that produced it has expired.

Separate account fit from contactability. An organization may fit the campaign while no lawful, relevant, and appropriately reviewed contact route is available. That is not permission to buy more data or contact unrelated employees. Keep the account in a research or hold state and apply the organization’s privacy, advertising, and channel rules.

Use the commercial opportunity ranking method after real project evidence enters the pipeline. A campaign hypothesis and a qualified opportunity are different records. The first decides whether a bounded conversation is worth attempting. The second allocates delivery resources after the customer and project have supplied better evidence.

Map the account before mapping messages

A commercial solar decision can touch facilities, operations, energy, finance, procurement, sustainability, legal, property, executive leadership, and outside advisers. The exact group varies. Build a role map, not a rigid title list.

For each person, record the apparent role, evidence source, confidence, likely question, and permitted contact channel. “Chief financial officer” does not automatically mean project owner. A facilities manager may control access and evidence while a procurement lead controls vendor process. A sustainability lead may sponsor exploration without controlling capital.

Separate known relationships from inferred ones. Public biographies and organization charts can show formal responsibilities, but internal influence is rarely visible from outside. Use language such as “likely facilities reviewer, confirm on reply” rather than writing inference as fact.

Identify a coordination hypothesis. Which role has a useful reason to introduce another? For example, a facilities contact who confirms roof plans may bring in energy management for interval data. The outreach should make that handoff easy by naming the question, not by asking the contact to “loop in the decision-maker.”

Protect individual data. Collect only what the campaign needs, document source and permitted use, provide required notices and choices, and honor suppression. Regulatory requirements vary by jurisdiction and channel. Have qualified counsel review the operating process instead of treating a software setting as legal approval.

Research the facility in layers

Start with identity. Confirm legal or trading name, relevant facility, address, and relationship to a broader portfolio. Then record physical context from dated, attributable materials. Finally, record business context the organization has chosen to publish.

Do not perform a hidden “design” from unverified imagery. A roof sketch can help formulate questions, but outreach should label it preliminary and avoid module counts, savings, or schedule claims that depend on unknown conditions. The most credible opening may be a two-sentence observation followed by a request for the evidence that would test it.

EPA’s ENERGY STAR benchmarking resources provide public resources for tracking and managing building energy information. Use relevant materials to understand stakeholder language and program structures, not to suggest that a named account has participated or will obtain the same outcome.

Create an account evidence card with five sections:

1. Verified organization and site identifiers.
2. Publicly stated energy, facility, or capital context with dates.
3. Physical observations with source, age, and uncertainty.
4. Open technical and commercial questions.
5. Contact permissions, interactions, owners, and next review date.

The card should survive a staff change. Another person should understand why the account was selected without hearing the original researcher’s explanation.

What should an account record contain before outreach?

Before outreach, an account record should contain verified organization and facility identifiers, selection evidence with dates, physical observations, business context, role hypotheses, contact permissions, open technical and commercial questions, message boundaries, suppression status, owners, and review events. It should show why the account belongs, what is still unknown, and which evidence would justify the next stage or a disqualification decision.

Build the record around provenance, not enrichment volume. A long export can contain several names, inferred titles, firmographic categories, and platform attributes while failing to show which facility the campaign means. A smaller record with a verified site, current source, relevant role hypothesis, and clear open question gives the seller something defensible to say.

Use this copy-ready named-account card:

1. Account and facility identifiers, parent relationship, and source:
2. Campaign, segment, service boundary, and admission state:
3. Fit hypothesis in one sentence:
4. Verified selection evidence with source and observation date:
5. Physical observations with source age and uncertainty:
6. Publicly stated business context with exact scope and date:
7. Known disqualifiers and unresolved fit fields:
8. Buying-role map with person, apparent role, source, confidence, and question:
9. Contact source, permitted channel, notice status, suppression state, and applicable review:
10. Approved message spine, prohibited inference, and offered next decision:
11. Interaction history, customer wording, corrections, and evidence received:
12. Owner, next action, review event, expiry trigger, and downstream handoff status:

The role map should preserve uncertainty. “Facilities reviewer confirmed by reply” is different from “facilities role inferred from public title.” Record who controls site access, energy records, finance, operations, procurement, legal terms, and approval only when evidence supports that conclusion. Otherwise, record the question the campaign needs to resolve.

The message boundary prevents a strong source from becoming a strong claim. A corporate report may support that the organization published an objective. It does not prove a particular facility has budget, site control, technical fit, or approval. The account card should pair each useful observation with the inference it cannot support.

Illustrative workflow example, not a customer result: A researcher finds a dated company page describing an energy objective and public information identifying a distribution facility inside the EPC’s service area. The card admits the account for research but marks roof condition, site control, load data, utility context, and buying roles unknown. Outreach offers a facility-data readiness checklist instead of a savings estimate.

Treat corrections as first-class evidence. If a recipient says the organization leases the site, record the exact scope and source of that correction. Do not generalize one person’s statement to every facility unless they establish that scope. Update the admission state, related messages, and downstream audiences, then preserve the earlier version so the campaign can explain why routing changed.

Access to the record should follow the organization’s data controls. Retain only necessary personal data, define retention and deletion events, honor suppression everywhere, and prevent exported lists from becoming uncontrolled copies. A campaign brief does not replace the privacy or legal review required for the market and channel.

Build one message spine, then adapt by role

The campaign needs a consistent claim, evidence boundary, and next action. It does not need identical copy. Write a message spine that states the observed context, the question worth examining, what evidence is missing, and the small next step offered.

Adapt the concern by role. Facilities may care about roof access, planned works, and disruption. Energy management may care about interval data and load alignment. Finance may care about assumption governance, approval stages, and scenario comparability. Procurement may care about scope definition and evaluation consistency.

Do not invent personalization. Mentioning a person’s college, hobby, or unrelated social post is not account insight. Use information connected to the work and explain its relevance. A strong message can be brief because the research is specific.

Avoid premature financial promises. “We noticed a large roof and can save you 40 percent” stacks several unsupported assumptions. A responsible alternative is: “Your public site information suggests the warehouse may merit a preliminary screen. We would need current electricity data, roof information, and site constraints before discussing production or financial scenarios.”

The FTC’s advertising guidance is a useful U.S. starting point for truthful marketing duties. Campaign review should cover subject lines, landing pages, diagrams, calculators, proposals, and seller scripts, not email copy alone.

Coordinate channels without stalking the account

Channel coordination means the account receives a coherent sequence. It does not mean surrounding every identified employee with ads, email, calls, and social messages. Set contact pressure limits, role limits, suppression rules, and cool-down periods before launch.

Document what each channel can prove. An advertising platform may report delivery or interaction according to its definitions. A website visit may show that someone loaded a page. Those signals do not confirm a project, authority, identity in every case, or readiness to buy.

Google Ads Customer Match guidance and LinkedIn’s Matched Audiences documentation describe their respective platform processes and eligibility. Treat those first-party pages as documentation about the platforms, not proof that a tactic is suitable or compliant for every list and jurisdiction.

Do not equate a researched account list with an eligible upload list. Google’s Customer Match policy restricts uploaded customer information to a first-party collection context; public or purchased contact details do not satisfy that condition merely because they are relevant to an EPC. LinkedIn documents different company, contact, and engagement sources. Check the rules for the actual source, market, and configured channel rather than copying one platform’s workflow to another.

Give suppression the same attention as activation. Remove or pause people who opt out, request no contact, leave the company, enter an active sales conversation, become customers under a different communication plan, or prove the account is not a fit. Apply the approved suppression policy across applicable vendors and controlled exports, and test the delay and failure paths. Identity matching and platform eligibility can limit enforcement; verify available exclusions for each campaign and pause activation where a required restriction cannot be enforced.

For U.S. commercial email, review the FTC’s CAN-SPAM compliance guide. The guide explicitly includes business-to-business commercial email; a work address or a reply does not create a blanket exemption. Determine the message’s primary purpose and applicable requirements. Other jurisdictions and channels can impose different requirements. The campaign record should name the applicable review, not use CAN-SPAM as a universal permission slip.

Build the destination before activating media

A role-specific message should land on a page or asset that keeps the same promise. If an ad offers a portfolio data checklist, the page should not open with a generic residential quote form. If an email discusses an assumption review, the form should ask only for information needed to arrange that review.

State who the resource is for, what it helps decide, what information is required, and what happens after submission. Do not conceal a sales call behind a download. If a person will contact the prospect, say so. If the asset is available without contact, do not manufacture urgency.

Keep technical claims aligned across ad, page, asset, email, and proposal. Maintain a claim registry with approved wording, evidence, owner, jurisdiction, review date, and expiry. A copied sentence can outlive the report or rule that once supported it.

Test the destination on a small screen, with keyboard navigation, and without relying on images. Technical diagrams need text equivalents and readable labels. Use the W3C WAI forms guidance when reviewing field labels, instructions, error identification, and feedback; a checklist alone does not establish accessibility conformance. Forms should retain consent language and error messages when embedded in campaign pages.

Define the marketing-to-technical handoff

An engaged account is not design-ready. Write the handoff criteria before the first response arrives. The record may require a confirmed site, a named customer decision, evidence owner, available electricity data, known facility plans, timeline context, and permission for the next conversation.

Route by evidence, not enthusiasm. One reply may justify a short qualification call. Another may justify a data request. A third may reveal that the account leases the site and lacks control. The correct outcome can be continue, nurture, refer, defer, or disqualify.

Do not ask designers to rescue incomplete briefs. Marketing and sales should attach the account evidence card, interaction history, requested output, open questions, and customer wording. The technical team can then decide whether a preliminary screen is responsible.

Define what returns to marketing. If the technical reviewer finds imagery too old, load data incomplete, a facility out of scope, or a portfolio structure misunderstood, update the selection logic. This feedback is more valuable than a dashboard celebrating clicks from poor-fit accounts.

The solar project intake process provides a useful boundary between a conversation and design-ready work. Use that distinction explicitly in campaign operations.

Before adopting campaign tooling, apply a solar design software checklist to the downstream workflow so a marketing experiment does not quietly create an unsupported technical promise.

When should marketing hand an account to a solar technical team?

Marketing should hand an account to a solar technical team only when the site, customer decision, requested output, evidence owner, available records, open conditions, consent, and follow-up responsibility are clear enough for a bounded review. Engagement alone is insufficient. The handoff should let the reviewer accept, narrow, defer, refer, or reject the request without inventing missing project facts or assumptions.

Define the minimum handoff by output. A short evidence-readiness conversation needs less than a preliminary site screen. A concept comparison needs more than either. The campaign should never promise a design, production figure, savings result, engineering conclusion, or schedule before the receiving team confirms that the required inputs and review capacity exist.

Use the following acceptance table:

Make the receiving review visible in the account stage. “Handoff sent” reports an activity. “Accepted for bounded screen,” “returned for current energy data,” “referred outside scope,” or “declined because the facility is unverified” reports a decision. Marketing can then improve selection and offers from the reasons work was returned.

Do not punish the technical team for narrowing the request. A reviewer who changes “full proposal” to “data-readiness review” may be protecting the customer from a premature output. Sales should take that revised boundary back to the account and explain what evidence would support the next stage.

Capture the return path before launch. Technical findings can change the account hypothesis, public-message claims, destination copy, and campaign exclusions. If several handoffs fail because ownership control is unknown, add that question earlier. If imagery is repeatedly too old, stop using roof-specific personalization until a better evidence route exists.

The best handoff is uneventful. The reviewer recognizes the customer question, finds the evidence where the account card says it is, sees every open condition, and can make a bounded decision without reconstructing the campaign from emails. That standard is more useful than a target that rewards the number of leads delivered regardless of readiness.

Measure account movement and evidence quality

Create a funnel that reflects decisions rather than channel events. Useful stages include selected, researched, contactable, engaged, evidence exchange, qualified next step, technical review, opportunity, deferred, and disqualified. Define the entry evidence for each stage.

Track platform metrics as diagnostics. Low delivery may reveal poor data. High clicks and low evidence exchange may reveal a weak destination. Replies from irrelevant roles may reveal a bad contact map. None should be converted into revenue or project claims without the necessary data.

Measure coverage carefully. “Three contacts” is less meaningful than “facilities role confirmed, energy role inferred, procurement unknown.” Count roles with their confidence and relationship, not merely database rows.

Record disqualification reasons in controlled categories plus notes. Common reasons can include geography, site control, timing, data availability, project type, delivery capacity, and explicit no-contact request. Do not use a catch-all “not interested” label when the response contains information that should change targeting.

Freeze a dated account cohort and report unique accounts at each defined stage. Keep people, sessions, facilities, opportunities, and organizations as separate units; state the rule for an account with multiple facilities or contacts. If reporting accepted handoffs divided by admitted accounts, use the same cohort, observation window, eligibility and acceptance definition, and show both counts. A zero eligible denominator makes the rate undefined, and open reviews should not silently become failures.

Review cohort maturity before comparing campaigns: later replies and long technical reviews can leave one cohort less observed than another. Compare campaigns only when account definitions, channels, offers, observation windows, and stage definitions are sufficiently similar. A before-and-after change or an attributed reply alone does not prove incremental campaign impact.

Run a prelaunch account audit

Before launch, sample accounts across the priority range. Ask a reviewer who did not build the list to find the source for every fit statement. Remove claims that cannot be traced. Mark inferences. Check whether any public information is stale or concerns the wrong subsidiary or facility.

Then rehearse the response paths. A prospect asks where the roof image came from. A facilities leader says the site is leased. A finance contact asks for savings. A recipient opts out. A named employee has left. Each scenario needs an owner, approved response boundary, and system action.

Audit links, forms, routing, notifications, and suppression. Confirm that the seller sees the same account note the marketer used. Confirm that the technical team can refuse an unsupported deliverable without breaking the customer communication.

Finally, approve a stop rule. Pause if claims drift, opt-outs fail to sync, research quality falls, follow-up capacity is exceeded, or technical teams repeatedly reject briefs. Spending more media cannot repair a broken evidence chain.

Treat the first campaign as a controlled operating test

Do not launch every segment, channel, and asset at once. A bounded first cohort makes failures observable. Choose accounts that represent the intended market without selecting only the easiest examples. Freeze the selection criteria and message versions for the observation window so the team knows what it actually tested.

Hold a short review after the first replies and again after the first technical handoffs. Marketing should bring delivery, interaction, opt-out, and message data. Sales should bring reply context and role corrections. Technical reviewers should bring evidence gaps, unsuitable requests, and differences between the public hypothesis and the real site.

Separate a process correction from a campaign result. A broken form, wrong owner, missing suppression, or delayed follow-up invalidates part of the test. Fix the control and record the date rather than averaging bad and corrected periods into one reassuring metric.

Read silence cautiously. It can reflect timing, channel, deliverability, relevance, authority, workload, or no current interest. It does not prove that the account lacks a solar opportunity. Likewise, a reply can be polite curiosity rather than buying intent. Advance the record only when the defined evidence appears.

Version research when the account changes. If the company sells a property, announces roof work, changes an energy objective, or identifies a different contact, preserve the old entry and add the new source. This prevents the team from quoting stale personalization months later.

Close the test with decisions. Keep, revise, or remove each selection field. Keep, revise, or retire each message. Adjust the role map. Change the handoff threshold if technical reviewers received premature requests. Review suppression evidence across controlled exports and supported advertising exclusions. Record unavailable identity matches, delays, and activation limits instead of treating a campaign label as proof that every individual was excluded.

The outcome is an operating system the team can explain, not just a campaign report. If the next cohort cannot see how accounts were selected, why messages were sent, how consent was managed, and what qualified a handoff, the test has produced activity without a reusable method.

The operational checklist

• One customer decision and one bounded offer are written.
• Market, geography, project types, exclusions, and capacity are explicit.
• Every named account has a dated fit hypothesis with sources.
• Physical observations are separated from verified site facts.
• Role maps record evidence, confidence, concern, and contact permission.
• Personalization is relevant, proportionate, and reviewable.
• Claims match across advertising, pages, assets, email, and seller scripts.
• Channel pressure, suppression, and cool-down rules are configured.
• Required privacy, advertising, and communication reviews are recorded.
• The destination states the resource, information request, and follow-up.
• Engagement does not automatically trigger design or proposal work.
• Handoff fields name the decision, evidence, gaps, owner, and next action.
• Stage definitions require observable evidence.
• Disqualification and corrections feed back into account selection.
• A named owner can pause the campaign when controls fail.

For SurgePV, 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.

Frequently Asked Questions

What makes a solar campaign account-based?

An account-based campaign begins with a named organization and a documented reason it may fit, then coordinates research, messages, people, and follow-up around that account. It is not a mass list with company names inserted. The account record should show evidence, uncertainty, buying roles, consent status, and the next useful decision.

How many accounts should an EPC include in one campaign?

There is no universal number. Capacity depends on research depth, seller coverage, market size, deal complexity, data quality, and the degree of personalization promised. Start with the number the team can research, review, contact lawfully, and follow consistently. Expand only after the handoff and learning process works.

Which roles belong on a commercial solar buying map?

Map the roles that control the site, energy data, finance, operations, facilities, procurement, sustainability objectives, legal terms, and final approval. Titles vary by organization, so record the role each person appears to play and how that was inferred. Do not treat a contact database title as proof of authority.

Should an EPC send a preliminary solar design in cold outreach?

Usually begin with a bounded observation or useful diagnostic rather than a design that implies access to verified site data. If a preliminary image is used, label its source, date, assumptions, and limitations. Never imply that imagery confirms roof, structural, electrical, tariff, authority, utility, or commercial conditions.

How should an EPC measure an account-based campaign?

Measure movement in named accounts: verified contacts, useful replies, evidence obtained, meetings with relevant roles, qualified next decisions, and documented disqualification. Keep advertising and email metrics as diagnostic signals. An impression, click, or page visit does not prove buying intent, technical fit, or project readiness.