About
We built this because we kept watching good plans stop shaping decisions.
Lattice came out of a planning practice, not a software company.
It started with a pattern we couldn't stop seeing
Our founder, Juan Mullerat, has spent twenty-five years leading long-range plans through PlusUrbia Design — among them Little Havana and Wynwood in Miami. That work follows a familiar shape. A city commissions a plan. Residents come to meetings after work. They sit through workshops and hearings and talk about housing, safer streets, parks, the things they want their neighborhood to become. Months of that becomes a document, and the commission adopts it. It is, at that moment, a legal commitment about the next twenty years.
Then, more often than not, very little changes. The budget moves on its own track. Capital projects get approved without anyone checking them against the plan. Staff turn over, administrations change, institutional memory thins out, and within a few years the document that carried all that public trust is guiding almost nothing. It stops being operational and becomes aspirational.
The cost of that isn't only wasted planning money. Every time an adopted vision quietly fails to happen, some trust goes with it — and fewer people turn up to the next meeting. That is the part that bothered us enough to do something about it.
It isn't a software shortage
The obvious assumption is that cities lack tools. They don't. A mid-sized city runs budgeting and ERP, GIS, permitting, asset management, performance dashboards, engagement platforms, financial reporting. Every one of them works well inside its own lane. Every one of them is organized around a function — track a project, manage a budget, map a pipe.
Almost none of them start from the plan. So the one document meant to connect every major decision is the only thing not wired into the systems that run the city. The failure isn't in any single tool. It's the gap between them.
The problem nobody had solved
There's a specific technical reason "just put the plan in a database" had never worked. Comprehensive plans get amended, and amendments renumber things. Policy 1.1.1 becomes 1.1.3. Every conventional system keys on that number — so when it changes, everything tracked against it breaks. Every dollar, every departmental assignment, every year of performance history gets orphaned in a single vote.
Solving that is the core of what we built. Each goal, policy, and action gets a permanent internal identity the moment it is imported, so renumbering moves the whole history with it. Re-imports don't overwrite: every field is classified by who owns it, adopted legal text stays locked, operational data staff added is carried forward, and genuine conflicts are shown side by side rather than silently resolved. And data flows one way — the plan informs operations, operations never rewrite the plan. When operations reveal that something in the plan ought to change, it surfaces as an amendment candidate for a person to take through the real legislative process.
Those three ideas exist separately elsewhere. Combining them to keep a municipal plan's operational record intact through amendment is the subject of a U.S. provisional patent application filed in July 2026.
What it became
Three connected products. Create authors a new plan in structured form from the start. Update takes an existing or legacy plan — a PDF, a Word file — and normalizes it into the same standard. Both seed Monitor, which runs the plan live against budget, capital program, departments, and outcomes.
That shape also settles where consultants fit. A firm authors or refreshes the plan, seeds the Monitor, and hands the city something it can run — then returns for the update and amendment cycles. The consultant's role stops ending at adoption, which is the same problem from the other side.
Why a nonprofit sits alongside it
The communities with the least capacity to keep a plan alive are usually the ones that can least afford software. So the Center for Comprehensive Planning, our nonprofit arm, carries the same tools at no cost to under-resourced cities and publishes the research, training, and case studies that come out of the pilots. This is, at bottom, a good-government project.
Where we are
Civic Lattice, Inc. was incorporated in 2026 and is based in Miami. Lattice is built and running. We are bringing on our first municipal partners in South Florida — the region where this started, and where our founder has led plans for the last two decades.
A comprehensive plan should not sit on a shelf. It should be the system a city runs on.