[{"data":1,"prerenderedAt":443},["ShallowReactive",2],{"footer-vacatures-en":3,"use-case-is-ai-nodig-en":4,"content-by-keys-offers-en-ai-reality-check":93,"content-by-keys-useCases-en-ai-idee-technisch-haalbaar,zelf-bouwen-of-software-kopen":234,"content-by-keys-cases-en-":389,"content-by-keys-buyerTriggers-en-starten-met-ai":390},[],{"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":83,"stem":86,"summary":87,"visuals":88,"__hash__":92},"useCases_en\u002Fuse-cases\u002Fis-ai-nodig.md","Do we need AI for our idea?",{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],{"intro":15,"items":16},"You want the technically simplest solution that solves the real problem well enough. Even if there turns out to be no AI in it.\n",[17,20,23],{"title":18,"text":19},"Clarity about the real need","We sharpen which problem the user or organisation is actually trying to solve.\n",{"title":21,"text":22},"Alternatives side by side","AI is compared with rules, search functionality, automation, integrations and existing software.\n",{"title":24,"text":25},"No unnecessary complexity","You only choose AI when the benefits outweigh the extra uncertainty, cost and maintenance.\n","md",{"intro":28},"AI is a means, not a mandatory part of a modern software project. Sometimes a model delivers exactly the flexibility you need. Sometimes it mainly makes a problem more expensive, slower and less predictable.\n","is-ai-nodig",{},true,"\u002Fuse-cases\u002Fis-ai-nodig",{"intro":34,"causes":35},"AI lowers the barrier to automating complex tasks, but at the same time introduces uncertainty that regular software often doesn't have.\n",[36,39,42],{"title":37,"text":38},"Technology is chosen before the problem","So later you try to make the process fit the chosen solution.\n",{"title":40,"text":41},"Non-determinism has a price","Validation, monitoring and error handling become more important as soon as model output is part of the workflow.\n",{"title":43,"text":44},"Existing solutions are forgotten","An API, integration or standard software can sometimes deliver the same result faster and cheaper.\n",{"intro":46,"points":47},"9to5 software would rather earn from a good technical decision than from unnecessary complexity. We build AI, but have no interest in AI as the default answer to every problem.\n",[48,51,54],{"title":49,"text":50},"Software engineers, not just AI consultants","That's why we can also seriously assess simpler technical alternatives.\n",{"title":52,"text":53},"Build, buy or don't build","Not building is a valid technical conclusion.\n",{"title":55,"text":56},"No automatic follow-up engagement","If the Reality Check gives enough of an answer, nothing needs to follow.\n",{"intro":58,"signals":59},"This is an especially good question when AI was named as the solution early on, while the problem itself hasn't been worked out technically yet.\n",[60,63,66,69],{"title":61,"text":62},"The project started with \"we need to do something with AI\"","There is enthusiasm about the technology, but the concrete problem is still vague.\n",{"title":64,"text":65},"The task seems fairly predictable","You wonder whether regular rules or existing software wouldn't be enough.\n",{"title":67,"text":68},"Reliability is extremely important","Variable model output may be undesirable for the core of the process.\n",{"title":70,"text":71},"You want to avoid vendor and model complexity","AI should only be added when that dependency really delivers something.\n",{"intro":73},"The AI Reality Check deliberately compares several technical routes. The outcome can be AI, a combination of AI and regular software, or simply: don't build with AI. Only if AI really adds something do we then determine a logical next step.\n",{"buyerTriggerKeys":75,"primaryOfferKey":77,"offerKeys":78,"caseKeys":79,"relatedUseCaseKeys":80},[76],"starten-met-ai","ai-reality-check",[77],[],[81,82],"ai-idee-technisch-haalbaar","zelf-bouwen-of-software-kopen",{"title":84,"description":85},"Do we need AI for our idea? | 9to5 software","Not every problem needs AI. 9to5 compares AI with regular software, automation, integrations and existing solutions.\n","use-cases\u002Fis-ai-nodig","You have a problem or product idea and suspect AI could be a solution, but first want to know whether that is technically and practically the wisest route.\n",{"hero":89,"problem":90,"proof":91},"sq-orient-options","sq-process-steps","ls-route-converge","jY_wiimcbcgfU4hJZSC-MbkrLdhoPA3RYSnl1nrt4UI",[94],{"id":95,"title":96,"body":97,"catalogue":101,"cta":111,"description":11,"extension":26,"fit":116,"hero":122,"key":77,"meta":125,"navigation":31,"next":126,"outcome":141,"path":153,"price":154,"process":157,"proof":172,"relations":186,"scope":193,"seo":221,"stem":224,"summary":225,"summaryPanel":226,"visuals":231,"__hash__":233},"offers_en\u002Foffers\u002Fai-reality-check.md","AI Reality Check",{"type":8,"value":98,"toc":99},[],{"title":11,"searchDepth":12,"depth":12,"links":100},[],{"audience":102,"promise":103,"deliverables":104,"note":110,"visual":89},"For organisations that first want to know what's technically sound and feasible.\n","In one compact engagement, you'll learn what to do, what to avoid and what's needed technically.\n",[105,106,107,108,109],"Technical feasibility and key risks","Build \u002F buy \u002F don't build","Recommended technical approach","What AI should and shouldn't do","A concrete next step","Decision document + discussion with a senior engineer.",{"title":112,"body":113,"primaryCta":114,"local":115},"Want to know what is wise first?","Share your AI question with us. If a Reality Check isn't needed, we'll tell you.\n","Book an AI Reality Check","Senior AI and software engineering from Delft, for organisations in Delft, The Hague, Rotterdam and the surrounding area.\n",{"title":117,"intro":118,"useCaseKeys":119},"When is this offer a fit?","When the main question is not yet how to build something, but what you should be building in the first place.\n",[120,121,81,29],"processen-automatiseren-met-ai","interne-ai-assistent-met-eigen-kennis",{"headline":123,"intro":124,"primaryCta":114},"Know what to do with AI before you start building.","You see opportunities for AI, but first want to know what is wise. We examine one concrete process or up to three ideas and give you a well-founded technical direction. Even if the conclusion is that you are better off without AI.\n",{},{"title":127,"items":128},"What happens next?",[129,133,137],{"title":130,"text":131,"offerKey":132},"Prove that it works first?","Then an AI Prototype Sprint is often the logical next step.\n","ai-prototype-sprint",{"title":134,"text":135,"offerKey":136},"Keep building yourself?","Then a Vibe Code Kickstart lets us set up the technical foundation properly.\n","vibe-code-kickstart",{"title":138,"text":139,"offerKey":140},"Scope already clear enough?","Then we can go straight to Build & Integrate.\n","build-integrate",{"title":142,"items":143},"Afterwards you have...",[144,147,150],{"title":145,"text":146},"A clear technical direction","You know which approach is promising and which options you are better off leaving alone.\n",{"title":148,"text":149},"The main uncertainties on the table","Integrations, data, reliability, risks and human oversight are made concrete enough to make a decision.\n",{"title":151,"text":152},"A logical next step","You know whether to build, buy, integrate, validate something first or stop.\n","\u002Foffers\u002Fai-reality-check",{"label":155,"type":156},"€1,950 excl. VAT","fixed",{"title":158,"steps":159},"How it works.",[160,163,166,169],{"title":161,"text":162},"Sharpen the question","We determine which decision you need to make and what a good result would be.\n",{"title":164,"text":165},"Understand the technical context","We look at processes, data, existing software, integrations and preconditions.\n",{"title":167,"text":168},"Test the options","We compare realistic routes on feasibility, risk and technical complexity.\n",{"title":170,"text":171},"Deliver decision + route","You get our conclusion, technical direction and a concrete next step.\n",{"title":173,"intro":174,"points":175,"caseKeys":185},"Why should you believe this?","We don't advise from a fixed preference for AI or custom software. Because we build software ourselves, we can judge when building is wise and when it is not.\n",[176,179,182],{"title":177,"text":178},"Engineers look at the real system","We look at the AI idea and also at data, integrations, software and operations.\n",{"title":180,"text":181},"AI isn't always the answer","Plain automation, existing software or building nothing are real alternatives.\n",{"title":183,"text":184},"We can carry out the follow-up too","If building turns out to make sense, the advice doesn't have to go to another technical party first.\n",[],{"buyerTriggerKeys":187,"useCaseKeys":188,"relatedOfferKeys":191,"caseKeys":192},[76],[120,121,81,29,189,82,190],"ai-betrouwbaar-genoeg","ai-toevoegen-aan-bestaand-product",[132,136,140],[],{"title":194,"intro":195,"activities":196,"deliverables":205,"exclusions":214},"What is included in this offer?","A bounded technical investigation with a concrete decision as the result.\n",{"intro":197,"items":198},"A senior engineer examines the actual question and the context around it.\n",[199,200,201,202,203,204],"Intake and sharpening the problem","Examining one concrete process or up to three AI ideas","Assessing feasibility, dependencies, integrations and risks","Comparing build, buy, integrate or not building","Determining where AI does and does not make sense","Taking human oversight and key preconditions into account",{"intro":206,"items":207},"Not a generic AI report, but a compact decision document that lets you move forward.\n",[107,208,209,210,211,212,213],"What AI should and should not do","Rough solution direction and relevant integrations","Main risks and assumptions","Build \u002F buy \u002F don't build advice","Indication of size and the next step","Review session with a senior engineer",{"intro":215,"items":216},"The Reality Check is meant to make a decision, not to build the whole system already.\n",[217,218,219,220],"Production-ready implementation","Fully worked-out UX or product design","Extensive organisation-wide AI strategy","Unbounded research into multiple processes or business units",{"title":222,"description":223},"AI Reality Check | Technical feasibility of AI | 9to5 software","A senior AI and software engineer assesses what is feasible and worthwhile: an AI agent, Claude, ChatGPT or conventional software? With an approach, risks and next step.\n","offers\u002Fai-reality-check","In a compact engagement we determine what is technically sensible and feasible, where the risks are and what a wise next step is.\n",{"qualifier":227,"result":228,"duration":229,"nextStep":230},"Fixed price · one process or up to three AI ideas","A reasoned technical direction and build \u002F buy \u002F don't build advice","About two weeks","Build, validate with a prototype first, or deliberately stop",{"hero":89,"proof":232,"process":91},"sq-guardrails-check","yAAdWR1HeTz_g1hVnQ1w2rPY4-tRkksM8Ro6yjOmeok",[235,311],{"id":236,"title":237,"body":238,"description":11,"desiredOutcome":242,"extension":26,"hero":254,"key":81,"meta":256,"navigation":31,"path":257,"problem":258,"proof":270,"recognition":282,"recommendedApproach":297,"relations":299,"seo":304,"stem":307,"summary":308,"visuals":309,"__hash__":310},"useCases_en\u002Fuse-cases\u002Fai-idee-technisch-haalbaar.md","Is our AI idea technically feasible?",{"type":8,"value":239,"toc":240},[],{"title":11,"searchDepth":12,"depth":12,"links":241},[],{"intro":243,"items":244},"You want enough technical evidence to decide whether it is wise to invest time and budget in the idea.\n",[245,248,251],{"title":246,"text":247},"A clear feasibility verdict","You know which parts are realistic and where fundamental uncertainty remains.\n",{"title":249,"text":250},"The biggest technical risks","Data, integrations, reliability and operational limitations are made explicit.\n",{"title":252,"text":253},"A logical validation step","You know what still needs testing before you responsibly build in full.\n",{"intro":255},"An idea can sound logical on paper and still turn out to be technically hard. Conversely, something can sound complicated while a small experiment quickly brings clarity. We help you see that difference early.\n",{},"\u002Fuse-cases\u002Fai-idee-technisch-haalbaar",{"intro":259,"causes":260},"Technical feasibility is more than the question whether a model can perform the task successfully once.\n",[261,264,267],{"title":262,"text":263},"Demo and production are different requirements","An impressive example says little about consistent behaviour at scale.\n",{"title":265,"text":266},"Your own data matters a lot","The quality and availability of information can make or break the solution.\n",{"title":268,"text":269},"Integrations can be decisive","Sometimes the AI part is simple and the real complexity sits in existing systems.\n",{"intro":271,"points":272},"We look at this as engineers. Whether a concept sounds interesting matters less than what it technically takes to make it work reliably enough.\n",[273,276,279],{"title":274,"text":275},"Risks visible early","You discover technical showstoppers before the full project has started.\n",{"title":277,"text":278},"A no is also an answer","A Reality Check may also conclude that the idea is not wise in this form.\n",{"title":280,"text":281},"A concrete technical route","If it is promising, you know which parts then need to be proven or built.\n",{"intro":283,"signals":284},"This question usually comes up when the problem is clear, but the technical possibilities have not yet been sufficiently proven.\n",[285,288,291,294],{"title":286,"text":287},"A vendor says it can be done","But you want to know independently under which conditions that really holds.\n",{"title":289,"text":290},"The demos online look convincing","It's just unclear whether the same technology works with your own data and requirements.\n",{"title":292,"text":293},"One technical part determines the project","For example accuracy, latency, integration or processing of specific documents.\n",{"title":295,"text":296},"The investment after this step is large","You want to reduce uncertainty before having a full product built.\n",{"intro":298},"The AI Reality Check makes the technical assumptions explicit and determines which are plausible and which are not. If one crucial assumption can't be answered on paper yet, an AI Prototype Sprint can validate it in practice.\n",{"buyerTriggerKeys":300,"primaryOfferKey":77,"offerKeys":301,"caseKeys":302,"relatedUseCaseKeys":303},[76],[77,132],[],[189,29],{"title":305,"description":306},"Is our AI idea technically feasible? | 9to5 software","Have the technical feasibility of your AI idea assessed. 9to5 examines models, data, integrations, risks and a realistic solution direction.\n","use-cases\u002Fai-idee-technisch-haalbaar","You have a concrete AI idea and want to know whether it can really be built with the available models, data, systems and constraints.\n",{"hero":89,"problem":232,"proof":91},"nXhvMZpj-Ze0VcqpMSJ12RYkFCrsaViqtrzaF2WVJiI",{"id":312,"title":313,"body":314,"description":11,"desiredOutcome":318,"extension":26,"hero":330,"key":82,"meta":332,"navigation":31,"path":333,"problem":334,"proof":346,"recognition":358,"recommendedApproach":373,"relations":375,"seo":381,"stem":384,"summary":385,"visuals":386,"__hash__":388},"useCases_en\u002Fuse-cases\u002Fzelf-bouwen-of-software-kopen.md","Should we build ourselves, use existing software or connect systems?",{"type":8,"value":315,"toc":316},[],{"title":11,"searchDepth":12,"depth":12,"links":317},[],{"intro":319,"items":320},"You don't want to choose a platform you later have to build around, nor fund custom software for something that already exists and works fine.\n",[321,324,327],{"title":322,"text":323},"A reasoned build-buy-integrate choice","You know which parts can be standard and where custom work really adds value.\n",{"title":325,"text":326},"Understand dependencies up front","Lock-in, integrations, data and extensibility are part of the choice.\n",{"title":328,"text":329},"A practical technical route","You know where to start and which investments may come later.\n",{"intro":331},"Building yourself gives control. Existing software gives speed. Smart integration can sometimes be just enough. The best route is the one that fits what you actually need, even if it's the least exciting one technically.\n",{},"\u002Fuse-cases\u002Fzelf-bouwen-of-software-kopen",{"intro":335,"causes":336},"Build versus buy is rarely a binary choice. Many good solutions deliberately combine standard software, APIs and custom work.\n",[337,340,343],{"title":338,"text":339},"Comparing features is not enough","Data ownership, permissions, integrations and future changes often matter more than the feature list.\n",{"title":341,"text":342},"Lock-in only becomes visible later","A quick start can become expensive when important data or workflows are hard to move.\n",{"title":344,"text":345},"Custom work is too quickly seen as all-or-nothing","Sometimes only the distinguishing part needs to be built yourself.\n",{"intro":347,"points":348},"Because 9to5 both builds software and integrates existing systems, we don't automatically reason towards one type of solution.\n",[349,352,355],{"title":350,"text":351},"Custom work is not a goal in itself","We only build ourselves where that offers enough advantage.\n",{"title":353,"text":354},"Integrations are a fully-fledged route","Good existing software doesn't need to be thrown away.\n",{"title":356,"text":357},"Future freedom counts","The cheapest start isn't always the best technical choice in the longer term.\n",{"intro":359,"signals":360},"This question often arises when the first search turns up dozens of AI tools, but not a single solution fits the process exactly.\n",[361,364,367,370],{"title":362,"text":363},"Many possible tools already exist","It's hard to judge which differences matter and which are mostly marketing.\n",{"title":365,"text":366},"No product fits completely","Standard software covers a large part, but misses a few important pieces.\n",{"title":368,"text":369},"Custom software sounds attractive and expensive","You want to know what control or flexibility the extra investment really delivers.\n",{"title":371,"text":372},"Integrations can be a middle ground","Maybe one system doesn't have to do everything if existing parts can be connected well.\n",{"intro":374},"The AI Reality Check compares the relevant technical routes and makes clear what you'd better buy, connect or build yourself. If you then mainly want to develop software yourself, a Vibe Code Kickstart can lay the foundation. For larger custom implementation, Build & Integrate can follow.\n",{"buyerTriggerKeys":376,"primaryOfferKey":77,"offerKeys":377,"caseKeys":378,"relatedUseCaseKeys":379},[76],[77,136,140],[],[29,380],"vibe-coding-goed-beginnen",{"title":382,"description":383},"Build yourself, buy software or connect systems? | 9to5 software","Build versus buy for AI or automation? 9to5 compares custom software, existing software and integrations on technology, risk, cost and flexibility.\n","use-cases\u002Fzelf-bouwen-of-software-kopen","The problem is clear, but there are several technical routes. You want to know which combination of buying, building and integrating is wisest.\n",{"hero":89,"problem":387,"proof":91},"sq-connect-nodes","EszLeZUAC_mOFpltDkfCOfBHj_6V8ytDWYOk1Zj_vmQ",[],[391],{"id":392,"title":393,"approach":394,"body":409,"cta":413,"description":11,"extension":26,"hero":416,"key":76,"label":418,"meta":419,"navigation":31,"path":420,"proof":421,"relations":432,"seo":436,"stem":439,"summary":440,"visuals":441,"__hash__":442},"buyerTriggers_en\u002Fbuyer-triggers\u002Fstarten-met-ai.md","We want to get started with AI, but aren't sure how.",{"title":395,"steps":396},"From a challenge to a sound technical approach.",[397,400,403,406],{"title":398,"text":399},"Define the problem","We establish which decision you need to make, which process you want to improve and what a good result would look like.\n",{"title":401,"text":402},"Understand the context and systems","We look at existing software, data, integrations, users and technical constraints.\n",{"title":404,"text":405},"Assess the options","We compare AI, automation, existing software, integrations and custom development in terms of feasibility, risk and value.\n",{"title":407,"text":408},"Deliver a decision and a way forward","You get a concrete technical direction, the main risks and a logical next step.\n",{"type":8,"value":410,"toc":411},[],{"title":11,"searchDepth":12,"depth":12,"links":412},[],{"title":414,"body":415},"Not sure whether AI is the right solution here?","Briefly describe the idea or process you have in mind. We'll quickly tell you what looks technically promising and what a sensible first step would be.\n",{"intro":417},"You might have an idea, a process that could work better or simply a sense that AI could do more for you. We help you work out what looks promising, where the risks lie and whether AI is actually the right solution.\n","Start with AI",{},"\u002Fbuyer-triggers\u002Fstarten-met-ai",{"intro":422,"points":423},"We don't advise from a fixed preference for AI or custom software. Because we build software ourselves, we can honestly assess what is technically feasible and worthwhile, and what you are better off not building.\n",[424,426,429],{"title":177,"text":425},"We look at the AI idea, but also at the data, existing software, integrations and users.\n",{"title":427,"text":428},"AI is a tool, not the default answer","Automation, existing software, an integration or building nothing are all serious options too.\n",{"title":430,"text":431},"Advice and implementation from the same people","If building turns out to make sense, we can carry out the next steps ourselves. That keeps our advice realistic.\n",{"useCaseKeys":433,"offerKeys":434,"caseKeys":435},[120,121,81,29,189,82,190,380],[77,136,132],[],{"title":437,"description":438},"Getting started with AI? From idea to technical approach | 9to5 software","Help with a serious AI challenge. An AI agent, ChatGPT, Claude or conventional software? We assess what is feasible, what not to build and the next step.\n","buyer-triggers\u002Fstarten-met-ai","We see opportunities for AI, but first want to know what makes sense, what is feasible and what is technically sound.\n",{"hero":89,"proof":91,"approach":91},"oMS04pD9lTBstiI46yn57yKInU-_urtigoQYGlj0PWA",1792049912214]