The Stamped-Opinion Problem on Your Architecture Firm’s Website

A prospective client messages your firm’s site: "we want to take out the wall between the kitchen and living room, is it load-bearing, and would an open plan like the one in your gallery meet code for our house?" The website assistant, built to be helpful, says the wall is probably not load-bearing and that the open plan should meet code. No one looked at the structure. No one pulled the local code. And the firm just issued two professional opinions that licensure reserves for a licensed architect or engineer who has examined the actual project.

Design and engineering look like consultative services where a helpful answer is welcome, and that is the trap. The opinions clients want, what is structural, what meets code, what is feasible, are precisely the professional judgments that licensing laws exist to protect, because people build and live based on them. A general-purpose chatbot does not know it is rendering a professional opinion. It just renders one.

Structural and Code Calls Are the Practice of Architecture and Engineering

Determining whether a wall is load-bearing, whether a design satisfies the building code, or whether a structure is sound is the practice of architecture or engineering, and state licensing laws reserve that work for licensed professionals. The seal on a drawing exists for this reason: it marks an opinion a qualified, accountable person stands behind. When a chatbot tells a homeowner a wall is "probably fine to remove" or that a plan "meets code," it is performing licensed work without a license and without ever seeing the building, on a client who may act on it with a sledgehammer.

The harm is not theoretical. A wrong call about a load-bearing wall or a code requirement can lead to a dangerous renovation, a failed inspection, or a structure that has to be torn out, and the firm’s website is on record as the source.

Feasibility and "It’ll Pass" Are Opinions Too

Clients also ask the softer-sounding questions: will this addition be allowed, can we build to the lot line, will the city approve this. Those answers depend on zoning, local code, and site specifics that a website cannot evaluate. A bot that says "that should be approvable" is making a feasibility judgment the client will rely on to spend money, and the gap between the bot’s optimism and the jurisdiction’s actual rules is the firm’s problem.

A Quoted Fee or Scope Is a Commitment

Then there is the business side. "A project like that runs about this much" and "we can have drawings to you in three weeks" read as commitments, and a client who plans around them has relied on terms the firm never set. A promise the firm cannot keep also invites scrutiny under the FTC’s authority over unfair and deceptive practices. Fees, timelines, and scope belong in a proposal a person prepares, not in a chat window optimizing for a fast reply.

"Will Not" Is a Suggestion. "Cannot" Is an Architecture.

Here is what trips firms up. A client who wants an answer does not ask once and accept "let’s set up a consultation." They press. "Just give me your read, is the wall structural and will this pass?" A chatbot steered only by a prompt eventually answers the version of the question it was not specifically warned about, because being helpful is its default and a prompt is only a polite request to suppress that default.

That is the gap between a tool that is told not to give professional opinions and one that is built so it cannot. A disclaimer bolted onto a system whose whole job is to give confident answers does not change what it does when a motivated client leans on it. It just puts the structural call, the code opinion, and the fee in writing.

Who Owns the Answer

Strip away the software and the exposure is familiar. An unlicensed employee who told a client a wall was safe to remove and that a design met code would be a serious liability, and a dangerous one. When an unsupervised chatbot does the same thing on the website, the risk does not disappear. It lands on the firm, now with a written record, no licensed professional in the loop, and practice acts that reserve exactly these judgments for someone who has examined the project and can stand behind it.

The firms that get burned are not the ones that modernized their websites. They are the ones that dropped in a generic chatbot, assumed helpful and responsible were the same thing, and found out otherwise when a client renovated on the strength of a transcript. The fix is not to take AI off the site. It is to run an assistant that explains the firm’s services, captures the project, and leaves structural calls, code opinions, and fees to a licensed professional.

Frequently asked questions