Vibe coding at work: what a non-technical CEO learned trying it
This is Part V of Matt Blumberg’s five-part series on vibe coding as a non-technical founder. Part I covered the basics, Part II covered setup, Part III covered the build, and Part IV covered testing. This final installment is about the one place most guides skip: doing this inside a real company, with real colleagues and real systems on the line.
The short version: it’s possible, but it requires a different frame than solo projects.
What Blumberg Actually Tried
Blumberg had an idea for reengineering major swaths of his company’s workflow and business processes. The trigger was AI’s impact on how work gets done inside a software company. He wanted a whole new system underneath to match.
So he started designing that system inside a Claude Project. And the design phase worked.
Where the Personal Build Gets Complicated at Work
Building something for yourself is one thing. Building something that connects to your company’s internal systems is another. The risk profile changes completely when colleagues, company data, and production integrations enter the picture.
Blumberg found that the solo vibe coding approach that works fine for personal projects runs into a real responsibility problem at work. One amateur builder carrying the quality and security burden for systems other people depend on isn’t a sustainable setup.
The Answer: A Platform That Carries the Burden
The solution Blumberg landed on was a managed internal platform. The framing matters here. It’s a safe environment where people across the company can build applications that connect into internal systems, without any single person becoming what he describes as “the security problem.”
That platform does two things a solo builder can’t personally promise:
- Quality control built into the environment, not dependent on the individual builder’s discipline
- Security guardrails that sit at the platform level, not bolted on after the fact
The implication is that vibe coding at work isn’t a “don’t do this” situation. It’s a “do this inside the right container” situation.
The Operator Takeaway
If you’re a non-technical founder or operator thinking about applying AI-assisted building to internal company systems, the lesson from this series finale is specific: the design phase with Claude is genuinely useful, even for complex workflow problems. The build phase at a company scale requires a platform that handles the quality and security accountability you can’t personally absorb.
That’s a different answer than “don’t try this at work.” It’s closer to “build the right scaffolding first, then let your team loose.”
Blumberg says more on the underlying workflow redesign is coming in subsequent posts. The series on vibe coding basics wraps here.
I’m founder of BizStack at Cagri Sarigoz LLC and a passionate advocate for entrepreneurs.
With over 14 years in tech, marketing, and AI, including my role as Head of SEO at CitizenShipper and co-founder of TaleBot at Intale AI, I’m dedicated to sharing genuine, useful product insights and tips.
At BizStack, I aim to cut through the digital noise to provide clear, actionable advice.
And more than all else, I’m a father to a (always) little girl and a husband.
Contact me at [email protected] for assistance.
