How I Work
Please do not apologize.
It happens anyway. Someone tells me they should already know this, that their grandkid set it up for them once, that they feel behind. I have heard it at kitchen tables, in back offices, and over video calls pointed at a laptop screen — and it is the least useful thing you could believe about yourself before we start.
So here is the whole arc, no mystery.
It starts with a free 30-minute call. No card, no pressure, no pitch deck. You tell me what you are actually trying to do, and I tell you honestly whether I can help. Sometimes the answer is that you do not need coaching at all — you need one setting changed, and I will just tell you which one.
Then we pick a tier together — Foundations or Builder. Most people start with a single session, which is the right amount of commitment for something you have never tried. You are not signing up for a program. You are booking an afternoon.
Your first real session is hands-on, on your own device. This part matters more than it sounds. Not my laptop, not a demo account, not a tidy example that works because someone tidied it — your files, your messy folder names, your actual inbox. That is where the useful stuff hides, and it is the only place the learning sticks. Within 24 hours you get a written recap, the prompts we built together, and a homework exercise.
Then you build, at your pace. Every session after the first runs the same shape — ten minutes checking in on the homework, forty to sixty building something new, ten wrapping up and setting the next exercise. Take one a week for a month if that suits you, or disappear for six weeks and come back with three good questions. Both work, and the second one is not the lesser option.
And then results, which arrive unevenly.
That last part deserves more than a bullet, because it is where most honest disagreement with the industry lives. Confidence comes faster than you would expect. Fluency comes slower than you would hope. In the first session you will do something you did not think you could do, and that feels like a breakthrough — it is real, and it is also the easy part. The slower thing is judgement: knowing when the tool is confidently wrong, knowing what to check, knowing which jobs are worth handing over at all. That is the part I actually teach.
My honest timing: comfort early, tested workflows over a couple of months, and within a season this is just part of your daily toolkit. That last clause carries a condition — if you use what we cover between sessions. Nobody has ever become fluent in anything an hour at a time.
One thing I will not do is hand you a workflow you cannot inspect. "Trust, but verify" is the mantra I keep coming back to, and it applies to me as much as to the tools. If you cannot see why something works, you cannot fix it when it breaks, and it will break — quietly, at the least convenient moment, in a way that looks like success.
That is the arc. It is not complicated, and it is not supposed to be.
The full walkthrough is here: How It Works →
If you would like a hand with your own tools, the easiest way to reach me is a text to 503-664-0546.
#ernestGoesToAI