[{"data":1,"prerenderedAt":591},["ShallowReactive",2],{"footer-vacatures-en":3,"use-case-weg-bij-ai-platform-of-leverancier-en":4,"content-by-keys-offers-en-vibe-code-rescue-audit,build-integrate":94,"content-by-keys-useCases-en-ai-oplossing-te-duur,technische-second-opinion-ai":376,"content-by-keys-cases-en-":533,"content-by-keys-buyerTriggers-en-vastgelopen-met-ai":534},[],{"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\u002Fweg-bij-ai-platform-of-leverancier.md","We want to leave an AI platform or vendor but are technically stuck",{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],{"intro":15,"items":16},"You want the vendor to become a technical choice again, instead of a condition for your product's survival.\n",[17,20,23],{"title":18,"text":19},"Insight into real dependencies","You know which data, functionality and workflows are tied specifically to the vendor.\n",{"title":21,"text":22},"A realistic migration route","Not everything has to be replaced in one risky big bang.\n",{"title":24,"text":25},"More technical freedom of choice","The new architecture makes future changes easier.\n","md",{"intro":28},"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","weg-bij-ai-platform-of-leverancier",{},true,"\u002Fuse-cases\u002Fweg-bij-ai-platform-of-leverancier",{"intro":34,"causes":35},"Vendor lock-in rarely sits in a single API call. Dependencies can be spread across data, code, infrastructure and operational processes.\n",[36,39,42],{"title":37,"text":38},"Convenience hides technical choices","Managed platforms combine several functions, so the boundaries only become visible when you want to leave.\n",{"title":40,"text":41},"Proprietary functionality grows along","The longer the platform is used, the more specific features become part of the product.\n",{"title":43,"text":44},"Migration risk becomes too big","Eventually nobody dares to change anything because it's unclear what will be affected.\n",{"intro":46,"points":47},"We're not tied to one model provider or AI platform. The technology should serve the product, not the other way around.\n",[48,51,54],{"title":49,"text":50},"Independent technical advice","We assess keeping, migrating and replacing as real alternatives.\n",{"title":52,"text":53},"Integrations are core work","We can build adapters and migration layers where a phased switch is smarter.\n",{"title":55,"text":56},"Deliberately reduce lock-in","The new situation should offer more freedom of choice than the old one.\n",{"intro":58,"signals":59},"Lock-in often only becomes visible the moment you actually want to change something.\n",[60,63,66,69],{"title":61,"text":62},"Exporting data turns out to be hard","Important information sits in proprietary storage or formats.\n",{"title":64,"text":65},"Workflows use platform-specific features","The functionality isn't easily available one-to-one elsewhere.\n",{"title":67,"text":68},"Costs or terms are changing","The platform is no longer as attractive as when you started.\n",{"title":70,"text":71},"Nobody knows how big a migration will be","Your own code and vendor functionality have become intertwined over time.\n",{"intro":73},"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":75,"primaryOfferKey":77,"offerKeys":78,"caseKeys":80,"relatedUseCaseKeys":81},[76],"vastgelopen-met-ai","vibe-code-rescue-audit",[77,79],"build-integrate",[],[82,83],"ai-oplossing-te-duur","technische-second-opinion-ai",{"title":85,"description":86},"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":90,"problem":91,"proof":92},"sq-connect-nodes","sq-orient-options","ls-system-connect","UI0SAkxx7iW6IyBmiPQtsI2VrQR5eXizTsvaZCFyAP4",[95,237],{"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__":236},"offers_en\u002Foffers\u002Fvibe-code-rescue-audit.md","Vibe Code Rescue Audit",{"type":8,"value":99,"toc":100},[],{"title":11,"searchDepth":12,"depth":12,"links":101},[],null,{"title":104,"body":105,"primaryCta":106,"local":107},"No idea what to fix anymore?","Let us first figure out what you actually have. Then you can make a technical decision without blindly prompting on or throwing everything away.\n","Book a Rescue Audit","Vibe Code Rescue by senior engineers from Delft, for teams in Delft, The Hague, Rotterdam and the surrounding area.\n",{"title":109,"intro":110,"useCaseKeys":111},"When is this offer a fit?","When you sense something is technically wrong, but the actual cause or extent isn't clear yet.\n",[112,113,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,127,130],{"title":124,"text":125,"offerKey":126},"A clear rescue goal?","Then we can tackle it in a focused Rescue Sprint.\n","rescue-sprint",{"title":128,"text":129,"offerKey":79},"Turns out to be a bigger build project?","Then we scope Build & Integrate as a fixed engagement.\n",{"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,184,82,83,185,186,187,29,115],"ai-prototype-naar-productie","ai-code-breekt-steeds","security-en-privacy-ai-oplossing","ai-oplossing-te-langzaam","ai-project-overnemen-van-andere-leverancier","ai-experiment-heeft-echte-gebruikers","prototype-naar-onderhoudbaar-softwareproduct",[126,79],[],{"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":91,"process":235},"sq-tangle-knot","ls-route-converge","IWSlwlvSU82rOHwWTXtSCvLbfXjNUybu2L5bZ-96IJY",{"id":238,"title":239,"body":240,"catalogue":244,"cta":254,"description":11,"extension":26,"fit":259,"hero":266,"key":79,"meta":269,"navigation":31,"next":270,"outcome":282,"path":293,"price":294,"process":297,"proof":311,"relations":323,"scope":334,"seo":363,"stem":366,"summary":367,"summaryPanel":368,"visuals":373,"__hash__":375},"offers_en\u002Foffers\u002Fbuild-integrate.md","Build & Integrate",{"type":8,"value":241,"toc":242},[],{"title":11,"searchDepth":12,"depth":12,"links":243},[],{"audience":245,"promise":246,"deliverables":247,"note":253,"visual":92},"For organisations that know what needs to be built and want 9to5 to build and integrate it professionally.\n","Not an AI demo, but something that works with your real software, data, processes and people.\n",[248,249,250,251,252],"Architecture and production-ready implementation","Integrations with existing software and data","Permissions, error handling and human oversight","Tests, monitoring and deployment where relevant","Documentation and handover to your team","We define the scope together first, then agree a fixed price for the result.\n",{"title":255,"body":256,"primaryCta":257,"local":258},"Do you know what needs to be built?","Share the desired outcome and your existing technical context with us. If the scope is clear, we turn it into a fixed engagement.\n","Discuss what you need built","AI engineering and software implementation from Delft, for organisations in Delft, The Hague, Rotterdam and the surrounding area.\n",{"title":109,"intro":260,"useCaseKeys":261},"When the desired outcome is clear enough to scope a professional implementation.\n",[262,263,264,265],"ai-agent-laten-bouwen","interne-ai-assistent-laten-ontwikkelen","bedrijfsproces-automatiseren-met-ai","ai-toevoegen-aan-bestaande-software",{"headline":267,"intro":268,"primaryCta":257},"Not an AI demo, but something that works with your real software, data and people.","The problem and the desired direction are clear. Now it has to be built properly. We take on architecture, AI, integrations and production-grade engineering as one whole and hand it back over afterwards.\n",{},{"title":121,"items":271},[272,275,278],{"title":273,"text":274},"You take it over","That is what we work towards. We don't want you to keep needing us.\n",{"title":276,"text":277},"A new bounded question comes up later","Then we scope it again instead of automatically keeping capacity running.\n",{"title":279,"text":280,"offerKey":281},"Still too much technical uncertainty?","Then an AI Prototype Sprint or Reality Check before Build & Integrate may be wiser.\n","ai-prototype-sprint",{"title":134,"items":283},[284,287,290],{"title":285,"text":286},"Working software instead of a demo","The agreed functionality works end to end within the real technical environment.\n",{"title":288,"text":289},"Reliable integration with what is already there","Data, systems, permissions and human processes are part of the solution.\n",{"title":291,"text":292},"A product you can hand over","Architecture, code and key choices are documented well enough to continue independently.\n","\u002Foffers\u002Fbuild-integrate",{"label":295,"type":296},"Fixed price after scoping","scoped",{"title":150,"steps":298},[299,302,305,308],{"title":300,"text":301},"Scope + success criteria","We make exact enough what needs to work to agree on responsibility and price.\n",{"title":303,"text":304},"Architecture + integrations","We determine how AI, data, existing software, permissions and users come together.\n",{"title":306,"text":307},"Build + test","We implement the hard part and also test errors, edge cases and reliability.\n",{"title":309,"text":310},"Go live + hand over","We bring the solution to production in a controlled way, document it and hand it over.\n",{"title":165,"intro":312,"points":313,"caseKeys":322},"AI only becomes truly valuable when it works together with existing software, data and business processes. That is simply serious software engineering.\n",[314,317,319],{"title":315,"text":316},"The same people advise and build","Advice and execution sit with the same technical people.\n",{"title":52,"text":318},"We don't treat APIs, databases, auth and existing systems as an afterthought around the AI.\n",{"title":320,"text":321},"Production and handover are part of it","The work isn't done when the demo works, but when the solution is manageable.\n",[],{"buyerTriggerKeys":324,"useCaseKeys":326,"relatedOfferKeys":331,"caseKeys":333},[325,76],"ai-laten-bouwen",[262,263,264,265,327,328,329,330],"eigen-data-en-kennis-gebruiken-met-ai","documenten-en-mails-automatisch-verwerken","agentic-workflows-bestaande-software","tools-vervangen-door-maatwerkflow",[332,281,77,126],"ai-reality-check",[],{"title":191,"intro":335,"activities":336,"deliverables":347,"exclusions":356},"The scope is defined up front. Then you get a fixed price for the agreed result.\n",{"intro":337,"items":338},"The exact work differs per engagement, but we take responsibility for the complete technical result.\n",[339,340,341,342,343,344,345,346],"Making scope and success criteria concrete","Designing the architecture","Implementing AI functionality or an agent flow","Building integrations with existing software and data","Setting up authentication, authorisation and data flows properly","Tests, evals, monitoring and error handling where relevant","Deployment and production setup","Documentation and technical handover",{"intro":348,"items":349},"The deliverables are defined per scope and are part of the fixed price.\n",[350,351,352,353,354,355],"Working agreed functionality","Production-grade implementation","Required integrations","Relevant tests and quality checks","Technical documentation","Deployment and handover as scoped",{"intro":357,"items":358},"No unbounded consultancy and no feature list that keeps growing afterwards.\n",[359,360,361,362],"Functionality outside the agreed scope","Ongoing retainer as a standard component","External model, API and hosting costs","Additional work without a new explicit scope and price",{"title":364,"description":365},"Have AI built and integrated | Build & Integrate | 9to5 software","Have an AI agent, internal tool, MCP integration or AI feature built with Claude or ChatGPT\u002FOpenAI and professionally integrated with your software, data and processes.\n","offers\u002Fbuild-integrate","You know what needs to be built. We build it professionally, connect it to your existing software and make sure it can be handed over production-ready.\n",{"qualifier":369,"result":370,"duration":371,"nextStep":372},"Fixed price after joint scoping","Working, integrated software your team can take over","Set in the scope","Handover to your team, or further development together",{"hero":90,"proof":374,"process":92},"sq-foundation-build","jlXsSL_a-hghGaOxvEHbZ2ARDUkoaAlfXaEkKLzQpSQ",[377,456],{"id":378,"title":379,"body":380,"description":11,"desiredOutcome":384,"extension":26,"hero":396,"key":82,"meta":398,"navigation":31,"path":399,"problem":400,"proof":412,"recognition":424,"recommendedApproach":439,"relations":441,"seo":446,"stem":449,"summary":450,"visuals":451,"__hash__":455},"useCases_en\u002Fuse-cases\u002Fai-oplossing-te-duur.md","The AI solution is becoming too expensive",{"type":8,"value":381,"toc":382},[],{"title":11,"searchDepth":12,"depth":12,"links":383},[],{"intro":385,"items":386},"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",[387,390,393],{"title":388,"text":389},"Costs become transparent","You know which actions, users or processes cause the most usage.\n",{"title":391,"text":392},"Waste disappears","Unnecessary calls, context and duplicate processing are reduced in a targeted way.\n",{"title":394,"text":395},"Growth becomes more predictable","You can better estimate what more usage means financially.\n",{"intro":397},"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",{},"\u002Fuse-cases\u002Fai-oplossing-te-duur",{"intro":401,"causes":402},"AI costs are often not just a pricing problem, but also an architecture and product problem.\n",[403,406,409],{"title":404,"text":405},"Expensive models are used everywhere","Simple tasks get the same heavy model choice as complex tasks.\n",{"title":407,"text":408},"Workflows do unnecessary work","Calls, retrieval and processing are repeated while results could be reused.\n",{"title":410,"text":411},"Costs are not part of observability","So you only see waste when the invoice arrives.\n",{"intro":413,"points":414},"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",[415,418,421],{"title":416,"text":417},"Cost and quality","Cheaper doesn't help if usability collapses.\n",{"title":419,"text":420},"Architecture over loose tweaks","Routing, caching and workflow design can deliver more than prompt micro-optimisation.\n",{"title":422,"text":423},"Measurable results","Optimisation is tied to actual usage per relevant flow.\n",{"intro":425,"signals":426},"Cost problems often only become visible when an experiment successfully starts to scale.\n",[427,430,433,436],{"title":428,"text":429},"Model costs grow faster than users","Every new user causes relatively a lot of extra usage.\n",{"title":431,"text":432},"Agents make many calls per task","A simple action can quietly involve dozens of model or tool calls.\n",{"title":434,"text":435},"Large prompts are sent along every time","Context grows along with the product without it being clear what is really needed.\n",{"title":437,"text":438},"Nobody knows the cost per flow","There is a monthly invoice, but hardly any insight into what causes it.\n",{"intro":440},"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":442,"primaryOfferKey":77,"offerKeys":443,"caseKeys":444,"relatedUseCaseKeys":445},[76],[77,126],[],[184,29],{"title":447,"description":448},"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":452,"problem":453,"proof":454},"sq-bottleneck-pressure","sq-process-steps","ls-optimize-flow","AvSDQPDw5Ui68JRE-XmUiKA5-WySdoPvNHAXTC42Cu0",{"id":457,"title":458,"body":459,"description":11,"desiredOutcome":463,"extension":26,"hero":475,"key":83,"meta":477,"navigation":31,"path":478,"problem":479,"proof":491,"recognition":503,"recommendedApproach":518,"relations":520,"seo":525,"stem":528,"summary":529,"visuals":530,"__hash__":532},"useCases_en\u002Fuse-cases\u002Ftechnische-second-opinion-ai.md","We want an independent technical second opinion",{"type":8,"value":460,"toc":461},[],{"title":11,"searchDepth":12,"depth":12,"links":462},[],{"intro":464,"items":465},"You don't want an extra opinion that makes the discussion bigger. You want enough technical clarity to make a better decision yourself.\n",[466,469,472],{"title":467,"text":468},"Separate facts from assumptions","You see which technical conclusions are solid and where uncertainty remains.\n",{"title":470,"text":471},"Alternatives become visible","You know whether the proposed route really is the only logical option.\n",{"title":473,"text":474},"A concrete next decision","After the review you know what to investigate, keep, adjust or drop.\n",{"intro":476},"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":480,"causes":481},"Technical choices are not fully objective. Everyone looks at the same situation from their own experience, interests and preferences.\n",[482,485,488],{"title":483,"text":484},"Vendors mainly know their own tools","A proposal can unconsciously steer towards solutions that suit the vendor.\n",{"title":486,"text":487},"Existing teams get used to limitations","What feels normal internally can be obvious technical debt to an outsider.\n",{"title":489,"text":490},"Big decisions become final too early","Sometimes evidence is still missing for assumptions on which a far-reaching choice is based.\n",{"intro":492,"points":493},"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",[494,497,500],{"title":495,"text":496},"Engineers first","The assessment is made from the perspective of technical feasibility and risk.\n",{"title":498,"text":499},"Build, buy or change nothing","We have no stake in one specific technical outcome.\n",{"title":501,"text":502},"Follow-up is not required","If the conclusion is clear, the engagement can simply end there.\n",{"intro":504,"signals":505},"A second opinion is especially useful when the next technical step is large, expensive or hard to reverse.\n",[506,509,512,515],{"title":507,"text":508},"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":510,"text":511},"Internal opinions differ","Different engineers judge the same risks differently.\n",{"title":513,"text":514},"The architecture feels more complicated than needed","Many new tools, platforms or layers are being proposed.\n",{"title":516,"text":517},"You're facing a big investment","Before continuing, you want to know whether the technical foundation makes sense.\n",{"intro":519},"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":521,"primaryOfferKey":77,"offerKeys":522,"caseKeys":523,"relatedUseCaseKeys":524},[76],[77,126],[],[185,29],{"title":526,"description":527},"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":531,"proof":235},"sq-guardrails-check","Mz9vCsA-Sb-E2hgZP7IGG0NRPbBoSbELaFOOyNALsPo",[],[535],{"id":536,"title":537,"approach":538,"body":552,"cta":556,"description":11,"extension":26,"hero":559,"key":76,"label":561,"meta":562,"navigation":31,"path":563,"proof":564,"relations":575,"seo":583,"stem":586,"summary":587,"visuals":588,"__hash__":590},"buyerTriggers_en\u002Fbuyer-triggers\u002Fvastgelopen-met-ai.md","We've already built something, but we're stuck.",{"title":539,"steps":540},"We step in, understand, repair and hand over.",[541,543,546,549],{"title":153,"text":542},"We establish what is actually going wrong, what is urgent and what needs to be demonstrably better after the rescue.\n",{"title":544,"text":545},"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":547,"text":548},"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":550,"text":551},"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":553,"toc":554},[],{"title":11,"searchDepth":12,"depth":12,"links":555},[],{"title":557,"body":558},"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":560},"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":565,"points":566},"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",[567,570,572],{"title":568,"text":569},"We work with existing software","A messy or AI-generated codebase is no reason to automatically start from scratch.\n",{"title":172,"text":571},"We look at everyday production problems and AI-specific failure modes, such as unreliable output and missing evals.\n",{"title":573,"text":574},"Move forward independently again","We document decisions and clear critical technical debt so your team can move forward on its own again.\n",{"useCaseKeys":576,"offerKeys":581,"caseKeys":582},[112,181,113,114,182,577,578,183,184,82,579,580,83,185,186,187,29,115],"vast-op-auth-database-of-rechten","ai-koppelen-aan-bestaande-systemen","tests-evals-monitoring-voor-ai","developmentteam-loopt-vast-met-ai",[77,126,79],[],{"title":584,"description":585},"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":589,"approach":589},"ls-rescue-repair","e0bDu3r1P4JqQOadOsQgPsL_EDOsQGpgsqBXrdwFTNw",1792049912880]