Quick Answer
Measure solar customer acquisition by building one traceable cost ledger for each defined cohort, then dividing only by a named, mature outcome. Include direct channel spend, external services, attributable people cost, sales tools, proposal support, approved allocations, and failed-outcome treatment. Keep signed, handed-off, installed, and paid-customer views separate.
A founder opens a channel report and sees a cheap cost per sale. The media invoice is there. Sales payroll is elsewhere, agency work sits in accounts payable, proposal support is charged to operations, cancelled deals vanished at the reporting cutoff, and the denominator counts signatures that have not passed handoff. The number is clean because the expensive parts live outside its frame.
That is the central problem in solar customer acquisition measurement. Teams debate whether paid search, referrals, events, partners, canvassing, or organic demand is cheaper before agreeing on which costs belong in the numerator and which customer state belongs in the denominator. A lower number can mean a better channel. It can also mean a narrower ledger, a younger cohort, a different project mix, or a missing invoice.
This guide builds a full-cost operating record per sale without inventing a benchmark. It does not tell a company how to recognize expenses, revenue, commissions, or contract assets. Those judgments belong to qualified accounting and legal owners under the company’s facts and jurisdiction.
There is a serious inventory conflict to resolve. The existing solar customer acquisition cost guide already targets benchmarks and channel economics. Editors should consolidate that page and this one unless a separate governance asset is required. This article is bounded to ledger construction, denominator control, cohort maturity, allocation evidence, and review.
The solar lead generation guide addresses demand creation. The solar sales funnel guide addresses stage flow. The solar sales KPI guide addresses metric contracts. Here the job is narrower: make the acquisition-cost number reconstructable before anyone uses it to move budget, judge a channel, or plan growth.
What does solar customer acquisition cost include?
Solar customer acquisition cost includes the spend and attributable work accepted by the company’s measurement policy for winning a defined customer outcome. A full operating view can include channels, outside services, people, commissions, systems, data, proposal support, failed outcomes, and approved shared-cost allocations. The ledger must state what it excludes and why.
Start with a boundary sentence, not a formula. For example: “For residential opportunities first accepted in the named market during the cohort window, measure approved acquisition resources through the selected outcome cutoff and divide them by customers reaching the stated outcome under the current policy.” That sentence exposes market, cohort, resource boundary, outcome, cutoff, and policy version.
The formula can remain symbolic until source records and calculation logic are validated:
Full acquisition cost per selected outcome = accepted cohort acquisition cost / eligible mature outcomes
The numerator still needs a ledger. “Sales and marketing spend” is too vague to audit because teams post related work under different departments and systems. The denominator still needs an event contract. “Customer” may mean a signed agreement, accepted operational handoff, completed installation, first payment, or another company-defined state.
Use cost families without deciding accounting treatment in the dashboard
An operating ledger can collect cost families while leaving formal accounting classification to the responsible owner. The point is visibility, not a casual ruling about capitalization, expense recognition, payroll allocation, tax, revenue, or financial statements.
| Cost family | Records to inspect | Boundary question | Common omission |
|---|---|---|---|
| Direct channel spend | Platform invoices, media exports, event bills, referral records | Which spend can be tied to the cohort under the accepted rule? | Credits, fees, local campaigns, or late invoices |
| Outside services | Agency invoices, creative work, call support, list services, partner fees | Which work served acquisition rather than brand, recruiting, or delivery? | Retainers allocated without a service-period rule |
| People cost | Time records, payroll inputs, contractor invoices, role mapping | Which activities and roles are attributable under policy? | Founder, manager, coordinator, or follow-up time |
| Commission and incentive | Approved plan, eligibility events, payments, reversals | Which event earns, accrues, pays, or reverses the amount? | Mixing quoted, approved, paid, and retained amounts |
| Systems and data | CRM, telephony, forms, enrichment, scheduling, analytics | Which systems support the cohort, and how is shared use allocated? | Annual tools omitted from a monthly view |
| Proposal and technical support | Request, design, review, finance, revision, presentation records | When does pre-sale technical work enter the acquisition boundary? | Work posted to operations because of team ownership |
| Failed and delayed outcomes | Declines, withdrawals, cancellations, duplicates, holds, expiry | Where does consumed cost remain after the outcome fails or matures late? | Removing spend with the lost opportunity |
| Shared cost allocations | Approved allocation schedule, driver, period, owner | Which driver reflects resource use well enough for the decision? | A flat percentage with no version or source |
This table is an operating inventory. It does not establish which entry belongs in a financial statement, tax return, commission plan, or contract calculation. Keep the original account, department, vendor, person, time period, project or opportunity link, allocation driver, and reviewer decision so a qualified owner can apply the proper treatment.
NASA describes configuration management as visibility into and control of changes to functional and physical characteristics across a product life cycle. A private solar cost ledger is not a NASA system. The useful analogy is version control. Channel mappings, commission rules, attribution windows, stage definitions, allocations, and outcome events change, so the report should retain the policy version that produced each cohort.
Separate observed cost, allocated cost, and excluded cost
An invoice tied directly to one campaign has a different evidence path from manager time allocated across several channels. Keep those categories separate. An observed cost has a source record and direct cohort connection. An allocated cost has a source total plus an approved driver. An excluded cost has a reason, owner, and policy reference.
Do not turn “hard to allocate” into zero. Put the amount in an unresolved bucket, preserve its source, and show how the current view changes if the bucket is included or excluded. The team can then decide whether the measurement is usable for a channel adjustment, rough capacity discussion, or formal financial process. Missing evidence should narrow the decision.
The cost boundary also needs a time boundary. A creative invoice may cover several campaigns. A software contract may cover a year. A commission may change state after cancellation. A proposal may be revised after the reporting period. Record service dates, event dates, posting dates, cohort dates, and the report cutoff rather than forcing every record onto one timestamp.
How should a solar company build the full cost stack per sale?
Build the full cost stack by naming the decision, fixing the cohort and outcome, mapping cost families to source records, documenting direct and allocated treatment, reconciling late or missing items, validating the denominator, and releasing the view with limitations. Every stage needs an owner, evidence link, policy version, and stop condition.
-
Name the decision. State whether the report supports channel budgeting, operating diagnosis, staffing, pricing discussion, forecast input, or another bounded decision. One ledger can feed several views, but each view needs its own fitness test.
-
Define the cohort. Choose the event that admits an opportunity, the market, offer, project type, route, accepted sources, start and end dates, maturity rule, and observation cutoff. Preserve duplicate and re-entry rules.
-
Define the selected outcome. Write the exact source-system event and responsible owner for a signed contract, accepted handoff, completed project, paid customer, or other state. Avoid one generic “sale” label across all of them.
-
Build the source map. Connect each cost family to invoices, platform exports, payroll or contractor inputs, commission records, tool contracts, proposal work, and allocation schedules. Record the system, field, period, identifier, and custodian.
-
Classify cost treatment. Mark each record direct, allocated, unresolved, excluded, credited, reversed, or pending under the operating policy. Never overwrite the source amount or original classification.
-
Reconcile timing and failures. Test late invoices, credits, refunds, delayed decisions, cancellations, withdrawals, duplicate leads, reopened opportunities, and outcomes occurring after cutoff. Decide how later facts revise a closed view.
-
Validate lineage and calculation. Sample displayed values and trace them backward through transformations to source records. Recompute any derived result with an approved script and declared units before showing it as fact.
-
Release with limits and next review. Publish the cohort, outcome, included and excluded cost, unresolved amount, allocation version, maturity, calculation version, owner, reviewer, use boundary, and refresh event.
The process deliberately delays arithmetic. A beautifully formatted cost-per-sale result is worthless if the cohort mixes markets, the numerator drops proposal work, or the denominator counts outcomes with different maturity. First make the records comparable enough for the decision. Then compute.
Build one acquisition event chain
Map the flow units before joining records. A person, household, account, inquiry, opportunity, site, design request, proposal, contract, project, invoice, commission record, and payment are different objects. One person may submit several inquiries. One opportunity may have several proposals. One contract may cover more than one site.
Write the allowed relationships and their cardinality. Joining two proposal revisions to three contact activities can create six rows even though neither table contains six unique acquisition events. The ledger owner should define primary keys, foreign keys, deduplication, selected versions, and treatment of deleted or merged records.
| Flow object | Admission event | Required identity | Exit or maturity evidence | Owner question |
|---|---|---|---|---|
| Inquiry instance | Accepted source receipt | Source event and person or account link | Routed, rejected, merged, or expired under policy | Did the record enter the process legitimately? |
| Opportunity | Approved opportunity creation | Account, site, offer, route, cohort | Defined decision or maturity cutoff | Which commercial question is being worked? |
| Design request | Accepted technical request | Opportunity, site, scope, inputs, output class | Returned, accepted, released, or closed | Was pre-sale technical work admitted with usable inputs? |
| Proposal candidate | Controlled release | Opportunity, design version, assumptions, reviewer | Revised, delivered, withdrawn, superseded, or accepted | Which version supported the decision? |
| Contract state | Approved contract-system event | Parties, scope, version, conditions | Signed, rescinded, cancelled, handed off, or other controlled state | Which commercial event actually occurred? |
| Project or customer outcome | Company-defined later event | Contract and operational identity | Mature under the selected policy | Does this denominator match the decision? |
| Cost record | Invoice, payroll, contract, or approved internal event | Vendor or person, period, amount, source account | Direct, allocated, excluded, reversed, or unresolved | Can another reviewer reconstruct its treatment? |
Digital.gov’s plain-language guidance emphasizes creating and testing content for the intended audience. Apply that principle to event and cost labels. “Marketing,” “sales,” “commission,” “proposal,” and “customer” are not sufficient definitions. The person reviewing a budget should be able to tell what entered the ledger without calling the report builder.
Connect proposal work to the acquisition record
SurgePV can support the design and proposal portion of a controlled solar workflow when source inputs, assumptions, versions, and responsible review remain visible.
Explore solar proposal workflowsWhich denominator makes customer acquisition cost usable?
The usable denominator is the named outcome that matches the decision and has matured under a documented cutoff. Keep cost per accepted inquiry, qualified opportunity, signed contract, accepted handoff, completed project, and paid customer as separate views. Never let one generic customer count silently substitute for a later operational or financial outcome.
Suppose the acquisition manager wants to understand media and follow-up efficiency. A mature qualified-opportunity view may be useful before installation outcomes exist. If operations wants to understand work arriving with complete evidence, accepted handoff is closer to the decision. A founder discussing cash planning needs records governed by the responsible finance process, not a sales signature tile.
The right practice is a denominator ladder, not a fight over one universal definition. Each rung states what happened and what did not yet happen.
| Denominator view | Event contract | Decision it may support | What it must not imply |
|---|---|---|---|
| Accepted inquiry | Valid source event accepted under current rules | Capture and routing operations | Qualified demand, sale, or customer value |
| Qualified opportunity | Controlled route decision with required evidence | Discovery and channel diagnostics | Proposal readiness or contract outcome |
| Proposal decision opportunity | Mature opportunity receiving a controlled proposal candidate | Proposal process review | Signature, revenue, or installation |
| Signed contract | Approved contract-system state under company policy | Sales-stage outcome review | Cash, recognized revenue, margin, or completion |
| Accepted operational handoff | Downstream owner accepts required scope and evidence | Sales-to-delivery interface review | Permit, installation, payment, or project quality |
| Completed project | Company-defined operational completion event | Later delivery-linked acquisition view | Cash collection, profit, or lifetime value |
| Paid customer | Responsible system records the selected payment state | A finance-governed view under stated policy | Universal accounting or tax treatment |
Use maturity rules before comparing cohorts
A January cohort and a June cohort have not had equal time to reach a later outcome at a July cutoff. Dividing all cost by current outcomes makes the younger cohort look more expensive even when its eventual path is unknown. Define a maturity rule that fits the outcome, preserve immature records, and label any early view as incomplete.
Maturity is not permission to discard delayed work. Keep status, next event, owner, and reason evidence. A permit wait, financing review, customer pause, technical hold, company capacity constraint, or unclassified delay carries different implications. The reason field describes the recorded state. It does not prove why the outcome occurred.
Cancelled and withdrawn outcomes deserve the same discipline. Preserve consumed acquisition cost under the chosen policy. If a cancelled contract later re-enters as a new opportunity, state whether the earlier cost follows it, remains with the original cohort, or is shown in both views with reconciliation. Silent reassignment lets reports improve without the business changing.
The FTC’s solar consumer guidance identifies project, site, bid, finance, contract, company, and sales-pressure questions for shoppers. DOE’s homeowner guide says there is no universal solar solution and discusses site, energy, utility, and commercial context. Those sources support keeping project context visible. They do not validate a private denominator, sale, customer, or cost result.
How should channels and cohorts be compared?
Compare acquisition channels only after preserving the attribution rule, market, offer, project type, route, cohort dates, maturity, cost boundary, allocation version, and selected outcome. Present both observed differences and unresolved evidence. A cheaper channel is a hypothesis for investigation until the team rules out missing cost, attribution leakage, and unequal case mix.
Channel names are rarely stable enough by themselves. “Organic” may contain branded search created by offline work. “Referral” may include partner payments, customer rewards, or unpaid word of mouth. “Paid search” may receive credit for a sale that began at an event. Record the attribution method and retain touch records rather than pretending the label is natural law.
Use a comparison contract before ranking channels:
| Comparison field | Required record | Review question |
|---|---|---|
| Attribution | Model, lookback, source events, override rule, version | Why did this channel receive credit? |
| Market and offer | Geography, service boundary, product class, campaign | Are buyers and projects comparable enough? |
| Cohort | Admission event, date range, maturity, cutoff | Has each group had equal opportunity to reach the outcome? |
| Numerator | Included, allocated, excluded, unresolved, credits, reversals | Did one channel lose costs posted elsewhere? |
| Denominator | Exact outcome event, eligibility, duplicate rule | Do the counts mean the same thing? |
| Route and case mix | Qualification route, project type, complexity, source restrictions | Did the channel receive different work? |
| Capacity conditions | Coverage, territory, staffing, design and delivery constraints | Did operating conditions change the observed path? |
| Evidence quality | Source completeness, join tests, missing values, late records | How much confidence can the decision carry? |
Treat attribution as a policy with version control
First-touch, last-touch, multi-touch, and source-system defaults answer different questions. None creates causal proof. Preserve raw touches, campaign identifiers, referral evidence, manual overrides, and the attribution version. When the policy changes, do not restate history without a bridge between old and new views.
Privacy and permission also belong in the acquisition workflow. NIST describes its Privacy Framework as a voluntary tool for identifying and managing privacy risk. It does not establish consent or legal compliance. Route collection, identity, permission, use, retention, deletion, access, profiling, and cross-system joining to qualified privacy and legal owners for the applicable jurisdiction.
That separation matters because a technically joinable record is not automatically appropriate to use. The cost analyst may need a bounded identifier or aggregated cohort instead of a full customer profile. Record who approved the use, what data was necessary, where it came from, and when the permission or policy must be reviewed.
Use a decision table instead of a winner label
The output of a channel review should be an evidence-backed next test, not a permanent ranking. State the observation, competing explanations, missing records, bounded action, owner, affected cohorts, guardrails, review date, and stop condition.
For example, a channel may show a lower current cost per signed contract. Before moving budget, test whether its cohort is older, manager time is omitted, proposal revisions are posted elsewhere, contract cancellations arrive later, or branded demand was credited to the final click. If those checks remain unresolved, the decision may be to improve source capture rather than change spend.
Which mistakes make acquisition cost look cheaper than it is?
Acquisition cost looks artificially cheap when labor, commissions, proposal support, shared tools, failed outcomes, late invoices, credits, or allocation changes fall outside the numerator, or when immature signatures inflate the denominator. Attribution leakage, duplicate joins, mixed markets, changed policies, and silent exclusions can produce the same false comfort without reducing one real cost.
The most dangerous report is not obviously broken. It reconciles to one source and carries a precise decimal. Precision says nothing about the boundary. Review the omissions and denominator before discussing the result.
| Failure mode | What the dashboard shows | What may be happening | Required response |
|---|---|---|---|
| Media-only numerator | Low channel cost | People, agency, systems, or proposal work is elsewhere | Reconcile all cost families and disclose excluded items |
| Signature denominator | Strong cost per customer | Later cancellation or handoff failure is immature | Keep stage-specific views and apply maturity rules |
| Lost-deal deletion | Improving cohort | Consumed cost left with removed records | Preserve failed-outcome cost and state the policy |
| Flat shared allocation | Stable comparison | Resource use differs by channel or period | Document the driver and test sensitivity |
| Final-click attribution | One channel wins | Earlier touches or offline demand are invisible | Retain touch evidence and compare attribution versions |
| Many-to-many join | High activity and distorted cost | Rows multiplied across contacts, proposals, and invoices | Test cardinality and deduplicate by declared keys |
| Missing becomes zero | Complete-looking ledger | Unknown cost or outcome is treated as none | Preserve missingness and block unsupported conclusions |
| Policy rewrite | Historical improvement | Definitions changed without a bridge | Version the policy and restate only with reconciliation |
| Blended case mix | Channel difference | Markets, project types, offers, or routes differ | Segment or narrow the claim |
| Cost used as causation | Budget moved with confidence | Observed association has competing mechanisms | Record a bounded test and guardrails |
Keep advertising claims and finance decisions in their own review lanes
The FTC’s advertising guidance says advertising must be truthful and non-deceptive and objective claims need evidence. A cost ledger does not approve a customer-facing savings claim, channel promise, testimonial, comparison, or offer. Keep message evidence and disclosure review connected to the campaign record.
Likewise, an internal full-cost operating view does not decide formal accounting, tax, contract, commission, employment, or revenue treatment. Retain source records and route those questions to qualified owners. A dashboard can show what the operating policy included. It should not disguise judgment as software output.
Copy-ready acquisition cost ledger and review record
Use this copy-ready operating record for one cohort and one selected outcome. Store links to source records rather than pasting sensitive customer or employee data into the worksheet.
| Record field | Entry |
|---|---|
| Decision supported | |
| Cohort admission event | |
| Cohort dates and market | |
| Offer, project type, and route | |
| Selected outcome event | |
| Maturity rule and observation cutoff | |
| Attribution method and version | |
| Direct channel cost sources | |
| Outside-service sources | |
| People-cost source and approved method | |
| Commission or incentive source and state | |
| Systems and data allocation | |
| Proposal and technical-support treatment | |
| Shared-cost allocation driver and version | |
| Failed, cancelled, delayed, and reopened treatment | |
| Credits, refunds, reversals, and late invoices | |
| Excluded costs and reasons | |
| Unresolved amounts and sensitivity view | |
| Source joins, keys, and deduplication | |
| Calculation specification and script | |
| Owner, reviewer, and qualified escalation | |
| Use boundary and prohibited interpretations | |
| Refresh event and next review |
Illustrative example: the cheapest channel changes after reconciliation
This is an illustrative example, not a customer case or benchmark. A founder sees Channel A below Channel B on a media-cost-per-signature view. The review finds that Channel A’s agency retainer and proposal-revision work were posted outside marketing, its cohort is older, and recent cancellations have not reached the report. Channel B includes its outside service and uses an accepted-handoff denominator.
The team does not invent adjusted results. It moves both channels onto the same cohort, cost families, allocation version, maturity rule, and outcome definition. Unresolved manager time remains visible as a sensitivity item. The next decision is a source-reconciliation task with an owner and due event, not an immediate budget transfer.
The example shows why full cost is a review method before it is a number. A missing amount can prevent a fine-grained ranking while the ledger still reveals a useful process defect.
Where SurgePV fits, and where it stops
SurgePV’s repository-verified scope includes solar array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. These functions can help a team keep pre-sale technical requests, assumptions, versions, and proposal outputs connected to the acquisition record.
No verified claim says SurgePV is the source of truth for advertising spend, lead attribution, identity, consent, CRM stages, timekeeping, payroll, commissions, accounting, tax, recognized revenue, contract status, installation completion, or customer lifetime value. The responsible systems and qualified owners must govern those records.
The practical handoff is precise. Acquisition operations creates a stable opportunity and technical-request identity. Responsible solar staff validate inputs and assumptions. SurgePV supports the bounded design and proposal work. The acquisition ledger records attributable treatment under the approved policy. Finance, legal, privacy, employment, technical, and operational owners retain their authority.
Frequently Asked Questions
What belongs in solar customer acquisition cost?
A decision-useful solar customer acquisition ledger can include direct media and lead costs, agencies and outside services, attributable employee and contractor cost, commissions under the company’s policy, sales systems and data, proposal and technical support, approved shared-cost allocations, and the chosen treatment of failed or delayed outcomes. Accounting treatment requires qualified review.
Should solar CAC use signed contracts or installations?
Use the denominator that matches the decision, label it precisely, and keep later outcomes separate. Cost per signed contract can support sales-process review. Cost per accepted handoff can expose delivery readiness. Cost per completed installation or paid customer answers a later question. None is a universal substitute for the others.
How should cancelled solar deals affect acquisition cost?
Keep the acquisition cost of cancelled, withdrawn, declined, duplicated, or stalled opportunities visible under a documented policy. Do not quietly remove their spend from the cohort or count them as successful outcomes. Classify the state, owner, reason evidence, maturity cutoff, and any later re-entry without treating a reason code as proven causation.
Can solar companies compare acquisition cost by channel?
Yes, after making channel cohorts comparable enough for the decision. Preserve attribution rule, market, offer, project type, route, observation window, maturity, shared-cost allocation, cancellation treatment, and outcome definition. A low channel cost can reflect an immature cohort, missing labor, different case mix, or attribution leakage rather than better acquisition.
Can SurgePV calculate complete customer acquisition cost?
No verified product claim says SurgePV is an advertising, CRM, payroll, commission, consent, accounting, revenue-recognition, or customer-acquisition-cost system of record. SurgePV supports solar layout, shading, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation. Companies must govern acquisition records and financial treatment in their responsible systems.
The number a founder can trust is not the one with the most decimal places. It is the one another reviewer can reconstruct, challenge, and narrow to a real decision. Build the ledger, keep each denominator honest, preserve missing cost, and let unresolved evidence reduce confidence before it redirects budget.
Review the design-to-proposal part of your acquisition workflow
See how SurgePV supports bounded solar design and proposal work while your responsible systems retain acquisition, accounting, and customer records.
Book a SurgePV demoSources
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.
