Housecall Pro
Understand the likely target contractor's operating system, with particular depth on how a lead becomes a quote/estimate, how scope becomes line items and price, how the result becomes a customer-facing proposal, and where Treehouse should integrate rather than replace.
- –What is the canonical customer / property / job ontology?
- –When does a lead become a job?
- –How does an estimate or quote actually get created?
- –What information must the contractor already know before the software is useful?
- –How are line items generated?
- –How much does the price book matter?
- –How are labor, material, and equipment represented?
- –Where does trade expertise enter the workflow?
- –How is a proposal generated, and is that distinct from an estimate?
- –How does customer acceptance occur, and what changes after it?
- –What does HCP do well enough that Treehouse should not rebuild it?
- –Where does HCP feel generic across trades?
- –What would Treehouse need to READ from HCP?
- –What would Treehouse need to WRITE BACK to HCP?
- –What could Treehouse calculate or generate before handing the project back to HCP?
Establish what a trade-specific proposal experience provides that a generic FSM proposal does not — and whether Treehouse's current approach is actually better or merely different.
HubSpot (customer/deal records) plus some current Zuper functionality
HCP's system-of-record role maps most closely to how Treehouse uses HubSpot for customer and deal state, with Zuper covering parts of the field-execution side. The analogue is about the role the system plays, not feature equivalence.Treehouse internal
Needing one place that holds customers, jobs, schedules, and invoices looks universal across the target segment. Which specific system fills that role is contractor-by-contractor, which is the argument for integrating rather than replacing.Hypothesis
ACompany thesis
- Product
Not yet researched.Unresearched
- Category
Not yet researched.Unresearched
- Primary customer
Not yet researched.Unresearched
- Primary user
Not yet researched.Unresearched
- Core JTBD
Not yet researched.Unresearched
- Initial wedge
Not yet researched.Unresearched
- System relationship
Not yet researched.Unresearched
- Value proposition
Not yet researched.Unresearched
- How they make money
Not yet researched.Unresearched
- Why Treehouse cares
Not yet researched.Unresearched
This company wins if Not yet researched.
BEnd-to-end product journey
GTM / pricing
8/16 collectedUniversalLens: What promise gets a contractor to try or buy? (Distinct from onboarding, which starts only after that decision is made.)
Signup & onboarding
3/7 collectedUniversalLens: How much effort is required before a contractor receives meaningful value? What business information does HCP require before the system becomes useful?
Customer + property record
17/18 collectedUniversalLens: What does HCP consider the canonical customer record? How is a homeowner/property represented?
Treehouse analogue: HubSpot contact / deal records
Lead / request intake
5/10 collectedUniversalLens: How does demand enter the system before it becomes scheduled work?
Treehouse analogue: HubSpot communications workflows
Estimate creation
4/13 collectedUniversalLens: How does technical/service knowledge become a priced customer offer? Where must the contractor already know the electrical answer?
Treehouse analogue: Edison products/services, BOM, pricing, margins and discounts
Proposal
0/10 collectedUniversalLens: What does HCP's paid proposal tool add over a plain estimate, and how does that compare to a trade-specific proposal layer?
Treehouse analogue: Treehouse's PandaDoc-based proposal generation
Estimate approval
3/6 collectedLens: How does an estimate become a committed job?
Job record
7/12 collectedLens: What becomes canonical once work is sold?
Treehouse analogue: Zuper job records
Scheduling + dispatch
3/9 collectedLens: This is likely functionality Treehouse should not rebuild — understand exactly why.
Treehouse analogue: Zuper scheduling / dispatch
Technician / field experience
10/15 collectedLens: What information does the technician need at the moment of execution?
Treehouse analogue: Zuper field workflows
Invoice + payment
10/11 collectedLens: Where and how does HCP monetize the contractor's economic activity?
Pipeline / reporting
2/6 collectedLens: How does the owner understand opportunities and business health?
Integrations
2/7 collectedUniversalLens: How does HCP define its ecosystem boundary?
AI / automation
4/8 collectedLens: Where is HCP already moving toward the contractor growth/automation layer? Do not force this flow if functionality is inaccessible.
CActivation
Signup → company setup → integrations → configuration → first meaningful value
- Narrative
Not yet researched.Unresearched
- Must be entered manually
Not yet researched.Unresearched
- What can be inferred
Not yet researched.Unresearched
- What gets imported
Not yet researched.Unresearched
- Domain knowledge assumed
Not yet researched.Unresearched
- Self-service or assisted
Not yet researched.Unresearched
- Time to magic
Not yet researched.Unresearched
Go-to-market & adoption
How does this company actually get adopted? Compares against a hypothetical upload a panel photo → receive a useful result immediately wedge.
- Likely purchasing decision-maker
Not yet researched.Unresearched
- Time to activation
Not yet researched.Unresearched
- Primary adoption wedge
A no-card 14-day trial, supported by a no-signup interactive product tour and free trade calculators as earlier-stage entry points.Company claimSource
- Initial commitment required
Not yet researched.Unresearched
- How they get in the door
Not yet researched.Unresearched
Low-software-maturity fit
UnknownUnresearchedCould a contractor who works locally, runs the business from a phone, may have no website, barely uses email, and may have no FSM at all realistically adopt this?
Not yet researched.Unresearched
DMoney flow
Lead → estimate → proposal → accepted → financed → paid
- Narrative / stages owned
Not yet researched.Unresearched
- Value event
Not yet researched.Unresearched
- Revenue event
Not yet researched.Unresearched
- Aligned?
Not yet researched.Unresearched
- Money through platform?
Not yet researched.Unresearched
- Who pays whom
Not yet researched.Unresearched
EAutomation & AI
Not yet researched.
FTrust & control
- Previews
Not yet researched.Unresearched
- Approvals
Not yet researched.Unresearched
- Human takeover
Not yet researched.Unresearched
- Explanations
Not yet researched.Unresearched
- Confidence
Not yet researched.Unresearched
- Error handling
Not yet researched.Unresearched
- Overrides
Not yet researched.Unresearched
- Editable recommendations
Not yet researched.Unresearched
- Audit / history
Not yet researched.Unresearched
- Exception handling
Not yet researched.Unresearched
GEcosystem & handoff
- FSM / CRM integrations
Not yet researched.Unresearched
- Payment providers
Not yet researched.Unresearched
- Financing
Not yet researched.Unresearched
- Marketing / lead sources
Not yet researched.Unresearched
- APIs
Not yet researched.Unresearched
- Accounting
Not yet researched.Unresearched
- OEM / product data
Not yet researched.Unresearched
- Suppliers
Not yet researched.Unresearched
Integrations
Not yet researched.
PRODUCT STOPS HERE →
Not yet researched.Unresearched
Treehouse system boundary
UnresearchedNot yet researched.Unresearched
Not yet established — the boundary should be derived from evidence, not assumed.
HBusiness model
- Who pays?
Not yet researched.Unresearched
- Pricing model
Tiered subscription with an annual/monthly toggle, plus a substantial paid add-on marketplace layered on top.Company claimSource
- Entry price
Two different price ladders. Advertised (Individual): Basic $59/mo annually ($79 monthly), Essentials $149 ($189), Max $299 ($329). Actual (Teams, shown after declaring 6-10 users): Essentials $299/mo including 5 users at +$100/mo each beyond that, Max $649/mo including 8 users at +$75/mo each. The headline figures are the solo-operator prices; the research persona's real entry price is roughly 4x that.ObservedSource
- Free tier / trial
14-day free trial, no credit card. No permanently free tier observed.Company claimSource
- Pricing unit
Per-company tier with a bundled seat allowance, then per-additional-user pricing that gets cheaper at the higher tier ($100/user on Essentials vs $75/user on Max).ObservedSource
- Subscription economics
Not yet researched.Unresearched
- Usage revenue
A paid add-on marketplace spanning CSR AI, a sales proposal tool, pipeline, payroll, accounting, business coaching, voice, campaigns, GPS/dashcams, tap-to-pay and websites. Only the sales proposal tool carries a public price ($40/mo value, bundled into Max).Company claimSource
- Payments revenue
Card processing "as low as 2.59%", with a 1% fee on bank payments — payments are monetized alongside the subscription, not instead of it.Company claimSource
- Financing revenue
Access to business and consumer financing is stated as included in every plan. Whether HCP earns on it is not yet established.Company claimSource
- Commerce revenue
Not yet researched.Unresearched
- Outcome-based economics
Not yet researched.Unresearched
- Partner / subsidy economics
Not yet researched.Unresearched
- Expansion strategy
Not yet researched.Unresearched
- Likely moat
Not yet researched.Unresearched
Business-model takeaway for Treehouse: Open question
Not yet researched.Unresearched
ITreehouse synthesis
Borrow
Not yet researched.Unresearched
Avoid
Not yet researched.Unresearched
White space
Not yet researched.Unresearched
If Treehouse borrowed only one strategic idea from Housecall Pro, it would be TBDbecause Not yet researched.