A number scribbled on an invoice pad at the curb, no insurance cert attached, no ISA credentials shown — that's why you're losing arborist work, not your rate. Glewit ships your tree-removal proposal as one branded document in minutes, with credentials and scope built in. Free trial. Tree care catalog included.
The proposal that should take 30 minutes takes three days.
A tree-care proposal has too many variables. You're estimating DBH on six trees from a customer's blurry email photos. You're trying to communicate why crane-assisted removal of one over-the-house oak costs more than three medium climbing-access removals combined. You're typing up the boundary-tree consent language for the third time this week. By the time the proposal goes out, the customer has called two other arborists and the homeowner who just had a limb drop on the garage has already called back.
Proposal → Contract → Handover
Project data flows forward — enter it once, render it three ways. Every field on the proposal carries through to the contract and the handover packet.
Glewit ships a tree care catalog seeded with the line items, prices, and scope language you actually quote. Edit it in Settings — or skip the seed and author your own.
Tree Removal
Per-DBH removal tiers (small / medium / large / extra-large)
Crane-assisted add-on for constrained drop zones
Limited-access add-on for backyards, fence lines
ISA-certified climbing or bucket-truck access
Pruning & Maintenance
Deadwooding (small / medium / large trees)
Crown thinning, raising, reduction to ISA / ANSI A300
Cabling — static support systems for weak unions
Bracing — steel-rod installation for split-prone unions
Stump Grinding & Site Recovery
Per-size stump grinding (small / medium / large)
Deep-grind add-on for planting or hardscape clearance
Chip-on-site or haul-away debris disposition
Log retention cut to firewood length
Emergency & Storm Response
Hazard tree and hazard-limb removal
After-hours / weekend rate add-on
Storm-damaged tree assessment
Utility-line proximity coordination (ANSI Z133)
Stihl, Bandit, Vermeer — embedded automatically.
Glewit embeds the actual manufacturer spec sheets in your proposal. Customers see the Stihl chainsaw, Bandit chipper, and Vermeer stump grinder catalogs exactly as the manufacturers publish them, not screenshots pasted into Word. Update the catalog once; every future proposal pulls the current sheet.
Stihl
Bandit
Vermeer
Simple pricing
If Glewit helps you close one extra job this year, it pays for itself.Sending proposals same-day instead of three days later changes how often you win. A single extra closed project at $75K covers Glewit for three years. The math is yours to do.
Free
$0/month
Try the workflow. See if it fits.
Generate proposals, contracts, and handover docs
Full service catalog with toggle-off builder
Print / PDF export
Logo, brand colors, and catalog saved to your account
Up to 3 active projects (advance to complete to free a slot)
How does the contract handle boundary trees where my customer doesn't have unilateral authority to authorize the work?
Section 7 (site access, easement, and neighbor consent) of the tree-care-construction pack's contract template explicitly covers boundary-tree authority — Contractor proceeds only with documented authorization from all affected parties. Whether that's the customer's neighbor (most residential cases) or a town tree warden (street trees, certain protected species per local ordinance), the section sets out who provides the consent and when. The clause is plain text you can edit in Settings → Contract Template — adjust for your jurisdiction's specific boundary-tree statute.
Do new plantings carry a survival warranty, and what's the homeowner's role?
Yes. Section 9 (warranty and conditional coverage) ships a one-year conditional warranty for new plantings and transplants. The condition is the aftercare schedule we hand over at completion — deep-soak watering on a documented schedule, mulch-ring discipline, no string-trimmer damage to the trunk. The handover document's "Caring for Your Property After the Work" page documents what the homeowner needs to do; the warranty references that schedule by name. Edit either the warranty terms or the aftercare content in Settings → Contract Template / Handover Content.
How does the proposal handle a job that needs a crane but the customer initially expected climber-access pricing?
The starter catalog separates removal from access approach — `tree-removal-large` is one line; `crane-assisted-removal-addon` is a separate line item. A customer who expected climber-access sees the crane add-on as an explicit upgrade with its own cost and lead-time note (crane scheduling typically runs 1-3 weeks out). The proposal can include both access approaches as customization variants for the same tree, or stay scoped to one with the other available via change order per Section 4.
When we open a removal and find internal decay or hidden hazard conditions, how does that get priced?
Section 4 (change orders and concealed conditions) covers exactly this pattern. Hidden internal decay, root-collar excavation revealing structural deficits, or unexpected rigging requirements get a written cost estimate before additional work proceeds. The clause is the tree-care analog of electrical's open-wall-discovery and septic's hidden-ledge clauses — same change-order procedure, scoped to the tree-care discovery patterns.
What about line-clearance work near overhead utilities?
Section 6 (permits and utility coordination) covers utility coordination. Line-clearance work within 10 feet of energized conductors requires ANSI Z133 compliance and a qualified line-clearance arborist — many shops hold this cert in-house; others coordinate with the utility's own contractor. The pack ships the language flexible: shops doing line-clearance work edit Section 6 to reference their own credentialing; shops referring it out edit it to that effect.
We work in multiple Northeast states — does the contract handle different jurisdictions, or do we need separate packs?
Section 10 (license and insurance) ships with the legacy `[LicenseNumber]` template DSL — single-state default, appropriate for RI-only operators. For multi-state operators, the `licensesByJurisdiction` schema field shipped with the electrical-construction pack handles the multi-state map natively; tenants who need it author a Section 10 clause variant per ADR-009 without a pack-version bump. The pack is jurisdiction-flexible at the schema layer; the default just optimizes for the most common case.