Most owners I talk to about this have had the same three months.

They paid for the good version of one of these tools, because everybody said to. They sat down in front of the empty box. They typed some version of what can you do for my business? It wrote them a LinkedIn post about teamwork and excellence. They closed the tab and went back to work.

Then they quietly filed the whole thing under things that are probably real for somebody else.

I want to tell you what went wrong there, because it wasn't the tool and it wasn't you. It was the first question.

The trap, and I fell in it too

We ask what AI can do for us before we have given it anything to work with.

Think about what that would look like with a person. Say you hire a guy with twenty years in the trade. Good hire. On his first morning you walk up to him with your arms folded and say: so, what can you do for me?

He'd stare at you. Not because he isn't good, but because he doesn't know what you sell, how you price it, which customers are worth chasing, what you refuse to bid on, or where anything is. He's capable and he's empty. He'll give you something generic, because generic is all he has.

That's the conversation almost everybody has with AI on day one. Then they judge the tool by it.

The people who get somewhere useful don't start by shopping for a model. They start by writing the business down well enough that a machine, or a new hire, or you at two in the morning, can act on it.

Knowledge first, then the tool.

An hour, one folder, three files

Here's the whole setup. It isn't clever and that's the point.

Make one folder. Put three plain files in it. Type them badly. Nobody is grading this.

File one is the company. Not the mission statement. The operating facts. What you actually sell and what you turn down. How you price, including the parts you'd never put in writing for a customer. Your terms. Your typical crew size and what a normal job costs. The words your customers use for things, which are usually not the words the industry uses. The standards you work to.

File two is you. How you write. What you sound like when you're being direct. What you refuse to sign off on. Which decisions never leave your desk.

File three is the rules. Safety, compliance, the client requirements you can't bend, the thing that got you burned in 2019 and now has a policy attached to it.

Then start the conversation with those files in front of it, every time.

An hour is the honest estimate, and the reason it takes an hour rather than a week is that you already know all of it. You're not researching anything. You're typing out things you explain to people constantly and have never once written down, which is why the new guy takes six months to get useful and why you can't take a real vacation.

Here's the difference, and it's not subtle. Cold, you ask for a follow-up on a bid and you get four paragraphs of I hope this email finds you well and we pride ourselves. With the files loaded, you get something that knows you don't discount, that the customer's shutdown window is in October, that you always name the lead time on cable, and that you sign off with your first name and nothing else. One of those you rewrite from scratch. The other one you read, fix a line, and send.

Same tool. Same day. The only variable is what it knew about you.

The catch

Wrong is worse than missing. If your files are thin, you get thin answers and you can see it. If your files are out of date, you get a confident, specific, well-organized answer built on something that stopped being true in March. That one you don't catch, and it's the subject of Wednesday's issue, because it cost me real money.

More is not better. There's a failure at the other end too. Bury it in forty documents where four would do and you'll spend the whole session watching it dig through paperwork instead of working. Enough context, well shaped, beats all of it.

You own the output. That's an actual policy at my company, written down and signed: whatever comes out of one of these tools has your name on it once you send it. You can't tell a customer the AI got it wrong. It's a good tool for helping you do your job. It can't do your job for you.

Carry this out

Stop asking what it can do. Spend one hour telling it what you do. Then ask again, and notice that you're talking to a different thing entirely.

And once those files exist, the fun starts. The same context that fixes a follow-up email is what lets it read a set of plans, price a job against what you charged the last five times, or catch that you're about to bid material you don't have. That's not a different tool. That's the same hour of typing, paying out.

Reply and tell me the one thing you'd have to explain to a sharp new hire on his first morning. Whatever you just thought of, that's file one, first paragraph.

Wednesday: the day one stale spreadsheet row cost me two thousand dollars, and made me more likely to win the job.

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

Reply

Avatar

or to participate