Flow 09·Company claim·airship, housecallpro

Proposal delivery / customer approval

The homeowner reviews the proposal and decides. For in-home sales tools (Airship), this happens on a tablet in the kitchen. For remote proposals, this happens asynchronously on the homeowner's own device.

Acceptance

User goal

Homeowner needs to understand what they are buying, why each item is needed, what it costs, and how they will pay. Contractor needs a clear accept or decline — not 'let me think about it.'Hypothesis

Treehouse implication

Treehouse's model is remote-first — the proposal is likely delivered before any site visit. In-home vs. remote is a different conversion model. What closes a homeowner who is sitting with a tech vs. a homeowner who receives a PDF link is a different question. Treehouse needs data on which model its contractors use and which produces better outcomes.Hypothesis

How competitors approach this

No companies mapped to this flow yet.

Treehouse read

What Treehouse owns, orchestrates, and defers to the FSM — plus six supporting questions that shape architecture decisions. All entries are hypothesis until validated internally.

Treehouse ownsCore IP or data that Treehouse controls and no partner provides.

The digital delivery mechanism. The acceptance and signature flow. The 'proposal analytics' layer (when did the homeowner open it, how long did they spend on each option, did they share it with someone else before accepting).Hypothesis

Treehouse orchestratesThird-party capabilities Treehouse coordinates but does not own.

The financing application (via partner). The FSM writeback on acceptance. The follow-up sequence for homeowners who open but don't sign.Hypothesis

Stays in the FSMWorkflow or data that belongs in the contractor's system of record.

Scheduling the accepted job. Dispatching the technician. The work order.Hypothesis

Differentiated intelligenceWhat Treehouse knows or computes that competitors cannot easily replicate.

The proposal's connection to a technical scope — the homeowner sees not just a price but WHY each item is required, backed by a load calculation and NEC citations. That technical credibility is unusual at the residential level.Hypothesis

Commodity infrastructureCapabilities that are table stakes — others have them too.

Digital signature (DocuSign or equivalent). Email/SMS delivery. PDF generation.Hypothesis

Persists across the journeyData or state from this step that must travel to later steps without re-entry.

The accepted option, selected equipment, financing choice, and digital signature. All flow forward to the work order, permit application, and invoice.Hypothesis

Contractor seesWhat the contractor-facing UI surfaces from this step.

Real-time notification when the proposal is opened, viewed, and signed. The accepted option and financing details. An alert if the homeowner opens but doesn't sign within a configured time.Hypothesis

Happens automaticallyWorkflow events that fire without a contractor action.

Digital delivery. Open/view tracking. FSM writeback on acceptance. Follow-up nudge if not signed within N hours.Hypothesis

Human takeoverConditions that require a contractor or Treehouse team member to intervene.

Any homeowner question that requires a licensed-trade answer. Financing application exceptions. Negotiation on scope or pricing.Hypothesis

Research detail11-field structured template: contractor workflow, information flows, product outputs, FSM read/write

User goalWhat the homeowner and contractor each need from this step.

Contractor workflowHow contractors handle this step today, with or without software.

In-home model (Airship): tech presents on tablet while sitting at the kitchen table. Homeowner selects an option, applies for financing if needed, and accepts on the spot. Remote model: contractor emails or texts a proposal link. Homeowner reviews on their own device and signs digitally.Hypothesis

Information entersWhat data flows in — from the homeowner, the FSM, prior steps.

From proposal: scope summary, options, pricing, financing details, rebates. From homeowner: option selection, financing application, digital signature.Hypothesis

What the product doesWhat the software handles — based on evidence, not assumptions.

Airship: interactive tablet presentation with option comparison, monthly payment display, inline financing application, digital acceptance. Homeowner experience designed for in-home conversion.Company claimSource

Contractor must doSteps that always require a human decision or action.

Present the proposal (in-home model). Answer homeowner questions about scope, pricing, or technical content. Handle financing application exceptions. Confirm acceptance.Hypothesis

Requires judgmentWhere automation breaks down and a licensed trade professional is needed.

Homeowner objections about price, scope, or timing. Negotiation on add-ons or discounts. Financing application results that require adjustments to the option presented.Hypothesis

Product outputsWhat the step produces — data, documents, FSM records.

An accepted proposal with the homeowner's option selection and financing choice. A declined proposal with notes. A digital signature and acceptance date.Hypothesis

FSM read / writeWhat the tool reads from and writes to the contractor's system of record.

Airship: accepted proposal writes back to ServiceTitan automatically. The accepted option, equipment, and pricing flow from Airship into the FSM job record.Company claimSource

Product strengthsWhat the best products in this step do unusually well.

Monthly payment alongside upfront cost in the same view removes the homeowner's need to calculate affordability. Inline financing keeps the homeowner in the proposal — no separate application.Company claimSource

Product weaknessesWhere current products fall short or create new problems.

All Airship product-interior captures are requires-sales-demo — financing application behavior, homeowner UX, and actual close rates are not independently verified. Remote delivery (email link) has a known drop-off rate that in-home does not.Hypothesis

Treehouse implicationWhat this step means for Treehouse's product positioning and architecture.

Open questions

01What is Treehouse's current close rate on proposals sent vs. accepted?
02Is there data on in-home vs. remote proposal acceptance rates for electrical work?
03Should Treehouse's proposal support in-home presentation (a tablet-optimized view) as well as async remote delivery?
04At what ticket size does inline financing materially improve close rates for electrical work?
05What happens when a homeowner declines — is there a nurture flow?