The number one reason business owners don't reach out about automation isn't cost. It's uncertainty. They don't know what they're buying. They don't know what the process looks like. They don't know how long it takes, what they'll need to provide, or what they'll have at the end.

That's a fair concern. "AI consulting" sounds like it could mean anything from a chatbot on your website to a six-month digital transformation project with weekly steering committees.

So here's exactly what the process looks like when you work with me. No jargon. No mystery.

Step 1: The discovery conversation

This is a 60 to 90 minute session, either in person or on a video call. It's a conversation, not a sales pitch. I'm trying to understand three things: what your business does, where the pain is, and whether automation is the right solution.

I'll ask you to walk me through a typical week. Where do you and your staff spend time on tasks that feel repetitive or low-value? What information do you wish you had at your fingertips but don't? What breaks or slows down when you're away?

The most useful question I ask is: "If I could fix one thing in your operations, what would it be?" The answer to that is usually the starting point.

I'll also ask about your current tools. What software do you use daily? Accounting, project management, CRM, email. Not because I need a technology audit, but because those are the systems any automation will need to connect to.

By the end of the session, we'll both know whether there's a good fit. Sometimes there isn't, and I'll tell you that directly.

Step 2: The proposal

Within 48 hours, I'll send you a short document. Maximum three pages. It covers:

What I heard. A summary of the pain points we discussed, in your language, not mine. This is where you confirm I actually understood the problem.

What I recommend. A specific solution described in plain English. What it does, how it works, and what your team's experience will be. No architecture diagrams. No technical jargon. Just: "Your invoices will be processed automatically and the data will appear in your tracking spreadsheet."

What it costs. Estimated hours, total cost range, and a breakdown of my fees versus any third-party costs like AI processing or hosting. I bill hourly in 15-minute increments, so you only pay for work done. No padded fixed-price quotes.

What happens first. A quick-win starting point wherever possible. Something that delivers a result within the first week so you can see the value before committing to the larger scope.

I frame everything in terms of return. "A 10-hour investment to eliminate 5 hours of weekly manual work pays for itself in 2 weeks." If I can't make that case clearly, the project probably isn't worth doing.

Step 3: The build

Once you approve the scope, I'll need a few things from you: access credentials for the systems we're connecting, 30 minutes to confirm some workflow details, and availability for a quick check-in midway through.

Then I build. In my environment first, tested against real data before anything touches your systems. I don't experiment in production.

For a typical first project, the build takes one to three weeks depending on complexity. During that time, you'll get at least one progress update per week so there are no surprises at the end.

I don't disappear for a month and come back with a finished product. You'll see working pieces along the way and have the chance to say "that's not quite right" before I've built everything on top of it.

Step 4: Deployment and testing

The solution goes live in your environment. For an automation, that means it starts processing your real data. For an agent, that means it's running and accessible to your team.

For the first two to four weeks, I recommend a human review period. Every output gets checked before it's acted on. Not because the system is unreliable, but because building trust takes time. You need to see it handle your edge cases, your unusual suppliers, your awkward invoice formats, before you're comfortable letting it run without oversight.

During this period, I'm watching for anything unexpected and tuning as needed. Prompt adjustments, edge case handling, formatting tweaks based on your preferences. This refinement stage is where the system goes from "works" to "works for your business specifically."

Step 5: Handover and documentation

Every project comes with documentation your team can actually use. Not technical specs. Practical guides: what the system does, how to use it, what can go wrong and how to fix it, and who to contact if something doesn't look right.

I'll run a training session with whoever needs it. Usually 30 to 60 minutes. The goal is that your team is self-sufficient for day-to-day operations without needing to call me.

You own everything. The code, the configuration, the documentation. Nothing is locked behind a proprietary system you can't leave. If you decide to part ways, you keep the lot.

Step 6: Ongoing support (optional)

Most clients move to a monthly retainer after the initial project. A few hours a month covers monitoring, tuning, minor updates, and the inevitable "could it also do this?" requests that come up once the team starts using the system and seeing what's possible.

This is where engagements naturally expand. The invoice processing works, so now you want cost variance alerts. The lead response is capturing jobs, so now you want marketing attribution. The agent answers operational questions, so now you want it to draft reports.

Each addition follows the same pattern: scope it, build it, test it, hand it over. No surprises.

What you won't get from me

A six-month discovery phase. A 20-page proposal full of buzzwords. A dependency on my proprietary platform that you can't walk away from. A vague promise of "transformation" without specific outcomes attached.

You'll get a clearly defined problem, a specific solution, a transparent cost, and a working system that delivers measurable results. That's the whole thing.

The first step

If you've been thinking about automation but weren't sure what you'd be getting into, now you know. The process is straightforward. The commitment starts small. And the first conversation is just a conversation.

What Happens When You Hire an AI Consultant (No Jargon)