Matt Graham (@Matt_Graham_)

When we partnered with Bubble, their original vision wasn't to build a network of agencies like RapidDev. It was the opposite: give people the tools to build for themselves. So when I got asked whether agencies still make sense in a world where AI can spin up software for anyone, I gave the honest answer. People will always hire vendors. I was on a walk-and-talk with a guy still selling websites for $10K. It doesn't matter how good the technology gets, there's an asymmetry of information. Busy owners don't want to learn the tools. They want the expert who's done it a thousand times, who knows how to structure a site, write the copy, get it right. Prices will collapse on the commodity end. That's already happening. But there will always be clients who want a professional job, and don't mind paying for it. That's the lane we're doubling down on at RapidDev. And it's why our bet on Bubble keeps paying off.

This is going viral on X. 1.5M+ views. And I know exactly why. We see it every single week. The app works, and revenue is real. That's not the problem. Vibe coding gives you the perception that you're on the right track. But you don't know what you don't know. You're just at the tip of the iceberg. The AI just kept building. Nobody was thinking about structure. This is vibe coding rescue. Founders come to us after this exact moment. And we have to go through the painful process of explaining what's actually there. The tools are impressive. And they're getting better. But right now, for most real builds, this is where it ends up. On @Bubble, you see what you're building as you build it. No mystery code piling up in the background. If this is where you're at, DM me. We can help.

From $25M to $70M in 3 years! No dev team. Just one non-technical builder with @Bubble. Simon-klobas helped a construction company replace 5 disconnected SaaS tools that couldn't talk to each other with a custom app on @Bubble. He connected the entire workflow: site managers to executives to finance. With zero overhead cost added! Traditional businesses are sitting on razor-thin margins that technology could fix overnight. But they never had access to engineering resources like this before. Simon's replicated this across four companies now: all non-technical builds, all solo operations, all on @Bubble. The ROI is stupid good. And the opportunity is massive. That's what @Bubble makes possible.

What would you do with an extra $250,000 in runway? For many founders, that’s already happening. @Bubble surveyed 793 builders who've used both vibe coding and visual development on real projects. When they built with visual development: 84.9% reduced their need to hire engineers 55.1% saw significant reductions That translated into real savings: 27.4% saved $10K–$50K per year 21.7% saved $50K–$250K per year 8% saved $250K+ 2.6% saved $1M+ Visual development changes the order of operations. Build → validate → get signal → THEN hire intentionally. That's the leverage @Bubble gives founders. Founders who understand this don't wait for permission to start.

Visual Coding vs Vibe Coding — when should you use each? Not every product needs “vibes & velocity”. And not every product needs enterprise-grade infrastructure either. Vibe coding works best in the early stages — when you’re exploring an idea, testing a concept, building an MVP, or creating internal tools where speed matters more than stability and occasional downtime isn’t business-critical. "Move fast and break things." But as soon as real users start depending on your product, the trade-offs change. Reliability becomes a feature, predictable performance starts to matter, compliance and security enter the roadmap, and infrastructure problems begin taking time away from actual product development. That’s typically where platforms like Bubble start to make sense: when your app is expected to stay online, you don’t have a dev team constantly handling operational issues, you don’t want to manage hosting or infrastructure yourself, and non-technical teams still need the ability to operate and evolve the product. It’s not Bubble vs vibe coding. It’s choosing the right approach for the stage you’re in. Vibe coding gives flexibility and speed. Visual coding gives stability and operational simplicity. Different stages, different constraints — the tool should match the problem, not the hype.