Orlando solar sales conversations: explain utility assumptions without promising the outcome
Prepare an Orlando proposal conversation around the actual utility, account history, self-use and exports, with an organized follow-up record.
Identify the account before using a savings example
Find the utility and service address on the customer’s bill. Do not choose an export assumption simply because the address says Orlando. Ask whether the property already has solar and whether ownership or the utility account holder is changing. Collect relevant records through the approved process, with the customer’s permission.
For OUC accounts, its announced export-credit changes take effect November 1, 2026. [1] Use the current approved proposal assumptions and identify their date. If you cannot explain which account treatment applies, write the question for the proposal team. Avoid presenting a neighbor’s bill or an older sales screenshot as evidence of this customer’s future outcome.
Explain the model as a set of assumptions
Ask the customer about daytime occupancy, work-from-home hours, planned EV charging and other changes. Then show how the proposal separates expected production, self-used energy, exports and grid purchases. A large annual generation number does not answer how a specific household uses energy over the day.
When a customer asks, “Will my bill be gone?”, review the estimated remaining charges and the solar payment together. Show which figures are modeled and what remains uncertain. If a battery is included, explain the stated operating goal and have technical questions checked by the appropriate reviewer. Do not substitute a product brochure for a property-specific backup assessment.
Keep the property questions in the same conversation
Ask about roof history, ownership approval, known shade concerns and related electrical work. Record observations without diagnosing the property. Use the exact address to confirm the permit authority; City of Orlando publishes its own solar review resources for work in its jurisdiction. [2] A mailing address is a starting point for verification, not a permit determination.
Explain what is included in the installed scope and which conditions can change it. Ask the customer to identify any decision that depends on a roof finding, another owner’s approval or a particular payment term. Preserve those conditions so the next reviewer sees the conversation the customer actually had.
Close the conversation with a bounded next step
A useful next step might be obtaining a missing bill, reviewing a written proposal or arranging the approved property assessment. Name the follow-up owner and the question to resolve. Keep customer preferences and agreed contact windows in the workspace. Do not promise a utility approval date or a savings outcome to get the next appointment.
Before representing Origin, confirm role approval, market coverage, permitted tools, training requirements and written compensation terms. New rep applications are reviewed; they do not create an account or guarantee work. Use the approved submission route and keep Origin Direct attribution separate when a customer chooses that path.
Bring these questions to onboarding
- Verify the utility, account history and service address.
- Date and explain the proposal’s utility assumptions.
- Review self-use, exports, purchases and payments separately.
- Preserve roof, ownership and scope questions for the project team.
- Record the agreed next step and authorized follow-up process.
Primary sources
- OUC: Rooftop Solar and TruNet Solar
Checked September 30, 2026. OUC states that announced export-credit changes take effect November 1, 2026. Verify account-specific treatment and current requirements.
- City of Orlando: Permitting Checklists
Checked September 30, 2026. Includes solar plan-review resources; an Orlando mailing address alone does not establish city jurisdiction.
Origin’s workflow questions are editorial guidance. Current account permissions and written agreements govern representation, compensation and project responsibility. Utility references do not imply an affiliation.