Estimates and Proposals

An estimate is built from the trees you already captured. You are not retyping the walk; you are pricing it.

Build one from an inventory

• Open the site you walked and choose New estimate.
• Every analysed tree is considered. Dead and hazardous trees come through as removal and stump grinding, deadwood and crown notes come through as pruning.
• Each line prices from your catalog. The AI proposes the scope. It never proposes the price.
• Trees the AI could not read are counted and shown to you rather than quietly left out.

Every line knows its trees

A line records which trees it covers. Open a line and you see them by species, and the count sits beside the description as you scan the estimate.

Pull a tree off a line and the line updates, because the list was never a copied note. This is also what the crew sees when they open the job in the field.

Pricing shapes

• Per line, from the catalog. Your services, your prices, your size bands.
• By quantity, when the work is not per tree.
• One flat day rate across everything, when that is how you sold it.
• Several properties on one proposal, priced per site or as one figure.

An unpriced line blocks sending. It never blocks drafting, so you can build the whole thing and fill the gaps after.

Send it

Send to client emails a link. The proposal opens in any browser with an interactive 3D map of the property inside it, so they can see the trees you are quoting on.

Your client accepts by typing their name. The version they accepted is stored exactly as it was at that moment, so a later edit cannot rewrite what they agreed to. Declines record a reason.

Replies to the estimate email reach your inbox, and you can resend with a fresh secure link at any time.

Deposits

An estimate can carry a deposit, stored as an amount rather than a percentage so it cannot drift when lines change.

What happens next

An accepted estimate becomes work waiting to be scheduled. See Scheduling and crews.