Practical answers before you write.

• How do you decide between existing software and custom development?

  We start with how work happens today and what you are trying to improve. If a setting change, a connection between systems, or a clearer process is enough, that is what we recommend. We only build custom software for the parts that standard tools cannot cover well.

• How do you approach project cost?

  We agree what the work is before we talk price. We prefer to keep what already works, connect systems, and automate simple steps — and we use AI only where reading or language is the slow part. We will not invent a number for a problem that is not yet clear.

• Can you work with our existing systems?

  Yes — that is usually the starting point. Many projects sit next to tools you already run: connections, a shared working screen, problem handling, and interfaces for the people doing the work. Replacing everything is rarely the first move.

• Do we need to know exactly what technology we need?

  No. Bring the problem, how work happens today, and what a good result would look like. We help compare keeping what you have, connecting systems, automation, AI and custom software — without assuming a large project.

• When would CodexCell tell us not to build something?

  When a smaller change solves it — a setting, a connection, a clearer process, or a lighter website change. If we are not the right fit, or if the process is still changing too often to turn into software, we say so, even when that means a shorter project than you expected.

• How does a first conversation work?

  Send a short description through the contact form or to support@codexcell.com. We reply with questions — usually within one working day — until the problem is clear enough to scope. Only then do we talk about an estimate.

• What happens to the details I send on the contact form?

  We store your name, email, optional organisation and interest, and your message so we can reply. Staff may receive an email notification. We do not sell enquiry data. Full detail is in the privacy statement; cookies and browser storage are listed in the cookie policy.

• Which languages and regions do you work in?

  We work in English and Dutch. CodexCell is focused on the Netherlands, with work across Belgium and the wider European Union where remote collaboration fits.

• Who owns the resulting software?

  You do. The source code, setup and data stay with you. We do not lock the product behind software you cannot leave.

• Where does our data live when you use AI?

  It depends on the work you are running and where data is allowed to live — AI Infrastructure is an engineering decision, not a shopping list. When data must stay in the EU, we use Mistral. When EU residency is not required, work can run on US servers — still treated as private: encrypted, with access limited, so the host is not reading the content. If data cannot sit on any outside server, we can design on-site compute and model-serving inside the organisation; that is the most private option and it costs more. We can also connect to Microsoft Foundry or AWS Bedrock when those are the services you already use — that is an integration, not a way of keeping data in the EU.

Op zoek naar een passende oplossing? Bekijk oplossingen