From intake to readout
Intake
You fill out a short survey about the business, the software you use, and what takes the most time. I read it before we talk.
Discovery call
One 60-minute call. You walk me through how the work actually runs, up to three workflows. What kicks it off, who touches it, where information gets typed twice, what falls through the cracks.
The Blueprint
Within five business days of the call, you get a written plan. I look at your current tools first and only suggest something new if it earns its place.
Readout
A 45-minute call to go through it. You react, ask questions, and tell me what doesn't fit.
After that
It's yours. Do it yourself, hand it to someone else, or ask me to help. The Blueprint stands on its own.
What I look at
How the work gets done today. What gets typed twice. What depends on someone remembering. Which software you already pay for and how much of it you use. Then what the recovered time would turn into: more clients seen, faster replies, less catching up at night.
What you end up with
A written AI Opportunity Blueprint with three to five opportunities, ranked by impact, effort, cost, and risk. For each one: what it is, what it's for, what it takes, and what could go wrong. Quick wins are marked. You also get tool recommendations, risks to watch, a 30-day action plan, and a list of what I'm not recommending, and why.
What the recommendations usually look like
Sometimes the answer is a setting in software you already have. Sometimes it's one less step, a template, or a better handoff. Sometimes it's a lightweight automation or an AI tool. Sometimes it's no change at all, and I'll say so.
What I won't promise
- A result in advance. I can tell you what's worth changing. What it pays back depends on what you do with the time.
- That AI is the answer. If it isn't, the Blueprint says so.
- That you need to hire me afterward. You don't.
What the Blueprint looks like
An illustration of the format, shortened. It's adapted from an earlier assessment for a small healthcare practice, with the name, the software names, and any numbers taken out. I've reworded this one so it fits any service business.
Explain what you offer in plain language
- What it is
- A short email or handout explaining a service, written for new clients and for existing ones.
- What it's for
- More people understanding something you already offer.
- What could go wrong
- Someone has to approve the wording, and it has to sound like you every time.
- Next step
- Draft one email or handout and send it to a small group.