Treehouse — Competitive Analysis
Flow 10·Unresearched·housecallpro

Contract / payment

The financial commitment: deposit, payment schedule, and terms. FSMs handle this natively for most contractors. Treehouse's role here is limited — this step stays in the contractor's existing system for most jobs.

Acceptance
User goal

Homeowner needs a clear payment schedule and confidence that the contract terms are fair. Contractor needs a deposit to commit materials and labor, and clear terms that protect against scope creep.Hypothesis

Treehouse implication

Payment and contract are not Treehouse's primary surface. Treehouse should write the accepted scope, option, and pricing to the FSM and let the FSM handle payment. The one exception: if Treehouse provides a deposit mechanism that allows payment before a site visit (as part of the remote-scoping workflow), that would need a payment integration.Hypothesis

How competitors approach this

No companies mapped to this flow yet.

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.

Not yet researched.Unresearched

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

Not yet researched.Unresearched

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

Not yet researched.Unresearched

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

Not yet researched.Unresearched

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

Not yet researched.Unresearched

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

Not yet researched.Unresearched

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

Not yet researched.Unresearched

Happens automaticallyWorkflow events that fire without a contractor action.

Not yet researched.Unresearched

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

Not yet researched.Unresearched

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.

Homeowner needs a clear payment schedule and confidence that the contract terms are fair. Contractor needs a deposit to commit materials and labor, and clear terms that protect against scope creep.Hypothesis

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

Deposit collection at proposal acceptance (or immediately after). For financed jobs: financing company disburses funds on completion. For unfinanced jobs: contractor collects by check, card, or bank transfer.Hypothesis

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

From proposal acceptance: accepted option, total price, financing selection. From payment processor: payment method, authorization.Hypothesis

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

Housecall Pro: integrated payment processing at 2.59% (card) or 1% (bank transfer). Payment collected within the HCP app. Invoice generated from the job record.Company claimSource

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

Collect deposit. Review payment terms. Handle financing disbursement coordination. Issue invoice at job completion.Hypothesis

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

Deposit amount negotiation. Payment-schedule exceptions for large jobs. Financing application denials that require an alternative plan.Hypothesis

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

A signed contract (if separate from proposal), a deposit receipt, a payment schedule.Hypothesis

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

FSM owns payment collection and invoicing. Treehouse should write the proposal acceptance to the FSM and then step back — payment lives in the FSM.Hypothesis

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

FSMs handle payment well — HCP, ServiceTitan, and Jobber all have integrated payment processing. Financing disbursement is handled by the financing partner.Company claimSource

Product weaknessesWhere current products fall short or create new problems.

Financing integration varies by contractor — some FSMs do not integrate directly with financing providers. Contract terms are often generic and may not protect contractors adequately on complex scoped jobs.Hypothesis

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

Payment and contract are not Treehouse's primary surface. Treehouse should write the accepted scope, option, and pricing to the FSM and let the FSM handle payment. The one exception: if Treehouse provides a deposit mechanism that allows payment before a site visit (as part of the remote-scoping workflow), that would need a payment integration.Hypothesis

Open questions

  • 01Does Treehouse collect a deposit today — if so, at what stage and through what mechanism?
  • 02For remote-scoped jobs, is there a Treehouse-specific payment event (deposit before site visit) that the FSM doesn't model?
  • 03Should Treehouse own the deposit collection for remote-scoped jobs, or always pass to the FSM?