The model is simple enough to explain in one breath. A homeowner needs a retaining wall, so he searches "retaining wall contractor near me," and up comes a company with a local-sounding name, a local number, a nearby address and a reassuring stack of five-star reviews. He calls. What he may not realize is that he isn't necessarily calling a retaining-wall contractor, he may just be calling whoever owns that phone number. That distinction matters more than it sounds like it sh

Walk into any public hearing on a data center these days and you'll notice something before the staff report even finishes: half the room has already made up its mind. Nobody's talking about the site. They're talking about how they feel about it.

So the real question was never should development occur. It's how should development occur. That distinction is the whole ballgame, and it's the foundation of everything that follows.

It's not enough to create value — people have to understand you created it, and honestly, our profession is bad at this. We describe activities: we prepared a master plan, we designed a stormwater-sensitive site. Clients don't buy activities. They buy outcomes.

Clients don't buy master plans, planting plans, or grading plans. They buy outcomes. The developer isn't excited about a set of drawings — he wants to know if the site will get approved, if it'll be marketable, if the infrastructure costs stay in check. The homeowner isn't buying a planting plan — she wants shade over the patio, privacy from the neighbor, and a yard that doesn't turn into a retention pond every August. The drawing is the delivery mechanism. It was never the v