Most businesses have tried AI and gotten nothing. Let's fix that in person.

Three things you should know

I build.

You get working systems, not slide decks. Three of them are public: Understudy, saybooks.io, and VoiceLender. In workshops I build live, in front of the room, on someone's real problem.

I've done this at scale.

Thirty years making enterprise software actually work. SAP delivery for Nokia, Nike, Apple, Delta, CVS Health. MSc in electrical engineering. Most local consultants have never seen systems this size.

I'm here.

Portland metro. I come to your office, sit with your people, and watch how the work really moves before I automate any of it.

Four ways to work with me

Start small. Each step pays for the next one.

Fixed scope, fixed price. You see something working before you spend more.

Step 0

The workshop

60 minutes, live

I build one real automation in front of the room, using a volunteer's actual problem. No slides beyond the title.

Freefor chambers, SBDC, coworking spaces, associations

Step 1

AI Opportunity Map

Two weeks, fixed

Half a day at your office mapping where the hours go, role by role. You get a one-page map, the two or three automations worth doing first, and one of them built as a working prototype.

$2,500fixed

Step 2

Build Sprint

Three to six weeks, fixed scope

One system built, installed, documented, and handed to your staff. Phone and web intake, quoting, invoicing and collections, document processing, an assistant over your own files.

$5,000 to $15,000fixed scope, quoted after the map

Step 3

On-call AI operations

Month to month

Keeps what was built running, adds small improvements each month, and gives you a person to call.

$1,500 to $2,500 a monthUp to eight hours a month. I answer within one business day.

Full scope, timelines, and questions people ask

How it works

Three steps, and you can stop after any of them.

We talk for 30 minutes.

You tell me what eats your week. I tell you honestly whether AI helps with it. Sometimes it doesn't, and I'll say so.

I map the work and build one thing.

Half a day at your office, role by role, where the hours go. Then I build one prototype so you can see it run on your own data.

I install it and stay reachable.

One system at a time, documented and handed to your staff. If you want, I keep it running and add to it monthly.

Proof

What I've built, and how I work.

Workshops. First sessions are being scheduled for fall 2026. Recordings and photos from each one will appear here.

Understudy, a tool that maps how work moves through a role

Understudy is the method.

Before automating anything, I map how the work really moves through your people. Understudy is the tool I built to do that. I used it first on my own role. understudy.team

saybooks.io, a business system where an AI agent and a person share the same books

saybooks.io is the kind of system I build.

Invoicing, customers, and jobs in one system of record, where an AI agent and a person operate the same books through the same rules. Your AI should work inside your system of record, not beside it. saybooks.io

VoiceLender, voice assistants grounded in a business's own data

VoiceLender is the phone getting answered.

A voice assistant that talks in real time, knows your customers and your schedule because it reads your own systems, and can act: look up an account, book the appointment, open a ticket. Built for phone and web intake. voicelender.com

About

An engineer, not a strategist.

I spent thirty years making enterprise software work for companies with tens of thousands of employees. Then I built a tool to map how work moves through a role, and used it on my own job first. Now I do the same thing for businesses where the owner still answers the phone.

More about me