Where you are with AI
You took the fit check. You're somewhere in the middle - your project moves sometimes, stalls other times, and you're not sure 1:1 coaching is the move right now. That's exactly the right time to slow down and look honestly at where you are. This page won't pitch you. It gives you a frame.
Three signals to watch
1. The redo-it-alone test
Take your last real win with AI. Could you redo it tomorrow - same result - with the chat closed?
Yes → you're building autonomy, not just delegating output. Keep going.
No → you're delegating results. The moment the tool changes, you're back to square one. That's the gap coaching closes.
2. How much got produced
Look at the last month. How much of your project actually reached someone - got sent, published, used - versus stayed as drafts and ideas in the chat?
Things got used → AI is moving your project. Healthy.
Mostly drafts → your bottleneck isn't ideas, it's getting them finished and used. More prompting won't fix that - you redo the same work and lose the time others use to move ahead.
3. The verify test
When AI hands you something wrong - a bug, a bad number, a confident mistake - what do you do?
I check it → proof, a test, a source. You can trust what you put out. Strong.
I re-prompt and hope → you can't trust your own output. That's the first thing to fix - before you automate anything.
Three experiments - this week
If a signal landed, here's what to try before paying anyone (including me).
1. Finish one small thing, end to end
Pick one piece of your project. Take it all the way this week with AI - done, used, finished. Not perfect. Done. Notice where you got stuck: that's your real coaching topic.
2. The "redo without looking" rule
After AI helps you do something, close it and redo one step from memory. What you can't redo on your own is exactly what you haven't learned yet - and what you'd want a session on.
3. The 3-reprompt stop
Next time you catch yourself rewriting a prompt, count. If you hit 3, stop. The problem isn't the prompt - it's the spec. Write one line: what does "done" look like? Then ask once.
When to come back
Come back when things like these show up:
- A blocker you can't get past alone, no matter how you prompt.
- Output you keep putting out but can't verify - and it's starting to cost you.
- A workflow you've tried to automate three times and it doesn't work as you expected.
You do the work yourself first - that's how it sticks. The call is where we look at your real week with AI: what's working, what's clunky, what could go faster - and your next move. Bring what you're actually working on.