AI rollout in the company
Tools fitted to your process in weeks, without buying another system or paying for modules nobody uses. Your people build with AI, we are responsible for data, security and operations.
- Your own CRM and document flow instead of more licences
- Data stays in the company: models in the EU or local
- A security review before every launch
An AI rollout in the company, as we do it, is not buying an assistant licence. It is a prepared environment in which sales, the back office, production or a law firm build tools for their own work in weeks rather than quarters, without paying for a system that gets used one fifth of the way.
What you get
Six elements on our side from day one, written into the contract.
-
An environment for applications
Test and production kept apart, on our servers in the EU or on yours. A new module does not break what already works.
-
Company login and permissions
Applications use the accounts you already have. Who sees what follows from roles in the company.
-
AI models in the EU or locally
Models matched to the task, in the EU region. For data that must not leave the company, a local model on your server.
-
Company data under control
ERP, email, files and databases connected through controlled connectors. An application gets only what it needs.
-
Review before launch
Before a module reaches people, we check access, data handling and whether it sends anything outside the company.
-
Operations and 24/7 support
Backups, updates, monitoring, response to outages. An application built on Friday works on Monday morning.
What the company gains
Tools fitted to the process, not a process fitted to the tool. Sales has a customer file with the stages that really exist, the back office has a contract workflow where a document reaches the right person on its own, production has an assistant that answers an operator's question about a machine.
Time measured in weeks, cost without licences for unused modules, and the knowledge of how the company works stays in the company. When the process changes, the module is changed by the same person who built it.
Division of responsibility
With you: the idea, the content and the pace. Your people describe what they need and build modules with AI. With us: everything that has to work when nobody is watching. Servers, access, backups, monitoring, security reviews and integrations with ERP and other systems.
When a module needs something AI cannot write, for example an integration with an undocumented system, we add our developers for an agreed scope.
Data and models, in the EU or locally
For tasks on ordinary company data we use models in the EU region, with a processing agreement and without passing data on for training. For data covered by professional secrecy, regulation or NIS2 we run a local language model on a server at your premises or in our EU data centre.
The rules are built into the environment, not into employees' heads: a prompt on sensitive data goes to the local model automatically. If the company works in Microsoft 365, we add Copilot with a configuration that tidies up access to files and email.
Already have your own application?
If someone at your company has built a prototype with AI, we start with a review of the code and data, then set up the production environment and take over operations.
Example scenario
A contract workflow built by administration
A services company signed contracts over email, with versions circulating between departments. A person from administration described to an AI assistant how the workflow should look and had a working module within days. From us she got an environment with company login, a connection to the staff directory and the document drive, a security review, backups and monitoring. The same department keeps developing the module.
How it works
Four stages. The first and the last are ours, the two in the middle we do together.
-
Groundwork
Test and production environments, company login, access to AI models and company data. Ready in a few days.
-
Rules of the game
A short training and written rules: what is allowed, what not to paste in, how to hand an application over for review.
-
You build
Departments build modules for their own work. We are nearby when data needs connecting or advice is needed.
-
We close the loop
A security review before release, then operations: backups, monitoring, 24/7 support.
- ISO/IEC 27001
- Servers in the EU
- 24/7 support
- About 20 specialists
Compliance
We run AI rollouts within our ISO 27001 system. Data stays in the EU, in your environment or on our servers, with a processing agreement, access control and audit logs. We design rollouts to meet GDPR, NIS2 and AI Act requirements, and for data that must not leave the company we run local models.
Frequently asked questions
Do employees need to know how to code?
No. They need to be able to describe their work and what they need from a tool. When a module needs something AI cannot write, we add our developers.
Where is the data and who has access to it?
Where it is today: in your systems, with you or on our servers in the EU. Applications get access through controlled connectors, permissions follow from roles in the company, and models run in the EU or locally, without training on your data.
What if someone builds something dangerous?
Nothing reaches users without our review. We check what the application connects to, what data it pulls and where it sends it. Test is cut off from production.
Will this replace our CRM or ERP?
Usually not the ERP. Departmental tools and CRM often yes, because that is where off-the-shelf systems fit worst. We start with one module next to the existing systems and connect it to them.
How long does it take and how is it billed?
The environment is set up in a few days, the first module appears within the first weeks. The environment and care are a monthly subscription; developer work for an agreed scope is quoted separately. You get an offer after a short conversation.
Does this work for law firms and companies with sensitive data?
Yes, with a local model or a model in the EU with a processing agreement, and access to cases following the firm's permissions. Professional secrecy is a design requirement, not an add-on.
See also
- Support for AI-built projectsYou have a prototype built with AI. We put it on a server, secure it and run it.
- Infrastructure for AIServers, databases and access to AI models in the EU for a team that builds on its own.
Related services: AI policy and AI Act compliance · Microsoft 365 deployment · DLP and data protection
Let us talk about your project
Answer 2 questions about your company. You will see a simple estimate right away, and we will prepare a full proposal within 24 business hours.
- 2 minutes, no commitment
- You talk to an engineer, not a salesperson
- No spam, one contact about your quote