Sample for variation
Include won, lost, declined, and delayed work across more than one segment. Do not select only successes.
Guiding instrument
Make 15 opportunities comparable.
One row per opportunity. Unknown stays visible. The ledger exists to reveal a repeated decision failure, not to make the business look measured.
Privacy boundary
Use anonymous row IDs on the public-safe copy. Keep customer names, prices, private correspondence, and relationship context in an approved private system.
Minimum useful schema
Capture the decision, delay, and outcome.
- FieldOpportunityRecordAnonymous row IDDecision valueDiscuss the sample without exposing a customer
- FieldSourceRecordHow the opportunity arrivedDecision valueTest which relationships or channels create suitable work
- FieldFit decisionRecordPursue, decline, or needs evidenceDecision valueMake qualification judgment visible
- FieldProposalRecordSent date, decision date, outcomeDecision valueReveal bidding delay and loss patterns
- FieldHandoffRecordOwner, delay, rework, missing contextDecision valueTest whether demand would create delivery damage
- FieldRelationshipRecordActor, contribution, consentDecision valueTest the relationship thesis without inferring trust
- FieldEconomicsRecordKnown, unknown, or approved rangeDecision valuePrevent invented ROI and expose the next finance question
| Field | Record | Decision value |
|---|---|---|
| Opportunity | Anonymous row ID | Discuss the sample without exposing a customer |
| Source | How the opportunity arrived | Test which relationships or channels create suitable work |
| Fit decision | Pursue, decline, or needs evidence | Make qualification judgment visible |
| Proposal | Sent date, decision date, outcome | Reveal bidding delay and loss patterns |
| Handoff | Owner, delay, rework, missing context | Test whether demand would create delivery damage |
| Relationship | Actor, contribution, consent | Test the relationship thesis without inferring trust |
| Economics | Known, unknown, or approved range | Prevent invented ROI and expose the next finance question |
Review for recurrence
Count repeated wait states and reasons. The largest count is a signal, not automatic proof of the constraint.
Put this to work
Code one opportunity
You are a careful business analyst protecting client privacy.Copy this prompt. Paste into Claude, ChatGPT, or any AI assistant. The page context is already loaded — send it and get analysis tailored to your role.
Help me code one Solar365 opportunity for a diagnostic ledger. Ask one question at a time for: 1. anonymous opportunity ID; 2. segment and source; 3. qualification decision and reason; 4. proposal dates, outcome, and delay reason; 5. delivery handoff, rework, or missing context; 6. relationship contribution and consent to record it; 7. known economics or UNKNOWN. Label every answer FACT, REPORTED, INFERRED, ESTIMATE, ASSUMPTION, or UNKNOWN. Do not calculate ROI or fill missing values. End with the one cheapest fact that would improve this row.
Verdict
CONDITIONAL GO
The ledger is ready to use. The diagnosis remains untested until 15 real opportunities are coded and reviewed by Mike.