Fractional AI for founders.

A retainer means I'm in your business every week.

Not dropping in quarterly with a deck.

Some months that's the workflow eating your ops team's Fridays.

Some months it's the AI tools you bought last year and never wired in.

Whatever stalls because nobody trusts the output yet… that's my desk.

I build alongside your team.

And I explain what I'm doing while I do it.

So the judgment stays in the building after I'm gone.

A few months in, the job changes.

I stop only building what you asked for… and start seeing things nobody asked for.

The content that could be cut three ways.

The hour a week your team spends on something a script should be doing.

That's the part I find most valuable.

And it only shows up once I'm embedded.

Nearly every founder I start with has the same problem.

And it has nothing to do with the tools.

You can articulate maybe a third of what you actually do.

The rest runs underneath.

How you diagnose the problem behind the one they described.

The sequence of questions… and what each one is really testing.

Why you push back here and let it go there.

It's why you're the only one who can close.

And why the thing that makes the company work is the one thing you can't hand to anybody.

Getting that out of your head and written down is Cognitive Fingerprint™.

And on a retainer, it usually comes first.

Because everything else gets built on top of it.

1. 01

   A weekly call

   Somebody brings a build in progress and walks the room through it.

   I push on the thinking and take it up a level with everyone watching.

   So people learn off each other's work instead of only their own.

2. 02

   Slack in between

   "Do you have a prompt for this."

   "I'm stuck here."

   "Is this even the right way to think about it."

   Most days, same day.

3. 03

   The big builds we finish together

   You bring the vision and a v1.

   I take it the rest of the way.

   Then walk the team back through how it was done… so they can run the next one without me.

4. 04

   A workshop when a gap opens

   Not on a schedule.

   When something shows up that the whole team needs, we stop and run a session on it.

Two questions I keep asking the entire time.

And they irritate people.

A month usually produces three to five things.

Not one grand system that arrives in December.

An extraction of how you think, written down.

A hub your team logs into.

A Claude project shaped around one person's actual job… then another… until everyone has one.

A dashboard sitting on data you already pay for and never look at.

Quiz funnels, landing pages, internal tools.

Voice agents your new hires practice on before they touch a customer.

The Notion cleanup nobody wanted to do and everything else depends on.

You own all of it.

If something genuinely heavy comes up… a compliance build or tearing out a whole software system… I flag it up front and quote it separately.

Most of what you need never gets near that line.

Create dependency.

Everything I build, you own.

If we part ways, you keep all of it.

The point is to make you more capable, not to make you need me.

Make you generic.

You've built something specific.

I'm not going to sand the edges off it with best practices that work for nobody in particular.

Waste your time.

If something isn't creating change you can see, we kill it.

I'd rather pivot fast than defend a bad idea I had in month one.

Add complexity.

You want fewer things to manage.

I take that seriously and I don't always meet it, but it's the bar.

There's one question I ask before anybody signs anything.

I'd rather know your actual success criteria than guess at them and find out in month four.

Most people have never been asked.

The ones who answer it quickly are usually the ones this works for.

For founders and operators with a business already running and something to point me at.

I take a few of these at a time. Not many.

The ones that stall don't stall on the building.

They stall when I can't get the material out of you.

The transcripts. The access. The half hour it takes to answer something only you can answer.

If nobody on your side has that half hour, this doesn't work.

And I'd rather say it now than bill you for three months of finding out.

If you're earlier than that, start with the newsletter or get your team into a workshop.

Both roads lead back here.