[{"data":1,"prerenderedAt":564},["ShallowReactive",2],{"footer-vacatures-en":3,"use-case-developmentteam-loopt-vast-met-ai-en":4,"content-by-keys-offers-en-rescue-sprint,vibe-code-rescue-audit":94,"content-by-keys-useCases-en-technische-second-opinion-ai,ai-koppelen-aan-bestaande-systemen":356,"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\u002Fdevelopmentteam-loopt-vast-met-ai.md","Our own development team is technically stuck",{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],{"intro":15,"items":16},"You don't want to replace the existing team, but to remove the technical blocker so the team can move forward on its own again.\n",[17,20,23],{"title":18,"text":19},"The hard part gets solved","Senior engineers tackle exactly the part the team is stuck on.\n",{"title":21,"text":22},"Knowledge stays in-house","Your engineers understand the solution and the most important trade-offs.\n",{"title":24,"text":25},"No extra dependency","After the rescue, 9to5 doesn't need to remain part of the team permanently.\n","md",{"intro":28},"Sometimes you don't need an extra team. You need someone who quickly gets to the bottom of one complicated technical problem, solves it together with your engineers and then leaves again. That is where we like to step in.\n","developmentteam-loopt-vast-met-ai",{},true,"\u002Fuse-cases\u002Fdevelopmentteam-loopt-vast-met-ai",{"intro":34,"causes":35},"AI projects combine several disciplines. Even a strong development team doesn't need to have immediate experience with every specialist part.\n",[36,39,42],{"title":37,"text":38},"The problem is multidisciplinary","Software architecture, models, data, integrations and observability all touch.\n",{"title":40,"text":41},"Experience with this specific failure mode is missing","Some problems are solved much faster when you've seen them before.\n",{"title":43,"text":44},"Internal experimenting gets expensive","After several failed routes, searching further costs more than temporary specialist help.\n",{"intro":46,"points":47},"This is how we want to work: bring in senior engineering where it gets hard and leave again once your own team can carry on.\n",[48,51,54],{"title":49,"text":50},"Engineers work with engineers","No advisory layer between the problem and the people who actually change the code.\n",{"title":52,"text":53},"The existing stack remains the starting point","We don't bring in a new tool or architecture by default.\n",{"title":55,"text":56},"Handover from the start","The solution doesn't become needlessly dependent on whoever built it.\n",{"intro":58,"signals":59},"A good software team doesn't automatically have all the experience with agents, LLMs, agentic coding (Claude Code, Codex) and production AI in-house.\n",[60,63,66,69],{"title":61,"text":62},"The team keeps returning to the same problem","Different solutions are tried without a structural breakthrough.\n",{"title":64,"text":65},"AI-specific choices remain uncertain","Model behaviour, evals, agent architecture or retrieval call for different experience.\n",{"title":67,"text":68},"An integration turns out much harder than expected","The problem sits on the boundary between existing software and the new AI functionality.\n",{"title":70,"text":71},"A senior hire is disproportionate","You need specific expertise now, but not necessarily permanently.\n",{"intro":73},"If the problem is sharp enough, we step in right next to the team with a Rescue Sprint. We work in the existing codebase, solve the blocker and transfer the relevant knowledge along the way. If the root cause is unclear, we start with an audit first.\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],"technische-second-opinion-ai","ai-koppelen-aan-bestaande-systemen",{"title":85,"description":86},"Development team stuck with AI | 9to5 software","Development team stuck with AI agents or agentic coding (Claude Code, Codex)? 9to5 steps in temporarily, solves the technical problem and hands it back over.\n","use-cases\u002Fdevelopmentteam-loopt-vast-met-ai","The team builds software just fine, but lacks the specific senior experience to solve a tricky AI problem properly.\n",{"hero":90,"problem":91,"proof":92},"sq-tangle-knot","sq-orient-options","ls-rescue-repair","G-CaoUkXnekooXGZnXL-EzJ47Frx3e9u27FGNRjxr3k",[95,223],{"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":148,"proof":163,"relations":177,"scope":182,"seo":210,"stem":213,"summary":214,"summaryPanel":215,"visuals":220,"__hash__":222},"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,83,113,29],"vast-op-auth-database-of-rechten","tests-evals-monitoring-voor-ai",{"headline":115,"intro":116,"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":119,"items":120},"What happens next?",[121,124,127],{"title":122,"text":123},"Done? Then we leave.","If you can continue independently, the Sprint has succeeded.\n",{"title":125,"text":126,"offerKey":77},"Another clear rescue goal?","Then you can use a next Sprint as a new fixed scope.\n",{"title":128,"text":129,"offerKey":130},"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":132,"items":133},"Afterwards you have...",[134,137,140],{"title":135,"text":136},"The concrete problem is tackled","The agreed technical blocker is solved or demonstrably moved forward.\n",{"title":138,"text":139},"The change is set up professionally","Where needed we add tests, evals, guardrails or production preconditions.\n",{"title":141,"text":142},"Your team can move forward again","Code, choices and follow-up are documented and technically handed over.\n","\u002Foffers\u002Frescue-sprint",{"label":145,"suffix":146,"type":147},"€5,950 excl. VAT","per Sprint","fixed",{"title":149,"steps":150},"How it works.",[151,154,157,160],{"title":152,"text":153},"Confirm the rescue goal","We check whether the problem is sharp enough for a Sprint.\n",{"title":155,"text":156},"Understand context + code","We read exactly enough to intervene responsibly.\n",{"title":158,"text":159},"Solve + test","We implement the fix and add the quality layer it needs.\n",{"title":161,"text":162},"Document + hand over","We record choices and make sure your team can continue independently again.\n",{"title":164,"intro":165,"points":166,"caseKeys":176},"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",[167,170,173],{"title":168,"text":169},"Senior AI + software engineers","We step in where it gets complicated and leave when it's done.\n",{"title":171,"text":172},"We work in what is already there","We don't expect you to migrate everything to our favourite stack first.\n",{"title":174,"text":175},"Yours as soon as it's done","We document, hand over and leave as soon as you can continue on your own.\n",[],{"buyerTriggerKeys":178,"useCaseKeys":179,"relatedOfferKeys":180,"caseKeys":181},[76],[112,83,113,29],[79,130],[],{"title":183,"intro":184,"activities":185,"deliverables":194,"exclusions":203},"What is included in this offer?","One Sprint has one clear rescue goal. That boundary keeps it fast and honest.\n",{"intro":186,"items":187},"We do what is technically needed to tackle the agreed problem responsibly.\n",[188,189,190,191,192,193],"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":195,"items":196},"Working engineering in the existing codebase, not an advice document someone else still has to carry out.\n",[197,198,199,200,201,202],"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":204,"items":205},"A Sprint is bounded and doesn't quietly turn into an open-ended project.\n",[206,207,208,209],"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":211,"description":212},"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":216,"result":217,"duration":218,"nextStep":219},"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":221,"process":92},"sq-guardrails-check","RBo-3uCvL4DWueBHoZFGrqKFPfwCZ1QLbywOlnLG0NY",{"id":224,"title":225,"body":226,"catalogue":102,"cta":230,"description":11,"extension":26,"fit":235,"hero":242,"key":79,"meta":245,"navigation":31,"next":246,"outcome":257,"path":268,"price":269,"process":271,"proof":284,"relations":297,"scope":311,"seo":343,"stem":346,"summary":347,"summaryPanel":348,"visuals":353,"__hash__":355},"offers_en\u002Foffers\u002Fvibe-code-rescue-audit.md","Vibe Code Rescue Audit",{"type":8,"value":227,"toc":228},[],{"title":11,"searchDepth":12,"depth":12,"links":229},[],{"title":231,"body":232,"primaryCta":233,"local":234},"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":236,"useCaseKeys":237},"When you sense something is technically wrong, but the actual cause or extent isn't clear yet.\n",[238,239,240,241],"vibe-coded-app-professionaliseren","ai-agent-niet-betrouwbaar","gegenereerde-code-niet-meer-begrijpelijk","vibe-code-project-vastgelopen",{"headline":243,"intro":244,"primaryCta":233},"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":247},[248,251,254],{"title":249,"text":250,"offerKey":77},"A clear rescue goal?","Then we can tackle it in a focused Rescue Sprint.\n",{"title":252,"text":253,"offerKey":130},"Turns out to be a bigger build project?","Then we scope Build & Integrate as a fixed engagement.\n",{"title":255,"text":256},"Turns out little is wrong?","Then we'll simply tell you. A follow-up is not required.\n",{"title":132,"items":258},[259,262,265],{"title":260,"text":261},"Technical grip on what is there","Architecture, key dependencies and critical risks are clear again.\n",{"title":263,"text":264},"A prioritised rescue plan","You know what can stay, what really needs to change and in which order.\n",{"title":266,"text":267},"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":270,"type":147},"€2,950 excl. VAT",{"title":149,"steps":272},[273,275,278,281],{"title":152,"text":274},"We determine which questions the Audit needs to answer and where the biggest uncertainty lies.\n",{"title":276,"text":277},"Reconstruct code + system","We read the architecture, code, deployment, data flows and relevant dependencies.\n",{"title":279,"text":280},"Prioritise problems","We distinguish cosmetic debt, development blockers and real production or security risks.\n",{"title":282,"text":283},"Rescue plan + debrief","You get a concrete route with what can stay, what needs to change and what makes sense next.\n",{"title":164,"intro":285,"points":286,"caseKeys":296},"Assessing an existing codebase takes more than an automated quality score. It takes senior engineers who can see which problems actually hurt.\n",[287,290,293],{"title":288,"text":289},"Existing software is where we work","A messy or AI-generated codebase is no reason to automatically start over.\n",{"title":291,"text":292},"Software engineering and AI","We look at both regular production-grade problems and AI-specific failure modes.\n",{"title":294,"text":295},"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":298,"useCaseKeys":299,"relatedOfferKeys":309,"caseKeys":310},[76],[238,300,239,240,301,302,303,304,82,305,306,307,308,241],"ai-prototype-naar-productie","ai-code-breekt-steeds","security-en-privacy-ai-oplossing","ai-oplossing-te-langzaam","ai-oplossing-te-duur","ai-project-overnemen-van-andere-leverancier","ai-experiment-heeft-echte-gebruikers","prototype-naar-onderhoudbaar-softwareproduct","weg-bij-ai-platform-of-leverancier",[77,130],[],{"title":183,"intro":312,"activities":313,"deliverables":325,"exclusions":336},"A technical diagnosis of one existing application or codebase, aimed at decision-making.\n",{"intro":314,"items":315},"We look broadly enough to find structural causes, without turning it into a theoretical code review.\n",[316,317,318,319,320,321,322,323,324],"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":326,"items":327},"You get a technical verdict you can actually base a follow-up on.\n",[328,329,330,331,332,333,334,335],"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":337,"items":338},"The Audit delivers understanding and a plan. Major fixes don't quietly become part of the analysis.\n",[339,340,341,342],"Full repair of the codebase","Complete rewrite","Unbounded pentest or formal security audit","Product development beyond small diagnostic changes",{"title":344,"description":345},"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":349,"result":350,"duration":351,"nextStep":352},"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":91,"process":354},"ls-route-converge","IWSlwlvSU82rOHwWTXtSCvLbfXjNUybu2L5bZ-96IJY",[357,433],{"id":358,"title":359,"body":360,"description":11,"desiredOutcome":364,"extension":26,"hero":376,"key":82,"meta":378,"navigation":31,"path":379,"problem":380,"proof":392,"recognition":404,"recommendedApproach":419,"relations":421,"seo":426,"stem":429,"summary":430,"visuals":431,"__hash__":432},"useCases_en\u002Fuse-cases\u002Ftechnische-second-opinion-ai.md","We want an independent technical second opinion",{"type":8,"value":361,"toc":362},[],{"title":11,"searchDepth":12,"depth":12,"links":363},[],{"intro":365,"items":366},"You don't want an extra opinion that makes the discussion bigger. You want enough technical clarity to make a better decision yourself.\n",[367,370,373],{"title":368,"text":369},"Separate facts from assumptions","You see which technical conclusions are solid and where uncertainty remains.\n",{"title":371,"text":372},"Alternatives become visible","You know whether the proposed route really is the only logical option.\n",{"title":374,"text":375},"A concrete next decision","After the review you know what to investigate, keep, adjust or drop.\n",{"intro":377},"Maybe your vendor says everything has to be rebuilt. Maybe your own team thinks it's fine. When a lot of money or risk depends on the next step, an independent technical view can be well worth having.\n",{},"\u002Fuse-cases\u002Ftechnische-second-opinion-ai",{"intro":381,"causes":382},"Technical choices are not fully objective. Everyone looks at the same situation from their own experience, interests and preferences.\n",[383,386,389],{"title":384,"text":385},"Vendors mainly know their own tools","A proposal can unconsciously steer towards solutions that suit the vendor.\n",{"title":387,"text":388},"Existing teams get used to limitations","What feels normal internally can be obvious technical debt to an outsider.\n",{"title":390,"text":391},"Big decisions become final too early","Sometimes evidence is still missing for assumptions on which a far-reaching choice is based.\n",{"intro":393,"points":394},"A good second opinion doesn't automatically sell a larger follow-up engagement. The outcome may simply be that the existing route is fine.\n",[395,398,401],{"title":396,"text":397},"Engineers first","The assessment is made from the perspective of technical feasibility and risk.\n",{"title":399,"text":400},"Build, buy or change nothing","We have no stake in one specific technical outcome.\n",{"title":402,"text":403},"Follow-up is not required","If the conclusion is clear, the engagement can simply end there.\n",{"intro":405,"signals":406},"A second opinion is especially useful when the next technical step is large, expensive or hard to reverse.\n",[407,410,413,416],{"title":408,"text":409},"A vendor wants to rebuild a lot","You want to know whether that's technically necessary or mainly the easiest route for them.\n",{"title":411,"text":412},"Internal opinions differ","Different engineers judge the same risks differently.\n",{"title":414,"text":415},"The architecture feels more complicated than needed","Many new tools, platforms or layers are being proposed.\n",{"title":417,"text":418},"You're facing a big investment","Before continuing, you want to know whether the technical foundation makes sense.\n",{"intro":420},"The Vibe Code Rescue Audit fits here as an independent technical review. We look at what's actually there, test the most important assumptions and give a concrete technical debrief. Follow-up work is only needed if there is a substantive reason for it.\n",{"buyerTriggerKeys":422,"primaryOfferKey":79,"offerKeys":423,"caseKeys":424,"relatedUseCaseKeys":425},[76],[79,77],[],[305,308],{"title":427,"description":428},"Technical second opinion for an AI project | 9to5 software","Need an independent technical second opinion on an AI solution, architecture or vendor? Senior engineers from 9to5 assess what's there.\n","use-cases\u002Ftechnische-second-opinion-ai","There's already an architecture, solution or proposal, but you want to know whether the technical choices make sense before investing further.\n",{"hero":91,"problem":221,"proof":354},"Mz9vCsA-Sb-E2hgZP7IGG0NRPbBoSbELaFOOyNALsPo",{"id":434,"title":435,"body":436,"description":11,"desiredOutcome":440,"extension":26,"hero":452,"key":83,"meta":454,"navigation":31,"path":455,"problem":456,"proof":468,"recognition":480,"recommendedApproach":495,"relations":497,"seo":502,"stem":505,"summary":506,"visuals":507,"__hash__":510},"useCases_en\u002Fuse-cases\u002Fai-koppelen-aan-bestaande-systemen.md","We can't get the solution connected to existing systems",{"type":8,"value":437,"toc":438},[],{"title":11,"searchDepth":12,"depth":12,"links":439},[],{"intro":441,"items":442},"The AI shouldn't stay an isolated island. It should become a reliable part of the systems and processes that already exist.\n",[443,446,449],{"title":444,"text":445},"Reliable data exchange","Data arrives at the right moment, in the right format and at the right system.\n",{"title":447,"text":448},"Errors are manageable","Timeouts, duplicates and temporary outages don't immediately lead to unpredictable behaviour.\n",{"title":450,"text":451},"Permissions stay correct","The integration respects existing users, roles and access rules.\n",{"intro":453},"The AI demo works. It just still needs to fetch data from system A, change something in system B and respect permissions from system C. That is where an AI project often becomes a serious software engineering project.\n",{},"\u002Fuse-cases\u002Fai-koppelen-aan-bestaande-systemen",{"intro":457,"causes":458},"An integration is more than a line between two boxes in an architecture diagram. It also has to cope with real-world conditions.\n",[459,462,465],{"title":460,"text":461},"Systems speak different languages","Data models, statuses and responsibilities rarely map one-to-one.\n",{"title":463,"text":464},"External systems are not always available","Retries, queues and error handling become important as soon as the integration reaches production.\n",{"title":466,"text":467},"AI actions have real consequences","When an agent is allowed to change something, it must be clear who is responsible and what happens when something goes wrong.\n",{"intro":469,"points":470},"Building integrations is at the core of how 9to5 software works. AI only becomes useful when it can work safely with real data, software and people.\n",[471,474,477],{"title":472,"text":473},"Existing software is the starting point","The organisation doesn't have to adapt to the AI solution first.\n",{"title":475,"text":476},"Engineering around the API","We also design retries, error handling, logging and permissions.\n",{"title":478,"text":479},"No demo integrations","The integration has to stay usable under real conditions.\n",{"intro":481,"signals":482},"Often the AI part has already been proven and the real technical blocker lies in everything around it.\n",[483,486,489,492],{"title":484,"text":485},"The API doesn't quite do what you need","Documentation is limited or outdated, or the desired flow doesn't map neatly onto the available endpoints.\n",{"title":487,"text":488},"Authentication between systems gets stuck","Tokens, service accounts or user delegation make the integration more complicated.\n",{"title":490,"text":491},"Data drifts apart","Different systems use different identifiers, statuses or data models.\n",{"title":493,"text":494},"The happy flow works, errors don't","As soon as an external system is temporarily unavailable, the workflow loses track.\n",{"intro":496},"If the desired integration is clear, we tackle it directly in a Rescue Sprint. If the intake shows that a completely new integrated component is actually needed, Build & Integrate is a better fit.\n",{"buyerTriggerKeys":498,"primaryOfferKey":77,"offerKeys":499,"caseKeys":500,"relatedUseCaseKeys":501},[76],[77,130],[],[112,305],{"title":503,"description":504},"Connect ChatGPT or Claude to your software | 9to5 software","Connect ChatGPT, Claude or OpenAI to your software? 9to5 connects AI to existing APIs, databases and business processes.\n","use-cases\u002Fai-koppelen-aan-bestaande-systemen","The AI works on its own, but the real value sits behind APIs, databases and business software where the integration gets stuck.\n",{"hero":508,"problem":90,"proof":509},"sq-connect-nodes","ls-system-connect","4sCin98vwNyw5GXs3xalBs9ncmpDvENKXA0rH4xhya4",[],[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":152,"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":291,"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},[238,300,239,240,301,112,83,302,303,304,113,29,82,305,306,307,308,241],[79,77,130],[],{"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":90,"proof":92,"approach":92},"e0bDu3r1P4JqQOadOsQgPsL_EDOsQGpgsqBXrdwFTNw",1792049911930]