Team sign in Better conversations.
Cleaner handoffs.
Practical reading for the people building a career, running a sales team and taking care of the customer along the way.
From the field desk
200 short articles · Page 10Starting solar discovery with energy-use questions
A useful solar discussion begins with how the homeowner uses energy and what they want to understand.
Read the field note ↗Solar conversationsKeeping utility-provider information accurate
The provider associated with a city or neighboring home may not be the provider for the selected property.
Read the field note ↗Solar conversationsDiscussing expected changes in electricity use
Future usage assumptions should be recorded as scenarios, not added silently to historical consumption.
Read the field note ↗Solar conversationsAsking about roof plans before a solar proposal
The timing of roof work can be relevant to a solar project and should be discussed before assumptions harden into a proposal.
Read the field note ↗Solar conversationsExplaining why a solar estimate is preliminary
An estimate is preliminary when important inputs or approvals still need confirmation.
Read the field note ↗Solar conversationsKeeping solar savings claims tied to their assumptions
A savings figure is only understandable when the inputs and comparison behind it are visible.
Read the field note ↗Solar conversationsHandling questions about solar incentives
Incentive questions need current, applicable information rather than a remembered example from another customer.
Read the field note ↗Solar conversationsExplaining an equipment substitution request
A product change should be reviewed for its effect on the proposal rather than described as interchangeable by default.
Read the field note ↗Solar conversationsDiscussing shading without making unsupported claims
A visual impression of shade can prompt a question but does not establish a complete performance analysis.
Read the field note ↗Solar conversationsPreparing a solar bill-review appointment
A bill review is more efficient when the relevant information is available through the approved process.
Read the field note ↗Solar conversationsKeeping solar proposal scope separate from optional additions
Optional equipment or related work should be easy to distinguish from the base proposal.
Read the field note ↗Solar conversationsResponding to a homeowner’s battery question
A battery question may be about backup, daily energy use or a concern the homeowner has not yet stated clearly.
Read the field note ↗Solar conversationsExplaining project stages in a solar conversation
A homeowner benefits from a clear sequence without being asked to learn every internal department name.
Read the field note ↗Solar conversationsComparing solar options with the same assumptions
An option comparison becomes confusing when the underlying usage or rate assumptions change between columns.
Read the field note ↗Solar conversationsRecording a homeowner’s existing solar system
Existing equipment should be documented as context for review rather than treated as an automatically compatible starting point.
Read the field note ↗Solar conversationsExplaining why an aerial image and a roof model differ
An image and a reconstructed model may reflect different dates, data limits or building selections.
Read the field note ↗Solar conversationsDiscussing a homeowner’s long-term plans
A proposal conversation should reflect the customer’s stated plans without treating uncertain future events as facts.
Read the field note ↗Solar conversationsPreparing a solar customer question log
A question log should make it easy to see what has been answered and what still affects the decision.
Read the field note ↗Solar conversationsKeeping a solar recommendation within your role
A sales rep can gather useful context without making decisions reserved for technical or specialized reviewers.
Read the field note ↗Solar conversationsEnding solar discovery with a useful summary
A discovery summary should connect the customer’s priorities to the information the next reviewer needs.
Read the field note ↗