AEC firms don't suffer from a lack of tools. They suffer from a lack of integration. Every layer of a project — design, code compliance, cost, documentation, permitting — has specialized software. None of them talk to each other in a way that eliminates the manual data-transfer step between them.
AI was supposed to change this. In some ways it has. In the ways AEC firms actually need, the gap remains.
What Foundational AI Models Miss
General-purpose language models are powerful for research, drafting, and synthesis. They weren't designed to interpret multi-sheet plan sets, understand jurisdiction-specific code amendments, evaluate zoning envelopes against real parcel dimensions, or maintain persistent project memory across a months-long design process.
Using a general-purpose AI for AEC-specific work means providing all the context manually, every session. The model has no memory of the project. It doesn't know the parcel. It can't read the drawing.
InQI uses foundational AI models as a base layer, then adds AEC-specific intelligence: parcel data, zoning lookup, code interpretation, project memory through the Binder system, and domain-trained IQ Agents for specific tasks.
What Code Platforms Miss
Platforms like UpCodes solve searchability. You can find the relevant code section faster than searching a PDF. That's genuinely useful.
What code search doesn't provide: interpretation against a specific project. Knowing what the code says and knowing what it means for your specific parcel, construction type, occupancy classification, and design parameters are different things. Codes.IQ provides the latter.
IQ Agents handle the research. You handle the project.
Sign up for freeWhat Permitting Platforms Miss
Tools focused on permit submission — PermitFlow, Pulley, and similar — operate downstream, after drawings are already prepared. They help you submit a complete package. They don't help you figure out, before you start designing, whether the proposed project is compliant.
Checking compliance at design time rather than permitting time is where most of the value is. Redesigning after a failed plan check is expensive. Designing correctly from the start requires intelligence upstream.
What InQI Provides That the Pieces Don't
The chain from "address" to "construction-ready intelligence":
- Site intelligence — parcel boundaries, setbacks, zoning class, existing conditions, terrain, via the Site Plan generator
- Code compliance — what this address and project type allow, in plain language
- Cost intelligence — early-stage estimates from Estimate.IQ connected to the design, not to a generic template
- Documentation — client deliverables, compliance reports, and permit packages generated from project data
- Project memory — all of the above persists and is queryable through the Binder system in InQuest
Each piece connects to the others through the property record and the Binder. The result is that changing a design parameter propagates through cost, compliance, and documentation automatically — rather than requiring manual updates to four separate tools.
The Infrastructure Layer AEC Has Been Missing
Every industry that has successfully adopted AI at scale has needed a domain-specific intelligence layer on top of general-purpose models. For AEC, that layer requires: understanding of building geometry and code, persistent project memory, and connection to authoritative property and regulatory data.
That's what InQI is built to be.
