Rolling Out Langdock: The Practical Guide for Companies

Part of your team is already using AI. Privately, on personal accounts, right past your IT. The question is no longer whether AI enters your company – it's whether it comes in controlled or through the back door. According to Salesforce's KI-Index Mittelstand 2026, 51.2% of small and mid-sized businesses (SMEs) are already using or testing AI. Roll out a clean platform now, and you pull the topic out of shadow IT and make it productive. Here's the guide – step by step, including the mistakes you can skip.

Quick context first: Langdock is an AI platform from Berlin – you'll find it at langdock.com. It gives your entire team secure, centrally managed access to leading AI models – GDPR-compliant, ISO 27001-certified, with hosting in the EU. Langdock's customers include Merck and Personio. What the platform can do in general is covered on our Langdock page. This article is about the practice: the rollout.

Transparency: This is a referral (affiliate) link. If you use it, we may earn a commission – the price you pay stays the same.

Step 1: Settle roles and permissions – before the first login

The most common opening mistake: give everyone access immediately and sort out the rest "later". Later never comes. Settle three things before the first login:

• Who is the admin? One person – plus a deputy – owns the platform: user management, permissions, settings. Without this role, the system manages itself. Badly.
• Who may do what? Not every team needs the same access. Sales, accounting and management work with data of different sensitivity – the permissions should reflect that. Better to start with a small group and expand than to claw permissions back afterwards.
• What's allowed? A short written rule is enough to start: which data may go into the platform, which may not? No legalese – one document everyone understands instantly and everyone knows exists.

Step 2: Get data protection right – the DPA first

Langdock brings the foundations: GDPR compliance, ISO 27001 certification, EU hosting. Your data stays within the European legal space. But "the platform is compliant" doesn't automatically mean "your use of it is too". Two things belong on your list before real customer data flows:

• Sign the DPA. The data processing agreement governs how Langdock handles data on your behalf – mandatory under GDPR as soon as personal data is involved. It's part of Langdock's standard, but it still has to be signed. Before the start, not after.
• Bring in your data protection officer. If your company has one, they belong at the table early, not after the rollout. A short conversation up front saves long discussions afterwards.

Important for how you communicate this to the team: data protection isn't the brake here – it's the argument. It's exactly why you're introducing a platform instead of tolerating private accounts.

Step 3: Start small – one team, one use case

The reflex to roll Langdock out to the whole company at once is understandable – and almost always a mistake. Big chunks fail; small wins carry. The better route: start with one department and one concrete use case.

Good first use cases share three traits: they happen often, they follow a recognizable pattern, and their output is easy to check. Typical candidates:

• Drafting emails and proposals – the daily writing work everyone knows and nobody loves.
• Summarizing documents – contracts, meeting notes, long email threads boiled down to the point.
• Preparing research – collecting and structuring information before a human decides.

And then: measure. Estimate roughly how many hours the use case costs per week today, and compare after the pilot phase. Then you have numbers instead of opinions – and a story that convinces the rest of the company without you having to evangelize. We hold ourselves to the same rule in everything: we measure ourselves in hours won back. Nothing else.

Step 4: Train the team – this is where the rollout is decided

The classic software training – slides, feature tour, Q&A – doesn't work for AI tools. The reason: the hurdle isn't the interface. Langdock runs in the browser and largely explains itself. The hurdle is the question of what to actually use the thing for in your own workday.

A good Langdock training therefore starts from real tasks: everyone brings an actual task from their week – an email, a proposal, a report – and completes it with Langdock during the session. The difference is enormous: after a slide training, people know what the platform can do. After a hands-on training, they've already worked with it – and come back the next day on their own.

Two more things that make the difference:

• Build champions. Every team has people who are curious on their own. Give them early access and a stage – they'll convince the rest more credibly than any announcement from above.
• Plan for follow-up. The real questions only surface after the training, in the middle of the work. A short recurring session or an internal channel for questions catches them.

And whoever asks "Will this replace me?" deserves an honest answer: no. The machine takes over the grunt work – judgment, customer relationships and responsibility stay with the humans.

Step 5: Build the first agents

Chat is the entry point – the real level above it is your own AI agents: digital employees that permanently take over a recurring task instead of being briefed from scratch every time. An agent knows its job, its tone and its limits – your team calls it up instead of retyping the same context over and over.

The good news: creating agents in Langdock takes no code. You define the job, the tone and the knowledge sources right in the interface – the real work isn't the technology, it's describing the task precisely. And if an agent needs to reach deeper into your systems than the interface allows: the Langdock API lets you connect the platform to your existing systems – CRM, inventory management, databases. We build those connections as custom software.

Start small here too: one agent for one task that costs the pilot team hours every week. Once it runs reliably, the next one follows. What agents can realistically take over today – and what they can't – is covered in detail on our AI agents page.

We don't just walk this path with clients, by the way: we use Langdock ourselves – daily, with 40+ of our own AI agents, from research to copywriting. Every step in this guide is one we've taken ourselves.

The classic rollout mistakes

For the record, straight from practice:

1. Buying licenses, forgetting the rollout. Access alone changes nothing. Without training and a first use case, the platform stays an icon on the desktop.
2. Everyone at once. A company-wide rollout without a pilot phase produces many half-convinced users instead of a few enthusiastic ones. The enthusiasts convince the rest – the half-convinced convince no one.
3. No owner. Without an admin and an internal point of contact, the platform fizzles out. It's not a full-time job, but it is a real role.
4. Postponing data protection. If the DPA only gets signed after launch, you've reproduced exactly the shadow-IT problem you set out to solve.
5. Training as a checkbox. Slides produce attendees, not users. Training has to start from people's actual tasks, or it stays theory.
6. No baseline. Without a before-number, you can't prove success afterwards. Then the rollout becomes a matter of faith. With a number, it's arithmetic.

How you'll know it's working

Not by the number of licenses. But by your team moving tasks into the platform on its own. By meeting-room sentences like "I had the assistant prep this." By the first department coming to you with its own agent idea. From that point on, the topic carries itself – and you can tackle the bigger processes.

The next step

You can implement this guide on your own – it works. Or you walk the path with people who know every pitfall in it from their own experience. We set up Langdock, train your team on your real tasks and build the first agents – as the SCALE² sprint: 3 weeks, 5 phases, fixed price, with 3 weeks of post-go-live support included. Details on the Langdock page.

The simplest first step remains the time-potential analysis: 45 minutes, free, no sales pitch. Together we look at where the most time sits in your business – and whether Langdock is the right lever for it. Book your time-potential analysis.

Is Langdock GDPR-compliant?

Yes. Langdock is GDPR-compliant, ISO 27001-certified and hosts in the EU. A data processing agreement (DPA) is part of the standard – it should be signed before productive use, as soon as personal data is processed.

Does my team need technical skills?

No. Langdock runs in the browser and works like a chat – anyone who can write an email can work with it. The difference between dabbling and productive use isn't prior knowledge; it's training built around real tasks from people's own workday.

What if the team doesn't use the platform after the rollout?

Almost always, it comes down to one of the classic rollout mistakes: no owner, no hands-on training, no clear use case or no baseline. The good news: all of them can be fixed after the fact – most effectively with training built around real tasks and one clearly defined pilot use case.