[{"data":1,"prerenderedAt":583},["ShallowReactive",2],{"footer-vacatures-en":3,"use-case-bedrijfsproces-automatiseren-met-ai-en":4,"content-by-keys-offers-en-build-integrate,ai-prototype-sprint":94,"content-by-keys-useCases-en-documenten-en-mails-automatisch-verwerken,tools-vervangen-door-maatwerkflow":372,"content-by-keys-cases-en-":526,"content-by-keys-buyerTriggers-en-ai-laten-bouwen":527},[],{"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\u002Fbedrijfsproces-automatiseren-met-ai.md","Automate a business process with AI",{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],{"intro":15,"items":16},"You don't want as much AI as possible. You want less manual work, fewer errors and a process that stays technically manageable.\n",[17,20,23],{"title":18,"text":19},"Less repetitive work","Predictable or time-consuming steps are carried out automatically.\n",{"title":21,"text":22},"AI only where it adds something","Interpretation and unstructured information go to AI; fixed rules stay regular software.\n",{"title":24,"text":25},"People stay in control","Critical exceptions or decisions can deliberately stay with an employee.\n","md",{"intro":28},"Not every process gets better with a fully autonomous agent. Sometimes the best solution is regular automation with one smart AI step in between. We build the workflow that fits the process.\n","bedrijfsproces-automatiseren-met-ai",{},true,"\u002Fuse-cases\u002Fbedrijfsproces-automatiseren-met-ai",{"intro":34,"causes":35},"AI automation works best when you first technically split the process into deterministic and non-deterministic steps.\n",[36,39,42],{"title":37,"text":38},"Not every step needs AI","Using a language model for fixed rules makes processes more expensive and less predictable.\n",{"title":40,"text":41},"Exceptions determine reliability","The system has to know when continuing automatically is not wise.\n",{"title":43,"text":44},"Integrations are part of the process","The workflow has to be able to read and write in the systems employees already use today.\n",{"intro":46,"points":47},"For us AI is one tool within software automation. So we don't make a process artificially agentic when a simpler design is more reliable.\n",[48,51,54],{"title":49,"text":50},"Process before technology","The desired outcome determines which steps need AI.\n",{"title":52,"text":53},"Existing systems stay usable","Integrations prevent an automation from becoming yet another standalone system.\n",{"title":55,"text":56},"Human oversight is part of the design","We explicitly design where exceptions should go to an employee.\n",{"intro":58,"signals":59},"Processes with a lot of copying, checking, interpreting and passing on are a good fit.\n",[60,63,66,69],{"title":61,"text":62},"People move information between systems","A large part of the work consists of reading, retyping or classifying.\n",{"title":64,"text":65},"The same decision rules keep coming back","A workflow usually follows a fixed pattern with a limited number of exceptions.\n",{"title":67,"text":68},"Unstructured information blocks classic automation","Emails, documents or free text first have to be interpreted.\n",{"title":70,"text":71},"Existing software has to stay part of it","You don't want to replace all current systems to make one process smarter.\n",{"intro":73},"With Build & Integrate we design and build the complete workflow around the existing process. If there is technical uncertainty about a crucial AI step, we can validate it first in an AI Prototype Sprint.\n",{"buyerTriggerKeys":75,"primaryOfferKey":77,"offerKeys":78,"caseKeys":80,"relatedUseCaseKeys":81},[76],"ai-laten-bouwen","build-integrate",[77,79],"ai-prototype-sprint",[],[82,83],"documenten-en-mails-automatisch-verwerken","tools-vervangen-door-maatwerkflow",{"title":85,"description":86},"Automate a business process with AI | 9to5 software","Automating a business process with AI? 9to5 builds workflows that practically combine AI, existing software, data and human oversight.\n","use-cases\u002Fbedrijfsproces-automatiseren-met-ai","The process is clear and contains work that could be smarter or largely automatic. Now it has to become a reliable technical workflow.\n",{"hero":90,"problem":91,"proof":92},"sq-process-steps","sq-guardrails-check","ls-workflow-flow","-G_t_-Jsnlyir8qFMNtC3gxskycjna1O6PRo9qtkdak",[95,241],{"id":96,"title":97,"body":98,"catalogue":102,"cta":113,"description":11,"extension":26,"fit":118,"hero":125,"key":77,"meta":128,"navigation":31,"next":129,"outcome":141,"path":153,"price":154,"process":157,"proof":172,"relations":186,"scope":197,"seo":227,"stem":230,"summary":231,"summaryPanel":232,"visuals":237,"__hash__":240},"offers_en\u002Foffers\u002Fbuild-integrate.md","Build & Integrate",{"type":8,"value":99,"toc":100},[],{"title":11,"searchDepth":12,"depth":12,"links":101},[],{"audience":103,"promise":104,"deliverables":105,"note":111,"visual":112},"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",[106,107,108,109,110],"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","ls-system-connect",{"title":114,"body":115,"primaryCta":116,"local":117},"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":119,"intro":120,"useCaseKeys":121},"When is this offer a fit?","When the desired outcome is clear enough to scope a professional implementation.\n",[122,123,29,124],"ai-agent-laten-bouwen","interne-ai-assistent-laten-ontwikkelen","ai-toevoegen-aan-bestaande-software",{"headline":126,"intro":127,"primaryCta":116},"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":130,"items":131},"What happens next?",[132,135,138],{"title":133,"text":134},"You take it over","That is what we work towards. We don't want you to keep needing us.\n",{"title":136,"text":137},"A new bounded question comes up later","Then we scope it again instead of automatically keeping capacity running.\n",{"title":139,"text":140,"offerKey":79},"Still too much technical uncertainty?","Then an AI Prototype Sprint or Reality Check before Build & Integrate may be wiser.\n",{"title":142,"items":143},"Afterwards you have...",[144,147,150],{"title":145,"text":146},"Working software instead of a demo","The agreed functionality works end to end within the real technical environment.\n",{"title":148,"text":149},"Reliable integration with what is already there","Data, systems, permissions and human processes are part of the solution.\n",{"title":151,"text":152},"A product you can hand over","Architecture, code and key choices are documented well enough to continue independently.\n","\u002Foffers\u002Fbuild-integrate",{"label":155,"type":156},"Fixed price after scoping","scoped",{"title":158,"steps":159},"How it works.",[160,163,166,169],{"title":161,"text":162},"Scope + success criteria","We make exact enough what needs to work to agree on responsibility and price.\n",{"title":164,"text":165},"Architecture + integrations","We determine how AI, data, existing software, permissions and users come together.\n",{"title":167,"text":168},"Build + test","We implement the hard part and also test errors, edge cases and reliability.\n",{"title":170,"text":171},"Go live + hand over","We bring the solution to production in a controlled way, document it and hand it over.\n",{"title":173,"intro":174,"points":175,"caseKeys":185},"Why should you believe this?","AI only becomes truly valuable when it works together with existing software, data and business processes. That is simply serious software engineering.\n",[176,179,182],{"title":177,"text":178},"The same people advise and build","Advice and execution sit with the same technical people.\n",{"title":180,"text":181},"Integrations are core work","We don't treat APIs, databases, auth and existing systems as an afterthought around the AI.\n",{"title":183,"text":184},"Production and handover are part of it","The work isn't done when the demo works, but when the solution is manageable.\n",[],{"buyerTriggerKeys":187,"useCaseKeys":189,"relatedOfferKeys":192,"caseKeys":196},[76,188],"vastgelopen-met-ai",[122,123,29,124,190,82,191,83],"eigen-data-en-kennis-gebruiken-met-ai","agentic-workflows-bestaande-software",[193,79,194,195],"ai-reality-check","vibe-code-rescue-audit","rescue-sprint",[],{"title":198,"intro":199,"activities":200,"deliverables":211,"exclusions":220},"What is included in this offer?","The scope is defined up front. Then you get a fixed price for the agreed result.\n",{"intro":201,"items":202},"The exact work differs per engagement, but we take responsibility for the complete technical result.\n",[203,204,205,206,207,208,209,210],"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":212,"items":213},"The deliverables are defined per scope and are part of the fixed price.\n",[214,215,216,217,218,219],"Working agreed functionality","Production-grade implementation","Required integrations","Relevant tests and quality checks","Technical documentation","Deployment and handover as scoped",{"intro":221,"items":222},"No unbounded consultancy and no feature list that keeps growing afterwards.\n",[223,224,225,226],"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":228,"description":229},"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":233,"result":234,"duration":235,"nextStep":236},"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":238,"proof":239,"process":112},"sq-connect-nodes","sq-foundation-build","jlXsSL_a-hghGaOxvEHbZ2ARDUkoaAlfXaEkKLzQpSQ",{"id":242,"title":243,"body":244,"catalogue":248,"cta":259,"description":11,"extension":26,"fit":264,"hero":270,"key":79,"meta":273,"navigation":31,"next":274,"outcome":285,"path":296,"price":297,"process":300,"proof":314,"relations":327,"scope":333,"seo":360,"stem":363,"summary":364,"summaryPanel":365,"visuals":370,"__hash__":371},"offers_en\u002Foffers\u002Fai-prototype-sprint.md","AI Prototype Sprint",{"type":8,"value":245,"toc":246},[],{"title":11,"searchDepth":12,"depth":12,"links":247},[],{"audience":249,"promise":250,"deliverables":251,"note":257,"visual":258},"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",[252,253,254,255,256],"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":260,"body":261,"primaryCta":262,"local":263},"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":119,"intro":265,"useCaseKeys":266},"When the idea is clear enough to build, but still needs to be proven before you go to production.\n",[267,268,269],"ai-prototype-laten-bouwen","ai-betrouwbaar-genoeg","ai-toevoegen-aan-bestaand-product",{"headline":271,"intro":272,"primaryCta":262},"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":130,"items":275},[276,279,282],{"title":277,"text":278,"offerKey":77},"The prototype proves the direction","Then Build & Integrate can deliver the production version.\n",{"title":280,"text":281},"The outcome calls for adjustment","Then you have learned concretely which technical route doesn't work, without building a complete product first.\n",{"title":283,"text":284,"offerKey":194},"The prototype has become production itself","If an experiment already has real users and needs professionalising, the Rescue route is a better fit.\n",{"title":142,"items":286},[287,290,293],{"title":288,"text":289},"A working end-to-end prototype","The key user flow actually works with the chosen AI technology and integrations.\n",{"title":291,"text":292},"Technical assumptions are tested","You know better where quality, reliability and integrations are or aren't feasible.\n",{"title":294,"text":295},"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":298,"type":299},"€6,950 excl. VAT","fixed",{"title":158,"steps":301},[302,305,308,311],{"title":303,"text":304},"Define use case + success criterion","We pin down which technical assumption this Sprint needs to prove.\n",{"title":306,"text":307},"Set up architecture + flow","We choose the shortest technical route that validates the real problem.\n",{"title":309,"text":310},"Build + evaluate","We deliver the end-to-end flow and test where the solution is fragile.\n",{"title":312,"text":313},"Demo + production advice","We show what works, what is still uncertain and what a next phase needs.\n",{"title":173,"intro":315,"points":316,"caseKeys":326},"A good prototype is more than a pretty click-through demo. It answers the technical question that decides whether the concept can work.\n",[317,320,323],{"title":318,"text":319},"We test the real thing","We test real integrations, data flows and model behaviour where relevant.\n",{"title":321,"text":322},"Small enough to learn","We keep you from building half a product before the key assumption is proven.\n",{"title":324,"text":325},"Ready for a real follow-up decision","Continuing, adjusting or stopping can all be a good outcome.\n",[],{"buyerTriggerKeys":328,"useCaseKeys":330,"relatedOfferKeys":331,"caseKeys":332},[329,76],"starten-met-ai",[267],[193,77,194],[],{"title":198,"intro":334,"activities":335,"deliverables":346,"exclusions":353},"One clear use case, one primary flow and a controlled amount of technology around it.\n",{"intro":336,"items":337},"We build enough to test the real technical risk, without building the complete end product right away.\n",[338,339,340,341,342,343,344,345],"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":347,"items":348},"A tangible prototype plus enough technical clarity for a follow-up decision.\n",[253,349,350,351,218,352],"Technical architecture direction","Validated core flow","Demo of the result","Advice for production and next steps",{"intro":354,"items":355},"A Prototype Sprint proves the core. Production hardening is a separate step.\n",[356,357,358,359],"Full production guarantees or SLAs","Extensive scalability and operationalisation","Unbounded integrations or multiple main flows","Full product development beyond the agreed use case",{"title":361,"description":362},"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":366,"result":367,"duration":368,"nextStep":369},"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":239,"proof":90,"process":258},"WOLcKM4lFt5312Z6kkvWsCyd0jk_equXhLoXFeu1UMg",[373,450],{"id":374,"title":375,"body":376,"description":11,"desiredOutcome":380,"extension":26,"hero":392,"key":82,"meta":394,"navigation":31,"path":395,"problem":396,"proof":408,"recognition":420,"recommendedApproach":435,"relations":437,"seo":442,"stem":445,"summary":446,"visuals":447,"__hash__":449},"useCases_en\u002Fuse-cases\u002Fdocumenten-en-mails-automatisch-verwerken.md","Process documents, messages, emails or requests automatically",{"type":8,"value":377,"toc":378},[],{"title":11,"searchDepth":12,"depth":12,"links":379},[],{"intro":381,"items":382},"You want to process faster without uncertain AI output automatically ending up in your systems as the truth.\n",[383,386,389],{"title":384,"text":385},"Recognise information automatically","Important fields, topics or intents are extracted from unstructured input.\n",{"title":387,"text":388},"Pass it on automatically where possible","Reliable cases move to the next step without manual retyping.\n",{"title":390,"text":391},"Exceptions go to a person","Doubtful cases are deliberately set aside for review.\n",{"intro":393},"A lot of administrative work starts with the same pattern: something comes in, someone reads it, pulls out the important information and enters it somewhere else. That is where AI and regular automation can work well together.\n",{},"\u002Fuse-cases\u002Fdocumenten-en-mails-automatisch-verwerken",{"intro":397,"causes":398},"Document processing looks like a single AI task at first sight, but a reliable solution consists of several technical steps.\n",[399,402,405],{"title":400,"text":401},"Input varies","Layout, writing style and completeness differ per sender or document.\n",{"title":403,"text":404},"AI output has to be validated","A plausible answer is not automatically correct data for an administrative system.\n",{"title":406,"text":407},"Processing ends somewhere else","The extracted information usually has to go on to a CRM, ERP, tickets or other software.\n",{"intro":409,"points":410},"In document automation, the difference between a demo and a usable system lies in everything around the model output.\n",[411,414,417],{"title":412,"text":413},"Validation is part of the design","Extraction is not blindly treated as correct data.\n",{"title":415,"text":416},"Human-in-the-loop for exceptions","Doubtful cases can be reviewed without making the whole flow manual.\n",{"title":418,"text":419},"The chain gets finished","We connect the output to the systems where the work continues.\n",{"intro":421,"signals":422},"This fits especially when employees spend a lot of time on recurring reading and data entry.\n",[423,426,429,432],{"title":424,"text":425},"A lot of information comes in as free text","Emails, forms and documents don't have a fully fixed structure.\n",{"title":427,"text":428},"Employees keep extracting the same data","Names, amounts, categories, dates or other attributes are copied by hand.\n",{"title":430,"text":431},"A predictable workflow follows","Information is entered, assigned, answered or forwarded.\n",{"title":433,"text":434},"Not every case can be fully automatic","Some documents are incomplete, exceptional or too important for automatic processing.\n",{"intro":436},"With Build & Integrate we build the complete processing flow: input, extraction, validation, human review and connection to existing systems. When document variety or required accuracy is still uncertain, an AI Prototype Sprint can first show what is feasible.\n",{"buyerTriggerKeys":438,"primaryOfferKey":77,"offerKeys":439,"caseKeys":440,"relatedUseCaseKeys":441},[76],[77,79],[],[29,190],{"title":443,"description":444},"Process documents and emails automatically with AI | 9to5 software","Process emails, documents and requests automatically? 9to5 builds AI workflows for extraction, classification, validation and integration with existing systems.\n","use-cases\u002Fdocumenten-en-mails-automatisch-verwerken","Information comes in as free text or documents and then has to be read, assessed, recorded or forwarded.\n",{"hero":448,"problem":90,"proof":92},"sq-knowledge-filter","ijOxRBH3LNiJuVnuU5z6aIBrVVQEpQfgLLa405EwYiM",{"id":451,"title":452,"body":453,"description":11,"desiredOutcome":457,"extension":26,"hero":469,"key":83,"meta":471,"navigation":31,"path":472,"problem":473,"proof":485,"recognition":497,"recommendedApproach":512,"relations":514,"seo":519,"stem":522,"summary":523,"visuals":524,"__hash__":525},"useCases_en\u002Fuse-cases\u002Ftools-vervangen-door-maatwerkflow.md","Replace several existing tools with one smart custom workflow",{"type":8,"value":454,"toc":455},[],{"title":11,"searchDepth":12,"depth":12,"links":456},[],{"intro":458,"items":459},"You want to simplify the process without blindly rebuilding all existing systems.\n",[460,463,466],{"title":461,"text":462},"One clear workflow","Users no longer have to stitch different tools and intermediate steps together themselves.\n",{"title":464,"text":465},"Automation where it helps","Manual copying, checking and routing is removed as much as possible.\n",{"title":467,"text":468},"Keep what works well","Systems that add value can stay part of the new flow through integrations.\n",{"intro":470},"Sometimes the problem isn't too little software, but too much. Employees jump between tools, copy information and keep track of how it all fits together themselves. Then one targeted custom workflow can be simpler than yet another SaaS subscription.\n",{},"\u002Fuse-cases\u002Ftools-vervangen-door-maatwerkflow",{"intro":474,"causes":475},"Separate tools each optimise their own part of the process. As a result, the complexity often arises precisely between those tools.\n",[476,479,482],{"title":477,"text":478},"Integration is missing","Data and status have to be moved by hand from one system to another.\n",{"title":480,"text":481},"The process has adapted to the software","Employees follow extra steps because separate tools don't fit together well.\n",{"title":483,"text":484},"Otherwise AI becomes yet another tool","A standalone chatbot on top of the existing pile doesn't reduce fragmentation.\n",{"intro":486,"points":487},"We don't replace standard SaaS with custom software by default. Because we both build software and connect systems, we can choose per part what is technically and commercially wise.\n",[488,491,494],{"title":489,"text":490},"Build and integrate","A good existing system doesn't need to be rebuilt.\n",{"title":492,"text":493},"The process leads","The new flow is designed around how the work ideally runs.\n",{"title":495,"text":496},"AI only where it fits","Smart interpretation is combined with regular automation and integrations.\n",{"intro":498,"signals":499},"This question often arises after a process has been extended bit by bit with new tools over the years.\n",[500,503,506,509],{"title":501,"text":502},"Employees work in many systems for one task","The process keeps jumping between SaaS tools, spreadsheets, email and internal software.\n",{"title":504,"text":505},"Information is entered twice","The same data is kept or copied in several places.\n",{"title":507,"text":508},"Nobody has an overview of the whole flow","Each tool solves one part, but the employee manually keeps it all together.\n",{"title":510,"text":511},"Another new tool doesn't feel like the solution","The pile of software has by now become part of the problem itself.\n",{"intro":513},"With Build & Integrate we design and build the custom workflow around the actual process. We only replace what makes sense and connect the systems that are better kept. If scope and process are still not sharp enough, an AI Reality Check is the more logical first step.\n",{"buyerTriggerKeys":515,"primaryOfferKey":77,"offerKeys":516,"caseKeys":517,"relatedUseCaseKeys":518},[76],[77,193],[],[29,191],{"title":520,"description":521},"Replace existing tools with a smart custom workflow | 9to5 software","Too many separate tools for one business process? 9to5 builds integrated custom workflows with automation, AI and connections to what should stay.\n","use-cases\u002Ftools-vervangen-door-maatwerkflow","The process has become fragmented across several tools, spreadsheets and manual handoffs. You want to bring it back to one coherent workflow.\n",{"hero":90,"problem":238,"proof":92},"mgSW-1h2BBXZlMWEViIVrX1-qaoPuBUr_YQ6D9XnX9A",[],[528],{"id":529,"title":530,"approach":531,"body":546,"cta":550,"description":11,"extension":26,"hero":553,"key":76,"label":555,"meta":556,"navigation":31,"path":557,"proof":558,"relations":570,"seo":576,"stem":579,"summary":580,"visuals":581,"__hash__":582},"buyerTriggers_en\u002Fbuyer-triggers\u002Fai-laten-bouwen.md","We know what we want. Now it needs to be built.",{"title":532,"steps":533},"From a clear scope to something that really works.",[534,537,540,543],{"title":535,"text":536},"Define the scope and success criteria","We make it clear what needs to work, who it is for and when it is good enough to go live.\n",{"title":538,"text":539},"Set up the architecture and integrations","We determine how AI, data, existing software, permissions and integrations should work together technically.\n",{"title":541,"text":542},"Build and test","We implement the difficult part and test more than the happy path, including reliability, errors and human oversight where needed.\n",{"title":544,"text":545},"Bring it into production and hand over","We launch it properly, document the important decisions and make sure your team can carry on independently.\n",{"type":8,"value":547,"toc":548},[],{"title":11,"searchDepth":12,"depth":12,"links":549},[],{"title":551,"body":552},"Know what needs to be built?","Explain what you need and which systems it should work with. We'll quickly tell you how to build it properly and what a logical first step would be.\n",{"intro":554},"You know what needs to be built. We help you build it properly, connect it to your existing systems and get it running reliably in production, using Claude, ChatGPT\u002FOpenAI, Codex or MCP where appropriate. We step in, build, document and hand over, without an open-ended staffing commitment.\n","Build with AI",{},"\u002Fbuyer-triggers\u002Fai-laten-bouwen",{"intro":559,"points":560},"AI is only really useful when it works with existing software, data and business processes. We build that as software engineering, not as a standalone demo.\n",[561,564,567],{"title":562,"text":563},"Integrations are central to our work","We treat APIs, databases, permissions and existing systems as core parts of the solution, not extras around the AI.\n",{"title":565,"text":566},"Reliable beyond the happy path","We also test errors, edge cases and human oversight where needed.\n",{"title":568,"text":569},"Production and handover are part of the job","The work is done when the solution is live, documented and manageable for your team.\n",{"useCaseKeys":571,"offerKeys":573,"caseKeys":575},[122,123,29,124,190,82,267,572,191,83],"product-goed-opzetten-voor-ai-development",[77,79,574],"vibe-code-kickstart",[],{"title":577,"description":578},"AI agent development and integration | 9to5 software","Have senior engineers build an AI agent, MCP integration, assistant or automation with Claude, ChatGPT\u002FOpenAI or Codex. From scope to production.\n","buyer-triggers\u002Fai-laten-bouwen","The problem and direction are clear. Now it needs to be built properly, integrated and brought into production.\n",{"hero":239,"proof":258,"approach":258},"ShT4oNEyuY5KbwbXvOuC2vEuCmku084FYvyfv89UAyM",1792049911885]