You got a quote from an AI automation agency. How do you know it’s not a mistake?

What is a quote actually telling you?

Most of a quote is prose. The part that matters is the part a vendor would be embarrassed to break, and on many quotes that part is a single number with no commitment attached to it.

A useful way to read one: cross out everything the vendor could walk away from without anyone calling it a broken promise. Capability lists, technology names, partner badges, “we’ll work closely with your team.” What survives is the actual offer. If what survives is a price with the word “estimated” in front of it and a timeline with the word “approximately,” you are looking at a starting position, not a quote.

That is not automatically dishonest. It is, though, the structure under most of the horror stories.

What do buyers who’ve been through it say went wrong?

On r/ITManagers, a buyer with quotes already in hand asked other IT managers a question worth quoting exactly: did you actually see a ROI in terms of man-hours saved, or did it just create more technical debt?

The replies described a project that took 14 months instead of the 8 that were quoted, and another that was, in the reply’s words, ultra expensive and impossible to maintain.

Those are three distinct failure modes, and they map onto three things a quote either addresses or doesn’t:

1. Overrun. The timeline moved and the cost moved with it, because nothing in the agreement made the vendor carry that.
2. Unmaintainable handover. The system worked on delivery day and became a liability afterwards, because nobody defined what “handed over” meant.
3. Unmeasured ROI. Nobody wrote down what success was, so a year later there is no way to say whether it worked. The buyer suspects it didn’t.

None of those is a technology problem. All three are contract shape problems, and all three are visible in the quote if you know to look.

The four questions that separate a quote from an estimate

1. Is the price fixed for a defined scope?

Ask directly: if this takes twice as long as you think, what do I pay? A fixed price for a written scope has one answer. An hourly rate has a different one, and it is the buyer’s answer.

Watch for the middle case, which is the most common: a fixed-looking number with a scope so loosely defined that any surprise is a change order. The number is fixed; what it buys isn’t.

2. Is there a success metric, in writing, before work starts?

Not “improved efficiency.” A number someone could check. Support tickets down 50%. Lead response under five minutes. Twenty hours a week returned.

The test isn’t whether the vendor is confident. It’s whether they’ll write it down before they’ve been paid.

3. Who pays when it runs long?

There are only three possible answers: you do, they do, or you split it. Get the answer before you sign, because after you sign it is always you.

4. What do you own at handover, and who runs it on day 31?

The running system, the credentials, the documentation, and enough of a walkthrough that a different engineer could take it over. Ask where the automation lives. If it only runs inside the vendor’s account, you’ve bought a subscription to them, not an asset.

How rare is a written guarantee?

Rarer than the category’s marketing suggests, and this is where a quote can be compared against something real.

We keep teardowns on 17 named done-for-you AI automation agencies. None of them publishes an outcome guarantee. Several publish something adjacent that isn’t one: a self-reported 90% satisfaction rate, a line about not walking away until it’s successful, a commitment to real-world robustness. Those are sentiments. None of them tells you what happens if the metric is missed.

Two honest qualifications on that claim, because an unqualified version of it would be wrong:

• Verified as of 2026-07-06, against 17 named competitors (Team 400 verified 2026-07-08). Competitors change their pages. If you’re reading this much later, check.
• Outside that tracked set, we have found an agency (AIDOLS) that does publish a refund guarantee. It applies to a build tier priced at $75K–$150K. So the claim we’ll actually defend is narrower than “nobody offers a guarantee”: a written outcome guarantee at the $10K–$20K level is the rare thing. At six figures, it exists.

If you want a single question that separates vendors quickly, it’s this one: what happens if you miss the number? A vendor who has thought about it answers in one sentence.

How rare is a fixed published price?

Also rare, and worth checking on the vendor who quoted you.

Across the same 17 teardowns, exactly one publishes a fixed price for a defined scope: Team 400, with packages from $25K and custom builds published at $50K–$250K. One more, Gearheart, publishes hourly rates ($40–$60/hr depending on role) against open-ended time and materials. For most of the rest, the only figure available anywhere is a directory estimate on a site like Clutch, which is the directory’s guess and not the vendor’s commitment.

This matters for reading your own quote, because it tells you what the number in front of you probably is. An hourly rate and a “$25K minimum” are not prices. They’re the shape of an engagement where the total is discovered later, by you.

What should you ask before you sign?

Ten questions. Any vendor worth hiring can answer all of them in a single call.

1. Is this price fixed for the scope as written, or an estimate?
2. What specifically is out of scope?
3. What’s the success metric, and will you put it in writing before starting?
4. What happens if it isn’t hit?
5. If it runs long, who pays?
6. Who exactly does the work, and are they the person on this call?
7. What does the agent have access to, and is that access scoped or admin-level?
8. Where does approval sit for actions that touch money or customers?
9. What’s logged, and can I see the log?
10. On day 31, who maintains this, and what do I own?

If the answers to 3, 4, 5 and 10 are all vague, the quote isn’t wrong on price. It’s a different product than the one you think you’re buying.

What does a good set of answers look like?

Ours, so you can hold us to the same list:

The Sprint is $10K–$20K, fixed, live in 2–5 weeks. Success metrics are agreed in writing before we start. If we don’t hit them within 30 days of deployment, we keep working at no extra cost until we do, or we refund 50%. Not 100%, and we’d rather say the real number than let a vague guarantee do the work. At handover you get the running system, full documentation, and Loom walkthroughs. Ongoing support is optional, from $1,000/mo, and it is not required for the build to keep working.

If you have a quote in hand from someone else and you want a second read on the scope, that is most of what the $1,500 Audit does. It maps your workflows, prices the real work, and gives you a build-ready blueprint you own, whether you build it with us or with the vendor who quoted you.