[{"data":1,"prerenderedAt":564},["ShallowReactive",2],{"footer-vacatures-en":3,"use-case-tests-evals-monitoring-voor-ai-en":4,"content-by-keys-offers-en-rescue-sprint,vibe-code-rescue-audit":94,"content-by-keys-useCases-en-ai-agent-niet-betrouwbaar,ai-code-breekt-steeds":358,"content-by-keys-cases-en-":511,"content-by-keys-buyerTriggers-en-vastgelopen-met-ai":512},[],{"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\u002Ftests-evals-monitoring-voor-ai.md","We're missing tests, evals or monitoring",{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],{"intro":15,"items":16},"You want to change things with confidence because you quickly see what a new prompt, model version or code change actually does.\n",[17,20,23],{"title":18,"text":19},"Regressions become visible","Important existing situations are automatically checked again.\n",{"title":21,"text":22},"AI quality becomes measurable","You compare changes against relevant examples and criteria.\n",{"title":24,"text":25},"Production gives feedback","Errors, latency and unusual behaviour no longer disappear quietly into logs.\n","md",{"intro":28},"\"It feels better\" is not a reliable test strategy. If you use AI functionality seriously, you need to be able to see what changes do and when things go wrong in production. We help set up that feedback loop.\n","tests-evals-monitoring-voor-ai",{},true,"\u002Fuse-cases\u002Ftests-evals-monitoring-voor-ai",{"intro":34,"causes":35},"Traditional software tests remain important, but AI adds behaviour for which there isn't always one exactly correct answer.\n",[36,39,42],{"title":37,"text":38},"AI output is probabilistic","Exact string comparisons are not enough for many AI tasks.\n",{"title":40,"text":41},"Good examples aren't recorded","Knowledge of what is right and wrong mainly lives in heads and scattered chats.\n",{"title":43,"text":44},"Observability stops at technical errors","An HTTP 200 says nothing about the quality of the answer.\n",{"intro":46,"points":47},"A measurement layer is only useful to us if it helps engineers see faster whether a change is safe and actually better.\n",[48,51,54],{"title":49,"text":50},"Regular tests where possible","Deterministic software simply stays deterministically testable.\n",{"title":52,"text":53},"Evals where needed","AI behaviour gets examples and criteria that fit the real use case.\n",{"title":55,"text":56},"Production data closes the loop","Monitoring shows which real-world situations need attention.\n",{"intro":58,"signals":59},"Without a good feedback loop, an AI product becomes harder and harder to develop responsibly.\n",[60,63,66,69],{"title":61,"text":62},"Testing is mostly manual","After every change someone tries a few known examples.\n",{"title":64,"text":65},"Prompt changes are hard to compare","You can't objectively tell whether version B is really better than version A.\n",{"title":67,"text":68},"Production errors are discovered by users","The system itself hardly flags deviating behaviour.\n",{"title":70,"text":71},"Model updates feel risky","A new provider or model version can change behaviour without clear warning.\n",{"intro":73},"If the scope is clear, we set up a practical feedback loop in a Rescue Sprint with the right combination of tests, evals, traces and monitoring. If broader research is needed first, we start with an audit.\n",{"buyerTriggerKeys":75,"primaryOfferKey":77,"offerKeys":78,"caseKeys":80,"relatedUseCaseKeys":81},[76],"vastgelopen-met-ai","rescue-sprint",[77,79],"vibe-code-rescue-audit",[],[82,83],"ai-agent-niet-betrouwbaar","ai-code-breekt-steeds",{"title":85,"description":86},"Tests, evals and monitoring for AI | 9to5 software","AI without proper tests, LLM evals or monitoring? 9to5 helps set up measurable quality, regression tests and production observability.\n","use-cases\u002Ftests-evals-monitoring-voor-ai","The AI functionality runs, but nobody can objectively see whether changes make it better, worse or quietly break something.\n",{"hero":90,"problem":91,"proof":92},"sq-guardrails-check","sq-process-steps","ls-workflow-flow","HLgbDqrGnq-G64ciWMNMDChkwkuEQEyI9a7eCclpOe0",[95,225],{"id":96,"title":97,"body":98,"catalogue":102,"cta":103,"description":11,"extension":26,"fit":108,"hero":115,"key":77,"meta":118,"navigation":31,"next":119,"outcome":132,"path":144,"price":145,"process":149,"proof":164,"relations":178,"scope":183,"seo":211,"stem":214,"summary":215,"summaryPanel":216,"visuals":221,"__hash__":224},"offers_en\u002Foffers\u002Frescue-sprint.md","Rescue Sprint",{"type":8,"value":99,"toc":100},[],{"title":11,"searchDepth":12,"depth":12,"links":101},[],null,{"title":104,"body":105,"primaryCta":106,"local":107},"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":110,"useCaseKeys":111},"When is this offer a fit?","When the technical problem is sharp enough to fix right away.\n",[112,113,29,114],"vast-op-auth-database-of-rechten","ai-koppelen-aan-bestaande-systemen","developmentteam-loopt-vast-met-ai",{"headline":116,"intro":117,"primaryCta":106},"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":120,"items":121},"What happens next?",[122,125,128],{"title":123,"text":124},"Done? Then we leave.","If you can continue independently, the Sprint has succeeded.\n",{"title":126,"text":127,"offerKey":77},"Another clear rescue goal?","Then you can use a next Sprint as a new fixed scope.\n",{"title":129,"text":130,"offerKey":131},"Turns out bigger than a Sprint?","Then we scope Build & Integrate. If the cause is unclear after all, the Rescue Audit comes first.\n","build-integrate",{"title":133,"items":134},"Afterwards you have...",[135,138,141],{"title":136,"text":137},"The concrete problem is tackled","The agreed technical blocker is solved or demonstrably moved forward.\n",{"title":139,"text":140},"The change is set up professionally","Where needed we add tests, evals, guardrails or production preconditions.\n",{"title":142,"text":143},"Your team can move forward again","Code, choices and follow-up are documented and technically handed over.\n","\u002Foffers\u002Frescue-sprint",{"label":146,"suffix":147,"type":148},"€5,950 excl. VAT","per Sprint","fixed",{"title":150,"steps":151},"How it works.",[152,155,158,161],{"title":153,"text":154},"Confirm the rescue goal","We check whether the problem is sharp enough for a Sprint.\n",{"title":156,"text":157},"Understand context + code","We read exactly enough to intervene responsibly.\n",{"title":159,"text":160},"Solve + test","We implement the fix and add the quality layer it needs.\n",{"title":162,"text":163},"Document + hand over","We record choices and make sure your team can continue independently again.\n",{"title":165,"intro":166,"points":167,"caseKeys":177},"Why should you believe this?","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",[168,171,174],{"title":169,"text":170},"Senior AI + software engineers","We step in where it gets complicated and leave when it's done.\n",{"title":172,"text":173},"We work in what is already there","We don't expect you to migrate everything to our favourite stack first.\n",{"title":175,"text":176},"Yours as soon as it's done","We document, hand over and leave as soon as you can continue on your own.\n",[],{"buyerTriggerKeys":179,"useCaseKeys":180,"relatedOfferKeys":181,"caseKeys":182},[76],[112,113,29,114],[79,131],[],{"title":184,"intro":185,"activities":186,"deliverables":195,"exclusions":204},"What is included in this offer?","One Sprint has one clear rescue goal. That boundary keeps it fast and honest.\n",{"intro":187,"items":188},"We do what is technically needed to tackle the agreed problem responsibly.\n",[189,190,191,192,193,194],"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":196,"items":197},"Working engineering in the existing codebase, not an advice document someone else still has to carry out.\n",[198,199,200,201,202,203],"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":205,"items":206},"A Sprint is bounded and doesn't quietly turn into an open-ended project.\n",[207,208,209,210],"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":212,"description":213},"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":217,"result":218,"duration":219,"nextStep":220},"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":222,"proof":90,"process":223},"sq-tangle-knot","ls-rescue-repair","RBo-3uCvL4DWueBHoZFGrqKFPfwCZ1QLbywOlnLG0NY",{"id":226,"title":227,"body":228,"catalogue":102,"cta":232,"description":11,"extension":26,"fit":237,"hero":243,"key":79,"meta":246,"navigation":31,"next":247,"outcome":258,"path":269,"price":270,"process":272,"proof":285,"relations":298,"scope":312,"seo":344,"stem":347,"summary":348,"summaryPanel":349,"visuals":354,"__hash__":357},"offers_en\u002Foffers\u002Fvibe-code-rescue-audit.md","Vibe Code Rescue Audit",{"type":8,"value":229,"toc":230},[],{"title":11,"searchDepth":12,"depth":12,"links":231},[],{"title":233,"body":234,"primaryCta":235,"local":236},"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":238,"useCaseKeys":239},"When you sense something is technically wrong, but the actual cause or extent isn't clear yet.\n",[240,82,241,242],"vibe-coded-app-professionaliseren","gegenereerde-code-niet-meer-begrijpelijk","vibe-code-project-vastgelopen",{"headline":244,"intro":245,"primaryCta":235},"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":120,"items":248},[249,252,255],{"title":250,"text":251,"offerKey":77},"A clear rescue goal?","Then we can tackle it in a focused Rescue Sprint.\n",{"title":253,"text":254,"offerKey":131},"Turns out to be a bigger build project?","Then we scope Build & Integrate as a fixed engagement.\n",{"title":256,"text":257},"Turns out little is wrong?","Then we'll simply tell you. A follow-up is not required.\n",{"title":133,"items":259},[260,263,266],{"title":261,"text":262},"Technical grip on what is there","Architecture, key dependencies and critical risks are clear again.\n",{"title":264,"text":265},"A prioritised rescue plan","You know what can stay, what really needs to change and in which order.\n",{"title":267,"text":268},"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":271,"type":148},"€2,950 excl. VAT",{"title":150,"steps":273},[274,276,279,282],{"title":153,"text":275},"We determine which questions the Audit needs to answer and where the biggest uncertainty lies.\n",{"title":277,"text":278},"Reconstruct code + system","We read the architecture, code, deployment, data flows and relevant dependencies.\n",{"title":280,"text":281},"Prioritise problems","We distinguish cosmetic debt, development blockers and real production or security risks.\n",{"title":283,"text":284},"Rescue plan + debrief","You get a concrete route with what can stay, what needs to change and what makes sense next.\n",{"title":165,"intro":286,"points":287,"caseKeys":297},"Assessing an existing codebase takes more than an automated quality score. It takes senior engineers who can see which problems actually hurt.\n",[288,291,294],{"title":289,"text":290},"Existing software is where we work","A messy or AI-generated codebase is no reason to automatically start over.\n",{"title":292,"text":293},"Software engineering and AI","We look at both regular production-grade problems and AI-specific failure modes.\n",{"title":295,"text":296},"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":299,"useCaseKeys":300,"relatedOfferKeys":310,"caseKeys":311},[76],[240,301,82,241,83,302,303,304,305,306,307,308,309,242],"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",[77,131],[],{"title":184,"intro":313,"activities":314,"deliverables":326,"exclusions":337},"A technical diagnosis of one existing application or codebase, aimed at decision-making.\n",{"intro":315,"items":316},"We look broadly enough to find structural causes, without turning it into a theoretical code review.\n",[317,318,319,320,321,322,323,324,325],"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":327,"items":328},"You get a technical verdict you can actually base a follow-up on.\n",[329,330,331,332,333,334,335,336],"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":338,"items":339},"The Audit delivers understanding and a plan. Major fixes don't quietly become part of the analysis.\n",[340,341,342,343],"Full repair of the codebase","Complete rewrite","Unbounded pentest or formal security audit","Product development beyond small diagnostic changes",{"title":345,"description":346},"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":350,"result":351,"duration":352,"nextStep":353},"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":222,"proof":355,"process":356},"sq-orient-options","ls-route-converge","IWSlwlvSU82rOHwWTXtSCvLbfXjNUybu2L5bZ-96IJY",[359,435],{"id":360,"title":361,"body":362,"description":11,"desiredOutcome":366,"extension":26,"hero":378,"key":82,"meta":380,"navigation":31,"path":381,"problem":382,"proof":394,"recognition":406,"recommendedApproach":421,"relations":423,"seo":428,"stem":431,"summary":432,"visuals":433,"__hash__":434},"useCases_en\u002Fuse-cases\u002Fai-agent-niet-betrouwbaar.md","Our agent is not reliable enough",{"type":8,"value":363,"toc":364},[],{"title":11,"searchDepth":12,"depth":12,"links":365},[],{"intro":367,"items":368},"No agent is perfect all the time. You do need to know where it can fail and how the system deals with that.\n",[369,372,375],{"title":370,"text":371},"More predictable behaviour","The agent more consistently chooses the right steps, tools and information.\n",{"title":373,"text":374},"Errors become visible","You can measure which situations go wrong instead of relying on scattered manual tests.\n",{"title":376,"text":377},"Risks are contained","Validation, guardrails and human oversight prevent a mistake from immediately becoming a big problem.\n",{"intro":379},"An agent that works well eight out of ten times can look fantastic in a demo and be unusable in production. We find out where the unreliability comes from and which technical measures are needed to make the system manageable.\n",{},"\u002Fuse-cases\u002Fai-agent-niet-betrouwbaar",{"intro":383,"causes":384},"The cause rarely sits in the prompt alone. An agent is a complete software system in which model, tools, context, state and error handling work together.\n",[385,388,391],{"title":386,"text":387},"The task is too open","The agent gets more freedom than it needs to carry out the process well.\n",{"title":389,"text":390},"The feedback loop is missing","Without evals and traces it is hard to see which part is actually failing.\n",{"title":392,"text":393},"Errors are not caught","A single wrong model decision can needlessly carry through into every following step.\n",{"intro":395,"points":396},"You don't get a reliable agent by endlessly tweaking a single prompt. You treat it as software, with clear responsibilities, observability and controlled failure paths.\n",[397,400,403],{"title":398,"text":399},"Looking at the whole system","We examine the entire agent flow, not just the instruction text.\n",{"title":401,"text":402},"Measure first, then optimise","Evals and traces show which changes actually help.\n",{"title":404,"text":405},"Autonomy doesn't have to be the goal","We deliberately choose where deterministic software or human oversight is the wiser option.\n",{"intro":407,"signals":408},"At first it often feels like a series of separate incidents.\n",[409,412,415,418],{"title":410,"text":411},"The same input gives different results","What went well yesterday can suddenly take a different route today.\n",{"title":413,"text":414},"The agent sometimes picks the wrong tool","It calls actions that are not needed or uses the wrong data.\n",{"title":416,"text":417},"Prompt changes move the problem around","An improvement for one situation makes another situation worse.\n",{"title":419,"text":420},"Errors mostly show up with real users","The demos are fine, but reality contains far more variation.\n",{"intro":422},"In a Vibe Code Rescue Audit we first make the behaviour understandable and measurable. Then we determine which combination of architecture, evals, validation, guardrails and human-in-the-loop is needed. The concrete fixes can then follow in a Rescue Sprint.\n",{"buyerTriggerKeys":424,"primaryOfferKey":79,"offerKeys":425,"caseKeys":426,"relatedUseCaseKeys":427},[76],[79,77],[],[29,303],{"title":429,"description":430},"AI agent not reliable? | 9to5 software","Does your AI agent sometimes work well and sometimes not? 9to5 examines tools, data flows, evals, guardrails and architecture and makes behaviour more manageable.\n","use-cases\u002Fai-agent-niet-betrouwbaar","The agent can do impressive things, but does not behave predictably enough to trust a serious process or product to it.\n",{"hero":91,"problem":90,"proof":223},"msXea1UQcF1EwGJ9TUI7fGQMHikENHvoI9katWwH8e0",{"id":436,"title":437,"body":438,"description":11,"desiredOutcome":442,"extension":26,"hero":454,"key":83,"meta":456,"navigation":31,"path":457,"problem":458,"proof":470,"recognition":482,"recommendedApproach":497,"relations":499,"seo":504,"stem":507,"summary":508,"visuals":509,"__hash__":510},"useCases_en\u002Fuse-cases\u002Fai-code-breekt-steeds.md","Every new AI code change breaks something else",{"type":8,"value":439,"toc":440},[],{"title":11,"searchDepth":12,"depth":12,"links":441},[],{"intro":443,"items":444},"You want to be able to make changes again without discovering afterwards, every time, what collateral damage they caused.\n",[445,448,451],{"title":446,"text":447},"Changes stay local","A change only has effects in the places where you expect them.\n",{"title":449,"text":450},"Regressions are found quickly","Tests and checks flag problems before users discover them.\n",{"title":452,"text":453},"Development becomes truly fast again","Less repair work means AI-assisted development saves time once more.\n",{"intro":455},"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":459,"causes":460},"AI coding tools are strong at local changes. They don't automatically know all the implicit agreements that run through a growing product.\n",[461,464,467],{"title":462,"text":463},"Tests don't cover critical agreements","The AI gets little feedback when a change breaks existing functionality.\n",{"title":465,"text":466},"Parts are too tightly coupled","A local change affects state, data or behaviour in unexpected places.\n",{"title":468,"text":469},"Interfaces are not clear enough","The codebase doesn't show well enough which contracts must stay stable.\n",{"intro":471,"points":472},"The AI doesn't need to write less code. The codebase needs enough feedback and structure to make errors visible quickly.\n",[473,476,479],{"title":474,"text":475},"Tests where they add value","We test critical contracts and flows, not every detail for a percentage.\n",{"title":477,"text":478},"Clear technical boundaries","Fewer hidden couplings means fewer unexpected regressions.\n",{"title":480,"text":481},"Practical AI guardrails","The development workflow helps coding agents stay within the architecture.\n",{"intro":483,"signals":484},"The pattern often becomes visible once the codebase grows and several parts depend on each other.\n",[485,488,491,494],{"title":486,"text":487},"A simple feature causes unexpected bugs","Functionality on other screens or flows suddenly stops working.\n",{"title":489,"text":490},"The same bug comes back later","A bug gets fixed, but nothing prevents it from reappearing.\n",{"title":492,"text":493},"Refactors are almost impossible","Too many parts turn out to depend on each other implicitly.\n",{"title":495,"text":496},"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":498},"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":500,"primaryOfferKey":79,"offerKeys":501,"caseKeys":502,"relatedUseCaseKeys":503},[76],[79,77],[],[241,29],{"title":505,"description":506},"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":222,"problem":90,"proof":223},"Wac_TNYZVCtWw1yfVa0Y41CtfZ--5euF9AMy8eplg3g",[],[513],{"id":514,"title":515,"approach":516,"body":530,"cta":534,"description":11,"extension":26,"hero":537,"key":76,"label":539,"meta":540,"navigation":31,"path":541,"proof":542,"relations":553,"seo":557,"stem":560,"summary":561,"visuals":562,"__hash__":563},"buyerTriggers_en\u002Fbuyer-triggers\u002Fvastgelopen-met-ai.md","We've already built something, but we're stuck.",{"title":517,"steps":518},"We step in, understand, repair and hand over.",[519,521,524,527],{"title":153,"text":520},"We establish what is actually going wrong, what is urgent and what needs to be demonstrably better after the rescue.\n",{"title":522,"text":523},"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":525,"text":526},"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":528,"text":529},"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":531,"toc":532},[],{"title":11,"searchDepth":12,"depth":12,"links":533},[],{"title":535,"body":536},"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":538},"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":543,"points":544},"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",[545,548,550],{"title":546,"text":547},"We work with existing software","A messy or AI-generated codebase is no reason to automatically start from scratch.\n",{"title":292,"text":549},"We look at everyday production problems and AI-specific failure modes, such as unreliable output and missing evals.\n",{"title":551,"text":552},"Move forward independently again","We document decisions and clear critical technical debt so your team can move forward on its own again.\n",{"useCaseKeys":554,"offerKeys":555,"caseKeys":556},[240,301,82,241,83,112,113,302,303,304,29,114,305,306,307,308,309,242],[79,77,131],[],{"title":558,"description":559},"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":222,"proof":223,"approach":223},"e0bDu3r1P4JqQOadOsQgPsL_EDOsQGpgsqBXrdwFTNw",1792049912573]