Vibe Coding Changed My Solopreneur Business — Here's How

I have never passed a coding interview. I would not know where to start. I do not know what a promise chain is without looking it up. If you put me in a whiteboard coding interview, I would stare at the marker and then leave.

And yet I have built — personally, not hired someone to build — a SaaS content engine, an autonomous SEO agent, a sales AI, a social distribution bot, and the site you are reading this on. All of them run in production. All of them handle real users and real money. All of them were built with vibe coding.

If that sounds impossible, it is because the old definition of "building software" required you to think in code. Vibe coding does not. Vibe coding requires you to think in systems, describe what you want in plain language, and let AI handle the syntax. It is the single biggest shift in what a solopreneur can do alone, and it changed everything about my business.

Here is the full story.

The Before: What Building Looked Like Without Code

Two years ago, my tech stack was: Notion, Canva, Google Sheets, and tears.

I had a wellness hotel brand generating real revenue, but every piece of the digital infrastructure — the website, the booking flow, the email sequences, the content pipeline — was stitched together with no-code tools that almost worked. Webflow for the site. Zapier to connect things. Mailchimp for emails. Calendly for bookings. Airtable for the database pretending to be a backend.

It cost me about $400 a month in subscriptions, and the whole thing was fragile. Zapier would break silently. The Webflow site loaded slowly because I did not know what a CDN was. The Mailchimp sequences were clunky and I could not customize them beyond the template limits. Every time I wanted to do something slightly different — slightly outside the box the tool was designed for — I hit a wall.

I remember the specific moment I decided this was not going to work long-term. I wanted to add a simple feature to my booking flow: send a personalized pre-arrival email based on which healing protocol the guest had selected. In a real application, this is trivial. In my Zapier-Mailchimp-Airtable stack, it required four zaps, two conditional paths, a custom Mailchimp merge field, and three hours of testing. It broke twice in the first week.

That was the wall. Not a big dramatic wall — a boring, practical, infuriating wall. The tools I could use were not powerful enough. The tools that were powerful enough required me to code. And I could not code.

The Discovery: Andrej Karpathy and a Late Night in Berlin

I found vibe coding the way most people find life-changing ideas: accidentally, at 2am, when I should have been sleeping.

It was a tweet — or maybe a YouTube clip, honestly I cannot remember — from Andrej Karpathy, the former Tesla AI director. He described a way of building software where you do not write code line by line. You describe what you want to an AI, it generates the code, you run it, you tell it what is wrong, it fixes it. He called it "vibe coding" because you are not engineering — you are vibing with the AI, steering it by feel.

I watched the clip three times. My heart was doing the thing it does when something is about to change — beating slightly too fast, slightly too high in the chest.

Because he was describing exactly what I needed. Not no-code, which gives you someone else's vision with limited customization. Not traditional coding, which requires years of learning. Something in between. Something where the human provides the intent and the AI provides the implementation.

I opened my laptop. I opened Claude. I typed: "I want to build a Node.js application that sends a personalized email based on a field in a Supabase database. Walk me through it step by step."

That was the first prompt. The beginning of everything.

The First Build: A Terrible Email Bot

Let me be honest about what happened next, because the "I discovered vibe coding and immediately built amazing things" narrative is a lie.

The first thing I built was bad. The email bot worked — technically. It connected to Supabase, pulled the guest data, matched the protocol field, and sent a personalized email through Resend. But it was held together with duct tape. No error handling. No logging. No retry logic. If the database returned null for any field, the whole thing crashed silently and nobody got an email.

I did not know it was bad, because I did not know what good looked like. That is the most dangerous phase of vibe coding — the phase where the code runs and you think you are done, but you have built something that will break the moment real-world complexity touches it.

It broke four days later. A guest entered their name with an accented character — something like Muller with an umlaut — and the email template choked on it. No email sent. No error notification. I only found out because the guest emailed me asking why they had not received the pre-arrival information.

So I went back to Claude. "The email bot crashes when names contain special characters. Also, I need error handling so I know when something fails. Also, I need it to retry if the email service is temporarily down. Also, I need logging."

Claude rewrote the bot. Better this time. I learned something crucial: vibe coding is not a single prompt. It is an ongoing conversation. You build, you discover what is wrong, you describe the problem, you rebuild. The cycle is the method.

The Real Builds: What Came After

Once I understood the cycle, I started building everything.

Soulin Social — my content multiplication tool. I described it to Claude as: "I want to write one raw idea and have it turned into 35 platform-ready posts in my voice." The first version took a weekend. It was ugly and the voice matching was terrible. Over the next two months, I iterated — refining the prompts, adding platform-specific formatting rules, training it on my actual writing. Today it is the tool I am most proud of, and other solopreneurs use it too.

The SEO Agent — an autonomous bot that monitors my search rankings, identifies content gaps, checks technical SEO issues, and sends me reports via Telegram. I built this over three days with Claude Code. The prompt that started it: "I want a Node.js process that runs continuously, checks my Google Search Console data, and sends me a Telegram message when something important changes." Three days later it was running on PM2 and I have not touched it in months.

KINS Sales Agent — an AI that handles initial inquiries for the hotel brand. Guests ask questions via chat, the agent responds with accurate information about protocols, availability, and pricing, and escalates to me only when a booking is ready to close. This one took a week because the conversation flow was complex and I needed to get the tone exactly right. A sales bot that sounds like a bot loses trust immediately.

The Social Distribution Bot — monitors my content calendar, formats posts for each platform, and sends them at optimal times. Built in two days. Runs on the same server as the SEO agent.

None of these required me to understand the code at a syntactic level. I understand them at a systems level — what each piece does, how they connect, what data flows where. When something breaks, I paste the error into Claude and we fix it together. I am not a developer. I am a vibe coder, and the distinction matters.

Get essays like this — plus behind-the-scenes builds — in your inbox every week. Subscribe free →

The Prompts That Actually Work

People always ask about the prompts, so here are real ones I have used:

"I want to build a Telegram bot that connects to a Supabase database and sends me a daily summary of new signups, revenue, and any error logs from the past 24 hours. Use Node.js and the Telegraf library."

"This bot crashes when the Supabase query returns no results. Add null checking and send me a Telegram message saying 'no data for today' instead of crashing."

"I want to add a new feature to Soulin Social: when generating LinkedIn posts, check the character count and if it exceeds 3,000 characters, split it into a carousel format with a hook slide, 3-5 content slides, and a CTA slide."

"The SEO agent is using too much memory. Can you optimize the Google Search Console API calls to paginate instead of loading everything at once?"

Notice the pattern. I do not write code. I describe what I want, what is wrong, and what should happen instead. The AI writes the code. I run it. We iterate.

The prompts that fail are the vague ones: "make it better" or "fix the bug." The prompts that work are specific about the problem and the desired outcome. You do not need to know how to code. You do need to know how to describe a system clearly. That is a different skill, and it is learnable.

The Mistakes I Made So You Do Not Have To

Mistake 1: Not using version control early enough. I built my first three projects without git. When I broke something, I could not go back to the working version. I lost an entire day of work on the email bot because I overwrote a file. Learn "git init" and "git commit" before you learn anything else. It takes five minutes and it will save you days.

Mistake 2: Building too much at once. My first attempt at Soulin Social was a 2,000-line monolith that did everything — content generation, scheduling, analytics, voice training. It was impossible to debug. I scrapped it and rebuilt it as small, separate pieces that talk to each other. Start small. Ship one thing. Then add the next.

Mistake 3: Not testing with real data. I tested the SEO agent with my own site only. The first time a user with a different site structure tried it, it broke in seven places. Real data is always messier than your test data.

Mistake 4: Ignoring security. My first Supabase setup had no row-level security. Anyone with the API key could read all the data. Claude helped me fix this, but I should have asked about security from the first prompt. Always ask: "What are the security considerations for this setup?"

What Vibe Coding Actually Costs

The tools:

• Claude Pro: $20/month
• Cursor Pro: $20/month
• Supabase: $25/month
• Vercel: $20/month
• Server for bots: $5-10/month

Total: about $90-95/month.

The time: the first project took me a weekend. Now I can ship a new bot or feature in hours. The learning curve is real but short — weeks, not years. And every project teaches you patterns that make the next one faster.

Compare this to hiring a developer: $5,000-15,000 for a custom application, weeks of back-and-forth, and you still cannot modify it yourself when your needs change.

What This Means for Solopreneurs

Vibe coding is not just a new way to build software. It is a power shift. For the first time in the history of building digital products, the bottleneck is not technical skill — it is clarity of vision.

If you know what you want to build and you can describe it clearly, you can build it. Today. Not after a coding bootcamp. Not after hiring a developer. Not after raising a round. Today, from your laptop, with an AI that writes the code while you steer.

This is what I teach at Soulin. Not how to code — how to build. How to think in systems. How to describe what you want clearly enough that AI can implement it. How to iterate when things break. How to go from idea to production as a single person with no technical background.

Because the truth is: the solopreneurs who figure this out in the next two years will have an absurd advantage over everyone else. They will be able to build custom tools, automate their specific workflows, and ship products at a speed that was previously impossible without a team.

I know this because I am living it. From a cafe in Canggu to an apartment in Berlin, from a spreadsheet to a SaaS product, from "I cannot code" to "I built this."

The gap between idea and execution just collapsed. And I am not going back.

This is what Soulin teaches — not code, but how to build. If you want the exact workflows, prompt libraries, and system architectures I use, they are inside the membership. But start here. Start with one prompt and one problem you want to solve.