“Vibe coding” is the latest buzz in software development, and while the hype is loud, the opportunity is real. Especially for businesses in the coming years. We explore the current state, where the risks are, and what can be done to prepare as vibe coding tools become more advanced.
Coined by Andrej Karpathy in 2025, it describes a new way of building software where developers and business users stay in “flow”, focusing on intent and outcomes while AI agents handle the code.
This matters because by 2028, Gartner predicts that 40% of new enterprise production software will be created with vibe coding techniques and tools. For businesses looking to speed up innovation and empower citizen developers, vibe coding is not a passing fad. It is a shift in how business apps will be created.
- What vibe coding actually is
- Opportunities for vibe coding business apps
- Why businesses should care now
- Risks and limitations today
- Strategic recommendations for enterprises
What vibe coding actually is
Vibe coding removes the distraction of code and focuses on results. Developers and business builders describe what they want, often in natural language or voice, and the AI does the heavy lifting. Errors are fed back to the AI to fix, keeping the human in a productive state rather than dropping into debugging.
The principles are simple:
-
Flow: staying focused on outcomes without interruptions
-
Intent: defining clear goals for what the software should achieve
-
Prototype: fast creation of testable versions of apps
-
Iteration: learning quickly by experimenting and adjusting
-
Cognitive offloading: letting AI agents handle repetitive or complex coding tasks
This is different from traditional coding or even low-code platforms. Vibe coding is about composing and orchestrating software components through conversation and intent, rather than dragging blocks or writing scripts.
Opportunities for vibe coding business apps
For businesses, vibe coding opens the door to faster, cheaper innovation. Instead of long development cycles, teams can prototype an internal tool or customer-facing app in hours, test it with users, and refine it immediately.
Citizen developers, product managers, and operations teams can be faster and more efficient by building apps around business needs without waiting in line for scarce IT resources. This results in a shorter cycle between idea and usable app, which is vital in competitive markets.
Why businesses should care now
Companies that experiment with vibe coding today will have a head start tomorrow. Those who can spin up prototypes quickly will adapt faster to market changes, respond to customer demands, and spot what ideas are worth scaling.
There is also a people angle. Developers and builders get to stay in flow, which reduces cognitive load and makes the work more enjoyable. A better developer and builder experience leads to stronger retention, and citizen developers feel empowered to contribute directly to business outcomes.
Risks and limitations today
The tools are still young. Code produced through vibe coding often lacks structure, and because the business builder may not even understand the code, errors and security flaws can go unnoticed until it is too late. For example, popular frontend vibe coding tools have had numerous issues where non-technical users accidentally expose sensitive information because they do not understand how to secure it.
There are also serious compliance considerations. Many larger businesses must adhere to certain regulations, and well-documented code and a thorough history of code changes can be critical to adhering to those regulations. There is also the question of IP. Who owns the generated code? Could it include snippets that raise intellectual property risks?
Testing, oversight, and governance are essential. For now, vibe coding is best suited to prototyping and experimentation, not mission-critical apps.
Strategic recommendations for enterprises
If you are thinking long term, here is where to focus your efforts so that as vibe coding and low/no-code tools improve, your business is ready to take advantage.
-
Culture: encourage teams to test ideas quickly while setting clear guardrails. Work with your IT team to establish these guardrails and encourage people to test safely. Many employees will likely want to try these tools anyway, providing an approved route helps avoid creating more shadow IT and security risks.
- Start small and with prototypes: the goal is to build confidence and understanding within teams, while keeping risks low. Prototypes that can then be shared with experienced developers or the IT team are a good, safe place to start.
-
Security and compliance: prioritise vendors that treat these as core features, not afterthoughts. As they grow in capabilities, your uses for vibe coding can scale easily in a safe environment.
Summary
Vibe coding is not science fiction. It is already reshaping how business apps are created, from faster prototyping to empowering more people to take part in development. The risks are real, but so is the opportunity.
Businesses that ignore vibe coding may find themselves outpaced by competitors who can learn and adapt faster. Start small, focus on pilots, and choose vendors carefully. If you prepare now, you will be ready when vibe coding matures into a standard way of building apps.