Built in public. Follow the build → Try the live intake →
Build log

Built in public, including the parts that went wrong.

Most software in this trade arrives finished, with a price and a testimonial from someone you can't call. This one is being assembled where you can watch it, and the mistakes stay in the log.

08

A lead stopped vanishing

17 September 2026

The intake priced jobs correctly and then kept no record of any of them anywhere a person could find. Somebody shown a price and promised a call back, on a record nobody wrote down, has been lied to — and it is the failure that looks identical to success from every angle except the one that matters.

A request now becomes a saved record the moment it is submitted — the answers, the photographs, and a summary an office can actually work from — held privately until the permanent database is in place. Nothing a customer sends depends on that database arriving.

Two things were found by reading a real stored lead rather than by reading the code. The customer's own note — two dogs in the back yard, gate code 4417, septic field on the left — was being thrown away on any job that flagged nothing, because it had been filed under what the software observed instead of what the person said. And a pruning job was telling people assumes the tree comes out over the structure on a crane, on a tree that is staying. Neither of those is something the automated checks can see; they only turn up by reading a real one.
07

The intake went live

17 September 2026

Five screens, photographs first, no account at any point. Every question is answered by comparing the tree to the house and to your own arms, because nobody standing in their driveway knows what diameter at breast height means and nobody should have to.

The power-line question is a hard stop rather than a field. Answer it wrong and there is no path from there to a price — the form ends and you get the utility and 911 on a fixed script. It is running here.

Four faults showed up only by opening it on a phone and using it. A customer could reach the end without ever answering the power-line question. Our logo was appearing on a tree company's own branded form, which is the kind of thing you can only catch by looking — searching the page for the word "TreePro" found nothing, because a logo is a picture. The form could show one company's name above a different company's answer. And answering the power-line question from two thirds of the way down the screen left you looking at the middle of the emergency instructions, below stay 35 feet back.
06

The site comes out of hiding

17 September 2026

The site had been hidden from search engines while it was being built. That came off, and search engines are now told directly when a page changes rather than waiting to find out. The argument for letting people find a half-built product is that the half that exists is honest, and the parts that aren't built yet say so on the page.

05

Three field diagrams, drawn rather than bought

17 September 2026

The seven structural defects, the one tree-length rule, and the tree care year. Stock photography of a tree says nothing, and this trade can tell at a glance.

Two mistakes only showed up by drawing them and looking. The tree-length arc swung from the base of the trunk instead of the top, which drew a meaningless hump instead of the one thing the diagram exists to show. And the seven defects came out numbered in the wrong order, because the labels had been placed by height up the tree rather than by the order you read them in.
04

Nothing could safely change the live site

17 September 2026

An internal check refused to sign the site off, and it was right to. Every page had been uploaded by hand, so there was no traceable path between the version we had and the version the public could see — and no reliable way to put it back if something went wrong.

That is fixed. Every change now goes through a single reviewed path that rebuilds the site and records exactly what changed, which is the only arrangement under which anything automatic should be allowed near a live site — ours or yours.

03

Every customer stays on the newest version

17 September 2026

There is a choice early on in something like this: build every customer their own separate copy, or run everybody on one system that improves for all of them at once. Separate copies are easier to start and much worse to live with.

They freeze each company at whatever the software could do on the day they signed up, and improving anything means going round and doing it by hand a hundred times. So: one system. A fix or a new capability reaches every tree company on it the day it ships, including the ones who signed up first and pay the least.

02

We described this wrong the first time

17 September 2026

The first plan had TreePro as an agency that happened to take tree companies as clients — people doing the work by hand, one customer at a time. That was the wrong shape, and it took a blunt correction to see it. It is a product instead: one system that many tree companies run on, with the arboriculture built into it rather than carried around in somebody's head.

01

Research, and a tool that had to be argued with

17 September 2026

The first search for "tree" came back full of computer science — binary search trees, spanning-tree protocol, not one word about an oak. The second was aimed properly and still came back thin, because a month of internet chatter about a trade this size is not much to go on.

What actually pointed at the gap was software review sites — tree companies describing, in detail, what the tools they pay for do to them. That is where the proposal problem came from: quotes that are sent and never arrive, and nobody finds out until the job is gone. It is why a proposal you can see was delivered is treated here as a feature rather than as something to take for granted.

Why publish this

Because the alternative is a page of stock photos and a fake quote.

Everyone selling to this trade arrives with a polished site and no evidence. Operators have learned to assume the polish is the product.

A log with the mistakes in it is checkable in a way a testimonial is not. If something here turns out to be wrong, it stays and gets a correction underneath rather than being quietly edited out.

When there are customers and real numbers, they will appear here with names attached and permission on file. Until then this page is what we have that is actually true.

Want to be in the log?

The first crews on this will be named here, if they want to be, and quoted accurately if they don't.