The trap: AI-last
Most of us adopted AI the way we adopted every other app. It's a destination. It sits in a tab, and we visit it when a task looks AI-shaped ... draft this, summarize that, brainstorm the other thing.
Then Tuesday at 9:37 AM shows up and we run the day the old way. Log into the CRM to check a number. Dig through last week's notes for a follow-up. Google the error message. Grind through the export by hand, one screen at a time.
The AI never gets asked, because asking isn't the reflex yet. That's AI-last: paying for a superpower and using it like a stapler.
The ten-second question
The shift is one habit, and it's brutally simple. Before you search, before you log in, before you book the meeting, before you decide something is too hard ... ask your AI first.
Ask even when you assume it can't help. Especially then. Every "surely it can't do that" you never test is leverage left on the table. The people getting the most out of AI aren't smarter prompters. They just ask first, every time, and let the tool prove what it can and can't do.
Would you hire a brilliant chief of staff and then keep running your own reports? That's what AI-last looks like from the outside.
The three levels of asking first
- 1Ask before you searchThe question you'd normally Google, the four articles you'd skim, the "how do I even start this" moment. Ask AI first and make it do the reading. Everyone starts here ... and most people stop here.
- 2Ask before you log inOnce AI is connected to your email, calendar, and CRM, you never run a report again. You just ask, and your chief of staff goes and gets it.
- 3Ask before you attemptThe scary project you've been circling for weeks. Don't research it and dread it. Ask for the plan, with a safety checkpoint at every step.
Level two: the unlock most business owners haven't felt yet
Once your AI is connected to your real systems, a whole category of work disappears. "How many people are registered for the upcoming webinar?" Ten seconds. No login, no dashboard, no export.
Getting connected is the mountain, and yes, it's a pain in the ass. Every system has its own keys and its own quirks, and the temptation is to put it off. Climb it anyway. The connection is a one-time cost. The asking is forever. And even the connecting itself is a level-one problem ... you don't have to figure out how, you just have to ask:
The connect prompt
Connect to my [SYSTEM] MCP. Figure out how, ask me to authenticate when you need me, and when you're in, show me three questions I could now ask you that I used to log in for.
Most major platforms already publish an MCP ... a standard connector your AI knows how to use. You supply the yes; it does the plumbing.
Level three: ask before you attempt
The deepest level. The project with real downside if it goes wrong ... moving your setup to a new machine, untangling a system, anything you've been deferring. The old reflex is to research it, dread it, and defer it again. Ask first. Not to do it blind ... to plan it:
The plan-first prompt
I want to [THE SCARY PROJECT]. Here's why: [REASON]. Give me a migration plan, then execute it step by step yourself where you can. Do not move to the next step until you've confirmed the last one is safe.
That last sentence is the seatbelt. You get the plan, you get the execution, and you get a checkpoint at every rung so nothing irreversible happens without a confirmation.
And here's the same move pointed at a disaster you haven't had yet. Your AI employees are folders and files on a computer you own. Computers die. Ask first, before it happens:
The resurrection prompt
Write me a resurrection prompt. If this machine dies tomorrow, that prompt should tell a fresh AI where my files are backed up, what to install, and how to recreate my whole setup step by step. Then email it to me so it lives somewhere outside this machine.
One question, and the thing you'd lose sleep over becomes an email in your inbox.
Asking first isn't accepting first
One guardrail. Ask AI first doesn't mean believe AI first. The reflex is about where you start, not where you stop. You still check the number against the source once in a while. You still read the plan before you approve step one. First draft, first answer, first plan ... then your judgment.
That's a whole shift of its own, and it gets its own week. For now: ask first, verify before you act.
What the reflex buys you
Each level compounds. Level one saves you minutes. Level two deletes entire categories of logging-in-and-looking-things-up from your week. Level three turns the projects you've been avoiding into an afternoon of supervised execution.
And something else happens along the way. Every time you ask first, you learn a little more about what your AI can actually do, and it learns a little more about your business. The reflex is the training program ... for both of you.
Your homework
Log every default moment this week. Each time you catch yourself about to Google something, log into a system, or start a task by hand, stop and ask your AI first. Keep a running list of the hits and the misses, and bring the misses back to the room ... the misses are where the next unlock is hiding.
