[{"data":1,"prerenderedAt":563},["ShallowReactive",2],{"footer-vacatures-en":3,"use-case-gegenereerde-code-niet-meer-begrijpelijk-en":4,"content-by-keys-offers-en-vibe-code-rescue-audit,rescue-sprint":94,"content-by-keys-useCases-en-ai-code-breekt-steeds,vibe-code-project-vastgelopen":357,"content-by-keys-cases-en-":510,"content-by-keys-buyerTriggers-en-vastgelopen-met-ai":511},[],{"id":5,"title":6,"body":7,"description":11,"desiredOutcome":14,"extension":26,"hero":27,"key":29,"meta":30,"navigation":31,"path":32,"problem":33,"proof":45,"recognition":57,"recommendedApproach":72,"relations":74,"seo":84,"stem":87,"summary":88,"visuals":89,"__hash__":93},"useCases_en\u002Fuse-cases\u002Fgegenereerde-code-niet-meer-begrijpelijk.md","Nobody understands the generated code anymore",{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],{"intro":15,"items":16},"You don't need to know every file by heart. But an engineer does need to be able to understand where functionality belongs and what a change affects.\n",[17,20,23],{"title":18,"text":19},"An understandable structure","Responsibilities and boundaries in the codebase are recognisable again.\n",{"title":21,"text":22},"Fewer surprises","Engineers can better predict what a change affects elsewhere.\n",{"title":24,"text":25},"AI tools become useful again","Good structure also gives coding agents better context to work with responsibly.\n","md",{"intro":28},"AI can produce code faster than a team can understand it. That works until every change first requires archaeological research. We help you bring the codebase back to software people can get a grip on again.\n","gegenereerde-code-niet-meer-begrijpelijk",{},true,"\u002Fuse-cases\u002Fgegenereerde-code-niet-meer-begrijpelijk",{"intro":34,"causes":35},"Code that compiles is not automatically a coherent software system.\n",[36,39,42],{"title":37,"text":38},"Every task was solved locally","Today's solution doesn't always fit last month's choices.\n",{"title":40,"text":41},"Architecture stayed implicit","Technical boundaries only exist in developers' heads, or not at all.\n",{"title":43,"text":44},"Cleaning up kept being postponed","AI makes adding cheap, so removing and consolidating get relatively little attention.\n",{"intro":46,"points":47},"With a messy codebase, the main job is judging what is essential, which debt really hurts, and how to stop the clean-up from becoming the new problem.\n",[48,51,54],{"title":49,"text":50},"Understand first","We don't blindly change code before it's clear what role that code plays.\n",{"title":52,"text":53},"Risk over beauty","Not every ugly construction needs to be rewritten right away.\n",{"title":55,"text":56},"Document what matters","Important architecture choices are made explicit so knowledge doesn't disappear again.\n",{"intro":58,"signals":59},"The code is usually readable enough. It's just that nobody understands how the whole fits together anymore.\n",[60,63,66,69],{"title":61,"text":62},"There are several solutions to the same problem","Old and new implementations live side by side and nobody knows which one leads.\n",{"title":64,"text":65},"Files and components keep growing","More and more responsibilities end up in the same places.\n",{"title":67,"text":68},"Deleting feels dangerous","Nobody knows for sure whether seemingly unused code is needed somewhere after all.\n",{"title":70,"text":71},"Every prompt needs enormous context","You have to explain to the AI over and over how large parts of the project work.\n",{"intro":73},"A Vibe Code Rescue Audit first maps the actual structure, duplication and technical risks. Then we only tackle the parts that actually block development. We don't refactor for the sake of it.\n",{"buyerTriggerKeys":75,"primaryOfferKey":77,"offerKeys":78,"caseKeys":80,"relatedUseCaseKeys":81},[76],"vastgelopen-met-ai","vibe-code-rescue-audit",[77,79],"rescue-sprint",[],[82,83],"ai-code-breekt-steeds","vibe-code-project-vastgelopen",{"title":85,"description":86},"Generated code no longer understandable? | 9to5 software","AI-generated code that nobody understands any more? 9to5 maps the architecture and technical debt and makes the codebase manageable again.\n","use-cases\u002Fgegenereerde-code-niet-meer-begrijpelijk","The software grows fast, but its structure and technical choices have become so opaque that changes are getting riskier and riskier.\n",{"hero":90,"problem":91,"proof":92},"sq-tangle-knot","sq-foundation-build","ls-rescue-repair","Xz-f4kDEFuXwEdtsDZ6LRB0w0C3Rm0d5OcJI8Pk0jts",[95,237],{"id":96,"title":97,"body":98,"catalogue":102,"cta":103,"description":11,"extension":26,"fit":108,"hero":114,"key":77,"meta":117,"navigation":31,"next":118,"outcome":131,"path":143,"price":144,"process":147,"proof":162,"relations":176,"scope":190,"seo":223,"stem":226,"summary":227,"summaryPanel":228,"visuals":233,"__hash__":236},"offers_en\u002Foffers\u002Fvibe-code-rescue-audit.md","Vibe Code Rescue Audit",{"type":8,"value":99,"toc":100},[],{"title":11,"searchDepth":12,"depth":12,"links":101},[],null,{"title":104,"body":105,"primaryCta":106,"local":107},"No idea what to fix anymore?","Let us first figure out what you actually have. Then you can make a technical decision without blindly prompting on or throwing everything away.\n","Book a Rescue Audit","Vibe Code Rescue by senior engineers from Delft, for teams in Delft, The Hague, Rotterdam and the surrounding area.\n",{"title":109,"intro":110,"useCaseKeys":111},"When is this offer a fit?","When you sense something is technically wrong, but the actual cause or extent isn't clear yet.\n",[112,113,29,83],"vibe-coded-app-professionaliseren","ai-agent-niet-betrouwbaar",{"headline":115,"intro":116,"primaryCta":106},"Find out what is really wrong before you rebuild everything.","You already have software, but no longer know which problems are superficial and which are structural. We reconstruct how the system works, separate technical debt from real risks and give you a prioritised route forward.\n",{},{"title":119,"items":120},"What happens next?",[121,124,128],{"title":122,"text":123,"offerKey":79},"A clear rescue goal?","Then we can tackle it in a focused Rescue Sprint.\n",{"title":125,"text":126,"offerKey":127},"Turns out to be a bigger build project?","Then we scope Build & Integrate as a fixed engagement.\n","build-integrate",{"title":129,"text":130},"Turns out little is wrong?","Then we'll simply tell you. A follow-up is not required.\n",{"title":132,"items":133},"Afterwards you have...",[134,137,140],{"title":135,"text":136},"Technical grip on what is there","Architecture, key dependencies and critical risks are clear again.\n",{"title":138,"text":139},"A prioritised rescue plan","You know what can stay, what really needs to change and in which order.\n",{"title":141,"text":142},"A decision on the follow-up approach","Fixing, partially rebuilding, developing further at a larger scale or doing nothing becomes a conscious choice.\n","\u002Foffers\u002Fvibe-code-rescue-audit",{"label":145,"type":146},"€2,950 excl. VAT","fixed",{"title":148,"steps":149},"How it works.",[150,153,156,159],{"title":151,"text":152},"Confirm the rescue goal","We determine which questions the Audit needs to answer and where the biggest uncertainty lies.\n",{"title":154,"text":155},"Reconstruct code + system","We read the architecture, code, deployment, data flows and relevant dependencies.\n",{"title":157,"text":158},"Prioritise problems","We distinguish cosmetic debt, development blockers and real production or security risks.\n",{"title":160,"text":161},"Rescue plan + debrief","You get a concrete route with what can stay, what needs to change and what makes sense next.\n",{"title":163,"intro":164,"points":165,"caseKeys":175},"Why should you believe this?","Assessing an existing codebase takes more than an automated quality score. It takes senior engineers who can see which problems actually hurt.\n",[166,169,172],{"title":167,"text":168},"Existing software is where we work","A messy or AI-generated codebase is no reason to automatically start over.\n",{"title":170,"text":171},"Software engineering and AI","We look at both regular production-grade problems and AI-specific failure modes.\n",{"title":173,"text":174},"Follow-up work is not a requirement","If the best conclusion is that your current route is fine, the engagement can end there.\n",[],{"buyerTriggerKeys":177,"useCaseKeys":178,"relatedOfferKeys":188,"caseKeys":189},[76],[112,179,113,29,82,180,181,182,183,184,185,186,187,83],"ai-prototype-naar-productie","security-en-privacy-ai-oplossing","ai-oplossing-te-langzaam","ai-oplossing-te-duur","technische-second-opinion-ai","ai-project-overnemen-van-andere-leverancier","ai-experiment-heeft-echte-gebruikers","prototype-naar-onderhoudbaar-softwareproduct","weg-bij-ai-platform-of-leverancier",[79,127],[],{"title":191,"intro":192,"activities":193,"deliverables":205,"exclusions":216},"What is included in this offer?","A technical diagnosis of one existing application or codebase, aimed at decision-making.\n",{"intro":194,"items":195},"We look broadly enough to find structural causes, without turning it into a theoretical code review.\n",[196,197,198,199,200,201,202,203,204],"Examining architecture and code quality","Assessing dependencies and technical debt","Reviewing authentication and authorisation","Examining the data layer and relevant integrations","Assessing deployment and error handling","Reviewing tests, logging and monitoring","Listing security risks at a high level","Examining AI-specific failure modes","Assessing maintainability and lock-in",{"intro":206,"items":207},"You get a technical verdict you can actually base a follow-up on.\n",[208,209,210,211,212,213,214,215],"Architecture overview","Prioritised list of problems and risks","What can stay","What needs to be adjusted","What may need to be redone","Advice: fix \u002F partially rebuild \u002F rebuild","Proposed order and size of the follow-up","Technical debrief with a senior engineer",{"intro":217,"items":218},"The Audit delivers understanding and a plan. Major fixes don't quietly become part of the analysis.\n",[219,220,221,222],"Full repair of the codebase","Complete rewrite","Unbounded pentest or formal security audit","Product development beyond small diagnostic changes",{"title":224,"description":225},"Vibe Code Rescue Audit | Stuck with AI code | 9to5 software","Vibe-coded app (Lovable, Cursor, Bolt, Replit) or AI project stuck? 9to5 examines architecture, code, security, tests and deployment and gives you a rescue plan.\n","offers\u002Fvibe-code-rescue-audit","We examine what you have, what can stay as it is, where the real risks are and how you can move forward responsibly again.\n",{"qualifier":229,"result":230,"duration":231,"nextStep":232},"Fixed price · one existing application or codebase","Technical grip on what exists and a prioritised rescue plan","About two weeks","A Rescue Sprint for the most important problem, or continue yourself",{"hero":90,"proof":234,"process":235},"sq-orient-options","ls-route-converge","IWSlwlvSU82rOHwWTXtSCvLbfXjNUybu2L5bZ-96IJY",{"id":238,"title":239,"body":240,"catalogue":102,"cta":244,"description":11,"extension":26,"fit":249,"hero":256,"key":79,"meta":259,"navigation":31,"next":260,"outcome":271,"path":282,"price":283,"process":286,"proof":299,"relations":312,"scope":317,"seo":344,"stem":347,"summary":348,"summaryPanel":349,"visuals":354,"__hash__":356},"offers_en\u002Foffers\u002Frescue-sprint.md","Rescue Sprint",{"type":8,"value":241,"toc":242},[],{"title":11,"searchDepth":12,"depth":12,"links":243},[],{"title":245,"body":246,"primaryCta":247,"local":248},"Do you know what's broken?","Share the technical problem with us. If it's sharp enough, we don't need to sell you an extra audit first.\n","Plan a Rescue Sprint","Temporary senior engineering from Delft, available for technical AI and software problems in the region.\n",{"title":109,"intro":250,"useCaseKeys":251},"When the technical problem is sharp enough to fix right away.\n",[252,253,254,255],"vast-op-auth-database-of-rechten","ai-koppelen-aan-bestaande-systemen","tests-evals-monitoring-voor-ai","developmentteam-loopt-vast-met-ai",{"headline":257,"intro":258,"primaryCta":247},"One clear technical problem. One week of senior engineering.","You know where the problem is, but your team can't solve it or lacks exactly the specialist experience needed right now. We step in with focus, fix the hard part and make sure you can move forward again afterwards.\n",{},{"title":119,"items":261},[262,265,268],{"title":263,"text":264},"Done? Then we leave.","If you can continue independently, the Sprint has succeeded.\n",{"title":266,"text":267,"offerKey":79},"Another clear rescue goal?","Then you can use a next Sprint as a new fixed scope.\n",{"title":269,"text":270,"offerKey":127},"Turns out bigger than a Sprint?","Then we scope Build & Integrate. If the cause is unclear after all, the Rescue Audit comes first.\n",{"title":132,"items":272},[273,276,279],{"title":274,"text":275},"The concrete problem is tackled","The agreed technical blocker is solved or demonstrably moved forward.\n",{"title":277,"text":278},"The change is set up professionally","Where needed we add tests, evals, guardrails or production preconditions.\n",{"title":280,"text":281},"Your team can move forward again","Code, choices and follow-up are documented and technically handed over.\n","\u002Foffers\u002Frescue-sprint",{"label":284,"suffix":285,"type":146},"€5,950 excl. VAT","per Sprint",{"title":148,"steps":287},[288,290,293,296],{"title":151,"text":289},"We check whether the problem is sharp enough for a Sprint.\n",{"title":291,"text":292},"Understand context + code","We read exactly enough to intervene responsibly.\n",{"title":294,"text":295},"Solve + test","We implement the fix and add the quality layer it needs.\n",{"title":297,"text":298},"Document + hand over","We record choices and make sure your team can continue independently again.\n",{"title":163,"intro":300,"points":301,"caseKeys":311},"This is exactly the kind of work senior engineers are valuable for: quickly understanding an unfamiliar codebase, solving the hard part and leaving again.\n",[302,305,308],{"title":303,"text":304},"Senior AI + software engineers","We step in where it gets complicated and leave when it's done.\n",{"title":306,"text":307},"We work in what is already there","We don't expect you to migrate everything to our favourite stack first.\n",{"title":309,"text":310},"Yours as soon as it's done","We document, hand over and leave as soon as you can continue on your own.\n",[],{"buyerTriggerKeys":313,"useCaseKeys":314,"relatedOfferKeys":315,"caseKeys":316},[76],[252,253,254,255],[77,127],[],{"title":191,"intro":318,"activities":319,"deliverables":328,"exclusions":337},"One Sprint has one clear rescue goal. That boundary keeps it fast and honest.\n",{"intro":320,"items":321},"We do what is technically needed to tackle the agreed problem responsibly.\n",[322,323,324,325,326,327],"Understanding the relevant code and context","Reproducing and confirming the root cause","Implementing a targeted fix or technical improvement","Adding relevant tests, evals or checks","Adjusting integration, deployment or data where the goal requires it","Recording and handing over technical choices",{"intro":329,"items":330},"Working engineering in the existing codebase, not an advice document someone else still has to carry out.\n",[331,332,333,334,335,336],"Implemented technical change","Relevant tests or quality checks","Working code in the agreed environment","Documentation of key choices","Handover to your own team","Clarity about any remaining follow-up",{"intro":338,"items":339},"A Sprint is bounded and doesn't quietly turn into an open-ended project.\n",[340,341,342,343],"Multiple separate rescue goals at once","Unbounded refactor of the whole codebase","Major new product features beyond the rescue goal","Automatic extension or retainer",{"title":345,"description":346},"Rescue Sprint | Senior AI & software engineering | 9to5 software","One week of senior engineering for a technical blocker in AI, an AI agent or vibe-coded software. Repair, test, document and hand over, €5,950 excl. VAT.\n","offers\u002Frescue-sprint","One week of senior engineering focused on one clear technical rescue goal. No retainer and no endless engagement.\n",{"qualifier":350,"result":351,"duration":352,"nextStep":353},"Per Sprint · one clear rescue goal","The agreed technical blocker solved, tested and handed over","One week","You take it over, or another Sprint for a new goal",{"hero":90,"proof":355,"process":92},"sq-guardrails-check","RBo-3uCvL4DWueBHoZFGrqKFPfwCZ1QLbywOlnLG0NY",[358,434],{"id":359,"title":360,"body":361,"description":11,"desiredOutcome":365,"extension":26,"hero":377,"key":82,"meta":379,"navigation":31,"path":380,"problem":381,"proof":393,"recognition":405,"recommendedApproach":420,"relations":422,"seo":427,"stem":430,"summary":431,"visuals":432,"__hash__":433},"useCases_en\u002Fuse-cases\u002Fai-code-breekt-steeds.md","Every new AI code change breaks something else",{"type":8,"value":362,"toc":363},[],{"title":11,"searchDepth":12,"depth":12,"links":364},[],{"intro":366,"items":367},"You want to be able to make changes again without discovering afterwards, every time, what collateral damage they caused.\n",[368,371,374],{"title":369,"text":370},"Changes stay local","A change only has effects in the places where you expect them.\n",{"title":372,"text":373},"Regressions are found quickly","Tests and checks flag problems before users discover them.\n",{"title":375,"text":376},"Development becomes truly fast again","Less repair work means AI-assisted development saves time once more.\n",{"intro":378},"You ask for one small change and three other things stop working. That is usually not bad luck. It points to missing boundaries, tests or technical coherence. We find out where that fragility comes from.\n",{},"\u002Fuse-cases\u002Fai-code-breekt-steeds",{"intro":382,"causes":383},"AI coding tools are strong at local changes. They don't automatically know all the implicit agreements that run through a growing product.\n",[384,387,390],{"title":385,"text":386},"Tests don't cover critical agreements","The AI gets little feedback when a change breaks existing functionality.\n",{"title":388,"text":389},"Parts are too tightly coupled","A local change affects state, data or behaviour in unexpected places.\n",{"title":391,"text":392},"Interfaces are not clear enough","The codebase doesn't show well enough which contracts must stay stable.\n",{"intro":394,"points":395},"The AI doesn't need to write less code. The codebase needs enough feedback and structure to make errors visible quickly.\n",[396,399,402],{"title":397,"text":398},"Tests where they add value","We test critical contracts and flows, not every detail for a percentage.\n",{"title":400,"text":401},"Clear technical boundaries","Fewer hidden couplings means fewer unexpected regressions.\n",{"title":403,"text":404},"Practical AI guardrails","The development workflow helps coding agents stay within the architecture.\n",{"intro":406,"signals":407},"The pattern often becomes visible once the codebase grows and several parts depend on each other.\n",[408,411,414,417],{"title":409,"text":410},"A simple feature causes unexpected bugs","Functionality on other screens or flows suddenly stops working.\n",{"title":412,"text":413},"The same bug comes back later","A bug gets fixed, but nothing prevents it from reappearing.\n",{"title":415,"text":416},"Refactors are almost impossible","Too many parts turn out to depend on each other implicitly.\n",{"title":418,"text":419},"You mostly rely on clicking through by hand","After every change someone has to walk through the whole application to see whether everything still works.\n",{"intro":421},"A Vibe Code Rescue Audit first finds out why changes cause so much collateral damage. We can then tackle the most important technical causes in a focused Rescue Sprint.\n",{"buyerTriggerKeys":423,"primaryOfferKey":77,"offerKeys":424,"caseKeys":425,"relatedUseCaseKeys":426},[76],[77,79],[],[29,254],{"title":428,"description":429},"AI code keeps breaking something else | 9to5 software","Does AI-generated code keep breaking existing functionality? 9to5 examines architecture, tests and dependencies and makes changes safer.\n","use-cases\u002Fai-code-breekt-steeds","New features ship quickly, but regressions, unexpected errors and repair work take more and more time.\n",{"hero":90,"problem":355,"proof":92},"Wac_TNYZVCtWw1yfVa0Y41CtfZ--5euF9AMy8eplg3g",{"id":435,"title":436,"body":437,"description":11,"desiredOutcome":441,"extension":26,"hero":453,"key":83,"meta":455,"navigation":31,"path":456,"problem":457,"proof":469,"recognition":481,"recommendedApproach":496,"relations":498,"seo":503,"stem":506,"summary":507,"visuals":508,"__hash__":509},"useCases_en\u002Fuse-cases\u002Fvibe-code-project-vastgelopen.md","We've vibe-coded ourselves into a corner",{"type":8,"value":438,"toc":439},[],{"title":11,"searchDepth":12,"depth":12,"links":440},[],{"intro":442,"items":443},"You don't want to stop AI-assisted development. You want to be able to build again without every change introducing a new technical risk.\n",[444,447,450],{"title":445,"text":446},"Grip on the codebase again","You understand how the most important parts fit together and where you can safely make changes.\n",{"title":448,"text":449},"Changing without roulette","New features no longer unexpectedly break other parts of the application.\n",{"title":451,"text":452},"Able to carry on yourself","The technical foundation and way of working are clear enough to build on independently with AI tools again.\n",{"intro":454},"At first it felt like you had superpowers, with a new feature every evening. Then came the point where the AI mainly found new ways to move old problems around. Often you don't have to redo everything.\n",{},"\u002Fuse-cases\u002Fvibe-code-project-vastgelopen",{"intro":458,"causes":459},"AI coding tools are very good at momentum. But without clear architecture, tests and technical boundaries, that momentum can eventually work against you.\n",[460,463,466],{"title":461,"text":462},"Local solutions pile up","Every prompt solves the problem of that moment, but doesn't automatically take the architecture of the whole into account.\n",{"title":464,"text":465},"Technical feedback is missing","Without good tests, types, conventions and deployment checks, the AI only notices late that a change causes damage somewhere else.\n",{"title":467,"text":468},"The codebase itself becomes the bottleneck","More and more context is needed to make a change properly. So fast building slowly becomes slow and unpredictable again.\n",{"intro":470,"points":471},"This is where senior software engineering makes the difference: understanding an existing codebase, reducing technical risks and making sure your own team can continue independently afterwards.\n",[472,475,478],{"title":473,"text":474},"We're not against vibe coding","Building yourself with AI can actually be very effective when the technical foundation stays good enough.\n",{"title":476,"text":477},"We don't automatically start over","First determine what is usable, only then decide what really has to change.\n",{"title":479,"text":480},"The idea is that you build again","A rescue has succeeded when you don't need 9to5 for every next feature afterwards.\n",{"intro":482,"signals":483},"Vibe coding rarely gets stuck all at once. First small technical problems pile up, until more and more prompts are needed to change anything.\n",[484,487,490,493],{"title":485,"text":486},"One fix breaks something else","A seemingly small change suddenly causes errors in places you didn't touch.\n",{"title":488,"text":489},"The AI keeps suggesting bigger refactors","According to the coding tool, even simple changes seem to need a major rework of the code.\n",{"title":491,"text":492},"Nobody knows what leads anymore","Several implementations, old files and half-replaced solutions exist side by side.\n",{"title":494,"text":495},"You hardly dare touch working code","The project still works, but every change feels like you might knock over something important.\n",{"intro":497},"Don't keep prompting blindly, and don't automatically rebuild everything either. In a Vibe Code Rescue Audit we separate the good parts from temporary solutions and structural risks. You then get a concrete route: what can stay, what needs improving and what really doesn't need redoing.\n",{"buyerTriggerKeys":499,"primaryOfferKey":77,"offerKeys":500,"caseKeys":501,"relatedUseCaseKeys":502},[76],[77,79],[],[112,29],{"title":504,"description":505},"Stuck with vibe coding? | 9to5 software","Vibe-coded yourself into a corner with Lovable, Cursor, Bolt or Replit? 9to5 analyses your codebase, finds the blockers and helps you build on responsibly.\n","use-cases\u002Fvibe-code-project-vastgelopen","With AI coding tools it went incredibly fast at first. Now new changes mainly make the project more complicated and you no longer know how to get out.\n",{"hero":90,"problem":355,"proof":92},"ao7p7vb_k93FD1bj9inbhcKsmZaEIvN9j4_hOr_0TkA",[],[512],{"id":513,"title":514,"approach":515,"body":529,"cta":533,"description":11,"extension":26,"hero":536,"key":76,"label":538,"meta":539,"navigation":31,"path":540,"proof":541,"relations":552,"seo":556,"stem":559,"summary":560,"visuals":561,"__hash__":562},"buyerTriggers_en\u002Fbuyer-triggers\u002Fvastgelopen-met-ai.md","We've already built something, but we're stuck.",{"title":516,"steps":517},"We step in, understand, repair and hand over.",[518,520,523,526],{"title":151,"text":519},"We establish what is actually going wrong, what is urgent and what needs to be demonstrably better after the rescue.\n",{"title":521,"text":522},"Understand the context and code","We examine the code, architecture, data flows, integrations and deployment until the source of the problem is clear.\n",{"title":524,"text":525},"Fix and test","We make targeted repairs, add tests, evals and guardrails where needed and check that the solution works under real conditions too.\n",{"title":527,"text":528},"Document and hand over","We document decisions, clear critical technical debt and make sure your team can move forward independently again.\n",{"type":8,"value":530,"toc":531},[],{"title":11,"searchDepth":12,"depth":12,"links":532},[],{"title":534,"body":535},"Stuck with AI or vibe-coded software?","Briefly describe what you have and where it is going wrong. We'll take a look and quickly tell you what makes sense to repair, keep or rebuild.\n",{"intro":537},"You don't have to start over just because things have become complicated. We step in, including when you have a vibe-coded app or code generated by AI tools such as Claude Code, Codex or Cursor. We understand what is there, find what is really going wrong and make it technically manageable again.\n","Stuck with AI",{},"\u002Fbuyer-triggers\u002Fvastgelopen-met-ai",{"intro":542,"points":543},"Assessing an existing codebase takes more than an automated quality score. It takes senior engineers who can identify the problems that really hurt and make targeted repairs.\n",[544,547,549],{"title":545,"text":546},"We work with existing software","A messy or AI-generated codebase is no reason to automatically start from scratch.\n",{"title":170,"text":548},"We look at everyday production problems and AI-specific failure modes, such as unreliable output and missing evals.\n",{"title":550,"text":551},"Move forward independently again","We document decisions and clear critical technical debt so your team can move forward on its own again.\n",{"useCaseKeys":553,"offerKeys":554,"caseKeys":555},[112,179,113,29,82,252,253,180,181,182,254,255,183,184,185,186,187,83],[77,79,127],[],{"title":557,"description":558},"Stuck with AI? Rescue by senior engineers | 9to5 software","Stuck with an AI agent, prototype or vibe-coded app (Lovable, Cursor, Bolt, Replit)? We analyse the problem, make targeted repairs and restore maintainability.\n","buyer-triggers\u002Fvastgelopen-met-ai","Something is already there, but it is unreliable, hard to understand or technically stuck. We need to get it back under control.\n",{"hero":90,"proof":92,"approach":92},"e0bDu3r1P4JqQOadOsQgPsL_EDOsQGpgsqBXrdwFTNw",1792049912085]