[{"data":1,"prerenderedAt":460},["ShallowReactive",2],{"offer-rescue-sprint-en":3,"footer-vacatures-en":143,"content-by-keys-useCases-en-vast-op-auth-database-of-rechten,ai-koppelen-aan-bestaande-systemen,tests-evals-monitoring-voor-ai,developmentteam-loopt-vast-met-ai":144,"content-by-keys-cases-en-":459},{"id":4,"title":5,"body":6,"catalogue":13,"cta":14,"description":10,"extension":19,"fit":20,"hero":28,"key":31,"meta":32,"navigation":33,"next":34,"outcome":47,"path":59,"price":60,"process":64,"proof":79,"relations":93,"scope":100,"seo":128,"stem":131,"summary":132,"summaryPanel":133,"visuals":138,"__hash__":142},"offers_en\u002Foffers\u002Frescue-sprint.md","Rescue Sprint",{"type":7,"value":8,"toc":9},"minimark",[],{"title":10,"searchDepth":11,"depth":11,"links":12},"",2,[],null,{"title":15,"body":16,"primaryCta":17,"local":18},"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","md",{"title":21,"intro":22,"useCaseKeys":23},"When is this offer a fit?","When the technical problem is sharp enough to fix right away.\n",[24,25,26,27],"vast-op-auth-database-of-rechten","ai-koppelen-aan-bestaande-systemen","tests-evals-monitoring-voor-ai","developmentteam-loopt-vast-met-ai",{"headline":29,"intro":30,"primaryCta":17},"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","rescue-sprint",{},true,{"title":35,"items":36},"What happens next?",[37,40,43],{"title":38,"text":39},"Done? Then we leave.","If you can continue independently, the Sprint has succeeded.\n",{"title":41,"text":42,"offerKey":31},"Another clear rescue goal?","Then you can use a next Sprint as a new fixed scope.\n",{"title":44,"text":45,"offerKey":46},"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":48,"items":49},"Afterwards you have...",[50,53,56],{"title":51,"text":52},"The concrete problem is tackled","The agreed technical blocker is solved or demonstrably moved forward.\n",{"title":54,"text":55},"The change is set up professionally","Where needed we add tests, evals, guardrails or production preconditions.\n",{"title":57,"text":58},"Your team can move forward again","Code, choices and follow-up are documented and technically handed over.\n","\u002Foffers\u002Frescue-sprint",{"label":61,"suffix":62,"type":63},"€5,950 excl. VAT","per Sprint","fixed",{"title":65,"steps":66},"How it works.",[67,70,73,76],{"title":68,"text":69},"Confirm the rescue goal","We check whether the problem is sharp enough for a Sprint.\n",{"title":71,"text":72},"Understand context + code","We read exactly enough to intervene responsibly.\n",{"title":74,"text":75},"Solve + test","We implement the fix and add the quality layer it needs.\n",{"title":77,"text":78},"Document + hand over","We record choices and make sure your team can continue independently again.\n",{"title":80,"intro":81,"points":82,"caseKeys":92},"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",[83,86,89],{"title":84,"text":85},"Senior AI + software engineers","We step in where it gets complicated and leave when it's done.\n",{"title":87,"text":88},"We work in what is already there","We don't expect you to migrate everything to our favourite stack first.\n",{"title":90,"text":91},"Yours as soon as it's done","We document, hand over and leave as soon as you can continue on your own.\n",[],{"buyerTriggerKeys":94,"useCaseKeys":96,"relatedOfferKeys":97,"caseKeys":99},[95],"vastgelopen-met-ai",[24,25,26,27],[98,46],"vibe-code-rescue-audit",[],{"title":101,"intro":102,"activities":103,"deliverables":112,"exclusions":121},"What is included in this offer?","One Sprint has one clear rescue goal. That boundary keeps it fast and honest.\n",{"intro":104,"items":105},"We do what is technically needed to tackle the agreed problem responsibly.\n",[106,107,108,109,110,111],"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":113,"items":114},"Working engineering in the existing codebase, not an advice document someone else still has to carry out.\n",[115,116,117,118,119,120],"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":122,"items":123},"A Sprint is bounded and doesn't quietly turn into an open-ended project.\n",[124,125,126,127],"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":129,"description":130},"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":134,"result":135,"duration":136,"nextStep":137},"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":139,"proof":140,"process":141},"sq-tangle-knot","sq-guardrails-check","ls-rescue-repair","RBo-3uCvL4DWueBHoZFGrqKFPfwCZ1QLbywOlnLG0NY",[],[145,223,302,381],{"id":146,"title":147,"body":148,"description":10,"desiredOutcome":152,"extension":19,"hero":164,"key":24,"meta":166,"navigation":33,"path":167,"problem":168,"proof":180,"recognition":192,"recommendedApproach":207,"relations":209,"seo":216,"stem":219,"summary":220,"visuals":221,"__hash__":222},"useCases_en\u002Fuse-cases\u002Fvast-op-auth-database-of-rechten.md","We're stuck on authentication, the database or permissions",{"type":7,"value":149,"toc":150},[],{"title":10,"searchDepth":11,"depth":11,"links":151},[],{"intro":153,"items":154},"You don't want a complete redesign. You want the concrete technical blocker to disappear without introducing new problems.\n",[155,158,161],{"title":156,"text":157},"The blocker is solved","The auth, database or permission flow in question demonstrably works as intended.\n",{"title":159,"text":160},"The solution is safe","We fix the problem without compromising data integrity or access.\n",{"title":162,"text":163},"Your team can move on","The relevant choices and points of attention are clear enough to carry on developing yourselves.\n",{"intro":165},"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":169,"causes":170},"Authentication, authorisation and databases are fundamental parts of software. A quick workaround can therefore cause much bigger problems.\n",[171,174,177],{"title":172,"text":173},"The problem touches several layers","Frontend, backend, provider, database and permission model all need the same picture of the user.\n",{"title":175,"text":176},"Mistakes have serious consequences","A wrong fix can lead to data loss or access to data that should not be visible.\n",{"title":178,"text":179},"External providers add complexity","Auth and database platforms abstract a lot away, until you leave their happy flow.\n",{"intro":181,"points":182},"These are ordinary senior software engineering problems. That's exactly why they don't necessarily need a whole AI engagement around them.\n",[183,186,189],{"title":184,"text":185},"Straight into the code","No weeks of analysis when the technical problem is already sharp enough.\n",{"title":187,"text":188},"Security counts","A working login isn't enough if the permissions are wrong afterwards.\n",{"title":190,"text":191},"No permanent dependency","We fix, test, document and hand over again.\n",{"intro":193,"signals":194},"This is usually a well-defined technical problem that can still eat up a surprising amount of time.\n",[195,198,201,204],{"title":196,"text":197},"Login or OAuth doesn't work reliably","Redirects, callbacks, tokens or sessions behave differently than expected.\n",{"title":199,"text":200},"Roles and permissions are unclear","Users can do too much, too little or inconsistently different things.\n",{"title":202,"text":203},"The data model gets in the way","New functionality doesn't fit well with the existing tables and relations.\n",{"title":205,"text":206},"Migrations or data problems block deployment","You can't safely continue without first solving the underlying database problems.\n",{"intro":208},"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":210,"primaryOfferKey":31,"offerKeys":211,"caseKeys":212,"relatedUseCaseKeys":213},[95],[31,98],[],[214,215],"security-en-privacy-ai-oplossing","ai-code-breekt-steeds",{"title":217,"description":218},"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":139,"problem":140,"proof":141},"xePc9f5VpI4uja65DBv7Mo4zT3X8M-utSIVOkv5ZLHs",{"id":224,"title":225,"body":226,"description":10,"desiredOutcome":230,"extension":19,"hero":242,"key":25,"meta":244,"navigation":33,"path":245,"problem":246,"proof":258,"recognition":270,"recommendedApproach":285,"relations":287,"seo":293,"stem":296,"summary":297,"visuals":298,"__hash__":301},"useCases_en\u002Fuse-cases\u002Fai-koppelen-aan-bestaande-systemen.md","We can't get the solution connected to existing systems",{"type":7,"value":227,"toc":228},[],{"title":10,"searchDepth":11,"depth":11,"links":229},[],{"intro":231,"items":232},"The AI shouldn't stay an isolated island. It should become a reliable part of the systems and processes that already exist.\n",[233,236,239],{"title":234,"text":235},"Reliable data exchange","Data arrives at the right moment, in the right format and at the right system.\n",{"title":237,"text":238},"Errors are manageable","Timeouts, duplicates and temporary outages don't immediately lead to unpredictable behaviour.\n",{"title":240,"text":241},"Permissions stay correct","The integration respects existing users, roles and access rules.\n",{"intro":243},"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":247,"causes":248},"An integration is more than a line between two boxes in an architecture diagram. It also has to cope with real-world conditions.\n",[249,252,255],{"title":250,"text":251},"Systems speak different languages","Data models, statuses and responsibilities rarely map one-to-one.\n",{"title":253,"text":254},"External systems are not always available","Retries, queues and error handling become important as soon as the integration reaches production.\n",{"title":256,"text":257},"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":259,"points":260},"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",[261,264,267],{"title":262,"text":263},"Existing software is the starting point","The organisation doesn't have to adapt to the AI solution first.\n",{"title":265,"text":266},"Engineering around the API","We also design retries, error handling, logging and permissions.\n",{"title":268,"text":269},"No demo integrations","The integration has to stay usable under real conditions.\n",{"intro":271,"signals":272},"Often the AI part has already been proven and the real technical blocker lies in everything around it.\n",[273,276,279,282],{"title":274,"text":275},"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":277,"text":278},"Authentication between systems gets stuck","Tokens, service accounts or user delegation make the integration more complicated.\n",{"title":280,"text":281},"Data drifts apart","Different systems use different identifiers, statuses or data models.\n",{"title":283,"text":284},"The happy flow works, errors don't","As soon as an external system is temporarily unavailable, the workflow loses track.\n",{"intro":286},"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":288,"primaryOfferKey":31,"offerKeys":289,"caseKeys":290,"relatedUseCaseKeys":291},[95],[31,46],[],[24,292],"ai-project-overnemen-van-andere-leverancier",{"title":294,"description":295},"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":299,"problem":139,"proof":300},"sq-connect-nodes","ls-system-connect","4sCin98vwNyw5GXs3xalBs9ncmpDvENKXA0rH4xhya4",{"id":303,"title":304,"body":305,"description":10,"desiredOutcome":309,"extension":19,"hero":321,"key":26,"meta":323,"navigation":33,"path":324,"problem":325,"proof":337,"recognition":349,"recommendedApproach":364,"relations":366,"seo":372,"stem":375,"summary":376,"visuals":377,"__hash__":380},"useCases_en\u002Fuse-cases\u002Ftests-evals-monitoring-voor-ai.md","We're missing tests, evals or monitoring",{"type":7,"value":306,"toc":307},[],{"title":10,"searchDepth":11,"depth":11,"links":308},[],{"intro":310,"items":311},"You want to change things with confidence because you quickly see what a new prompt, model version or code change actually does.\n",[312,315,318],{"title":313,"text":314},"Regressions become visible","Important existing situations are automatically checked again.\n",{"title":316,"text":317},"AI quality becomes measurable","You compare changes against relevant examples and criteria.\n",{"title":319,"text":320},"Production gives feedback","Errors, latency and unusual behaviour no longer disappear quietly into logs.\n",{"intro":322},"\"It feels better\" is not a reliable test strategy. If you use AI functionality seriously, you need to be able to see what changes do and when things go wrong in production. We help set up that feedback loop.\n",{},"\u002Fuse-cases\u002Ftests-evals-monitoring-voor-ai",{"intro":326,"causes":327},"Traditional software tests remain important, but AI adds behaviour for which there isn't always one exactly correct answer.\n",[328,331,334],{"title":329,"text":330},"AI output is probabilistic","Exact string comparisons are not enough for many AI tasks.\n",{"title":332,"text":333},"Good examples aren't recorded","Knowledge of what is right and wrong mainly lives in heads and scattered chats.\n",{"title":335,"text":336},"Observability stops at technical errors","An HTTP 200 says nothing about the quality of the answer.\n",{"intro":338,"points":339},"A measurement layer is only useful to us if it helps engineers see faster whether a change is safe and actually better.\n",[340,343,346],{"title":341,"text":342},"Regular tests where possible","Deterministic software simply stays deterministically testable.\n",{"title":344,"text":345},"Evals where needed","AI behaviour gets examples and criteria that fit the real use case.\n",{"title":347,"text":348},"Production data closes the loop","Monitoring shows which real-world situations need attention.\n",{"intro":350,"signals":351},"Without a good feedback loop, an AI product becomes harder and harder to develop responsibly.\n",[352,355,358,361],{"title":353,"text":354},"Testing is mostly manual","After every change someone tries a few known examples.\n",{"title":356,"text":357},"Prompt changes are hard to compare","You can't objectively tell whether version B is really better than version A.\n",{"title":359,"text":360},"Production errors are discovered by users","The system itself hardly flags deviating behaviour.\n",{"title":362,"text":363},"Model updates feel risky","A new provider or model version can change behaviour without clear warning.\n",{"intro":365},"If the scope is clear, we set up a practical feedback loop in a Rescue Sprint with the right combination of tests, evals, traces and monitoring. If broader research is needed first, we start with an audit.\n",{"buyerTriggerKeys":367,"primaryOfferKey":31,"offerKeys":368,"caseKeys":369,"relatedUseCaseKeys":370},[95],[31,98],[],[371,215],"ai-agent-niet-betrouwbaar",{"title":373,"description":374},"Tests, evals and monitoring for AI | 9to5 software","AI without proper tests, LLM evals or monitoring? 9to5 helps set up measurable quality, regression tests and production observability.\n","use-cases\u002Ftests-evals-monitoring-voor-ai","The AI functionality runs, but nobody can objectively see whether changes make it better, worse or quietly break something.\n",{"hero":140,"problem":378,"proof":379},"sq-process-steps","ls-workflow-flow","HLgbDqrGnq-G64ciWMNMDChkwkuEQEyI9a7eCclpOe0",{"id":382,"title":383,"body":384,"description":10,"desiredOutcome":388,"extension":19,"hero":400,"key":27,"meta":402,"navigation":33,"path":403,"problem":404,"proof":416,"recognition":428,"recommendedApproach":443,"relations":445,"seo":451,"stem":454,"summary":455,"visuals":456,"__hash__":458},"useCases_en\u002Fuse-cases\u002Fdevelopmentteam-loopt-vast-met-ai.md","Our own development team is technically stuck",{"type":7,"value":385,"toc":386},[],{"title":10,"searchDepth":11,"depth":11,"links":387},[],{"intro":389,"items":390},"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",[391,394,397],{"title":392,"text":393},"The hard part gets solved","Senior engineers tackle exactly the part the team is stuck on.\n",{"title":395,"text":396},"Knowledge stays in-house","Your engineers understand the solution and the most important trade-offs.\n",{"title":398,"text":399},"No extra dependency","After the rescue, 9to5 doesn't need to remain part of the team permanently.\n",{"intro":401},"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",{},"\u002Fuse-cases\u002Fdevelopmentteam-loopt-vast-met-ai",{"intro":405,"causes":406},"AI projects combine several disciplines. Even a strong development team doesn't need to have immediate experience with every specialist part.\n",[407,410,413],{"title":408,"text":409},"The problem is multidisciplinary","Software architecture, models, data, integrations and observability all touch.\n",{"title":411,"text":412},"Experience with this specific failure mode is missing","Some problems are solved much faster when you've seen them before.\n",{"title":414,"text":415},"Internal experimenting gets expensive","After several failed routes, searching further costs more than temporary specialist help.\n",{"intro":417,"points":418},"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",[419,422,425],{"title":420,"text":421},"Engineers work with engineers","No advisory layer between the problem and the people who actually change the code.\n",{"title":423,"text":424},"The existing stack remains the starting point","We don't bring in a new tool or architecture by default.\n",{"title":426,"text":427},"Handover from the start","The solution doesn't become needlessly dependent on whoever built it.\n",{"intro":429,"signals":430},"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",[431,434,437,440],{"title":432,"text":433},"The team keeps returning to the same problem","Different solutions are tried without a structural breakthrough.\n",{"title":435,"text":436},"AI-specific choices remain uncertain","Model behaviour, evals, agent architecture or retrieval call for different experience.\n",{"title":438,"text":439},"An integration turns out much harder than expected","The problem sits on the boundary between existing software and the new AI functionality.\n",{"title":441,"text":442},"A senior hire is disproportionate","You need specific expertise now, but not necessarily permanently.\n",{"intro":444},"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":446,"primaryOfferKey":31,"offerKeys":447,"caseKeys":448,"relatedUseCaseKeys":449},[95],[31,98],[],[450,25],"technische-second-opinion-ai",{"title":452,"description":453},"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":139,"problem":457,"proof":141},"sq-orient-options","G-CaoUkXnekooXGZnXL-EzJ47Frx3e9u27FGNRjxr3k",[],1792049910231]