Howdy wizards,
I read something that stuck with me.
How do we make sure we keep the fun stuff for us, for the humans, and give the AI the stuff thatβs less interesting and less fun?
The wording puts a sense of responsibility on the reader.
We need to make sure AI gets used for the right stuff.
Increasingly, using AI doesnβt mean one-off prompting. It means agent-run automation.
That raises two questions:
Which processes should you automate, and which do you keep manual?
Once youβve decided to automate, which parts of those processes (if any) should remain manual?
This is my take on question 1.
Iβll answer number 2 later this week.
This is not a tutorial on how to automate (Iβll save that for later).
In the mood for something more hands-on? Todayβs sponsor has a webinar tomorrow that you really shouldnβt miss:
IN PARTNERSHIP WITH OUMI
A general-purpose model doesnβt learn from your production failures, operator corrections, or the work that makes your business different.
On August 11, Oumi is launching the AI Factory that runs the complete loop: Evaluate, Synthesize, Train, Deploy, Compound. Weβll show it live on a real task and reveal three product announcements.
Join Manos Koukoumidis and the Oumi team at 10:00 AM PT / 1:00 PM ET.
β¦
Deciding whether to automate or not
Before I get into explaining this chart, take a sizeable pinch of this: π§ (thatβs salt btw)
This is how I think when I automate my stuff.
Thought it might resonate with others too.

probably my magnum opus of flowcharts
The chart asks about money first: does it actually contribute to your bottom line?
Two reasons thatβs the first question:
Building an automation takes time and cognitive capacity from you. Both are limited resources for humans. The type of mental capacity needed to automate a process well is especially limited, I personally have a few hours of it per day. Even with AI handling the technical implementation, you still have to get deeply involved to create an automation thatβs actually helpful.
Building and running an automation costs money. Building it costs tokens or usage credits. Running it often costs money forever (e.g. model calls, APIs, hosting, ++); everyone thought this didnβt really matter with AI, until they realised itβs getting really expensive. It only makes sense if it earns more than it costs.
Time savings are not enough. Once you start automating things, youβll discover itβs a bottomless well. Thereβs an endless supply of little tasks that could save you time. Automating these indiscriminately sinks your best hours into things that donβt necessarily move the needle, and leaves you less focus for the things that do.
Thatβs also why Iβve made it a double step in the chart. I donβt know about you β but my ego gladly assumes any process Iβm doing is contributing to my business. Else, why would I have been doing it manually up until now?
But when I start to examine the things I do in an honest way, I find the good olβ Pareto principle harder at work than anywhere else.
Chances are, thereβs a few things that move the needle in your business, and a lot of little things that just exist.
The stuff that doesnβt earn money
When you identify a process that doesnβt really contribute to your businessβ growth, itβs time to get brutally honest.
Why am I even doing this?
For me, often, itβs that I enjoy it. Even though I know deep down itβs not really a money-generating activity. And thatβs okay. God forbid a man has hobbies! I just make sure itβs not my main focus.
The flipside is when a task isnβt really contributing to my business and itβs boring. Letβs call these by their name: inefficiencies.
Having a meeting out of politeness, keeping a social channel alive without a single lead to show for it, the project that loses money & drains me but Iβm too emotionally attached to let it go. And so on.
Those processes are ripe for killing.
If I canβt, or I donβt want to yet, I keep doing them manually. I donβt automate them.
That way, the inefficiencies in my business stay visible where they can actually be seen, and removed or transformed when their time has come. When they annoy me enough that Iβll finally toss them out of the window.
If I abstract these things away into automation Iβd basically pour concrete around them. And eventually, Iβd have a huge messy drawer of inefficiencies Iβve lost track of why are even there.
The stuff that earns money
This one is easy to get wrong.
Once you know something earns money the impulse is to scale that thing. And with AI, anything you can render on a screen can be scaled. That doesnβt mean you should.
For me, the deciding factor is enjoyment. If something makes me money and I enjoy it, why would I automate it?
But: I use common sense. If something I do is about to get turned into an absolute commodity by AI, and I can see it coming, Iβd use that information.
Even things I like doing have aspects of them which Iβm less fond of. You can automate sub-processes, so your time only goes to the highest leverage sub-processβlikely the thing youβre most passionate about. Iβll go into how I identify those sub-processes in my own work in my next post.
Finally, thereβs the stuff that makes money and is no fun for you. For me, itβs things like accounting, analytics, research, proofreading and more. Essential yes, and also perfect automation candidates.
β¦
Right now thereβs someone automating the thing youβve decided to keep for yourself.
Thereβs pressure in that.
And when the numbers are bad, everything starts looking like a cost to cut. Fun or not.
Automating boring, money-generating processes is the antidote. It gives results.
And results give us freedom to do what we want, including deciding which parts of our work stay human.
This is how to make sure we keep the fun stuff for us: make the boring stuff pay for it.
What's your verdict on today's email?
See which AI use cases are paying off with Context Windows Pro
Most companies pick AI use cases by brainstorming internally. 90% of those initiatives fail.
Iβve created Context Windows just so you can pick the winners.
π¦ Find high-performing use cases from 2,000+ companies at contextwindows.ai, or book a demo with me
Disclosure: To cover the cost of my email software and the time I spend writing this newsletter, I sometimes work with sponsors and may earn a commission if you buy something through a link in here. If you choose to click, subscribe, or buy through any of them, THANK YOU β it will make it possible for me to continue to do this.



