[{"data":1,"prerenderedAt":567},["ShallowReactive",2],{"footer-vacatures-en":3,"use-case-ai-oplossing-te-duur-en":4,"content-by-keys-offers-en-vibe-code-rescue-audit,rescue-sprint":94,"content-by-keys-useCases-en-ai-oplossing-te-langzaam,weg-bij-ai-platform-of-leverancier":359,"content-by-keys-cases-en-":514,"content-by-keys-buyerTriggers-en-vastgelopen-met-ai":515},[],{"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\u002Fai-oplossing-te-duur.md","The AI solution is becoming too expensive",{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],{"intro":15,"items":16},"You don't simply want to use the cheapest models. You want costs to be in proportion to the value of every user flow.\n",[17,20,23],{"title":18,"text":19},"Costs become transparent","You know which actions, users or processes cause the most usage.\n",{"title":21,"text":22},"Waste disappears","Unnecessary calls, context and duplicate processing are reduced in a targeted way.\n",{"title":24,"text":25},"Growth becomes more predictable","You can better estimate what more usage means financially.\n","md",{"intro":28},"A few euros during the prototype is very different from hundreds or thousands of users running the same workflow every day. We find out where the costs come from and how to lower them without optimising the solution into the ground.\n","ai-oplossing-te-duur",{},true,"\u002Fuse-cases\u002Fai-oplossing-te-duur",{"intro":34,"causes":35},"AI costs are often not just a pricing problem, but also an architecture and product problem.\n",[36,39,42],{"title":37,"text":38},"Expensive models are used everywhere","Simple tasks get the same heavy model choice as complex tasks.\n",{"title":40,"text":41},"Workflows do unnecessary work","Calls, retrieval and processing are repeated while results could be reused.\n",{"title":43,"text":44},"Costs are not part of observability","So you only see waste when the invoice arrives.\n",{"intro":46,"points":47},"The cheapest model call is often the call that turns out not to be needed. That is why we look at the whole system, not just the model providers' price list.\n",[48,51,54],{"title":49,"text":50},"Cost and quality","Cheaper doesn't help if usability collapses.\n",{"title":52,"text":53},"Architecture over loose tweaks","Routing, caching and workflow design can deliver more than prompt micro-optimisation.\n",{"title":55,"text":56},"Measurable results","Optimisation is tied to actual usage per relevant flow.\n",{"intro":58,"signals":59},"Cost problems often only become visible when an experiment successfully starts to scale.\n",[60,63,66,69],{"title":61,"text":62},"Model costs grow faster than users","Every new user causes relatively a lot of extra usage.\n",{"title":64,"text":65},"Agents make many calls per task","A simple action can quietly involve dozens of model or tool calls.\n",{"title":67,"text":68},"Large prompts are sent along every time","Context grows along with the product without it being clear what is really needed.\n",{"title":70,"text":71},"Nobody knows the cost per flow","There is a monthly invoice, but hardly any insight into what causes it.\n",{"intro":73},"With a Vibe Code Rescue Audit we map the costs per relevant flow and the biggest technical causes. We then carry out the most worthwhile optimisations in a Rescue Sprint.\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-oplossing-te-langzaam","weg-bij-ai-platform-of-leverancier",{"title":85,"description":86},"AI solution too expensive? Optimise costs | 9to5 software","AI costs (OpenAI, Claude, tokens) rising? 9to5 examines model usage, agent flows, caching and infrastructure to find unnecessary costs.\n","use-cases\u002Fai-oplossing-te-duur","Usage is growing, and with it the model, infrastructure or API costs. The current architecture turns out not to scale well economically.\n",{"hero":90,"problem":91,"proof":92},"sq-bottleneck-pressure","sq-process-steps","ls-optimize-flow","AvSDQPDw5Ui68JRE-XmUiKA5-WySdoPvNHAXTC42Cu0",[95,238],{"id":96,"title":97,"body":98,"catalogue":102,"cta":103,"description":11,"extension":26,"fit":108,"hero":116,"key":77,"meta":119,"navigation":31,"next":120,"outcome":133,"path":145,"price":146,"process":149,"proof":164,"relations":178,"scope":190,"seo":223,"stem":226,"summary":227,"summaryPanel":228,"visuals":233,"__hash__":237},"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,114,115],"vibe-coded-app-professionaliseren","ai-agent-niet-betrouwbaar","gegenereerde-code-niet-meer-begrijpelijk","vibe-code-project-vastgelopen",{"headline":117,"intro":118,"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":121,"items":122},"What happens next?",[123,126,130],{"title":124,"text":125,"offerKey":79},"A clear rescue goal?","Then we can tackle it in a focused Rescue Sprint.\n",{"title":127,"text":128,"offerKey":129},"Turns out to be a bigger build project?","Then we scope Build & Integrate as a fixed engagement.\n","build-integrate",{"title":131,"text":132},"Turns out little is wrong?","Then we'll simply tell you. A follow-up is not required.\n",{"title":134,"items":135},"Afterwards you have...",[136,139,142],{"title":137,"text":138},"Technical grip on what is there","Architecture, key dependencies and critical risks are clear again.\n",{"title":140,"text":141},"A prioritised rescue plan","You know what can stay, what really needs to change and in which order.\n",{"title":143,"text":144},"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":147,"type":148},"€2,950 excl. VAT","fixed",{"title":150,"steps":151},"How it works.",[152,155,158,161],{"title":153,"text":154},"Confirm the rescue goal","We determine which questions the Audit needs to answer and where the biggest uncertainty lies.\n",{"title":156,"text":157},"Reconstruct code + system","We read the architecture, code, deployment, data flows and relevant dependencies.\n",{"title":159,"text":160},"Prioritise problems","We distinguish cosmetic debt, development blockers and real production or security risks.\n",{"title":162,"text":163},"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":166,"points":167,"caseKeys":177},"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",[168,171,174],{"title":169,"text":170},"Existing software is where we work","A messy or AI-generated codebase is no reason to automatically start over.\n",{"title":172,"text":173},"Software engineering and AI","We look at both regular production-grade problems and AI-specific failure modes.\n",{"title":175,"text":176},"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":179,"useCaseKeys":180,"relatedOfferKeys":188,"caseKeys":189},[76],[112,181,113,114,182,183,82,29,184,185,186,187,83,115],"ai-prototype-naar-productie","ai-code-breekt-steeds","security-en-privacy-ai-oplossing","technische-second-opinion-ai","ai-project-overnemen-van-andere-leverancier","ai-experiment-heeft-echte-gebruikers","prototype-naar-onderhoudbaar-softwareproduct",[79,129],[],{"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":234,"proof":235,"process":236},"sq-tangle-knot","sq-orient-options","ls-route-converge","IWSlwlvSU82rOHwWTXtSCvLbfXjNUybu2L5bZ-96IJY",{"id":239,"title":240,"body":241,"catalogue":102,"cta":245,"description":11,"extension":26,"fit":250,"hero":257,"key":79,"meta":260,"navigation":31,"next":261,"outcome":272,"path":283,"price":284,"process":287,"proof":300,"relations":313,"scope":318,"seo":345,"stem":348,"summary":349,"summaryPanel":350,"visuals":355,"__hash__":358},"offers_en\u002Foffers\u002Frescue-sprint.md","Rescue Sprint",{"type":8,"value":242,"toc":243},[],{"title":11,"searchDepth":12,"depth":12,"links":244},[],{"title":246,"body":247,"primaryCta":248,"local":249},"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":251,"useCaseKeys":252},"When the technical problem is sharp enough to fix right away.\n",[253,254,255,256],"vast-op-auth-database-of-rechten","ai-koppelen-aan-bestaande-systemen","tests-evals-monitoring-voor-ai","developmentteam-loopt-vast-met-ai",{"headline":258,"intro":259,"primaryCta":248},"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":121,"items":262},[263,266,269],{"title":264,"text":265},"Done? Then we leave.","If you can continue independently, the Sprint has succeeded.\n",{"title":267,"text":268,"offerKey":79},"Another clear rescue goal?","Then you can use a next Sprint as a new fixed scope.\n",{"title":270,"text":271,"offerKey":129},"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":134,"items":273},[274,277,280],{"title":275,"text":276},"The concrete problem is tackled","The agreed technical blocker is solved or demonstrably moved forward.\n",{"title":278,"text":279},"The change is set up professionally","Where needed we add tests, evals, guardrails or production preconditions.\n",{"title":281,"text":282},"Your team can move forward again","Code, choices and follow-up are documented and technically handed over.\n","\u002Foffers\u002Frescue-sprint",{"label":285,"suffix":286,"type":148},"€5,950 excl. VAT","per Sprint",{"title":150,"steps":288},[289,291,294,297],{"title":153,"text":290},"We check whether the problem is sharp enough for a Sprint.\n",{"title":292,"text":293},"Understand context + code","We read exactly enough to intervene responsibly.\n",{"title":295,"text":296},"Solve + test","We implement the fix and add the quality layer it needs.\n",{"title":298,"text":299},"Document + hand over","We record choices and make sure your team can continue independently again.\n",{"title":165,"intro":301,"points":302,"caseKeys":312},"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",[303,306,309],{"title":304,"text":305},"Senior AI + software engineers","We step in where it gets complicated and leave when it's done.\n",{"title":307,"text":308},"We work in what is already there","We don't expect you to migrate everything to our favourite stack first.\n",{"title":310,"text":311},"Yours as soon as it's done","We document, hand over and leave as soon as you can continue on your own.\n",[],{"buyerTriggerKeys":314,"useCaseKeys":315,"relatedOfferKeys":316,"caseKeys":317},[76],[253,254,255,256],[77,129],[],{"title":191,"intro":319,"activities":320,"deliverables":329,"exclusions":338},"One Sprint has one clear rescue goal. That boundary keeps it fast and honest.\n",{"intro":321,"items":322},"We do what is technically needed to tackle the agreed problem responsibly.\n",[323,324,325,326,327,328],"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":330,"items":331},"Working engineering in the existing codebase, not an advice document someone else still has to carry out.\n",[332,333,334,335,336,337],"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":339,"items":340},"A Sprint is bounded and doesn't quietly turn into an open-ended project.\n",[341,342,343,344],"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":346,"description":347},"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":351,"result":352,"duration":353,"nextStep":354},"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":234,"proof":356,"process":357},"sq-guardrails-check","ls-rescue-repair","RBo-3uCvL4DWueBHoZFGrqKFPfwCZ1QLbywOlnLG0NY",[360,436],{"id":361,"title":362,"body":363,"description":11,"desiredOutcome":367,"extension":26,"hero":379,"key":82,"meta":381,"navigation":31,"path":382,"problem":383,"proof":395,"recognition":407,"recommendedApproach":422,"relations":424,"seo":429,"stem":432,"summary":433,"visuals":434,"__hash__":435},"useCases_en\u002Fuse-cases\u002Fai-oplossing-te-langzaam.md","The AI solution is too slow",{"type":8,"value":364,"toc":365},[],{"title":11,"searchDepth":12,"depth":12,"links":366},[],{"intro":368,"items":369},"The solution doesn't have to be instant everywhere. But it does have to feel fast enough for the process in which people actually use it.\n",[370,373,376],{"title":371,"text":372},"Faster critical flows","The steps users wait for get attention first.\n",{"title":374,"text":375},"Insight into bottlenecks","You know which part of the model, application or integration causes the wait.\n",{"title":377,"text":378},"Deliberate performance choices","Speed, quality and cost are weighed against each other instead of being optimised separately.\n",{"intro":380},"An AI feature that works correctly but needs twenty seconds for every step still feels broken. We find out where the time is really lost and which optimisations make sense.\n",{},"\u002Fuse-cases\u002Fai-oplossing-te-langzaam",{"intro":384,"causes":385},"Choosing a faster model helps little if the system meanwhile runs six unnecessary steps.\n",[386,389,392],{"title":387,"text":388},"The architecture is fully sequential","Work that could run in parallel or in the background now blocks the user.\n",{"title":390,"text":391},"Too much AI for simple tasks","Deterministic logic runs through a model where regular code would be faster.\n",{"title":393,"text":394},"Nothing is measured in a targeted way","Without timings and traces you easily end up optimising the wrong part.\n",{"intro":396,"points":397},"Speed depends on the whole system. That's why we look at AI, backend, database, integrations and the user flow at the same time.\n",[398,401,404],{"title":399,"text":400},"Measure before optimising","Find the bottleneck first, only then make technical choices.\n",{"title":402,"text":403},"AI where it adds value","Not every step needs to go through a language model.\n",{"title":405,"text":406},"UX counts too","Sometimes the best improvement lies in processing differently or giving smarter feedback.\n",{"intro":408,"signals":409},"AI latency often doesn't come from one big problem, but from a whole series of small waits added together.\n",[410,413,416,419],{"title":411,"text":412},"Every step waits for a model","Calls run one after another when that isn't always necessary.\n",{"title":414,"text":415},"Agents do much more work than expected","One user action leads to a long chain of tool and model calls.\n",{"title":417,"text":418},"Large amounts of context are sent again and again","The same information is fetched and processed over and over.\n",{"title":420,"text":421},"External systems slow down the whole flow","One slow API holds back the rest of the user experience.\n",{"intro":423},"In a Vibe Code Rescue Audit we first measure where time is actually lost. We can then optimise in a targeted way in a Rescue Sprint, without endlessly tinkering with models and prompts.\n",{"buyerTriggerKeys":425,"primaryOfferKey":77,"offerKeys":426,"caseKeys":427,"relatedUseCaseKeys":428},[76],[77,79],[],[29,113],{"title":430,"description":431},"AI solution too slow? | 9to5 software","Slow AI app or agent? 9to5 examines models, tool calls, architecture, caching and integrations and tackles the real bottleneck.\n","use-cases\u002Fai-oplossing-te-langzaam","The functionality works, but users wait so long that the product or process isn't pleasant to use in practice.\n",{"hero":90,"problem":91,"proof":92},"SBc7Xo_WFVh7eL0GKxJFFPUMszF10AfU3LJbwWTcw7c",{"id":437,"title":438,"body":439,"description":11,"desiredOutcome":443,"extension":26,"hero":455,"key":83,"meta":457,"navigation":31,"path":458,"problem":459,"proof":471,"recognition":483,"recommendedApproach":498,"relations":500,"seo":505,"stem":508,"summary":509,"visuals":510,"__hash__":513},"useCases_en\u002Fuse-cases\u002Fweg-bij-ai-platform-of-leverancier.md","We want to leave an AI platform or vendor but are technically stuck",{"type":8,"value":440,"toc":441},[],{"title":11,"searchDepth":12,"depth":12,"links":442},[],{"intro":444,"items":445},"You want the vendor to become a technical choice again, instead of a condition for your product's survival.\n",[446,449,452],{"title":447,"text":448},"Insight into real dependencies","You know which data, functionality and workflows are tied specifically to the vendor.\n",{"title":450,"text":451},"A realistic migration route","Not everything has to be replaced in one risky big bang.\n",{"title":453,"text":454},"More technical freedom of choice","The new architecture makes future changes easier.\n",{"intro":456},"A platform that gave you speed at the start can later hold you back. Maybe the costs are too high, functionality is missing or you want more control. We find out how deep the dependency really goes and how to get out in a controlled way.\n",{},"\u002Fuse-cases\u002Fweg-bij-ai-platform-of-leverancier",{"intro":460,"causes":461},"Vendor lock-in rarely sits in a single API call. Dependencies can be spread across data, code, infrastructure and operational processes.\n",[462,465,468],{"title":463,"text":464},"Convenience hides technical choices","Managed platforms combine several functions, so the boundaries only become visible when you want to leave.\n",{"title":466,"text":467},"Proprietary functionality grows along","The longer the platform is used, the more specific features become part of the product.\n",{"title":469,"text":470},"Migration risk becomes too big","Eventually nobody dares to change anything because it's unclear what will be affected.\n",{"intro":472,"points":473},"We're not tied to one model provider or AI platform. The technology should serve the product, not the other way around.\n",[474,477,480],{"title":475,"text":476},"Independent technical advice","We assess keeping, migrating and replacing as real alternatives.\n",{"title":478,"text":479},"Integrations are core work","We can build adapters and migration layers where a phased switch is smarter.\n",{"title":481,"text":482},"Deliberately reduce lock-in","The new situation should offer more freedom of choice than the old one.\n",{"intro":484,"signals":485},"Lock-in often only becomes visible the moment you actually want to change something.\n",[486,489,492,495],{"title":487,"text":488},"Exporting data turns out to be hard","Important information sits in proprietary storage or formats.\n",{"title":490,"text":491},"Workflows use platform-specific features","The functionality isn't easily available one-to-one elsewhere.\n",{"title":493,"text":494},"Costs or terms are changing","The platform is no longer as attractive as when you started.\n",{"title":496,"text":497},"Nobody knows how big a migration will be","Your own code and vendor functionality have become intertwined over time.\n",{"intro":499},"With a Vibe Code Rescue Audit we first map dependencies and migration risks. Build & Integrate can then carry out a controlled migration if that turns out to be the wisest route.\n",{"buyerTriggerKeys":501,"primaryOfferKey":77,"offerKeys":502,"caseKeys":503,"relatedUseCaseKeys":504},[76],[77,129],[],[29,184],{"title":506,"description":507},"Leave an AI platform or vendor | 9to5 software","Facing vendor lock-in with OpenAI or another AI platform? 9to5 maps dependencies and migrates models, data and workflows in a controlled way.\n","use-cases\u002Fweg-bij-ai-platform-of-leverancier","The current vendor, tool or AI platform no longer fits, but data, workflows or technical dependencies make switching hard.\n",{"hero":511,"problem":235,"proof":512},"sq-connect-nodes","ls-system-connect","UI0SAkxx7iW6IyBmiPQtsI2VrQR5eXizTsvaZCFyAP4",[],[516],{"id":517,"title":518,"approach":519,"body":533,"cta":537,"description":11,"extension":26,"hero":540,"key":76,"label":542,"meta":543,"navigation":31,"path":544,"proof":545,"relations":556,"seo":560,"stem":563,"summary":564,"visuals":565,"__hash__":566},"buyerTriggers_en\u002Fbuyer-triggers\u002Fvastgelopen-met-ai.md","We've already built something, but we're stuck.",{"title":520,"steps":521},"We step in, understand, repair and hand over.",[522,524,527,530],{"title":153,"text":523},"We establish what is actually going wrong, what is urgent and what needs to be demonstrably better after the rescue.\n",{"title":525,"text":526},"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":528,"text":529},"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":531,"text":532},"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":534,"toc":535},[],{"title":11,"searchDepth":12,"depth":12,"links":536},[],{"title":538,"body":539},"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":541},"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":546,"points":547},"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",[548,551,553],{"title":549,"text":550},"We work with existing software","A messy or AI-generated codebase is no reason to automatically start from scratch.\n",{"title":172,"text":552},"We look at everyday production problems and AI-specific failure modes, such as unreliable output and missing evals.\n",{"title":554,"text":555},"Move forward independently again","We document decisions and clear critical technical debt so your team can move forward on its own again.\n",{"useCaseKeys":557,"offerKeys":558,"caseKeys":559},[112,181,113,114,182,253,254,183,82,29,255,256,184,185,186,187,83,115],[77,79,129],[],{"title":561,"description":562},"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":234,"proof":357,"approach":357},"e0bDu3r1P4JqQOadOsQgPsL_EDOsQGpgsqBXrdwFTNw",1792049911516]