In partnership with

Whats up whats uppp!

You're getting this email because you subscribed to aidstation. If you're new here, welcome. I share what I'm using, what I'm learning, and what's happening in AI every week.

I wanted to shoutout to Mateo Romano for sharing this newsletter with his network. Mateo runs Adaptig, they help companies adopt AI through hands-on workshops and training programs. Check them out.

By the way, I like to shout out everyone helping us grow. So if you share this with a friend and they subscribe, just let me know, you're in the next one.

I need your help

I want to make this newsletter better and I need your input.

I’ve been testing a bunch of different formats, news, full guides, tools and so on. I want to know what actually works for you.

Login or Subscribe to participate

Is the newsletter...

Login or Subscribe to participate

And feel free to reply with whatever's on your mind. Even one word. I read every response and it directly shapes what comes next.

Now let’s get into it

What I've been using

Turning OpenClaw into our internal AI workforce

I've been talking about OpenClaw for a over a month now. If you missed it, it's an open-source framework for building AI agents that actually do things, not just answer questions.

Most of us at Kleva were already using it individually, each for our own stuff.

But last week I decided we should stop treating it as a personal tool and start building real internal agents for the company.

So we launched Kleo with the idea of having a workforce of AI agents that run our business.

We started with the lower hanging fruit, sales.

After just a day of work, Kleo now monitored our CRM, catched leads that need attention, drafted personalized follow-ups based on the full email history, and sent them to Slack for the team to review.

But this was just the start.

Then we built a vacation and time-off agent. No more spreadsheets, no more "who's out next week?" in Slack. It handles the full approval process with managers per team, tracks balances, and keeps everyone on the same page.

These are the closest things we have to fully autonomous AI agents. They're not assistants waiting for instructions. They're doing someone's job, on their own, around the clock.

And we now have a full pipeline of agents we are building next.

The pattern is simple. You look at your operation and find the tasks that are repetitive, that depend on someone remembering to do them, that break when people get busy. Those are the ones you turn into agents.

The hard part isn't building them. With OpenClaw and Claude, that part is fast. The hard part is figuring out which processes in your business are ready to be handed off.

If you're thinking about building something like this for your team, reply and tell me what you'd automate first. I'll tell you if it's a good fit and how we'd approach it.

What caught my attention this week

OpenAI bought OpenClaw

This one hit close to home. OpenClaw is the framework we use to build our internal agents.

Both OpenAI and Meta submitted billion-dollar bids for it. Peter Steinberger, the creator, chose OpenAI. Sam Altman said he'll help build "the next generation of personal agents."

OpenClaw had 180,000 GitHub stars. It became the foundation that thousands of people used to build their own AI agents. All open-source, all customizable.

VentureBeat called it "the beginning of the end of the ChatGPT era," the shift from chatbots you talk to, to agents that actually do things for you.

Steinberger says it will transition to a foundation structure to stay open source. We'll see.

When big companies acquire open-source projects, the promises don't always hold up. For now, everything still works. And even if OpenClaw changes direction, we own our fork. Nobody can take that away.

SaaS is going open-source, and vibecoders are the reason

The OpenClaw acquisition is part of something bigger.

A year ago, if you needed a tool for your business, you bought a SaaS subscription. $30/month for this, $100/month for that, $350/month for something else. That was the only option unless you had a team of engineers.

That's changing fast.

We replaced Perspective, a $350/month funnel platform, with a custom tracking system built in a couple of days with Claude Code. We replaced a chunk of our sales automation with Kleo, built on an open-source framework and a $5 server. One person built each of these. No engineering team, no six-month project.

And we're not special. This is happening everywhere.

People are vibe-coding their own CRMs, their own analytics dashboards, their own internal tools. Not because they want to, but because AI makes it faster to build exactly what you need than to learn and adapt to someone else's product.

Open-source projects are exploding because they give you the foundation. You don't start from zero, you start from 80% and customize the last 20% for your specific workflow.

That's why OpenClaw hit 180,000 stars. That's why OpenAI and Meta were willing to pay billions for it.

The SaaS companies that are going to struggle are the ones selling generic tools that a vibe coder can replicate in a weekend. The ones that survive will be the ones with real data moats, network effects, or complexity that AI can't shortcut yet.

If you're building a business right now, this matters. The cost of internal tooling just dropped by 100x. The question isn't "which SaaS should I buy" anymore, it's "should I just build this myself."

That's it for this week.

-Ed

Liked this? Sign up here to get more.

Dictate prompts and tag files automatically

Stop typing reproductions and start vibing code. Wispr Flow captures your spoken debugging flow and turns it into structured bug reports, acceptance tests, and PR descriptions. Say a file name or variable out loud and Flow preserves it exactly, tags the correct file, and keeps inline code readable. Use voice to create Cursor and Warp prompts, call out a variable like user_id, and get copy you can paste straight into an issue or PR. The result is faster triage and fewer context gaps between engineers and QA. Learn how developers use voice-first workflows in our Vibe Coding article at wisprflow.ai. Try Wispr Flow for engineers.

Reply

Avatar

or to participate