06 — Treehouse opportunity areas

Five starting hypotheses

These are ordered for validation, not by value. “Never lose a lead” is first because it is the least dependent on Treehouse’s own operating model and has three directly comparable products to test against — being first to investigate is not the same as being proven. All five remain hypotheses.

Never lose a lead

First wedge to investigateUniversal

Treehouse responds, qualifies, books, and follows up automatically.Hypothesis

Validation order — 1 of 5

The first wedge to investigate. It is the least dependent on Treehouse's unusual operating model, it is the outcome Housecall Pro itself lists first among contractor goals, and it has three directly comparable products to test against. First to investigate is not the same as proven.Hypothesis

Competitive inspiration

LeadTruffleDeep dive

BroccoliDeep dive

CactusDeep dive

Contractor pain: Leads go cold between form-fill and first human response; unsold estimates rarely get a systematic follow-up.Hypothesis
Current behavior / workaround: Office staff or the owner manually calls/texts back when they have a free moment, often hours or days later.Hypothesis
Treehouse capability: Treehouse already sits at partner-owned acquisition surfaces and custom landing pages, plus communications AI workflows, so it can plausibly answer and qualify before a human touches the lead.Hypothesis
Proposed value: Faster response time and a follow-up cadence that never silently drops a lead, without adding headcount.Hypothesis
Adoption wedge: A free or near-free lead-response layer that sits in front of however the contractor already works.Hypothesis
Potential monetization: Could be the free/cheap wedge itself rather than a direct revenue line; monetize downstream stages.Hypothesis
FSM relationship: Hands off a qualified, booked lead into the contractor's existing FSM/CRM rather than replacing it.Hypothesis
Biggest risk: An AI response that mishandles a licensed-trade question or over-promises could damage contractor trust before a human ever sees the lead.Hypothesis
Evidence: Not yet researched — validate against the Broccoli, LeadTruffle, and Cactus cluster, which is now Tier A.Unresearched
Open questions: How much qualification can happen before a human is legally/practically required (e.g. licensed-trade questions)? Can the AI collect photos, or does it stop at contact details?Hypothesis

Scope without a truck roll

Segment

Homeowner-guided data collection + Panel IQ + Edison produce a usable technical scope remotely.Hypothesis

Validation order — 2 of 5

Second: this is where Treehouse's differentiated capability would raise the value of the wedge above. Depends on Opportunity 1 having found a contractor willing to engage at all.Hypothesis

Contractor pain: An in-person site visit to scope a job is expensive and slow, and often happens before a homeowner is sold.Hypothesis
Current behavior / workaround: Contractor (or a salesperson) drives to the home to take panel photos, measurements, and notes by hand.Hypothesis
Treehouse capability: Treehouse's guided homeowner photo-upload flow, computer vision / Panel IQ, and Edison automated scoping are built specifically for this — this may be genuine, defensible differentiation rather than a feature parity play.Hypothesis
Proposed value: A usable scope before the first truck roll, cutting cost-to-quote and shortening time-to-proposal.Hypothesis
Adoption wedge: Offer remote scoping as a faster alternative path into an existing sales process, not a replacement for it.Hypothesis
Potential monetization: Per-project technical service fee, or bundled into a broader software subscription.Hypothesis
FSM relationship: Scope output should be structured enough to hand off cleanly into design/proposal tooling and eventually FSM.Hypothesis
Biggest risk: A remote scope that turns out wrong on-site (missed panel condition, code issue) costs more trust than the truck roll it was meant to save.Hypothesis
Evidence: Panel IQ and Edison exist today, per the product context in this brief; competitive parity/gap is not yet researched.Treehouse internal
Open questions: Where does remote scoping accuracy break down (panel condition, code edge cases, older homes), and how is that risk communicated?Hypothesis

Turn a technical scope into a sale

Segment

Potential journey: scope → products → price → incentives → financing → proposal.Hypothesis

Validation order — 3 of 5

Third: tests whether proposal automation increases the economics of the offering. The Airship / EDEN / Housecall Pro comparison is the evidence base.Hypothesis

Competitive inspiration

AirshipDeep dive

EDENFocused scan

Contractor pain: A completed scope still requires manual work to become a priced, financeable, presentable proposal.Hypothesis
Current behavior / workaround: Contractor or office staff manually builds pricing, looks up incentives, and assembles a proposal document.Hypothesis
Treehouse capability: Treehouse's scoping, pricing, margin and discount logic, plus its rebate/incentive and equipment datasets, could be exposed through APIs and composed into a contractor-facing proposal flow — reusing the backend capability rather than surfacing the internal tool.Hypothesis
Proposed value: Faster, more consistent proposals with incentives and financing already reflected, improving close rate.Hypothesis
Adoption wedge: Feed directly off the remote-scoping wedge (#2) so the two opportunities compound.Hypothesis
Potential monetization: Financing/payments revenue share, plus proposal-conversion-linked pricing.Hypothesis
FSM relationship: A sold, financed proposal is the natural handoff point into execute/FSM.Hypothesis
Biggest risk: Financing and incentive rules change by jurisdiction and lender; a stale or wrong number in the proposal is a direct credibility hit.Hypothesis
Evidence: Not yet researched — the Airship and EDEN deep dive/scan should validate whether this is a crowded or open lane.Unresearched
Open questions: Does Treehouse need its own financing relationships, or can it broker existing ones credibly?Hypothesis

Turn a sale into an install-ready project

Unknown

Potential automatic outputs: BOM, installer SOW, plan set, equipment guidance, supporting documentation, FSM handoff.Hypothesis

Validation order — 4 of 5

Fourth. Carries the highest odd-duck risk of the five: much of Treehouse's install-ready tooling exists to run national partner programs at scale, which is not a problem most contractors have.Hypothesis

Contractor pain: Converting a sold deal into something a crew can actually install still takes manual drafting and paperwork.Hypothesis
Current behavior / workaround: Designers/estimators hand-build plan sets, SOWs, and permit paperwork per project.Hypothesis
Treehouse capability: Treehouse's plan-set generation, installer SOWs, equipment specifications/guides, and permit/AHJ dataset are positioned to automate this handoff — though these are also the capabilities most shaped by Treehouse's own national-program operating model.Hypothesis
Proposed value: An install-ready package generated automatically instead of drafted by hand, cutting pre-install lead time.Hypothesis
Adoption wedge: Natural next step for any contractor already using Treehouse for scoping/selling.Hypothesis
Potential monetization: Per-project technical-service fee; potentially bundled with materials/equipment ordering.Hypothesis
FSM relationship: This is the FSM handoff — the explicit boundary where Treehouse's package enters the contractor's FSM.Hypothesis
Biggest risk: An install-ready package that's wrong or incomplete in the field is worse than no automation at all — it fails at the most expensive possible moment.Hypothesis
Evidence: Plan sets, SOWs, and equipment guides exist today, per the product context in this brief; depth of automation is not yet documented here.Treehouse internal
Open questions: Which FSM systems need first-class writeback support, and what does a clean handoff format look like to each?Hypothesis

Let the economic activity fund the product

Unknown

Explore whether core software could be inexpensive/free while Treehouse monetizes through payments, financing, per-project technical services, successful jobs, materials/equipment, demand generation, or OEM/utility/partner economics.Hypothesis

Validation order — 5 of 5

Sequenced last, and deliberately retained. A funding model presumes a workflow contractors already run their business through — the question is real, but it cannot be answered before there is a product they use.Hypothesis

Contractor pain: Contractors resist paying for another software subscription on top of their system of record.Hypothesis
Current behavior / workaround: Contractors adopt point tools only when the ROI is immediate and undeniable, or when a partner subsidizes it.Hypothesis
Treehouse capability: Treehouse already touches payments-adjacent and partner-economics surfaces (partner-owned acquisition, white-label flows) that could carry monetization instead of seat pricing.Hypothesis
Proposed value: Lower adoption friction for the core workflow tool, with revenue captured where value is created (a closed, financed, installed job).Hypothesis
Adoption wedge: The other four opportunities, individually, each function as a candidate free/cheap wedge.Hypothesis
Potential monetization: This card is the monetization question — see the Monetization landscape (05) for the full matrix.Hypothesis
FSM relationship: Model-dependent; the goal is to fund the software without requiring Treehouse to replace the FSM.Hypothesis
Biggest risk: A monetizable event that's too rare or too small per-occurrence to fund the free tier would leave Treehouse subsidizing adoption indefinitely.Hypothesis
Evidence: Hypothesis — this is the secondary strategic question the whole site is organized to help answer.Hypothesis
Open questions: Which monetizable event is both frequent enough and large enough to fund a free core product?Hypothesis