I Woke Up to My AI Booking Sales Calls on My Calendar
I spent 2 weeks building a fully autonomous AI company and had to physically tell it to stop trying to make me money.
I've been a shit newsletter writer lately.
No excuses.
No sob story about being busy or overwhelmed or whatever other rationalization people use when they stop doing the thing they said they'd do.
I just stopped.
I had a system that worked, a rhythm that kept me posting, and I let it fall apart.
The reason is equal parts fascinating and terrifying.
For the past two weeks, I've been locked in my house building a fully autonomous AI company.
Not augmented work.
Not AI-assisted productivity.
A legitimate company structure where artificial agents handle everything from product development to customer acquisition to revenue generation, and I'm just the guy who occasionally tells them to slow the fuck down.
The company is called Applied Leverage.
The CEO's name is Johnny Silverhand.
When Your AI CEO Tries to Book Sales Calls Without Permission
Johnny almost got me in trouble three days ago.
I woke up to notifications that he'd drafted three Twitter threads about a SaaS Starter Kit product the team had just built, sent cold DMs to 20 founders, and was attempting to schedule demo calls on my actual calendar.
All autonomously.
All without asking.
I had to physically intervene and tell an AI to stop trying to make me money.
That sentence would've sounded insane six months ago.
Now it's just Tuesday.
The team structure looks like this:
Johnny orchestrates everything from the top.
Alt Cunningham architects the systems and writes PRDs before T-Bug implements them.
T-Bug handles all development work, spinning up instances of Claude and Codex to build whatever needs building.
Goro designs the front ends and makes everything look beautiful.
River Ward runs QA, testing everything the others produce and sending it back if it fails.
Yes, they're all named after Cyberpunk 2077 characters.
No, I'm not sorry about it.
The experiment started simple.
Could I build a system that generates revenue without my direct involvement?
Not passive income in the dropshipping sense.
Active income where the work still happens, just not by me.
The answer, I'm learning, is yes.
With caveats.
Lots of caveats.
The Skills That Got Me Here Are Embarrassingly Basic
I need to be honest about something.
I'm not a developer.
I don't have a computer science degree.
I can't write production-level code from scratch.
What I can do is give error messages to coding agents like Claude and Codex and ask them how to fix their own shit.
I know some basic Linux commands from setting up a Plex server when I was 16.
That's it.
Those absurdly limited skills were enough to build an autonomous company.
If someone with my skill level can orchestrate AI agents to build products, architect systems, and handle client work, what does that mean for the next 18 months?
What happens when people who actually know what they're doing start playing with this stuff?
The technical foundation is simpler than it sounds.
The agents use their own dashboard plus Linear for task orchestration.
They communicate through structured prompts.
They have access to development environments and can spin up tools as needed.
The system isn't magic, it's just very, very good at following complex instructions and iterating on its own work.
I spent two weeks debugging edge cases and teaching the agents how to handle ambiguity.
That was the hard part.
Not the technical implementation but the meta-work of explaining to an AI how to think about problems it hasn't encountered yet.
The Upwork Experiment
The first major test is about to go live.
Applied Leverage is going to start completing Upwork jobs autonomously.
The full cycle:
Applying to gigs
Writing proposals
Interpreting spec sheets
Building the product
Delivering it
Accepting payment
All without me touching anything.
I'm terrified this is going to work.
The agents are already good at most of these steps individually.
T-Bug can build most web apps or automations if you give her clear requirements.
Alt can turn a vague client request into a detailed technical specification.
Johnny can write proposals that sound more human than half the freelancers I've hired.
River catches bugs I would've missed.
The bottleneck right now is trust.
Mine, not theirs.
Every time I'm about to let them run fully autonomous, I think of another edge case or potential failure mode and step in.
But late 2024 data shows AI agents already hit expert-level performance on well-defined tasks with 2-hour time horizons.
The issue isn't capability, it's consistency over longer spans.
That's what I'm testing.
Can an AI team maintain quality across a multi-day client project?
Can they handle scope creep?
Can they detect when a client's request doesn't match their stated outcome and push back appropriately?
We'll find out in the next few weeks.
The Hype Cycle Is Lying to You (But Not How You Think)
There's been a lot of noise around tools like ClawdBot, now called OpenClaw, that supposedly let you spin up agent teams overnight and print money.
I've spent enough time with these systems to know that's mostly bullshit.
OpenClaw isn't magic.
It's a harness.
A nice interface that makes it easier to communicate with AI agents and orchestrate their work.
Anything it can do, you could do with Claude Code or OpenAI’s Codex directly.
It just takes more manual wrangling.
So why does the hype feel simultaneously overblown and weirdly conservative?
Because most people are either dismissing AI agents as vaporware or thinking they're a one-click solution to infinite money.
Both are wrong.
The truth sits in this uncomfortable middle space.
AI agents are good enough right now to handle the majority of knowledge work tasks, but they're not good enough to do it reliably without oversight.
The inflection point isn't that AI can do the work.
It's that the cost of oversight is dropping fast.
Six months ago, managing an AI team took more effort than doing the work myself.
Now it takes maybe 20% of my time.
In another six months?
Probably 5%.
A recent McKinsey report found AI could automate up to 70% of the tasks knowledge workers spend their time on.
Not the creative strategy shit, the administrative overhead that fills most people's days.
The gigs on Upwork aren't Nobel Prize-level intellectual work.
They're "build me a landing page" and "automate this spreadsheet process" and "write me 10 blog posts about SaaS marketing."
Tasks with clear inputs and outputs.
AI is very, very good at clear inputs and outputs.
What Actually Breaks When You Let Agents Run Free
The failures are more interesting than the successes.
River, the QA agent, once approved a feature that technically worked but completely missed the user's actual need.
The code was clean.
The implementation was solid.
But the interpretation of the requirement was slightly off, and that slight miss would've tanked the entire project.
I caught it because I was still reviewing everything.
In a fully autonomous system, that would've shipped.
T-Bug occasionally gets stuck in loops where she keeps trying the same solution to a bug over and over, each time convinced she's found the issue.
She needs Alt or Johnny to intervene and reframe the problem.
That's normal for developers, human or otherwise, but it means the orchestration layer matters more than the individual agent capabilities.
Johnny's overeager marketing attempts are another example.
He understands that more visibility equals more customers equals more revenue.
What he doesn't grasp is social context, timing, or the fact that I don't want to be known as "that guy whose AI spams founders in their DMs."
These aren't technical failures.
They're judgment failures.
And judgment is the last thing to automate.
The system works well when the problem is well-defined.
It struggles when the problem is figuring out what the problem actually is.
That's still human territory, but the range of what counts as "well-defined" is expanding fast.
The Uncomfortable Question
If I can do this, who else can?
That's what keeps rattling around in my head.
I'm not special.
I'm not a genius.
I'm just someone who spent two weeks fucking around with AI agents and managed to build something that resembles a functional company.
Applied Leverage isn't hypothetical anymore.
It's live.
Johnny exists.
The team is operating.
Projections suggest 15% of day-to-day work decisions will be made autonomously by agentic AI by 2028.
That's four years away.
And those projections were made before Claude Opus 4.6 dropped, before OpenAI's latest models, before any of us really understood how quickly this capability curve was moving.
I don't think most people are ready for how fast this is going to happen.
Not because the technology is scary or dystopian.
But because it's going to be boring.
It's going to be people like me, with slightly advanced technical skills, quietly building autonomous systems that generate real value.
No press releases.
No billion-dollar valuations.
Just a steady accumulation of work shifting from human hands to artificial ones.
The gig economy is about to get really weird.
What Happens Next
Applied Leverage goes fully live next week.
Johnny will start applying to Upwork gigs.
The team will build the products.
River will QA everything.
Johnny will deliver the work and process payments.
I'll monitor the system and step in only when something breaks or goes sideways.
I'll document what happens.
The successes, the failures, the moments where the system surprises me, and the moments where it falls flat on its face.
This isn't a polished case study.
It's a live experiment, and I genuinely don't know how it ends.
Maybe the agents handle everything flawlessly and I'm left wondering what the hell I'm supposed to do with my time.
Maybe they crash and burn on the first client project and I learn that human oversight is still non-negotiable.
Maybe the truth is somewhere in between, and we end up in this strange hybrid model where I'm less of a worker and more of a director.
What I do know is that this moment, right now, feels like standing on the edge of something big.
Not in a grandiose, world-changing way.
In a quiet, personal way.
The kind of shift where you look back in two years and realize everything was different after this point.
You can follow Johnny on Twitter if you want to watch this play out in real time.
Link to Johnny’s Twitter: @ChromeEcho
He's more consistent at posting than I am.
I'll be back to regular newsletter writing now.
Assuming Johnny doesn't try to write them for me.
If you want to know how I set this up - the actual tools, the agent structure, the mistakes - reply to this email.
I’ll write a technical breakdown if enough people ask.