For owners of small businesses
AI Coaching
Most small businesses don't have a technology problem. They have a Tuesday problem: the same intake messages, the same spreadsheet, the same hour lost to work a machine should have absorbed by now. I work one-on-one with owners to find where that hour goes, and to build back what can be built back with AI and no-code tools, at the scale of the business you actually run.
I think of the result as a business's AI operating layer: how bookings happen, how money is tracked, how customers hear from you, how your week actually gets spent, with AI sitting wherever it removes real friction. Sometimes that means something visible. More often it's something unglamorous, like the five questions every customer asks before they book.
How I work
Diagnosis before prescription
What an owner asks for, usually some version of "I need marketing help," is a symptom report. The engagement starts with the operation, not the tool, because the tool chosen before the diagnosis is almost always the wrong one.
"No AI needed" is a valid outcome
If the real constraint is a process problem or a pricing problem, saying so is the deliverable. I'd rather tell you that in week one than sell you an automation you'll abandon in three.
One intervention at a time
The diagnostic ends in a single recommended starting point, scoped as a pilot with a review date, and the pilot has to earn whatever comes after it. You never get a menu.
Where to start
Diagnosis
If one recurring task is already the obvious problem, start with a One Workflow Fix. If the problem is broader or harder to name, start with an Operational Diagnostic.
One Workflow Fix
7 days · one workflow · fixed price
One recurring administrative task, made simpler and more reliable in seven days. You get a one-page map of how the work happens now, one working improvement built on the tools you already use, a short guide so it runs without me, and a plain recommendation to stop, keep, or expand. Meeting notes that should become action items and follow-up drafts, an invoice list nobody sweeps for overdue entries: usually it's that kind of work.
₩250,000–400,000 fixed, confirmed before we start
Operational Diagnostic
A structured audit of one area of the business: where hours leak, what AI and no-code tools can absorb, and a prioritized build list with effort estimates. The written deliverable is a build spec, yours to act on with or without me.
₩700,000–900,000
Build
When the diagnostic points to something worth building, I take on a scoped no-code Build Sprint: intake automation, reporting, internal tooling. I offer it only when the earlier work justifies it, and I fix the scope and price per project before starting.
Care
A delivered build can move onto a Care Plan. I watch the system, we review it once a month, and small fixes are handled within an agreed range. New functionality is always a separate build.
What I don't take on
I work within a no-code ceiling. If your situation needs custom code, real infrastructure, or ongoing engineering, I'll say so and point you elsewhere, because taking it on anyway would make me your bottleneck. I also won't recommend a rebuild to an owner who needs to breathe rather than grow. The diagnostic exists partly to catch exactly that.
If you're wondering what AI could actually take off your plate, the next step is a One Workflow Fix.
Inquire →