Skip to content

Built by an arborist,
for arborists.

Serg ISA Certified Arborist

I'm Serg, an ISA Certified Arborist. I built LogLog because I was doing the same survey twice — once on paper, once in a spreadsheet — and I got tired of it.

The routine was always the same: print the site plan, walk the property with a clipboard, mark tree locations by hand, photograph anything worth noting on a phone that had nothing to do with the paper plan, then get back to the office and re-key every measurement into a spreadsheet before the report could go out. Five separate steps, and the data got typed twice — once in the field, once at the desk.

The part that actually bothered me wasn't the typing. It was the risk. Field notes in the rain smear. A tree number scrawled next to the wrong pin on a hand-marked plan sends the wrong DBH into the wrong row of a report a client might use for a permit application or an insurance claim. That's not a productivity problem, that's a liability problem.

So I built the tool I actually wanted: load the client's own site plan PDF, tap directly on it to drop a numbered pin, fill in species and DBH and condition right there next to the tree, attach the photo to that exact record instead of a camera roll, and export a ZIP that has the annotated plan, the spreadsheet, and every photo already sorted by tree number. One pass, not two.

It started as my own field tool — I'm still the first user of every feature that ships. It's a solo build, not a funded startup with a support team, and I'd rather say that upfront than pretend otherwise. If something breaks or a term on this site doesn't match how your jurisdiction does it (BS5837 categories, TRAQ risk fields, whatever), email me directly — I read it.

Curious what's actually shipped versus what's still on the roadmap? The changelog has real dated entries, and the data & trust page spells out exactly where your data lives and what you keep if you ever leave.

Get early access