Ask an AI itself and within two seconds you get "yes" back, complete with sources. That's not a trick: it's simply correct. The language question is a solved question that still gets asked out of habit.

What's underneath isn't solved. Almost no one asking whether AI speaks Dutch is worried about grammar. The real concern is that something will end up under your name that you would never have said that way yourself. That's a legitimate concern, and it's the most underestimated reason people drop out.

Below is where the difference exactly lies, what a voice actually is once you take it apart, and how you capture it without starting with a blank document.

01 / the languageHow good is AI in Dutch, really?

Good enough that, on grammar and fluency, it's indistinguishable from an average copywriter. The large language models are trained on enormous amounts of Dutch text and switch effortlessly between registers: formal, informal, businesslike, warm.

Where it sometimes falls short: very local expressions, jargon from small niches, and the nuance between Netherlands Dutch and Flemish if you don't explicitly ask for it. Those are edge cases and they're solvable with examples. The language itself is no longer a reason to doubt.

02 / the differenceWhy doesn't AI text sound like me, then?

Because correct Dutch and your Dutch are two different things. A model without knowledge of you writes the average of everyone: neat, smooth and interchangeable. You recognise it by sentences no one could ever object to, and which for that reason move no one either.

Your voice lies in the deviations from that average. The words you do use and the buzzwords you refuse. How directly you address someone. Whether you make jokes, and what you never joke about. The examples you've been citing for years because they work.

None of those things are in a language model. They're in your head, and as long as they only exist there, no system can write with them.

03 / the breakdownWhat is a voice, actually, in practical terms?

Three layers, and all three can be captured. That's the good news: a voice isn't a mystical talent but a set of repeatable choices you already make, you just haven't written them down anywhere yet.

The most honest source for all three is existing material: sent emails, written quotes, old posts. That's where you find how you actually write, not how you think you write. That difference is bigger than most people expect.

04 / the captureHow do you capture a voice without a blank document?

By recording what you already do, instead of starting to write. The blank-document problem is the reason this stays on almost everyone's to-do list: you have to pour your entire way of working into something in one go, and that moment never comes.

Four steps, in this order:

• Record what you already do. A conversation in which you explain your approach. Don't re-enact it, just record it when it actually happens.
• Transcribe it. From recording to text. This is the step that requires no thinking, and that's why it always succeeds.
• Organise into fixed themes. This is where the difference between a pile and a system emerges.
• Deduplicate. You explain the same things more often than you think. What remains is the core.

Collecting gives you an archive. Organising gives you a system.

This is also how we work it out with a client: a conversation of sixty to ninety minutes in which someone explains their own way of working, which becomes the base layer. Not because a recording is magic, but because people are more precise about their own field when speaking than when writing. In a form you fill in what you think is expected. In a conversation you say what you mean.

In that conversation, three types of questions do the work:

• How. Walk me through a real case. Not "how do you do an intake" but "take the last client who said yes, what exactly happened".
• Why. Why did you do it that way? This is where your reasoning surfaces.
• Unless. And when don't you do it that way? The exceptions are the difference between a system that's usable and a system that gets it wrong half the time.

05 / the learningHow does a system learn my voice?

In two phases. First you feed it that existing material, so the first drafts already come close. After that, the correction loop does the real work: every draft you adjust before sending is a lesson. If you adjust the same type of sentence three times, that pattern should become the default.

That's exactly why everything comes in as a draft with us, rather than sending itself. The approval step isn't a safety lock we bolted on afterwards: it's the point where your voice flows into the system. A system that publishes on its own learns nothing. More on that in why we don't publish your posts automatically.

Expect a few weeks in which you'll be correcting more than you'd like. That's not a flaw, that's lesson one through twenty.

06 / what remainsWhat remains of me in the end result?

If all goes well: everything that counts. The system carries the form, the structure and the volume. You supply the opinions, the examples and the final word. Readers notice no difference, because there shouldn't be one: every piece is approved by you and refined where needed.

And if something still doesn't sound like you, you don't send it. That's how simple the safeguard is. There's no version of this where you're stuck with text you're not allowed to change; what's yours and what isn't is covered in who owns it when it works.

What you can ask any provider about this:

• How does my way of working get into the system, and how long does that step take? An answer measured in minutes is a form.
• What happens to my exceptions, the cases where I do it differently?
• Can I read back what's been recorded about my way of working, and correct it?
• What happens to my corrections: do they disappear, or do they go into something?

That makes "does AI work in Dutch" ultimately a small question. The big question is whether you're willing to capture your voice. That work can't be taken over by anyone, not even us.

This text was created with AI support and checked and approved by a human before publication.