Client took over development by vibe coding. What to do?

I’ve worked on a project for one year now, a marketplace web application for one of my clients. It involves a web shop frontend, integration with suppliers, payment platforms, product management, stock syncing, and much more. I built the project from scratch with open source components, guided other developers on the project, and was leading all the technical decisions.Last year I started using LLM’s for cumbersome tasks, and since the beginning of this year I started working with Claude Code to implement features. Still, I always need to think about the implementation, and actively direct and correct the bot. As many of you will know, it can speed up development, but I still need to use my more than ten years of experience as a developer. I thought the project for my client would be safe.This changed when they started developing some of their own, much smaller and simpler projects on an AI-powered no-code platform. They immediately concluded this also must be applied to the marketplace project that will run their core business. I tried to convince them with good arguments that this wouldn’t be a good idea, but failed. Since I am not the owner of the code, and don’t want to be a gatekeeper, I instructed them how to participate in the development with their coding agents.The additions they made to the codebase in only a week are huge, around 10,000 lines of code. To be honest, most of the features they introduced are functional, but the performance of the application has suffered already. What I am most concerned about is the maintainability of the project and how we will get this live. Before, I had a clear mental model of how everything was built, and I added human readable documentation where needed. They still want me to participate in the project and work on the most critical parts of the application, DevOps and other parts they and their coding agents will not succeed in themselves.It seems some people are possessed by the promises of AI-tools, and do not have

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

72

out of 100

Verdict

BUILD

high confidence

Competition

10

competitors found, emerging market, funded players

Trend

No signal yet

An AI-powered tool to transform messy, unmaintainable 'vibe coded' software into secure, scalable, and polished production-ready applications for mid-market teams.

The pain

Developers and companies are struggling with rapidly accumulating technical debt, performance degradation, and maintainability nightmares caused by AI-generated 'vibe code' that lacks architectural structure and is difficult to debug or understand.

The gap

While general code analysis tools and expensive human services exist, there is a gap for an automated product specifically designed to address the unique architectural and maintainability challenges of AI-generated code for mid-market teams, offering actionable refactoring guidance rather than just security or linting.

Build angle

Focus on an 'Architectural Health Check' MVP that scans AI-generated code, highlights structural flaws and maintainability hotspots, and provides prioritized, AI-assisted refactoring recommendations (e.g., 'extract service X from module Y'). Target mid-market companies or specific developer roles (Lead Devs, CTOs).

Strengths

  • Extremely real and severe pain point, explicitly confirmed by market data and user frustrations.
  • Rapidly growing market driven by AI adoption, with strong investor interest (Qodo $70M Series B).
  • Clear willingness to pay, evidenced by custom service pricing and existing tool subscriptions.
  • Specific, addressable complaints that current generic tools don't fully solve.
  • High leverage for a solo builder in a cutting-edge field (AI, code analysis).

Risks

  • High technical complexity for a solo builder to create a truly effective architectural analysis and refactoring tool.
  • Crowded competitive landscape with funded players (Qodo, SonarQube, DeepSource) and established open-source tools.
  • Risk of being 'yet another code analysis tool' if the unique angle for AI-generated architectural debt isn't sharp enough.
  • Monetization could be challenging against free/cheaper alternatives or highly integrated enterprise solutions.
  • Validation needed to confirm mid-market teams prefer a product over human services for deep architectural issues.

Next steps

  1. Conduct in-depth interviews with Lead Developers/CTOs at mid-market companies that are heavily using AI for coding. Focus on their specific pain points related to architectural quality and maintainability, beyond security or simple code smells.
  2. Develop a very focused MVP concept for an 'AI Code Architectural Health Report' that could be demonstrated with mock data. Get feedback on the most critical architectural issues and the ideal format for actionable recommendations.
  3. Research specific open-source tools or academic papers on AI code quality assessment and architectural analysis to evaluate feasibility and potential building blocks for a solo builder. Explore ways to integrate with existing AI coding assistants (e.g., Claude Code, GitHub Copilot) to offer 'pre-commit' architectural analysis.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Client took over development by vibe coding. What to do?”.

Open FlyBot