There's a sketch on the back of a job folder in my truck right now. Anode locations, a rough tank outline, arrows, a number circled twice. It explains the job perfectly to me and to anybody who's done the work. I would never in my life put it in front of a customer.

So what usually happens is one of two things. Either the proposal goes out with no picture at all and the customer nods through a paragraph he doesn't follow, or somebody spends an hour fighting with shapes in Word to produce something that looks worse than the napkin.

There's a third option now, and it takes about four minutes.

Image tools crossed a line in the last couple of years. They stopped being toys for making dragons and started being able to do plain, useful, boring work — the kind that shows up in a proposal.

Two things changed that matter to us. First, you can hand one a photo of your own sketch, say "make this clean," and it will keep your layout and your labels and give back something presentable. Second, you can talk to it in normal English about what to change. Not menus, not layers. "Move the label to the left. Make the tank gray instead of blue. Drop the arrow on the right."

If you've ever tried to nudge a text box in Word and watched the whole page reflow, that second part is the one that'll get you.

Cleaning up your own sketch. Photograph the napkin. Upload it. "This is my hand sketch of a tank with anode placements. Redraw it clean and simple, keep all my labels exactly as written, plain lines, white background, no shading." You'll get something proposal-ready that still says what you drew.

Marking up a site photo. You've got forty photos from a walkthrough and one of them shows the actual problem. Upload it and say "circle the corroded flange in red and add an arrow with the label 'active pitting.'" Now the report points at the thing instead of describing where to look.

Turning words into a simple diagram. Paste in a process, six steps of a shutdown, or how a job moves from estimate to invoice, and ask for a clean flow chart, plain boxes and arrows, no decoration. Good enough to hang in the shop or drop in a training packet.

Fixing photos you already have. Dark shop photo, blown-out exterior, a faded print of a job from 1998 you'd like on the website. Brightening, sharpening, and color restoration all work from a plain request. It's the cheapest visual upgrade available to a company with a bad photo library, which is most of us.

One habit separates a usable image from twenty minutes of frustration: say what you don't want, in the same breath.

These tools default to decorated. Gradients, glow, 3D, stock-photo gloss. Every time. So put the boundary in the request:

And when it's close but not right, don't start over. Talk to it: "same drawing, move the label off the arrow, make the text bigger." Same three-versions logic from Monday applies here too — ask for a few variations at once and pick, rather than trying to nail it on the first pull.

This one has real teeth, so read it twice.

It will confidently draw something wrong. These tools do not understand your equipment. They understand what pictures of your equipment tend to look like. It will happily put six bolts on a flange that has eight, or invent a fitting that doesn't exist. Fine for a concept sketch. Dangerous the second anyone treats it as a specification. Look at every image the way you'd look at a green apprentice's first drawing, because that's exactly what it is.

It can't read. Text inside generated images comes out garbled or misspelled more often than not. Keep labels short, check every one, and put anything that has to be exact, dimensions, part numbers, spec references, in the document rather than in the picture.

Nothing that must be accurate. Concept sketches, training visuals, and cleaned-up field photos: yes. Anything a crew works from, a permit references, or an inspector reads: no. That still goes to someone with a stamp.

Don't retouch evidence. Brightening a dark photo so a customer can see the corrosion is helpful. Changing what's in a photo that's going into a report or a claim is a different thing entirely, and there's no version of it that ends well. Brighten it. Never change it.

Once you're comfortable, the pictures stop being one-offs. The same description that makes one diagram makes fifteen, so a training packet that was never going to get illustrated suddenly gets illustrated. Site photos come off the phone and go into the report with the callouts already on them. The website stops using the one decent photo from 2019.

And that's still the small version. The interesting part is when the diagram isn't something you asked for. It comes out of the job file on its own, because the context is already written down and the drawing is just another thing that falls out of it.

You don't need a design tool. Photograph the sketch, describe what you want, tell it plainly what not to add, and check the picture like it came from an apprentice.

Reply and tell me: what's the one thing you're always trying to explain to customers in words because you don't have a picture of it? That's your first one.

Monday: the part of your business AI can't help with until you write it down.

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