Building It
Plain-language updates on what’s being architected, and why.
The design decisions behind the product, explained without the jargon, plus beta-test updates and feedback once the program is running.
We’re building ZoneLex in the open. This is where we’ll document what we’re building, what we’re hearing from the land-use professionals we’re talking to, and what’s changing as a result. We’ll also track the zoning and housing-policy news that’s shaping why this needs to exist in the first place: new state laws, court rulings, and reform efforts, as they happen.
Building It
The design decisions behind the product, explained without the jargon, plus beta-test updates and feedback once the program is running.
What We’re Hearing
Real insights and feedback from the people testing the tool.
Latest entries
The first post in our Follow the Journey series: an open diary of building ZoneLex, from the messy middle to launch day.
Every zoning question sounds simple until you try to answer it.
“What can I legally build on this land?”
That question sits at the center of every development project in America. Answering it means untangling a mosaic of more than 35,000 independent local governments, each with its own codes, its own vocabulary, and its own habit of changing the rules overnight. A zoning designation that means single-family residential in one city can mean rural agriculture in the next. Council amendments pass on a Tuesday night and quietly invalidate research finished on Monday.
We watched land-use attorneys and their teams fight this chaos with PDFs in folder structures, email chains, and countless hours of manual cross-checking. We saw a problem, and we’re building the fix.
That’s what this series is about. We’re going to be loud about the process: what we’re hearing, what we’re getting wrong, what we’re changing because of it. No polished launch theater. Just the journey.
So: where are we right now?
Here’s a thing we believe strongly: the worst way to build a tool for land-use legal teams is to build it in a vacuum and hope they like it.
So before anything else, we’re recruiting a small group of beta testers who live this work every day. And we’re being deliberate about who they are, because the people closest to the pain give the most honest feedback:
We’re not looking for people who will tell us we’re brilliant. We’re looking for people who will tell us where we’re wrong: which assumptions don’t survive contact with a real Tuesday afternoon, which workflow we misunderstood, which button belongs somewhere else entirely. That feedback is the whole point of a beta. The teams who give it to us will be shaping this platform in its most formative stage, and it will carry their fingerprints permanently.
Great tools for specialized professions don’t come from software people guessing. They come from listening. So alongside beta recruitment, we’ve been building an advisory bench of land-use attorneys, environmental counsel, digital forensics experts, and legal technology veterans. These are people who’ve spent careers in this world and can tell us, bluntly, when we’re solving the wrong problem.
We’ve also been doing homework that doesn’t look like software development at all: watching hours of recorded city council hearings, studying how developers petition for variances, and interviewing practitioners about what actually slows a project down. (Spoiler: it’s rarely the law itself. It’s the process of finding out what the law currently says.)
Legal work demands trust, and trust starts with security. Long before launch, we’re doing the unglamorous work: pursuing SOC 2 certification, designing for encryption in transit and at rest, two-factor authentication, and a firm commitment that your data is your data. Private to your workspace, never used to train our models, and deleted if you ever choose to leave.
We’re already sitting down with law firm IT and security teams to hear their concerns firsthand, because their sign-off matters as much as any attorney’s enthusiasm.
Worth saying plainly, early, and often: we are not building a replacement for attorneys, and we are not building another AI chatbot with a legal paint job.
Interpreting the law, forming the opinion, finding the leverage that gets a project across the finish line: that’s the attorney’s art, and it stays that way. Our job is the heavy lifting underneath it. We aggregate the fragmented data, surface the facts, flag the conflicts, and keep every finding tied to a verifiable public record so the humans can do what only humans can do.
Over the coming months, this series will follow the beta as it unfolds: the wins, the stumbles, and the moments a tester tells us something that changes our roadmap. If you’ve ever wondered what it actually looks like to build legal technology with the people who’ll use it instead of at them, this is your window.
And if you’re a land-use paralegal, associate, or attorney who’s tired of the folder-full-of-PDFs life and wants a hand in shaping what comes next, we’d love to talk. The honest critics get the best seats.
Know the Land. Know the Law.
The ZoneLex Team