Clone Yourself First
Before you build AI for customers, before you build a product, before you pitch your manager on an AI strategy: build an AI version of you. It's the highest-return investment you will make in AI.
The Highest-ROI Thing You Can Do With AI
Most of the AI work I see right now is for other people. AI products for customers, AI workflows for teams, AI demos for boardrooms. They’re spending months on work that looks incredible in the meeting and falls apart the moment a real user touches it.
They’re starting in the wrong place.
Clone yourself first. Before you build for customers, before you build a product, before you pitch your manager on an AI strategy: build an AI version of you. Automate your own work. Replace yourself. It’s the highest-return investment you will make in AI, and it’s not close.
You can only control one person: you. You can’t make a customer use your product, you can’t make your team change how they work, and you can’t talk your boss into funding an experiment when they need deliverables. But you can decide, today, to do your own work through AI instead of by hand. That decision is entirely yours, which is exactly why it works.
Time Is Not the Point. Cognitive Load Is.
You might read “clone yourself” and think this is about saving time. Getting your emails drafted, automating a report, managing your calendar. That stuff matters. It’s not the real prize.
The real scarcity in your life right now is not hours. It’s headspace. Every small obligation takes up cognitive territory. Updating a deck, answering a question about a number you already know, dragging a file into an email. A 30-second interruption doesn’t cost you 30 seconds. It costs you the thread of thought you were following before the ping arrived, the ten minutes it takes to find it again, and the growing chance that the next interruption hits before you do.
Clear that noise and you have something to invest: not just time to do things, but time to think about things. An hour every day processing ideas, talking through what you could build, where the opportunities are. You cannot get that hour if every available minute is consumed by tasks that could have been handled by something other than you.
Time is all you need.
Put that cleared space to work and it compounds fast. But that assumes you can build the thing that clears the space without burning months on it.
You Don’t Need Evals. You’re the Fucking Eval.
The bottleneck isn’t building things. Building things is cheap. The bottleneck is knowing whether the output is any good.
This is where AI projects die. Someone builds a demo, leadership signs off, they scale it to real users, and it collapses. The person who built the demo was unconsciously doing the evaluation, testing against cases they understood. The moment it lands in someone else’s hands, the failure modes multiply faster than anyone can catalog them.
I think engineers automated first because they could close that loop instantly. They looked at the output and knew whether it was right. Look, know, done.
When I try to do this at my day job, building AI tools for lawyers, it’s a completely different experience. I’m not a lawyer, so every time the AI produces output I can’t just look at it and know. I have to get the output into a format a lawyer can assess, which takes iteration because I probably won’t nail the UI the first time, then the lawyer reviews it on their schedule, then I review their review to make sure they evaluated it properly, then I feed the corrections back in, and maybe the annotations from one lawyer are biased so now I need a representative sample, and every time the underlying system changes I run through all of it again. Seven friction points, minimum.
When you build for yourself, all of that collapses. You look at the output, you know if it’s right, you fix it. Done. No validation pipeline. No waiting on someone else’s calendar. Just you and your own judgment, moving as fast as your brain can process.
It costs you almost nothing. The only question left is where you find the time.
The Byproduct Is the Work
When I tell people to automate themselves, they usually think they need to carve out time from their real work to build this AI thing. Ask their boss for two weeks to experiment, stay up late, squeeze in side projects on the weekend.
That’s not how it works. The byproduct of building the clone IS the work output. The best way to build an AI analyst is to do the analysis. You’re not doing something extra. You’re doing the exact same work you were going to do anyway, through AI instead of by hand.
What’s on your plate this week? What did your boss ask for by Friday? Do those things. Just do them with AI. Your five deliverables this sprint are your training data, your eval set, the thing you build the clone on. The first task might take the same amount of time, maybe more because you’re setting up scaffolding. The second one is already faster. By the end of two weeks, if you had five things to get done, you’re going to deliver 20, because every task teaches the system something that carries forward into the next one and the next one and the next one. That’s the whole damn point. You’re not taking time off from your work. You’re doing your work.
Your boss gave you five things to deliver. You delivered twenty. Nobody complains about that. And it happens faster than you think.
By Friday, You’re Faster
I’ll make the progression concrete.
Week one. You connect the AI to your actual data sources, the messy ones you work with every day. You run it on a report you were already going to produce. You force it to write the SQL for every number and output those queries where you can see them. Then you check them manually. You can do this fast because you wrote similar queries yourself last month.
The first time is clumsy. You’re teaching it what your metrics mean, correcting column names, explaining business logic you’ve known for years but never had to put into words because no one else needed to hear it. In multiple cases when I did this, the AI corrected queries where I had been reporting the wrong metric for months. In other cases it chose the wrong column and got the number wrong, but I caught it immediately because I know this data. Nudge it, save the correction, it doesn’t make that mistake again. Look at the output, know if it’s right, correct it, move on.
By my third analysis I was moving faster than I would have been by hand. Every correction gets stored. Every pattern it learns reduces the surface area of things that can go wrong. The return curve bends upward and it bends fast.
Being 10 days ahead of someone is a long time now. Ten days of compounding in this environment puts you in a different operational reality than the person who hasn’t started. But you can catch up quick. Don’t be scared to start.
The Person Who Can Replace Themselves Is Irreplaceable
The person who knows how to replace themselves is irreplaceable.
Three things happen once you’ve automated your own work, and they layer on top of each other.
First, the stuff you knew you had to do gets done in a fraction of the time. Your committed deliverables, your sprint goals, the reports leadership asked for. You haven’t changed what you deliver. You’ve changed how much of your life it costs.
Second, the stuff you always wanted to do but never had time for. That analysis you knew would be valuable but could never justify spending three weeks on, that process improvement you keep meaning to propose, the thing you’ve had in the back of your head for months that you never started because the urgent work always won. You have actual hours now. Not theoretical time. Real hours in your day that are no longer consumed by the work the clone handles.
Third, you start doing things you didn’t even know were possible. Problems you couldn’t see because you never had the bandwidth to look up from the work long enough to notice them. I started building systems to teach others the process. That wasn’t on any roadmap. It only became visible once the noise cleared.
That’s what’s happening to me right now. And it’s happening to people around me who started doing this. The most valuable person in the room isn’t the one doing the most. It’s the one who built the system and now sees what no one else can see.
Just Start
Clone yourself first.
Tomorrow morning, take whatever is at the top of your to-do list. Do it through AI instead. Look at the output, correct it, do the next one. By Friday, you’ll be faster.
Time is all you need. You’re about to get a lot of it back.
Want to build an AI Analyst in Claude Code?
Join our weekend bootcamp on April 4-5. Eight hours, three instructors, leave with a working repo.