Every AEC tool is drawn for the building; landscape finishes the terrain, grade, paving and planting by hand — the hatch that prints skewed, the legend built swatch by swatch, the canopy you're eyeballing the night before a deadline. So these tools finish the parts they left out — built by someone who's hit them on the board, not just at the keyboard.
Every tool begins at a problem you actually hit — the hatch that prints skewed, the legend built by hand, the canopy coverage you're guessing at against the EFSG 35%. The real pain gets named first, from the board — not a vendor's guess at your job. Where these come from ↗
Then the fix is built to actually end the pain, not paper over it — landscape judgment written straight into the tool, like counting canopy by boolean union so overlapping crowns aren't double-counted. That became the Canopy Coverage tool; grade compliance is next. It's the kind of fix a generic dev shop can't guess at. From method to tool ↗
And it's safe to just try. Each tool runs on your own file and only ever touches what it made — nothing else in your model moves. It lives right inside the software you already work in, so there's no exporting, no extra app, and nothing new to learn.
The terrain hatch prints skewed, the legend is built by hand, the canopy target is a guess — the night before a deadline.
Renaming the 200th drawing by hand to match the issue convention — one typo from mislabeling the whole set.
Your generic PM tool can't tell 'blocked on your side' from 'waiting on the council' — so the board lies about why work is stuck.