tree.claims

What It Is

tree.claims is vertical claims software for storm-damage tree cleanup, emergency mitigation, and insurance-covered tree work. It is not a general-purpose CRM or field service system. Instead, it is designed around one specific question: how to turn a storm job into an insurance-ready claim package that an insurer can accept. Contracts, photo evidence, invoices, rate cards, and the narrative letter for the adjuster are all tied to the same claim record.

Core Features and Workflow

The product workflow has four steps: create a claim, collect evidence, send the contract, and generate an invoice that can be submitted to the adjuster. Crews can upload photos from a mobile browser using a PIN and short link, and homeowners can also add photos through a public link, with no app installation required. Contracts are generated from company templates and signed electronically via Documenso. Sent versions are locked and include a SHA-256 hash and version history. Invoices can be generated based on the company’s rate card, with explanatory text attached to line items, while Claude drafts the adjuster narrative letter to reduce the time spent rewriting letters and supplying additional materials.

Pricing and Business Model

Its pricing is straightforward: no seat fees, no per-user charges, and no monthly minimum. The Self Managed plan costs 1% of the invoice amount and is suited to tree service companies with internal operations staff who can run the workflow themselves. The page also mentions a Fully Managed option at 10%, but the captured content does not provide the full scope of that service. A revenue-share model is friendly to low-frequency or seasonal storm work, but high-volume customers with large invoices should evaluate the long-term total cost.

Pros and Cons

Its main strength is focus. Photos, contracts, invoices, and narrative materials are organized under the same claim ID, which helps avoid the common problem of evidence being scattered across group chats and photo albums. Version locking and e-signature audit trails can also help address adjuster questions about which version was signed. Because crews do not need to install an app, adoption in the field should be relatively easy. The limitations are also clear: the product is built for the U.S. insurance claims context, does not disclose APIs, advanced permissions, or compliance certifications such as SOC 2/ISO, and is not intended to replace a full CRM or dispatch system.

Who It’s For and Access from China

It is best suited to U.S. tree service companies, storm response teams, ISA/TCIA-related teams, and businesses that frequently handle insurance-covered tree removal. Access from China is unknown, and supported payment methods are not disclosed. If used from China, key issues to evaluate include network accessibility, USD payments, and differences between U.S. insurance documentation and local claims processes. Domestic alternatives could combine a ticketing system, e-signature service, enterprise cloud storage, and project management tools, but these typically lack a dedicated workflow for tree-related insurance claims.