I Built Continio by Vibe Coding. Here's What That Actually Means.

There's a version of this conversation I keep having, and I imagine a lot of solo founders do too.

Someone finds out I built a product without being a developer. The response is either excitement (you built this yourself?!) or quiet suspicion (but is it... real?). Sometimes both from the same person.

So I want to be straight about it. I vibe coded Continio. I am not a developer. I have never written a line of code in my life that wasn't the result of a conversation with an AI. And I want to tell you what that actually looks like, because the internet version of vibe coding is missing most of the story.

What the internet says vibe coding is

Type a prompt. Get an app. Ship it. Become a millionaire.

That is the version being sold right now. And I understand why it's appealing. The idea that the technical barrier to building something has finally come down for people who have ideas but not computer science degrees? That is a genuinely exciting thing.

But it is about 20% of the reality.

What vibe coding actually is, at least for me

It is hours of conversation. It is understanding what you are building well enough to explain it to something that has no intuition and no assumptions. It is catching when the AI has solved a different problem to the one you asked about. It is knowing when a fix has introduced a new bug. It is being the one who holds the product vision when the tool just wants to make the tests pass.

Continio has been built across months of sessions. I have five core files. I have caught regressions, diagnosed database bugs, rebuilt pipelines, scoped features carefully and pushed back on implementations that technically worked but felt wrong. I have made hundreds of product decisions that no AI made for me.

That is not the same as writing the code myself. But it is also not the same as pressing a button and walking away.

Why I did it this way

Because the alternative was not hiring a developer. The alternative was not building Continio at all.

I had no funding. No co-founder. No income to redirect toward a technical hire. I had a product insight I believed in, a problem I had lived personally, and access to a tool that meant I could actually start.

But there's something else I haven't said yet, and it matters. Even if I'd had the budget to hire a developer from day one, I'm not sure it would have worked the way I needed it to. The problem Continio solves is something I'd lived personally, across years. The frustration of context loss, the cognitive overhead of re-explaining yourself, the specific way fragmented AI conversations degrade your thinking. I understood it the way you understand something you've had in your body, not just your head.

To hand that to a developer in a brief would have been to flatten it. The product would have come back technically correct and fundamentally off. Being able to think out loud, iterate in real time, and shape the thing against my own understanding of the problem - that's not something I could have outsourced. The AI-assisted build process was the only way I could hold the vision and build the product at the same time.

The question was never vibe coding vs. proper engineering. The question was vibe coding vs. nothing.

What I think the real risks are

I am not going to pretend there are no risks. The critics are not wrong about everything.

AI-generated code can be messy. It can skip security steps. It can produce something that works on the surface and has problems underneath. These are real concerns and the discourse around them is legitimate.

What I'd push back on is not the value of engineering - real engineers do things I can't. They think in systems. They catch edge cases I wouldn't see. They write code that's maintainable by someone other than the AI that wrote it. I have enormous respect for that expertise and I'm not suggesting it's equivalent to what I do. What I am saying is that the existence of that expertise doesn't close off the path for someone without it. The two things can both be true.

The answer isn't "only developers should build things." But it also isn't "anyone can build anything without understanding what they've made." It's: understand what you have built. Verify it. Test it. Know your limitations and be honest about them. Get proper engineers to review the foundations when you have the resources to do it.

I know what Continio does and does not do. I know where the risks are. I know the parts that need hardening as it grows. That kind of ownership does not require me to have written every line myself.

On transparency

A few people have suggested I should not tell people it was built this way, because it will put them off.

I disagree. Not because I am naive about perception, but because I think the cover-up is worse than the thing. If someone finds out later that I obscured how it was built, that is a trust problem. If someone knows from the start and chooses to use it anyway because it works, that is a relationship.

The honest version is this: Continio was built by a solo founder, using AI as a development partner, because that was the only way it was getting built. As it grows, I will bring in engineers to harden the code. Right now, the person who understands it best is me, and I built it because I lived the problem it solves.

That is not a disclaimer. That is a founding story.

What I actually think about vibe coding

It is not magic. It is not the end of real engineering. It is also not a shortcut for people who do not care about what they are making.

For me, it has been a way to build something real, from nothing, with no team and no runway. The tool made it possible. The judgement, the product thinking, the care about whether it actually works for real people: that part still came from a human.

It came from me.

And if that makes Continio more interesting to you, not less, then you are probably the kind of person it was built for.

---