Skip to main content

Solar365 · AI-native operating model · owner/operator report

Ready in 24 months or routed around.

This report turns the Reality, Dream, and Bridge lenses into one board-level decision: keep expert judgment trapped in the manual proposal loop, or codify it into a data spine and proposal cockpit.

Northstar

Ready in 24 months or routed around.

Solar365 has the assets to become the commercial-and-school solar partner that AI buying agents surface first. The risk is not lack of trust. The risk is that trust stays trapped in human memory, slow proposals, and unstructured proof.

First proof

90 days, not a vague roadmap

Stage 1 proves whether a commercial or school lead can reach a decision-ready proposal with less owner time before any larger transformation is funded.

Decision

Codify judgment or protect the bottleneck

The owner/operator decision is whether to keep expert judgment as the bottleneck, or codify that judgment into a data spine and proposal cockpit.

§1

Reality: The Stack Is Not Empty

Solar365 does not need to start from a blank page, because the operating trace already has documents, projects, accounts, contacts, sites, and captured value signal.

The risk is that this evidence stays ungoverned and cannot support fast, trusted proposals.

920

documents analysed

137

deduped projects

169

accounts

275

contacts

128

sites

$3.72M

estimated system value

5,874

DQ warnings

Unknown

consent state

documents analysed

Enough operating trace to start from evidence, not opinion.

deduped projects

Project signal exists after duplicate records are merged.

accounts

Commercial relationships can be grouped before proposal targeting.

contacts

Relationship data exists, but consent status must be resolved.

sites

Site-level data can become the spine for delivery and proof.

estimated system value

Captured value signal, subject to source confidence and reconciliation.

DQ warnings

Data quality is a workstream, not a blocker, if it is gated early.

consent state

No outreach automation should run until consent rules are explicit.

Compliance gate

Consent is unknown. No outreach automation, customer scoring, or raw-row exposure should run until consent, retention, and data-use rules are explicit.

§2

Dream: The Two-Year Position

In two years, Solar365 should be the commercial-and-school solar partner an AI buying agent surfaces first and trusts most in its region. That requires two things: fast structured proposals and machine-verifiable proof.

Agent-preferred

Readable by buyers and machines

The offer, evidence, ROI assumptions, delivery risk, and next step need to be structured enough for a human buyer and an AI buying agent to compare.

Extinction risk

Reputation can become invisible

If proposal speed and proof stay manual, AI-mediated procurement can route around Solar365 even when the company is trusted by humans.

§3

Operating Model: Five Business Functions

The operating model is not a chatbot. It is a tighter business system across demand, delivery, trust, finance, and platform. Each function needs one better loop, and each loop needs proof before the next bet.

Business functions map.

Business functions

Demand, delivery, trust, finance, and platform must improve together. Proposal speed cannot outrun delivery trust.

Business stack diagram.

Business stack

The first platform move is a data spine across existing tools, not a replacement platform.

Demand

Inbound demand exists, but high-value leads still need manual triage.

A scored intake queue routes commercial and school leads by value, urgency, and readiness.

Delivery

Proposal speed depends on expert review and unstructured handoff.

Each lead gets a decision brief, delivery-risk check, and proposal path before expert approval.

Trust

The 3,000-install record is real, but not machine-verifiable.

Install and performance proof becomes structured data an agent, buyer, or human can inspect.

Finance

Value appears late, after manual proposal work has already happened.

Proposal effort, margin signal, and won/lost outcomes guide the next funded cycle.

Platform

OpenSolar, Quotient, Xero, Outlook, and Excel need human glue.

A lead-to-proof data spine connects the tools without forcing a greenfield rebuild.

§4

Transformation Plan: First 90 Days

Stage 1 is the first proof loop. It does not ask Mike to buy a two-year AI program. It asks whether the highest-friction proposal work can become a cockpit with a kill signal.

Day 14

Discovery

20 enquiries mapped, 5 proposal paths timed, GO/NO-GO named.

Day 30

Cockpit

Scored intake and decision briefs active on real leads.

Week 6

Kill signal

Proposal effort must be down 30%, or scope narrows or stops.

Day 90

Decision

Fund the next cycle only from measured proof.

First proof metric

A qualified commercial or school enquiry reaches a decision-ready proposal with materially less owner time and no hidden delivery risk.

§5

Eight Cycles to the Northstar

The two-year horizon is roughly eight 90-day cycles. Each cycle earns the next one. A cycle that produces output without a decision signal does not count.

Cycle 1

90-day proposal cockpit proof

14-day discovery, Day 30 cockpit, Week 6 kill signal, Day 90 stage decision.

Cycle 2

Delivery-readiness loop

Proposal speed only increases when install capacity and handoff risk are visible.

Cycle 3

Win/loss and ICP targeting

Commercial and school segments are scored from actual outcomes, not memory.

Cycle 4

Performance proof spine

Install record starts becoming machine-verifiable trust data.

Cycle 5

Finance and margin cockpit

Proposal and delivery choices connect to margin, cash, and next-bet funding.

Cycle 6

Agent-readable commercial offer

Solar365 can be compared by buying agents without losing its local trust edge.

Cycle 7

Funded growth bet

Savings and confidence from earlier cycles fund the next growth surface.

Cycle 8

Agent-preferred operating model

Demand, delivery, trust, finance, and platform reinforce one another.

§6

Journey Modules

These seven modules show the transformation from different angles: agency, business functions, stack, buyer job, prompt system, route discipline, and protected expert attention.

Agency fulfillment journey diagram.

Agency fulfillment journey

The transformation is not tool adoption. It is an owner-operator path from trapped judgment to greater agency.

Business functions map.

Business functions

Demand, delivery, trust, finance, and platform must improve together. Proposal speed cannot outrun delivery trust.

Business stack diagram.

Business stack

The first platform move is a data spine across existing tools, not a replacement platform.

Jobs-to-be-done awareness journey.

JTBD awareness journey

The buyer job is a fast, credible solar decision. Solar365 must make that decision easier to trust.

Prompt deck builder workflow.

Prompt deck builder

Codified judgment becomes reusable prompts, briefs, and checks that humans can approve.

Routes journey framework.

Routes journey framework

Each 90-day cycle has a route, proof signal, kill signal, and next decision.

Time and mindset optimisation map.

Time and mindset optimisation

The point is to protect expert attention for judgment, not spend it on copying, chasing, and re-explaining.

§7

Decision Gate

Default path

Keep the manual expert bottleneck

Solar365 keeps using trust and experience, but proof stays hard to inspect and proposal speed stays bounded by owner attention.

Chosen path

Codify judgment into the cockpit

Solar365 turns expert judgment into a repeatable lead-to-proposal data spine, while humans still approve the judgment.

§8

Appendix

The report is the synthesis. These supporting pages hold the lenses and reusable patterns behind it.