Simon Høiberg

OpenClaw + n8n.
This is an extremely powerful combination.

People thought OpenClaw (or Claude Code) would replace n8n, but here's what they're missing.

n8n - as an application layer between the agent and the tool - still makes perfect sense for at least 3 reasons.

1️⃣ Observability

OpenClaw can write its own skills.
But instead of letting it script away, ask it to create n8n workflows for itself to use.

It is much easier for you to investigate and see what the agent built for itself in n8n, rather than looking through 100 ugly written JavaScripts.

2️⃣ Security

After the agent is done creating its n8n workflow, you can lock in place. Making it read-only from that point.

Instead of adding API keys to .env.local for the agent to use (and abuse) in any way it likes, you can now add the credentials securely to n8n.

From here, you can also easily add any additional safeguarding step, making sure your agent doesn't make a mess by mistake.

3️⃣ Performance

An agent adds value when it needs to make decisions.
But a lot of work is still predictable and deterministic.

Turn it into a workflow.
It's faster and you save tokens.

🔁 The flow

- The agent needs access to an API.
- It writes an n8n workflow with incoming webhook.
- You lock the workflow and add the API key.
- You add extra safeguarding steps.

The agent now proxies all calls through n8n.
It never sees the API key.
It's prevented from making crucial mistakes.

I know... It feels addictive to let OpenClaw do everything.

But this thing is a beast!
Use it responsibly.

6 days ago | [YT] | 180

Simon Høiberg

I don’t want every small AI workflow in my business running through OpenAI or Anthropic.

Frontier models are still best for serious work. I use them every day.

But a lot of SaaS workflows are not that deep:

Support triage.
Ticket tags.
Docs lookup.
PR summaries.
Log summaries.
Daily reports.

That stuff does not need the best model on earth.

It needs to be cheap, repeatable, private enough, and good enough to run without turning every tiny task into another hosted API dependency.

That is where local models start to make sense.

Not as a full replacement for Claude or ChatGPT.

As a layer for the normal business workflows you run over and over again.

Start there.

Then move up when the workflow is actually worth the GPU bill.

Here’s the practical map 👇

1 week ago | [YT] | 148

Simon Høiberg

We just got rug pulled by the US government.

Anthropic launched Fable 5, the safer version of Mythos.

Then a directive landed, and customer access had to be removed.

This is why founders need a local model strategy.

Hosted models are rented access.

Use them. I do.

But don’t let every AI workflow in your business depend on one provider keeping access open.

Start with the easy stuff:

Support triage.
Routing.
Summaries.
Internal search.
Small agents over company docs.

Here are 8 AI models you can self-host now 👇

Skip the Carousel

1 2 3 4 5 6 7 8 9 10

1 week ago | [YT] | 210

Simon Høiberg

You think bootstrapping a SaaS in 2026 is about scale? You got it upside down.

It's about doing more with less.

10-person teams can do +$10M ARR.
3-person teams can do +$1M ARR.
1-person teams can do 6 figures ARR.

And no, you don't have to be a superstar. This is fully achievable by the "average" person (just like myself).

Here's how it breaks down:

For product, you need:
→ AI-powered support
→ Streamlined feedback handling
→ CRM / simple database
→ Automation & workflows
→ Scaling & managing advertisement
→ Email newsletters & updates

For marketing, you need:
→ Monthly YouTube videos
→ Weekly email newsletters
→ Daily LinkedIn posts
→ Ads on Meta, Google, YouTube

For operations, you need:
→ AI Agent workflows.

Setups like these allow small teams to compete with billion-dollar enterprise companies.

And it allows solopreneurs to claim freedom and financial independence.

2026 still has plenty left.
Let's go 🚀

1 week ago | [YT] | 132

Simon Høiberg

Most SaaS advice assumes growth means hiring more humans.

AI makes that advice look old.

A lot of the classic founder advice came from a world where every bottleneck eventually turned into another person, another manager, another meeting, or another tool.

That is changing fast.

Here are 8 SaaS beliefs AI is killing 👇

Skip the Carousel

1 2 3 4 5 6 7 8 9 10

2 weeks ago | [YT] | 124

Simon Høiberg

Most AI support setups are still way too small.

They answer the ticket.
Maybe summarize the conversation.
Then everyone moves on.

That is fine if all you want is a slightly cheaper support queue.

But the interesting part is what happens before and after the reply.

A good support agent should read the actual context:

Aidbase tickets.
Stripe account state.
Product usage.
Grafana errors.
Docs and internal notes.

Then it should turn the ticket into useful work:

Product issue.
Docs update.
Churn flag.
Weekly pain report.

If support only answers users faster, you still have the same product problems.

The useful setup makes those problems harder to ignore.

2 weeks ago | [YT] | 91

Simon Høiberg

It's been a while!
I moved from Spain back to Switzerland and relocation always makes filming extra challenging.

But I'm back. Locked in.
And ready with new videos 🫡

I have a ton of new things I want to show you guys.
Stay tuned for more (gonna keep it coming more frequently from now on).

2 weeks ago | [YT] | 38

Simon Høiberg

Build a Micro-SaaS in 7 days.
Test the market. Then double down or kill it.

Rinse and repeat until you have a working product.

🔹 Days 1-2:
Think like a user, not a founder.
What makes this necessary?
Sketch the data and the screens.
Use your favorite boilerplate to get going.

🔹 Days 3-4:
Function over form.
Drag, drop, wire it up.
Draft a clean, functional UI.
Add essentials like auth and payment.

🔹 Day 5:
Reduce friction.
Onboard in one minute.
Create a place for feedback.
Ship a landing page that promises an outcome, not a feature list.

🔹 Days 6-7:
Show, don't tell.
A 60-second demo video.
Pair it with a simple launch offer and push it everywhere your users hang out.

With the right tools, this is possible in 2026.
🔸 Aidbase
🔸 n8n
🔸 Supabase
🔸 Lovable
🔸 Cursor

If it doesn't pick up, start over.
You can do at least 30 of these in a year.

2 weeks ago | [YT] | 169

Simon Høiberg

When a SaaS user churns, the lazy version is just logging it as churn and moving on.

I want the annoying version.

Start in Stripe:
Who cancelled, downgraded, failed payment, or changed plan?

Then pull the user context:
Aidbase tickets, chats, complaints, invoices, account notes.

Then rebuild the product path:
What features did they use?
Where did they drop off?
Which jobs failed?
Were there errors around the same window?
Did Grafana show something weird?

That is the part agents are ridiculously good at.

Not predicting churn from some magical model.

Just doing the boring context work every single time without getting tired of it.

OpenClaw can pull the scattered pieces together and hand me the useful version:

Here is what happened before they left.
Here is where usage dropped.
Here is the support context.
Here are the errors around the same time.
Here is the likely reason.
Here is the product/support/billing thing worth looking at.

That is way more useful than staring at a churn number and guessing from vibes.

3 weeks ago | [YT] | 105

Simon Høiberg

There are SaaS tools I use every day and still would not let become core infrastructure.

Not because they are bad.

Some of them are excellent.

But if one vendor can block exports, change pricing, remove an API, suspend an account, or break a workflow my business depends on, I want a way out.

That is the line for me.

I am fine renting convenience.
I am not fine renting the parts that hold the business together.

So I look at every tool through one simple question:

If this disappeared, became 5x more expensive, or locked me in tomorrow, would I still be able to run the business?

For some tools, the answer is yes.

For others, I want raw data, exports, APIs, self-hosted backups, or a boring fallback I understand.

Here are 8 SaaS dependencies I would not build my business on without owning the important parts myself 👇

Skip the Carousel

1 2 3 4 5 6 7 8 9 10

3 weeks ago | [YT] | 198