You ask AI to write a follow-up on a bid that's gone quiet. Ten seconds later you've got a paragraph. It's fine. Grammatically clean, professionally bland, says nothing anybody would remember. So you either send it, or you close the tab and file AI under "overhyped."

I did both, for months. Both were wrong, and for the same reason: I thought I was asking a question. I wasn't. I was pulling a lever.

It's drawing an answer, not looking one up

Here's the part nobody explains up front. When you ask AI something, it isn't pulling the answer off a shelf. It's generating one, word by word, out of an enormous range of possibilities. Ask the exact same question twice and you'll get two different replies. Both readable. Both plausible. Neither one is the answer, because there isn't one.

That makes it less like a calculator and more like a slot machine. Every request is one pull. Some pulls come back excellent. Most come back average, because average is the safe bet and the machine is built to play it safe.

So when your first result is mediocre, you haven't learned anything about the tool. You've learned about one pull.

Once that clicked for me, my hit rate went up without me getting any better at asking. I just stopped quitting after one.

The trap: treating it like a vending machine

Most of us show up with vending-machine expectations. Punch in the right code, get the right item. If the item's wrong, you assume you hit the wrong code, or the machine's broken.

That instinct is why so many owners try AI twice and quit. They got two average results and decided average was the ceiling. They never pulled a third time, and they never asked for options.

The people getting real work out of this aren't better writers. They're just more willing to throw attempts away. Which feels wasteful right until you notice each attempt costs about eleven seconds.

Do this instead: ask for three

One change fixes most of it. Stop asking for a thing. Ask for three of them, and spell out how they should differ.

Say a $40,000 tank recoat bid has been sitting quiet for three weeks. Instead of "write a follow-up email," try:

Write three versions of a follow-up on a bid that's been quiet three weeks. One short and direct, two sentences. One warmer, referencing that we walked the site together. One that leads with the schedule risk if they push past September. Same facts in all three. No fluff.

Now you're picking from three real options instead of guessing whether the one you got is as good as it gets. And you'll notice something the first time you do it: usually no single version wins outright. Version two has the right opening, version one has the right closing. So say that:

Take the opening from #2 and the last line from #1. Cut the middle paragraph.

That's the actual workflow. Generate wide, then assemble. Ninety seconds, and it beats anything you'd have squeezed out of one pull and a lot of squinting.

Three more moves worth having in your pocket:

Re-roll instead of repairing. If the draft is wrong at the bones, wrong angle entirely, don't fix it line by line. Say "start over, different approach." A fresh pull is faster than a rescue.

Make it grade its own work. "Read that back as the customer who's been ignoring me for three weeks. What lands wrong?" It will usually find something real. That's a second opinion for free.

Change one thing at a time. If a version is 80% right, don't rewrite the whole request. Name the single thing that's off: "same email, but drop the apology in the second line." Rewriting everything to fix one sentence is how people end up with ten drafts and no idea which one was closest.

The catch

Two limits, and they both matter.

More pulls is not a substitute for judgment. You're still the one deciding what goes out, and if you can't tell good from bad on the topic, ten options won't save you. You'll just pick a polished wrong one with more confidence. Pull the lever on work you can actually evaluate.

And re-rolling does not fix facts. If it got a spec, a date, or a dollar figure wrong, pulling again gets you a differently wrong number. Re-roll for tone, structure, and approach. Verify anything factual yourself, every time. That part never gets handed off.

Where this goes

Once three-versions is a habit, the same move works on much bigger things. Three takes on a scope of work. Three ways to organize a safety program. Five passes over the same job description to catch what you forgot to include. Ten rewrites of the one paragraph in your proposal that has never sounded right.

And eventually it stops being about writing at all. When twenty options cost you eleven seconds apiece, the bottleneck moves entirely onto your judgment, which happens to be the part of your business nobody can copy.

Carry this out

The first answer isn't an answer. It's a draft, and it cost you nothing. Ask for three, keep the best pieces, and pull again when it isn't there yet.

Reply and tell me: what's one thing you asked AI to write, got something mediocre, and never went back to? I'll show you the three-version version of it.

Wednesday: the fix for staring at a blank prompt box with no idea what to type.

New here? The fastest way to put all of this to work is the free Context Starter Pack — one folder, three files, one hour.

Reply

Avatar

or to participate