[{"data":1,"prerenderedAt":574},["ShallowReactive",2],{"footer-vacatures-en":3,"use-case-processen-automatiseren-met-ai-en":4,"content-by-keys-offers-en-ai-reality-check,ai-prototype-sprint":94,"content-by-keys-useCases-en-is-ai-nodig,zelf-bouwen-of-software-kopen":365,"content-by-keys-cases-en-":520,"content-by-keys-buyerTriggers-en-starten-met-ai":521},[],{"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\u002Fprocessen-automatiseren-met-ai.md","Which processes are suitable for AI or automation?",{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],{"intro":15,"items":16},"You don't want to end up with a list of twenty AI ideas. You want to know where a technical investment actually makes sense.\n",[17,20,23],{"title":18,"text":19},"The best opportunities first","You know which processes combine enough value, volume and technical feasibility to explore further.\n",{"title":21,"text":22},"AI where it's needed","We distinguish between AI, regular automation, existing software and simple integrations.\n",{"title":24,"text":25},"A concrete next step","You know which question to validate or build first, or which not to pursue any further.\n","md",{"intro":28},"Maybe you see opportunities for AI everywhere. Or so many that you don't know where to start. We help determine which processes are interesting, which technology fits them and which ideas you're better off leaving alone.\n","processen-automatiseren-met-ai",{},true,"\u002Fuse-cases\u002Fprocessen-automatiseren-met-ai",{"intro":34,"causes":35},"Not every annoying process is automatically a good AI problem. The value lies in the combination of process, data, technical feasibility and impact.\n",[36,39,42],{"title":37,"text":38},"AI is taken as the starting point too quickly","A fixed rule, integration or existing tool can sometimes solve the same problem more simply and reliably.\n",{"title":40,"text":41},"The real bottleneck is still unclear","What looks like manual work at first sight may be caused by a poor process or a missing integration.\n",{"title":43,"text":44},"Feasibility differs per task","Some tasks tolerate uncertainty, others require virtually error-free behaviour.\n",{"intro":46,"points":47},"We start with the problem you're trying to solve, and only then ask which AI model fits. Sometimes the best technical conclusion is that part of it doesn't need AI at all.\n",[48,51,54],{"title":49,"text":50},"Software engineering before AI hype","We also compare AI with automation, integrations and existing software.\n",{"title":52,"text":53},"Technical feasibility counts from the start","Data, systems and operational constraints are part of the assessment.\n",{"title":55,"text":56},"We can build the follow-up too","The advice doesn't have to be translated again by another technical party afterwards.\n",{"intro":58,"signals":59},"This question often comes up when there is clear inefficiency, but it's not yet clear which technical solution fits it best.\n",[60,63,66,69],{"title":61,"text":62},"Lots of repetitive knowledge work","Employees keep reading, checking, summarising or classifying similar information.\n",{"title":64,"text":65},"Information is copied over by hand","Data moves via people from email, documents or spreadsheets into other systems.\n",{"title":67,"text":68},"There are many AI ideas at once","Different teams see opportunities, but nobody knows which are the most interesting technically and commercially.\n",{"title":70,"text":71},"You don't want to automate for the sake of it","The solution has to demonstrably reduce time, errors or friction.\n",{"intro":73},"In an AI Reality Check we examine up to three ideas or one concrete process. We assess value, technical feasibility, data, integrations, risks and build versus buy. If one part then needs to be proven in practice, an AI Prototype Sprint can be the logical next step.\n",{"buyerTriggerKeys":75,"primaryOfferKey":77,"offerKeys":78,"caseKeys":80,"relatedUseCaseKeys":81},[76],"starten-met-ai","ai-reality-check",[77,79],"ai-prototype-sprint",[],[82,83],"is-ai-nodig","zelf-bouwen-of-software-kopen",{"title":85,"description":86},"Which processes are suitable for AI or automation? | 9to5 software","Find out which business processes are suitable for AI or automation. 9to5 examines processes, systems, data and technical feasibility.\n","use-cases\u002Fprocessen-automatiseren-met-ai","You see opportunities to make manual work smarter, but first want to know where AI actually adds value and where regular automation fits better.\n",{"hero":90,"problem":91,"proof":92},"sq-process-steps","sq-orient-options","ls-workflow-flow","Z9mZqpG5Qyu0wkGGaYeR4PecFC7nvQXcfsPeGf6UX80",[95,234],{"id":96,"title":97,"body":98,"catalogue":102,"cta":111,"description":11,"extension":26,"fit":116,"hero":122,"key":77,"meta":125,"navigation":31,"next":126,"outcome":140,"path":152,"price":153,"process":156,"proof":171,"relations":185,"scope":192,"seo":220,"stem":223,"summary":224,"summaryPanel":225,"visuals":230,"__hash__":233},"offers_en\u002Foffers\u002Fai-reality-check.md","AI Reality Check",{"type":8,"value":99,"toc":100},[],{"title":11,"searchDepth":12,"depth":12,"links":101},[],{"audience":103,"promise":104,"deliverables":105,"note":110,"visual":91},"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",[106,107,108,109,24],"Technical feasibility and key risks","Build \u002F buy \u002F don't build","Recommended technical approach","What AI should and shouldn't do","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",[29,120,121,82],"interne-ai-assistent-met-eigen-kennis","ai-idee-technisch-haalbaar",{"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,132,136],{"title":130,"text":131,"offerKey":79},"Prove that it works first?","Then an AI Prototype Sprint is often the logical next step.\n",{"title":133,"text":134,"offerKey":135},"Keep building yourself?","Then a Vibe Code Kickstart lets us set up the technical foundation properly.\n","vibe-code-kickstart",{"title":137,"text":138,"offerKey":139},"Scope already clear enough?","Then we can go straight to Build & Integrate.\n","build-integrate",{"title":141,"items":142},"Afterwards you have...",[143,146,149],{"title":144,"text":145},"A clear technical direction","You know which approach is promising and which options you are better off leaving alone.\n",{"title":147,"text":148},"The main uncertainties on the table","Integrations, data, reliability, risks and human oversight are made concrete enough to make a decision.\n",{"title":150,"text":151},"A logical next step","You know whether to build, buy, integrate, validate something first or stop.\n","\u002Foffers\u002Fai-reality-check",{"label":154,"type":155},"€1,950 excl. VAT","fixed",{"title":157,"steps":158},"How it works.",[159,162,165,168],{"title":160,"text":161},"Sharpen the question","We determine which decision you need to make and what a good result would be.\n",{"title":163,"text":164},"Understand the technical context","We look at processes, data, existing software, integrations and preconditions.\n",{"title":166,"text":167},"Test the options","We compare realistic routes on feasibility, risk and technical complexity.\n",{"title":169,"text":170},"Deliver decision + route","You get our conclusion, technical direction and a concrete next step.\n",{"title":172,"intro":173,"points":174,"caseKeys":184},"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",[175,178,181],{"title":176,"text":177},"Engineers look at the real system","We look at the AI idea and also at data, integrations, software and operations.\n",{"title":179,"text":180},"AI isn't always the answer","Plain automation, existing software or building nothing are real alternatives.\n",{"title":182,"text":183},"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":186,"useCaseKeys":187,"relatedOfferKeys":190,"caseKeys":191},[76],[29,120,121,82,188,83,189],"ai-betrouwbaar-genoeg","ai-toevoegen-aan-bestaand-product",[79,135,139],[],{"title":193,"intro":194,"activities":195,"deliverables":204,"exclusions":213},"What is included in this offer?","A bounded technical investigation with a concrete decision as the result.\n",{"intro":196,"items":197},"A senior engineer examines the actual question and the context around it.\n",[198,199,200,201,202,203],"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":205,"items":206},"Not a generic AI report, but a compact decision document that lets you move forward.\n",[108,207,208,209,210,211,212],"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":214,"items":215},"The Reality Check is meant to make a decision, not to build the whole system already.\n",[216,217,218,219],"Production-ready implementation","Fully worked-out UX or product design","Extensive organisation-wide AI strategy","Unbounded research into multiple processes or business units",{"title":221,"description":222},"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":226,"result":227,"duration":228,"nextStep":229},"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":91,"proof":231,"process":232},"sq-guardrails-check","ls-route-converge","yAAdWR1HeTz_g1hVnQ1w2rPY4-tRkksM8Ro6yjOmeok",{"id":235,"title":236,"body":237,"catalogue":241,"cta":252,"description":11,"extension":26,"fit":257,"hero":261,"key":79,"meta":264,"navigation":31,"next":265,"outcome":277,"path":288,"price":289,"process":291,"proof":305,"relations":318,"scope":324,"seo":352,"stem":355,"summary":356,"summaryPanel":357,"visuals":362,"__hash__":364},"offers_en\u002Foffers\u002Fai-prototype-sprint.md","AI Prototype Sprint",{"type":8,"value":238,"toc":239},[],{"title":11,"searchDepth":12,"depth":12,"links":240},[],{"audience":242,"promise":243,"deliverables":244,"note":250,"visual":251},"For a specific AI idea whose key technical assumptions need to be validated first.\n","From one clear use case to a working end-to-end prototype that lets you really test the technology.\n",[245,246,247,248,249],"Technical architecture for one use case","Working end-to-end prototype","Up to two key integrations","Validation of key assumptions and reliability","Demo, documentation and advice on moving to production","A working technical flow, not a clickable mock-up.","ls-system-assemble",{"title":253,"body":254,"primaryCta":255,"local":256},"Prove it works technically first?","Share the use case with us. We'll help you choose the smallest prototype that actually proves something important.\n","Start an AI Prototype Sprint","AI prototyping by senior engineers from Delft, for organisations in the region.\n",{"title":117,"intro":258,"useCaseKeys":259},"When the idea is clear enough to build, but still needs to be proven before you go to production.\n",[260,188,189],"ai-prototype-laten-bouwen",{"headline":262,"intro":263,"primaryCta":255},"Prove that it works before you turn it into a complete product.","You roughly know what you want, but not yet whether the technology behaves in practice as you hope. In one bounded Sprint we build the key flow and test the assumptions that determine whether investing further is wise.\n",{},{"title":127,"items":266},[267,270,273],{"title":268,"text":269,"offerKey":139},"The prototype proves the direction","Then Build & Integrate can deliver the production version.\n",{"title":271,"text":272},"The outcome calls for adjustment","Then you have learned concretely which technical route doesn't work, without building a complete product first.\n",{"title":274,"text":275,"offerKey":276},"The prototype has become production itself","If an experiment already has real users and needs professionalising, the Rescue route is a better fit.\n","vibe-code-rescue-audit",{"title":141,"items":278},[279,282,285],{"title":280,"text":281},"A working end-to-end prototype","The key user flow actually works with the chosen AI technology and integrations.\n",{"title":283,"text":284},"Technical assumptions are tested","You know better where quality, reliability and integrations are or aren't feasible.\n",{"title":286,"text":287},"A decision about production","You know what it takes to turn the prototype into a serious product or production component.\n","\u002Foffers\u002Fai-prototype-sprint",{"label":290,"type":155},"€6,950 excl. VAT",{"title":157,"steps":292},[293,296,299,302],{"title":294,"text":295},"Define use case + success criterion","We pin down which technical assumption this Sprint needs to prove.\n",{"title":297,"text":298},"Set up architecture + flow","We choose the shortest technical route that validates the real problem.\n",{"title":300,"text":301},"Build + evaluate","We deliver the end-to-end flow and test where the solution is fragile.\n",{"title":303,"text":304},"Demo + production advice","We show what works, what is still uncertain and what a next phase needs.\n",{"title":172,"intro":306,"points":307,"caseKeys":317},"A good prototype is more than a pretty click-through demo. It answers the technical question that decides whether the concept can work.\n",[308,311,314],{"title":309,"text":310},"We test the real thing","We test real integrations, data flows and model behaviour where relevant.\n",{"title":312,"text":313},"Small enough to learn","We keep you from building half a product before the key assumption is proven.\n",{"title":315,"text":316},"Ready for a real follow-up decision","Continuing, adjusting or stopping can all be a good outcome.\n",[],{"buyerTriggerKeys":319,"useCaseKeys":321,"relatedOfferKeys":322,"caseKeys":323},[76,320],"ai-laten-bouwen",[260],[77,139,276],[],{"title":193,"intro":325,"activities":326,"deliverables":337,"exclusions":345},"One clear use case, one primary flow and a controlled amount of technology around it.\n",{"intro":327,"items":328},"We build enough to test the real technical risk, without building the complete end product right away.\n",[329,330,331,332,333,334,335,336],"Sharpening scope and success criteria","Defining the technical architecture","Building a working prototype","Up to two key external integrations","Delivering one primary end-to-end flow","Configuring the model, agent or instructions","Validating the key technical assumptions","Evaluating reliability at a high level",{"intro":338,"items":339},"A tangible prototype plus enough technical clarity for a follow-up decision.\n",[246,340,341,342,343,344],"Technical architecture direction","Validated core flow","Demo of the result","Technical documentation","Advice for production and next steps",{"intro":346,"items":347},"A Prototype Sprint proves the core. Production hardening is a separate step.\n",[348,349,350,351],"Full production guarantees or SLAs","Extensive scalability and operationalisation","Unbounded integrations or multiple main flows","Full product development beyond the agreed use case",{"title":353,"description":354},"AI Prototype Sprint | Working AI prototype | 9to5 software","Turn one AI concept into a working end-to-end prototype, for example with Claude or OpenAI. Includes architecture, integrations, validation and production advice.\n","offers\u002Fai-prototype-sprint","From one concrete AI idea to a working end-to-end prototype that lets you actually test the key technical assumptions.\n",{"qualifier":358,"result":359,"duration":360,"nextStep":361},"Fixed price · one concrete AI idea","A working end-to-end prototype with tested technical assumptions","One bounded Sprint of about three weeks","A reasoned decision about production, for example via Build & Integrate",{"hero":363,"proof":90,"process":251},"sq-foundation-build","WOLcKM4lFt5312Z6kkvWsCyd0jk_equXhLoXFeu1UMg",[366,442],{"id":367,"title":368,"body":369,"description":11,"desiredOutcome":373,"extension":26,"hero":385,"key":82,"meta":387,"navigation":31,"path":388,"problem":389,"proof":401,"recognition":413,"recommendedApproach":428,"relations":430,"seo":435,"stem":438,"summary":439,"visuals":440,"__hash__":441},"useCases_en\u002Fuse-cases\u002Fis-ai-nodig.md","Do we need AI for our idea?",{"type":8,"value":370,"toc":371},[],{"title":11,"searchDepth":12,"depth":12,"links":372},[],{"intro":374,"items":375},"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",[376,379,382],{"title":377,"text":378},"Clarity about the real need","We sharpen which problem the user or organisation is actually trying to solve.\n",{"title":380,"text":381},"Alternatives side by side","AI is compared with rules, search functionality, automation, integrations and existing software.\n",{"title":383,"text":384},"No unnecessary complexity","You only choose AI when the benefits outweigh the extra uncertainty, cost and maintenance.\n",{"intro":386},"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",{},"\u002Fuse-cases\u002Fis-ai-nodig",{"intro":390,"causes":391},"AI lowers the barrier to automating complex tasks, but at the same time introduces uncertainty that regular software often doesn't have.\n",[392,395,398],{"title":393,"text":394},"Technology is chosen before the problem","So later you try to make the process fit the chosen solution.\n",{"title":396,"text":397},"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":399,"text":400},"Existing solutions are forgotten","An API, integration or standard software can sometimes deliver the same result faster and cheaper.\n",{"intro":402,"points":403},"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",[404,407,410],{"title":405,"text":406},"Software engineers, not just AI consultants","That's why we can also seriously assess simpler technical alternatives.\n",{"title":408,"text":409},"Build, buy or don't build","Not building is a valid technical conclusion.\n",{"title":411,"text":412},"No automatic follow-up engagement","If the Reality Check gives enough of an answer, nothing needs to follow.\n",{"intro":414,"signals":415},"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",[416,419,422,425],{"title":417,"text":418},"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":420,"text":421},"The task seems fairly predictable","You wonder whether regular rules or existing software wouldn't be enough.\n",{"title":423,"text":424},"Reliability is extremely important","Variable model output may be undesirable for the core of the process.\n",{"title":426,"text":427},"You want to avoid vendor and model complexity","AI should only be added when that dependency really delivers something.\n",{"intro":429},"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":431,"primaryOfferKey":77,"offerKeys":432,"caseKeys":433,"relatedUseCaseKeys":434},[76],[77],[],[121,83],{"title":436,"description":437},"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":91,"problem":90,"proof":232},"jY_wiimcbcgfU4hJZSC-MbkrLdhoPA3RYSnl1nrt4UI",{"id":443,"title":444,"body":445,"description":11,"desiredOutcome":449,"extension":26,"hero":461,"key":83,"meta":463,"navigation":31,"path":464,"problem":465,"proof":477,"recognition":489,"recommendedApproach":504,"relations":506,"seo":512,"stem":515,"summary":516,"visuals":517,"__hash__":519},"useCases_en\u002Fuse-cases\u002Fzelf-bouwen-of-software-kopen.md","Should we build ourselves, use existing software or connect systems?",{"type":8,"value":446,"toc":447},[],{"title":11,"searchDepth":12,"depth":12,"links":448},[],{"intro":450,"items":451},"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",[452,455,458],{"title":453,"text":454},"A reasoned build-buy-integrate choice","You know which parts can be standard and where custom work really adds value.\n",{"title":456,"text":457},"Understand dependencies up front","Lock-in, integrations, data and extensibility are part of the choice.\n",{"title":459,"text":460},"A practical technical route","You know where to start and which investments may come later.\n",{"intro":462},"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":466,"causes":467},"Build versus buy is rarely a binary choice. Many good solutions deliberately combine standard software, APIs and custom work.\n",[468,471,474],{"title":469,"text":470},"Comparing features is not enough","Data ownership, permissions, integrations and future changes often matter more than the feature list.\n",{"title":472,"text":473},"Lock-in only becomes visible later","A quick start can become expensive when important data or workflows are hard to move.\n",{"title":475,"text":476},"Custom work is too quickly seen as all-or-nothing","Sometimes only the distinguishing part needs to be built yourself.\n",{"intro":478,"points":479},"Because 9to5 both builds software and integrates existing systems, we don't automatically reason towards one type of solution.\n",[480,483,486],{"title":481,"text":482},"Custom work is not a goal in itself","We only build ourselves where that offers enough advantage.\n",{"title":484,"text":485},"Integrations are a fully-fledged route","Good existing software doesn't need to be thrown away.\n",{"title":487,"text":488},"Future freedom counts","The cheapest start isn't always the best technical choice in the longer term.\n",{"intro":490,"signals":491},"This question often arises when the first search turns up dozens of AI tools, but not a single solution fits the process exactly.\n",[492,495,498,501],{"title":493,"text":494},"Many possible tools already exist","It's hard to judge which differences matter and which are mostly marketing.\n",{"title":496,"text":497},"No product fits completely","Standard software covers a large part, but misses a few important pieces.\n",{"title":499,"text":500},"Custom software sounds attractive and expensive","You want to know what control or flexibility the extra investment really delivers.\n",{"title":502,"text":503},"Integrations can be a middle ground","Maybe one system doesn't have to do everything if existing parts can be connected well.\n",{"intro":505},"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":507,"primaryOfferKey":77,"offerKeys":508,"caseKeys":509,"relatedUseCaseKeys":510},[76],[77,135,139],[],[82,511],"vibe-coding-goed-beginnen",{"title":513,"description":514},"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":91,"problem":518,"proof":232},"sq-connect-nodes","EszLeZUAC_mOFpltDkfCOfBHj_6V8ytDWYOk1Zj_vmQ",[],[522],{"id":523,"title":524,"approach":525,"body":540,"cta":544,"description":11,"extension":26,"hero":547,"key":76,"label":549,"meta":550,"navigation":31,"path":551,"proof":552,"relations":563,"seo":567,"stem":570,"summary":571,"visuals":572,"__hash__":573},"buyerTriggers_en\u002Fbuyer-triggers\u002Fstarten-met-ai.md","We want to get started with AI, but aren't sure how.",{"title":526,"steps":527},"From a challenge to a sound technical approach.",[528,531,534,537],{"title":529,"text":530},"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":532,"text":533},"Understand the context and systems","We look at existing software, data, integrations, users and technical constraints.\n",{"title":535,"text":536},"Assess the options","We compare AI, automation, existing software, integrations and custom development in terms of feasibility, risk and value.\n",{"title":538,"text":539},"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":541,"toc":542},[],{"title":11,"searchDepth":12,"depth":12,"links":543},[],{"title":545,"body":546},"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":548},"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":553,"points":554},"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",[555,557,560],{"title":176,"text":556},"We look at the AI idea, but also at the data, existing software, integrations and users.\n",{"title":558,"text":559},"AI is a tool, not the default answer","Automation, existing software, an integration or building nothing are all serious options too.\n",{"title":561,"text":562},"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":564,"offerKeys":565,"caseKeys":566},[29,120,121,82,188,83,189,511],[77,135,79],[],{"title":568,"description":569},"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":91,"proof":232,"approach":232},"oMS04pD9lTBstiI46yn57yKInU-_urtigoQYGlj0PWA",1792049912301]