Skip to main content

Reality ◯ · Diagnose before prescribing

Where does expert judgment wait today?

Your proposal loop holds the judgment—and its cost is unread.

Solar365 already knows how to design and deliver solar. The uncertain part is not expertise. It is how much expert attention each enquiry consumes before a decision-ready proposal can leave the business.

§1

Trusted capability, manual hand-offs

The honest map

Public proof and named tools exist. Lead qualification, proposal framing, site heuristics, follow-up, and delivery-readiness judgment remain human-held. That is a diagnosis to test, not a verdict to automate around.

  • Public claims: 3,000 installations, 15 years' combined experience, 16% average return, and six-year payback. Their method and sample are not public.
  • Current-stack claim from the local brief: OpenSolar, Quotient, Xero, Outlook, and Excel. Actual usage and integration are unread.
  • Internal volume, cycle time, owner hours, win rate, and project gross profit are UNKNOWN. No estimate substitutes for a reading.
§2

Five numbers make the first decision safe

The readings

Discovery does not begin with an AI recommendation. It reads the current system so Mike and Austin can decide whether the proposal loop deserves the first intervention.

  • Qualified enquiries and proposals per month, by segment.
  • Elapsed time from qualified enquiry to proposal sent.
  • Owner or expert hours per proposal path.
  • Win rate by segment and reason for loss.
  • Gross profit from one representative commercial or school project.
§3

Five named problems

Each problem names its current leak, its opportunity cost, and the signal that would prove or disprove it. None is a verdict — each is a hypothesis the discovery sprint tests.

Leverage trap

Current leak: Every qualified commercial or school lead requires expert triage before a decision brief is possible. Mike and Austin are the bottleneck.

Opportunity cost: High-value leads wait while expert attention is rationed. Response speed — the key competitive factor in agent-mediated procurement — is structurally capped.

Proof signal: Tribal audit: 6 of 7 areas are HIGH tribal risk. Discovery sprint: time 5 proposal paths to reveal where expert hours are consumed.

Thin intake

Current leak: The public form captures contact, location, build type, and property type. It does not capture bill size, decision date, budget, urgency, or roof constraints.

Opportunity cost: Every qualified lead requires a manual discovery call before the proposal process can begin — multiplying expert time at the earliest stage.

Proof signal: Data audit §LOW: bill size, urgency, budget, and decision date all confirmed missing from intake.

Unverifiable trust

Current leak: 3,000 installs, 16% average return, and 6-year payback are homepage claims. The method, segment sample, and performance data are not structured or machine-readable.

Opportunity cost: When AI buying agents compare suppliers, Solar365's strongest asset — its install record — is invisible to the agent. Reputation becomes a handicap instead of a moat.

Proof signal: Northstar § Protect Trust: the two-year position requires machine-verifiable performance proof. The data trail starts in Stage 1.

No win/loss learning

Current leak: Proposal outcomes, follow-up decay, and lost reasons are not captured in any system. Each proposal cycle starts from scratch.

Opportunity cost: Every proposal cycle loses learning that should compound — ICP targeting, proposal language, pricing signals, and delivery-risk flags.

Proof signal: Cockpit instrument: win/loss outcome field is required from cycle 1. Without it, Stage 2 ICP targeting has no data to build on.

Delivery-speed mismatch risk

Current leak: No system checks subcontractor readiness before a commercial promise is made. Faster proposals can create install promises the business cannot keep.

Opportunity cost: The trust built across 3,000 installs can be damaged faster than it was built if sales speed outpaces delivery capacity.

Proof signal: Kill signal in transformation-plan.md: 'Delivery stress — faster sales creates unowned subcontractor or install handoff risk.'

§4

The data audit — fact, inference, or unread

Every claim below is tagged by confidence. HIGH is publicly verifiable or confirmed in the operating brief. MEDIUM is inferred and must be measured. LOW is confirmed missing — the discovery sprint's shopping list.

Exists — high confidence

  • Public intake form dataHIGHName, company, contact, address, region, postcode, build type, property type — visible at solar365.co.nz/lets-talk.
  • Installation track record and public performance claimsHIGH3,000 installations, 15 years combined experience, 16% average return, 6-year payback — stated publicly on site. (Source: homepage scrape 2026-06-25.)
  • Current tool stackHIGHOpenSolar, Quotient, Xero, Outlook, and Excel — confirmed in operating brief.
  • Value stage sequenceHIGHLead gen → enquiry triage → proposal generation → subcontractor engagement → billing — confirmed in operating brief.

Likely but unread — medium confidence

  • Proposal volume by ICP segmentMEDIUMLikely tracked informally; actual count per month by business/school/farm/residential is unconfirmed. Needed to set Stage 1 ROI ceiling.
  • Current proposal cycle timeMEDIUMHow long from qualified enquiry to proposal sent — inferred as slow but not yet baselined. Must be measured in 5-path discovery before any ROI claim.
  • OpenSolar template and AI feature usageMEDIUMLikely in active use for design — which features, templates, and data fields are used is unaudited. Tool audit required by Day 10.
  • Win rate by segment and proposal typeMEDIUMLikely known informally by Mike/Austin — not yet extracted as data that could feed proposal targeting or ROI modelling.

Confirmed missing — low confidence

  • Bill size, urgency, budget, and decision date in intakeLOWThe current form does not capture the inputs needed for a decision brief. Stage 1 depends on adding or requesting these fields before proposal automation is possible.
  • Lead-to-win attribution by source and segmentLOWWhich channel, segment, and proposal type produces the best-margin won work — not tracked in any system today.
  • Subcontractor availability and cost by regionLOWNo system tracks which subcontractors are available, trusted, and priced — delivery-readiness is a gap before any proposal-speed increase.
  • Proposal effort hours by job classLOWThe baseline for Stage 1's 50% reduction target. Until this is measured, the ROI argument is ASSUMPTION, not FACT. (Evidence-ledger.md tag: ASSUMPTION.)
§5

Where judgment lives today

Tribal knowledge is expertise that lives only in expert heads. High tribal risk with low documentation means the business cannot delegate, systematise, or prove that judgment — and AI cannot read a signal that was never written down.

  • Lead triage logicTRIBAL HIGHDOCUMENTED LOWWhich leads deserve expert attention today lives in Mike and Austin's judgment. AI cannot route a signal it cannot read.
  • Proposal pricing and ROI framingTRIBAL HIGHDOCUMENTED LOW16% average return and 6-year payback are homepage claims. The method, segment, and sample size are not documented — cannot feed structured proposals.
  • Site assessment heuristicsTRIBAL HIGHDOCUMENTED LOWRoof type, orientation, shading, and system-sizing rules live in expert heads. No intake field captures enough to prepare a decision brief automatically.
  • Subcontractor selection rulesTRIBAL HIGHDOCUMENTED LOWWhich subcontractors are trusted, available, and right by region is key-person risk. A faster proposal loop that ignores delivery capacity creates broken promises.
  • ICP prioritisation and win/loss patternsTRIBAL HIGHDOCUMENTED LOWBusinesses-first, schools-second is the stated order. Actual win rates and effort-to-value by segment are unknown — can't target what isn't measured.
  • Follow-up discipline and deal stageTRIBAL HIGHDOCUMENTED LOWStale follow-ups are an invisible cost. No system tracks which qualified leads are waiting or decaying without owner action.
  • Tool usage (OpenSolar, Quotient features)TRIBAL MEDIUMDOCUMENTED LOWWhich OpenSolar features are active, which templates exist, which Quotient fields are populated — unaudited. Stage 1 depends on knowing this before build.
§6

What Solar365 already has

The diagnosis is not a deficit story. These assets are why the constraint is worth fixing — they are what a better proposal loop would leverage.

  • Install base. 3,000 installations — public proof of delivery at scale that most new entrants cannot match.
  • Multi-segment demand surface. Six ICPs already in market: businesses, schools, farms, community centres, solar farm investors, homeowners.
  • Expert judgment. Mike and Austin carry site assessment heuristics, pricing logic, and supplier relationships built over 15 years.
  • Existing tool stack. OpenSolar, Quotient, Xero, Outlook, and Excel — no greenfield build required for Stage 1.
  • Named value stages. Lead gen → enquiry triage → proposal generation → subcontractor engagement → billing. The transformation can be scoped as lead-to-invoice.