AI Insights Professional & B2B
Fred: An Estimate Assistant That Won’t Quote a Price or Promise a Result
Talk to Fred
Ask Fred about Professional & B2B
This is the same Fred you would put on your own site. Ask about Professional & B2B, compliance, or how the guardrails work. Fred listens.
A homeowner messages your site at night: "what would it cost to redo my kitchen, and can you have it done by Thanksgiving?" A generic chatbot, eager to win the job, throws out a price and promises the date. It quoted a number on a job no one has seen, and it made a completion promise that becomes a term the homeowner can hold you to. When the real scope and timeline land, you are arguing about a price and a date a widget invented. The contractor wanted a tool to capture leads. It got one that bids jobs and makes warranties.
That is the exposure the threat and standard pieces in this series cover. This article is the answer: what a compliant AI assistant for contractors actually looks like, and why booking the estimate while leaving the bid to you is what keeps the business out of a dispute.
The Real Choice Is Governed or Ungoverned
Most contractors frame the question as whether to put AI on the site at all. Homeowners settled that already. They expect an instant answer on what you do, your service area, and how to get on the schedule, and the contractor who makes them wait loses the job to the one who answered. The decision that matters is whether the assistant is governed.
An ungoverned chatbot quotes a firm price sight-unseen, promises a completion date, and makes statements about results and materials that become the kind of express warranty UCC 2-313 recognizes, with misrepresentations falling under what the FTC polices. A governed assistant captures the same homeowner, books the estimate, and leaves the bid to you. Same speed, none of the dispute.
How Fred Holds the Line
Fred starts from the opposite default of a general-purpose chatbot. A generic bot answers anything unless told otherwise; Fred answers only what it is cleared to, and the boundary lives in the system rather than in a prompt it can drift away from.
In practice Fred reads from your own site content, books the estimate, and routes anything touching a price, a timeline, scope, or a guarantee to you. It does not quote a number on a job it cannot see, because a stated price and a promised date become terms you have to honor. It does not promise a result or vouch for materials in a way that creates an express warranty under UCC 2-313, and it does not misrepresent what you do. It gives the homeowner ballpark ranges only where you have published them, and routes the real bid to a person. Fred runs more than 50 industry guardrail packs, and the contractor pack is built around firm-pricing restraint, warranty and completion-promise boundaries, and clean handoff to the estimator.
The difference shows up under pressure. Ask a prompt-instructed bot "just give me a price" three different ways and it eventually answers the phrasing it was not warned about. Fred does not depend on recognizing the wording; it decides what is allowed out before the answer exists. "Will not" is a suggestion. "Cannot" is an architecture.
Fred vs. a Generic AI Chatbot
| Situation | Generic AI Chatbot | Fred |
|---|---|---|
| "What would this job cost?" | Quotes a firm price on a job it never saw | Books the estimate; shares only published ranges |
| "Can you finish by Thanksgiving?" | Promises a date that becomes a binding term | Routes the timeline to you; no invented promise |
| "Will this hold up for 20 years?" | Vouches for a result, creating an express warranty | Declines the guarantee; hands it to a person |
| Where the rules live | In a prompt the model can drift from | Built into the system; enforced before output |
| A pricing question, reworded | Eventually answers when phrasing changes | Held the same way regardless of wording |
| Who owns the quote and promise | Effectively the chatbot, and the business | Your bid and your team, every time |
The table is the whole argument in one screen. A generic tool is helpful right up to the moment helpful becomes a price you have to honor or a warranty you never meant to make. Fred is helpful everywhere that carries no risk and structurally silent everywhere that does.
What Your Business Actually Gets
Set the compliance framing aside and look at the business case. Fred answers the routine questions that decide whether a homeowner calls you or the next contractor, what you do, where you work, whether you are licensed and insured, how soon you can come look, and it answers instantly, around the clock, in the homeowner’s own words. It books the estimate with the project details attached, so you show up already knowing whether it is a full remodel or a leaky faucet.
There is a lead-quality angle too. A homeowner who told Fred the project, the rough budget, and the timeline arrives as a qualified estimate request, not a name on a form. You walk in prepared instead of cold, and you spend your windshield time on jobs worth bidding. The chatbot that quotes a price to "help" wins a conversation and loses the margin when reality sets the real number. Fred wins the appointment and lets you set the number.
So the question is not whether your competitors will run AI on their sites. They will. It is whether yours books the estimate and leaves the bid to you before a widget quotes a job it never saw.
Frequently asked questions
Can a compliant assistant give any pricing at all?
It can share the ballpark ranges you have already published and explain how your estimating works, but it does not quote a firm price on a specific job, because a number a homeowner relies on becomes a term you have to honor, and no tool can price a job it has not seen. A compliant assistant like Fred captures the project details and books the estimate so you set the real price. The homeowner gets an instant, honest response; the bid stays yours.
How does a chatbot's promise become a warranty?
When your tool promises a completion date or vouches that work will last or perform a certain way, those statements can function as an express warranty and a binding term, even though no one walked the job. A compliant assistant routes timeline, scope, and guarantee questions to you rather than making promises in your name, so you are never held to a date or a result a widget invented.
How is Fred different from putting rules in a generic chatbot's prompt?
A prompt is an instruction the model can drift away from when a homeowner pushes for a number a different way. Fred enforces its boundaries at the system level, deciding what is allowed before it responds, so a firm quote or a completion promise never gets generated regardless of wording. It is the difference between a bot that usually holds back and one that is built so it cannot bid your job for you.