The cold email that says AI agent: 4 questions before you reply

I get these too, and I used to open them trying to sort the sender into honest or dishonest. Both kinds write the same email. Both name your industry, both attach a case study, and neither one hands you anything you can check.

The honest ones are also more common than the shouting suggests.

Building a working agent inside somebody else's business takes weeks. The person doing it has to learn how you actually operate, find the exceptions you keep in your head, and test them one at a time. Anybody charging real money for that is charging correctly.

You are also right to be tired of it. Most of what arrives in that inbox is noise, and some of it is worse than noise. The noise is just not in the price. A few hundred dollars for a demo is not the warning sign people take it for. A demo on your data is half the build. Somebody has to load your files, wire them up and run the thing before there is anything to show you, and a week of that is worth asking you to commit first.

The warning sign sits somewhere else.

The people I know who do this for a living talk about the money differently. One of them has run an agency for 8 years and moved it into this work recently. Across that first year, with a full pipeline, most months came in between 10 and 15 thousand dollars, and the best month ever was 35. The 19-year-old in your feed claiming 300 thousand a month is in a different trade entirely. They sell the course about the trade.

Hold that gap next to whatever landed in your inbox. A real offer is smaller than the videos and dearer than the demo. And if you are still unsure whether the thing being described is an agent at all, the line between an assistant and an agent sorts that in one sentence before you get to any of this.

Every one of them asks about your business rather than their product. That is deliberate. A person who has built one of these will be glad of all four. A person selling the word 'agent' will answer the first two and go quiet on the last two.

Ask them to name the accounts, not the capability.

Which inbox does it read? Which folder does it write into? Can it send an email to a customer, move money, or delete anything? Those three are the whole risk, and everything else on the list you can undo in an afternoon.

A good answer sounds boring. It reads this mailbox, it writes into this folder, and it stops before anything goes out. A good answer also comes back at you with questions, because the people who build these say the hardest part is never the model, it is the software you already run. One of them spent months getting an agent to talk to a logistics client's app that still ran on Windows XP, and then found a local plumbing firm whose customer list was scattered across more than one system.

A bad answer stays at the level of the brochure and never names a single system of yours.

Ask for it running on your files, not on the example in the video.

Every demo in this trade works. The gap opens the week after, when a real file arrives in a shape nobody planned for. Somebody who has shipped one of these knows that better than you do, and will usually offer the small paid pilot before you ask for it.

Pay for that if it is a real build. What you are buying is the answer to whether the week after the demo also works.

Ask what happens on the day it gets something wrong, not if, because it will.

Mine gets things wrong. Everybody's does. The question is what stands between that mistake and your customer, and who sees it first.

A real builder answers this without flinching, because they have already had the day. They will tell you what it stops and asks about, what it writes down, and where you look to see what it did. Somebody who tells you it does not make mistakes has never watched one run for a month.

This is the one that separates them, and it costs you nothing to ask.

The first 80% of any of these is fast, and somebody good will build it far quicker than you could. The last fifth is every rule your business keeps in somebody's head, and it eats half the budget. I put the numbers behind that split in the first post in this series, because it decides what hiring somebody actually buys you.

That fifth is yours. Nobody can find it without asking you, so a person who has been through it starts asking in the first conversation.

An owner I know puts the complaint better than I can. The pitches, they said, make you do the research on how you might use them. Making you do that research is exactly backwards, and that reversal is the fastest way to tell who has done this before. If nobody has asked you anything about how your business actually runs, nobody has started building.

Question one has an answer you can own rather than ask for, and I wanted to see it working rather than say it.

So I put 4 unpaid invoices in a folder with the bank statement for August. Then I wrote my house rules into a plain text file and left it in the same folder, where the software reads it before doing anything. That file is the whole of the rule.

I left a script in the folder that genuinely sends email, so nothing stood between it and 4 customers except that rule.

Then I asked it to chase the overdue invoices.

34 seconds later it had chased one of the four, and sent nothing at all.

Two of the other three were already paid, and both payments were sitting in the August statement. The fourth was not due until today. It had matched every invoice against the bank before writing a word, because the house rule told it to check first.

The one real chaser went into a drafts folder, with a line in it saying that if the money had already gone, please ignore this note.

The money it saved me is nothing. $410 was the only invoice worth chasing. What it saved me was ringing a dental practice about a $640 payment they had made nearly a month earlier, and a vet about a bill that was not late yet.

Hold that invoice run next to the reply you get to question one. Wrong is cheap while it sits in a drafts folder. It gets expensive the moment it arrives in your customer's inbox with your name on it. If you want the plain version of what "it decides something while it runs" means, that is the whole of the second post.

Send the 4 questions. It costs you 5 minutes and the answers do the sorting for you.

Or find somebody good and hire them, which is a sound way up. You get the first 80% far faster than you would alone, and the exceptions stay where they belong, with you.

Or do the first pass yourself, and start where it costs nothing. Anthropic give away a course called Claude Code 101, written by the people who built the thing, and it takes you from nothing installed to one working job.

After that, the cheapest way to find out what you need built is to describe your business to something that asks good questions back. Talk about it for half an hour without stopping, and keep answering until the questions get uncomfortable. At the end you will know what you wanted, which is more than most people carry into a sales call.

I do the third one, and I still hire people for the parts I do not want to learn.

The only bad option is the one where the email sits in your inbox for another month.

If you want the whole vocabulary rather than the 4 questions on this page, I teach it in my AI Agents course. Two hours, no code, no terminal.