[{"data":1,"prerenderedAt":564},["ShallowReactive",2],{"footer-vacatures-en":3,"use-case-security-en-privacy-ai-oplossing-en":4,"content-by-keys-offers-en-vibe-code-rescue-audit,rescue-sprint":94,"content-by-keys-useCases-en-vast-op-auth-database-of-rechten,weg-bij-ai-platform-of-leverancier":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\u002Fsecurity-en-privacy-ai-oplossing.md","We're worried about security or privacy",{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],{"intro":15,"items":16},"You want to be able to explain technically where data goes and who may do what, so you don't have to hope sensitive data is handled well.\n",[17,20,23],{"title":18,"text":19},"Clear data flows","You know which data stays internal and which external services process it.\n",{"title":21,"text":22},"Control over access","Authentication, authorisation and tenant isolation are set up deliberately.\n",{"title":24,"text":25},"Concrete risk priorities","You know which problems are truly urgent and which risks are acceptable.\n","md",{"intro":28},"Which data are we actually sending to which model? Can users see each other's data? What do we log? Where are the secrets? If you can't answer those questions convincingly, it's time to take a proper look at the technical situation.\n","security-en-privacy-ai-oplossing",{},true,"\u002Fuse-cases\u002Fsecurity-en-privacy-ai-oplossing",{"intro":34,"causes":35},"AI adds new data flows and external dependencies to ordinary software problems around security and privacy.\n",[36,39,42],{"title":37,"text":38},"Data moves through more systems","Model providers, vector stores, observability tools and integrations can all be part of the same flow.\n",{"title":40,"text":41},"AI input is less predictable","Users can provide unexpected content or try to influence system behaviour.\n",{"title":43,"text":44},"The underlying software remains decisive","Poor authorisation isn't fixed by choosing a safer language model.\n",{"intro":46,"points":47},"For us, AI security starts with ordinary software engineering, not with prompts: understanding data flows, limiting access, managing secrets and containing errors.\n",[48,51,54],{"title":49,"text":50},"End-to-end view","From user and database to model provider and logging.\n",{"title":52,"text":53},"Practical prioritisation","Not every theoretical risk gets the same urgency.\n",{"title":55,"text":56},"Able to build the fix too","The advice doesn't have to go to another technical party afterwards.\n",{"intro":58,"signals":59},"Security questions often only come up seriously when an experiment moves towards production or sensitive data.\n",[60,63,66,69],{"title":61,"text":62},"Nobody knows exactly which data goes to the model","Prompts, context and uploads are assembled in several places in the application.\n",{"title":64,"text":65},"Roles and permissions feel fragile","It's hard to demonstrate that users can only reach their own data.\n",{"title":67,"text":68},"Secrets and external services grew organically","API keys and vendors were added whenever they were needed.\n",{"title":70,"text":71},"Logging may contain sensitive content","Debugging information may expose more than is desirable.\n",{"intro":73},"A Vibe Code Rescue Audit maps the technical risks, data flows, permissions and external dependencies. Concrete improvements can then be carried out in a focused 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],"vast-op-auth-database-of-rechten","weg-bij-ai-platform-of-leverancier",{"title":85,"description":86},"Assess the security and privacy of an AI solution | 9to5 software","Concerned about security, privacy or data flows in your AI solution? 9to5 maps technical risks, permissions, vendors and data flows.\n","use-cases\u002Fsecurity-en-privacy-ai-oplossing","The solution works, but it isn't clear enough where data goes, who can access it and what technical risks there are.\n",{"hero":90,"problem":91,"proof":92},"sq-guardrails-check","sq-tangle-knot","ls-rescue-repair","kwq5CRw0CzrlXbFE7Foamr17AqEFniwI0gkZ6zHai1A",[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":191,"seo":224,"stem":227,"summary":228,"summaryPanel":229,"visuals":234,"__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":189,"caseKeys":190},[76],[112,181,113,114,182,29,183,184,185,186,187,188,83,115],"ai-prototype-naar-productie","ai-code-breekt-steeds","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",[79,129],[],{"title":192,"intro":193,"activities":194,"deliverables":206,"exclusions":217},"What is included in this offer?","A technical diagnosis of one existing application or codebase, aimed at decision-making.\n",{"intro":195,"items":196},"We look broadly enough to find structural causes, without turning it into a theoretical code review.\n",[197,198,199,200,201,202,203,204,205],"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":207,"items":208},"You get a technical verdict you can actually base a follow-up on.\n",[209,210,211,212,213,214,215,216],"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":218,"items":219},"The Audit delivers understanding and a plan. Major fixes don't quietly become part of the analysis.\n",[220,221,222,223],"Full repair of the codebase","Complete rewrite","Unbounded pentest or formal security audit","Product development beyond small diagnostic changes",{"title":225,"description":226},"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":230,"result":231,"duration":232,"nextStep":233},"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":91,"proof":235,"process":236},"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":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__":355},"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",[82,253,254,255],"ai-koppelen-aan-bestaande-systemen","tests-evals-monitoring-voor-ai","developmentteam-loopt-vast-met-ai",{"headline":257,"intro":258,"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":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":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":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":148},"€5,950 excl. VAT","per Sprint",{"title":150,"steps":287},[288,290,293,296],{"title":153,"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":165,"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],[82,253,254,255],[77,129],[],{"title":192,"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":91,"proof":90,"process":92},"RBo-3uCvL4DWueBHoZFGrqKFPfwCZ1QLbywOlnLG0NY",[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\u002Fvast-op-auth-database-of-rechten.md","We're stuck on authentication, the database or permissions",{"type":8,"value":361,"toc":362},[],{"title":11,"searchDepth":12,"depth":12,"links":363},[],{"intro":365,"items":366},"You don't want a complete redesign. You want the concrete technical blocker to disappear without introducing new problems.\n",[367,370,373],{"title":368,"text":369},"The blocker is solved","The auth, database or permission flow in question demonstrably works as intended.\n",{"title":371,"text":372},"The solution is safe","We fix the problem without compromising data integrity or access.\n",{"title":374,"text":375},"Your team can move on","The relevant choices and points of attention are clear enough to carry on developing yourselves.\n",{"intro":377},"Sometimes the problem isn't vague at all. Login doesn't work properly, permissions leak, a migration fails or your data model gets in the way. Then you don't need a big advisory engagement, but someone who solves the hard technical part.\n",{},"\u002Fuse-cases\u002Fvast-op-auth-database-of-rechten",{"intro":381,"causes":382},"Authentication, authorisation and databases are fundamental parts of software. A quick workaround can therefore cause much bigger problems.\n",[383,386,389],{"title":384,"text":385},"The problem touches several layers","Frontend, backend, provider, database and permission model all need the same picture of the user.\n",{"title":387,"text":388},"Mistakes have serious consequences","A wrong fix can lead to data loss or access to data that should not be visible.\n",{"title":390,"text":391},"External providers add complexity","Auth and database platforms abstract a lot away, until you leave their happy flow.\n",{"intro":393,"points":394},"These are ordinary senior software engineering problems. That's exactly why they don't necessarily need a whole AI engagement around them.\n",[395,398,401],{"title":396,"text":397},"Straight into the code","No weeks of analysis when the technical problem is already sharp enough.\n",{"title":399,"text":400},"Security counts","A working login isn't enough if the permissions are wrong afterwards.\n",{"title":402,"text":403},"No permanent dependency","We fix, test, document and hand over again.\n",{"intro":405,"signals":406},"This is usually a well-defined technical problem that can still eat up a surprising amount of time.\n",[407,410,413,416],{"title":408,"text":409},"Login or OAuth doesn't work reliably","Redirects, callbacks, tokens or sessions behave differently than expected.\n",{"title":411,"text":412},"Roles and permissions are unclear","Users can do too much, too little or inconsistently different things.\n",{"title":414,"text":415},"The data model gets in the way","New functionality doesn't fit well with the existing tables and relations.\n",{"title":417,"text":418},"Migrations or data problems block deployment","You can't safely continue without first solving the underlying database problems.\n",{"intro":420},"If the problem is clear enough during the intake, we start a Rescue Sprint straight away. We reproduce the problem, understand the relevant code and systems and fix the blocker in a targeted way. Only if the cause turns out to be much more fundamental is a broader audit needed first.\n",{"buyerTriggerKeys":422,"primaryOfferKey":79,"offerKeys":423,"caseKeys":424,"relatedUseCaseKeys":425},[76],[79,77],[],[29,182],{"title":427,"description":428},"Stuck on authentication, database or permissions? | 9to5 software","Stuck on auth, the database or authorisation? Senior engineers from 9to5 step in and solve the technical blocker.\n","use-cases\u002Fvast-op-auth-database-of-rechten","The feature is clear, but a concrete technical problem around login, data or authorisation is holding the project back.\n",{"hero":91,"problem":90,"proof":92},"xePc9f5VpI4uja65DBv7Mo4zT3X8M-utSIVOkv5ZLHs",{"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\u002Fweg-bij-ai-platform-of-leverancier.md","We want to leave an AI platform or vendor but are technically stuck",{"type":8,"value":437,"toc":438},[],{"title":11,"searchDepth":12,"depth":12,"links":439},[],{"intro":441,"items":442},"You want the vendor to become a technical choice again, instead of a condition for your product's survival.\n",[443,446,449],{"title":444,"text":445},"Insight into real dependencies","You know which data, functionality and workflows are tied specifically to the vendor.\n",{"title":447,"text":448},"A realistic migration route","Not everything has to be replaced in one risky big bang.\n",{"title":450,"text":451},"More technical freedom of choice","The new architecture makes future changes easier.\n",{"intro":453},"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":457,"causes":458},"Vendor lock-in rarely sits in a single API call. Dependencies can be spread across data, code, infrastructure and operational processes.\n",[459,462,465],{"title":460,"text":461},"Convenience hides technical choices","Managed platforms combine several functions, so the boundaries only become visible when you want to leave.\n",{"title":463,"text":464},"Proprietary functionality grows along","The longer the platform is used, the more specific features become part of the product.\n",{"title":466,"text":467},"Migration risk becomes too big","Eventually nobody dares to change anything because it's unclear what will be affected.\n",{"intro":469,"points":470},"We're not tied to one model provider or AI platform. The technology should serve the product, not the other way around.\n",[471,474,477],{"title":472,"text":473},"Independent technical advice","We assess keeping, migrating and replacing as real alternatives.\n",{"title":475,"text":476},"Integrations are core work","We can build adapters and migration layers where a phased switch is smarter.\n",{"title":478,"text":479},"Deliberately reduce lock-in","The new situation should offer more freedom of choice than the old one.\n",{"intro":481,"signals":482},"Lock-in often only becomes visible the moment you actually want to change something.\n",[483,486,489,492],{"title":484,"text":485},"Exporting data turns out to be hard","Important information sits in proprietary storage or formats.\n",{"title":487,"text":488},"Workflows use platform-specific features","The functionality isn't easily available one-to-one elsewhere.\n",{"title":490,"text":491},"Costs or terms are changing","The platform is no longer as attractive as when you started.\n",{"title":493,"text":494},"Nobody knows how big a migration will be","Your own code and vendor functionality have become intertwined over time.\n",{"intro":496},"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":498,"primaryOfferKey":77,"offerKeys":499,"caseKeys":500,"relatedUseCaseKeys":501},[76],[77,129],[],[184,185],{"title":503,"description":504},"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":508,"problem":235,"proof":509},"sq-connect-nodes","ls-system-connect","UI0SAkxx7iW6IyBmiPQtsI2VrQR5eXizTsvaZCFyAP4",[],[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":172,"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},[112,181,113,114,182,82,253,29,183,184,254,255,185,186,187,188,83,115],[77,79,129],[],{"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":91,"proof":92,"approach":92},"e0bDu3r1P4JqQOadOsQgPsL_EDOsQGpgsqBXrdwFTNw",1792049912434]