Tony Stark never had to open Jira, write a ticket, wait for a sprint, or explain to a developer what "round on both sides" means. He just said it and Jarvis made it happen.
That is what this felt like. I talked. It built. I decided. It shipped.
The thing most people miss about vibe coding is that it is not about AI writing code. It is about a founder making decisions at the speed of conversation. Every prompt I typed was a decision. Where to place it, what color, what copy, how to tag subscribers. The AI just executed faster than any developer could. That is the skill every marketer actually needs in 2026: knowing what you want and telling the machine clearly.
I am not a developer. I do not want to be one. I want to describe what I see in my head and have it exist on the internet 20 minutes later.
The glass lab and the mountain view would be nice. But honestly, Jarvis was the part that mattered.
And that part is real now.
What I Would Do Differently
Victor messaged me the next morning. "We got 11 signups overnight from the blog. But I cannot tell which articles convert best."
He was right. I would have asked Claude to build a conversion counter from day one. Right now I can see total signups in Beehiiv, but not the conversion rate per article.
I would also have asked Claude to A/B test the copy from the start. Three rounds of copy changes, but no way to measure which version actually converts better. Next time, I build the test before I push.
Frequently Asked Questions
Do I need coding experience to vibe code?
Not at all. I have zero coding experience. I describe what I want in plain English. Claude Code handles the implementation. If something looks wrong, I describe what is wrong and it fixes it.
The skill you need is not coding. It is knowing what you want. Clear instructions get clear results.
What is the difference between vibe coding and using a no-code tool?
No-code tools give you templates and drag-and-drop builders. You work within their constraints. Vibe coding has no constraints. You describe exactly what you want and the AI builds it from scratch.
I could not have auto-injected a component at the midpoint of 24 articles with any no-code tool. That required custom code. I just did not have to write it.
How long did this actually take?
Twenty minutes from first prompt to live on all 24 articles. The longest part was the copy. I spent about five minutes going back and forth on the button text and mobile font size.
The technical build, the component, the auto-injection, the Beehiiv integration, took maybe eight minutes total.
What tools do I need?
Claude Code (the CLI version of Claude), a code editor like VS Code or Cursor, and a website you can deploy to. I use Next.js on Vercel, but the approach works with any stack.
You also need a Beehiiv account if you want newsletter signups, but that part is specific to my setup.
Can I vibe code anything or just simple features?
I have vibe coded full blog deployments, LinkedIn content automation, and an AI analytics dashboard. The newsletter signup was a simple one. But the principle scales.
The more specific you are about what you want, the better the output. Vague prompts get vague results.
What if Claude Code builds something wrong?
You tell it what is wrong. "The button is square on one end, make it round on both sides." That is it. The feedback loop is instant. You do not file a bug report. You just say what you see and it fixes it.
In my 20-minute session, I made four corrections. Each one took less than 30 seconds to describe and fix.
Is vibe coding just for developers who want to code faster?
The opposite. Vibe coding is most powerful for people who cannot code at all. Developers already know how to build. Founders and marketers who know what they want but cannot implement it, those are the people who get the most value.
I went from "I need a developer for this" to "I will just tell Claude" in one afternoon. That shift changed everything about how fast we ship at Sucana.
How do I know the code Claude writes is good?
I do not read the code. I test the output. Does the signup form appear in the middle of every article? Yes. Does the Beehiiv tag show up when someone subscribes? Yes. Does it look right on mobile? Yes.
If the result works, the code is good enough. I am not trying to win a coding award. I am trying to ship features.
What was the conversion rate after adding the signup?
Too early to share real numbers. The signup went live today. I will update this article once I have 30 days of data.
What I can say is that mid-article placement consistently outperforms end-of-post placement by 3-5x based on the research Claude pulled.
Can I use this approach with ChatGPT instead of Claude Code?
ChatGPT can help you plan and write code snippets, but it cannot execute commands, push to GitHub, or test API connections directly. Claude Code runs in your terminal and does all of that.
For vibe coding where you want to go from idea to deployed in one session, Claude Code is the tool that makes it work end to end.
