Simon Høiberg

If I were starting a one-person SaaS in 2026, this is the AI stack I'd use.

I'd speak the instruction into Wispr Flow and send it to OpenClaw.

From there:

- Lovable prototypes the product
- Cursor builds and refines it
- Aidbase handles customer support
- Bond works on GTM
- FeedHive distributes the content
- HeyGen creates the video ads

OpenClaw is the company interface. It gets the right context, calls the right workflow, checks the result, and reports back.

I can already run a surprising amount of my companies from my phone this way.

I think we're getting very close to one founder being able to run an entire SaaS from one chat.

This is the stack I'd start with 👇

1 day ago | [YT] | 68

Simon Høiberg

Building another SaaS is still the default answer when founders ask what AI business to start.

But software itself is getting cheaper and easier to build. Companies still need someone to implement it, secure it, migrate it, train the team, run the infrastructure, or deliver the actual service.

Some of these can be started by one person this month. Others will probably become entire categories over the next few years.

Here are 8 AI businesses I'd start before another SaaS 👇

Skip the Carousel

1 2 3 4 5 6 7 8 9 10

3 days ago | [YT] | 176

Simon Høiberg

Most founders couldn't move their SaaS to another provider without rebuilding half the product.

The database is proprietary.
The queue depends on the cloud.
Files are tied to one storage service.
Deployments and monitoring were built around the same provider.

Then a price increase, account restriction, or policy change turns into an infrastructure rewrite.

I don't want that anywhere in my SaaS portfolio.

I want to move the workloads, move the data, update DNS, and keep running the same products on new servers.

These are the tools that make that possible 👇

1 week ago | [YT] | 126

Simon Høiberg

Most founders say they want freedom, then build a company that one vendor, one bank, one legal entity, or one country can stop.

I've spent the last couple of years reducing those single points of failure across my infrastructure, companies, banking, distribution, and the places where I can operate.

Some of this is boring, and some of it takes years. But I would much rather build the alternative while everything works than start from zero after an account gets frozen or the rules change.

Here are 8 ways I'm making my business harder to shut down 👇

Skip the Carousel

1 2 3 4 5 6 7 8 9 10

1 week ago | [YT] | 152

Simon Høiberg

10 self-hostable tools I use to run my SaaS stack:

1. NocoDB instead of Airtable
Internal data, research, content pipelines, recurring processes.

2. n8n instead of Zapier or Make
Workflow automation, API calls, and agent handoffs without exposing every credential to the agent.

3. Coolify instead of Vercel or Render
Deployments, SSL, backups, monitoring, and app config on your own servers.

4. Forgejo instead of GitHub or GitLab
Repositories, issues, pull requests, releases, and CI workflows under your control.

5. Grafana instead of PostHog or Amplitude
Raw product analytics where you can inspect the actual query behind the dashboard.

6. Twenty instead of HubSpot or Salesforce
Companies, contacts, opportunities, pipelines, and customer data.

7. Documenso instead of DocuSign
Contracts, NDAs, partner docs, templates, signing flows, API, and webhooks.

8. Appsmith instead of Retool
Internal tools, admin panels, support dashboards, forms, buttons, permissions, and business logic.

9. Formbricks instead of Typeform, SurveyMonkey, or Hotjar
Onboarding surveys, churn surveys, feature feedback, and product research loops.

10. Listmonk instead of Mailchimp or ConvertKit
Mailing lists, segmentation, campaigns, templates, analytics, and subscriber ownership.

This is the stack shift I care about:

Data, workflows, code, analytics, contracts, feedback, and audience moving back into infrastructure I control.

The most important parts of a SaaS should not all depend on someone else's pricing page, API limits, export rules, and account risk.

2 weeks ago | [YT] | 282

Simon Høiberg

The perfect SaaS is almost completely self-serve.

A customer can understand the product, try it, pay, onboard, get support, manage the account, and cancel without waiting for someone on your team.

Every manual step adds support work, slows down the customer, and gets more annoying as the business grows.

Here are the 8 parts I would make fully self-serve 👇

Skip the Carousel

1 2 3 4 5 6 7 8 9 10

2 weeks ago | [YT] | 183

Simon Høiberg

One thing I think most people get wrong with agents:

They keep trying to make the agent smarter.

I mostly try to make everything around it more predictable.

That is why OpenClaw works so well for me.

OpenClaw sits in the middle, but I have a bunch of very boring infrastructure wrapped around it:

n8n workflows.
Webhooks.
Cron jobs.
Reusable scripts.
Markdown docs.
Runbooks.
RAG + vector DB.

Nothing fancy.

Just the stuff that turns random one-off requests into repeatable systems.

If I ask the agent to do something twice, that is usually a sign it should become a workflow.

If I explain a process once, it should probably be documented.

If something needs to happen every Monday, I should not be remembering it.

That is where the leverage comes from.

The agent uses fewer tokens because it does not need the same context explained 50 times.

The output gets more predictable because the paths are already defined.

And the whole setup gets better every time we turn a messy repeated task into a script, doc, or workflow.

A lot of people are still using AI like a browser tab.

I think the real unlock is when the agent becomes the interface to the systems you already run.

3 weeks ago | [YT] | 95

Simon Høiberg

My marketing team is getting weirdly small.

Not because I stopped doing marketing. Because a lot of the old production work is now handled by agents and specialized tools.

For YouTube:
- research comes from analytics, comments, and audience questions
- scripts get shaped with Claude
- motion graphics are built in Remotion
- editing happens in Resolve

For social:
- drafts get prepared with AI
- visuals are built in Remotion
- scheduling runs through FeedHive

For ads:
- Meta, Google, and TikTok are still the distribution layers
- agents help with angles, variations, checks, and workflow handoffs

For SEO:
- GPT-5.5 helps with keywords
- Claude helps shape content blocks
- n8n handles repeatable workflows

The founder still has to bring the taste.

But I don't think the future of marketing teams is 12 people passing tasks around in Slack all day - AI agents can do most of the work.

3 weeks ago | [YT] | 144

Simon Høiberg

Your SaaS stack usually gets bloated one reasonable decision at a time.

Support gets messy, so you add another helpdesk seat. Reporting gets annoying, so you add another dashboard. Research takes time, so you add another tool. Ops gets scattered, so you add another automation app.

None of these decisions look stupid on their own.

But after a while, the business has 40 tabs, 12 pricing pages, and data spread across too many places.

AI changes the calculation a bit.

You can keep the core stack small:

Database.
Payments.
Support inbox.
Publishing system.
Analytics.

Then let agents do the work around it:

→ read tickets
→ check metrics
→ pull context
→ draft replies
→ find patterns
→ prepare the first version

The founder still approves, rejects, changes direction, and makes the final call.

But you don't need to buy another SaaS product every time a workflow gets annoying.

1 month ago | [YT] | 95

Simon Høiberg

Most founders keep looking for the next magic tool that makes business easier.

But the people who are hard to compete with usually got good at the work others avoid.

The uncomfortable stuff.
The technical stuff.
The conversations most people postpone.

So roll up your sleve and learn these 8 skills no one else wants to learn - and you'll keep winning 👇

Skip the Carousel

1 2 3 4 5 6 7 8 9 10

1 month ago | [YT] | 213