At a webinar in this category, someone in the audience asked the best question of the entire session: it looks like a miracle machine, what's the downside? The answer that came back was: I understand why you'd think that.

That's not an answer. And it's a shame, because the question deserves one — especially from the party selling the system. Below is the answer we would give, and it's usable with any provider in this market, including us.

One thing upfront: this isn't a doom story. AI systems work. They just do less than the brochures suggest, and the places where they do nothing are predictable enough to write down.

01 / the answerWhat's the downside of an AI system?

That it's an amplifier, not a solution. A system makes existing work faster and more consistent, but it doesn't invent a working method that isn't there. If something already runs well, it will soon run better and without you. If something is off, it will now go wrong faster and more often.

That's the core, and everything below is an elaboration of it. Whoever realizes this beforehand buys a system at the right moment. Whoever doesn't buys acceleration of something that had no direction yet.

02 / the boundaryDoes it solve a shortage of customers?

No. This is the most important boundary and also the most often left unsaid. A system takes over repetitive work: the work that exists because there are customers. If you have too little inflow, your bottleneck is the front end, not execution, and a system strengthens exactly the part that isn't the bottleneck.

We see this more often than we'd like in first conversations. Someone comes in with "I'm drowning in work," and on closer questioning it turns out not to be a volume problem but a foundation problem: an unclear offer, a shifting target audience, no fixed way of working. In that case, building a system is the most expensive way to keep that problem alive.

A system strengthens a working method that already runs. It doesn't create one.

If that's where you are, we say so in the conversation and it stops there. That's not modesty, it's self-interest: a system on top of a shaky foundation becomes a customer who's unhappy about something we couldn't fix.

03 / the judgmentDoes it take decisions off your hands?

No, and you shouldn't want it to. A system proposes what you would probably do based on what you did before. Whether you give that discount, take that assignment, have that conversation or let that customer go remains your job. The model has no stake in the outcome and doesn't bear the consequences.

In practice this means something is asked of you every day. Drafts wait for review. That costs minutes, not hours, but it comes back every day. Whoever postpones it builds up a queue and then experiences the system as pressure.

There's also a fixed maintenance moment attached to it: once a week you tell it what's changed about your offer, your target audience or your way of working. Skip that, and the knowledge layer quietly goes stale, and you only notice once the output starts to grate. That's work added, not work removed.

04 / the dipWhy does it cost more time in the first weeks?

Because the system doesn't know you yet. The first drafts are too formal or too loose, miss context only you have, or neatly answer the wrong question. You correct a lot, and sometimes correcting takes as long as doing it yourself. That's not a malfunction — it's the period during which your judgment enters the system.

This is the point where most people give up, and it's avoidable by knowing it beforehand. Whoever thinks in week two that they bought something broken, stops. Whoever knows week two is the dip continues, and by week six has something that works.

We don't give a fixed number of weeks for this. It depends on your volume and how consistently you correct, and anyone who gives you a precise number in advance can't actually know it.

05 / the wordsWhich promises don't hold up?

Three words you hear a lot in this market that rarely deliver what they suggest. They're not lies, they're just too big.

06 / at DataDriftWhat does DataDrift explicitly not do?

We're not a campaign agency and we don't work by the hour. We don't sell separate campaigns, ad budget or strategy days. What we deliver is a running system with maintenance on it, and that's a narrower offer than "we help with AI."

Further, the build layer is ours. The integrations, the instructions and the flows that do the work are not handed over. Your accounts, your data and your documented working method are and remain yours, but the engine on top is our methodology. If you're looking for a party that hands you the complete engine so you never need anyone again, that's not us. That trade-off is spelled out in who owns it when it works.

And we don't build a button that lets the system publish independently. That's a real limitation and you're welcome to weigh it as a downside. The reasoning behind it is in why we don't publish anything automatically.

07 / usableWhat do you ask any provider, including us?

Five questions. They cost nothing, they take two minutes, and the answer tells you more than a demo.

• What can your system explicitly not do? A provider without a sharp answer to that either hasn't thought about it or doesn't want to say.
• What will disappoint in the first weeks, and how will I be guided through it?
• For what type of business owner is this specifically not a good purchase? Whoever says "everyone" is selling.
• What do I keep if we stop: accounts, data, the built work? And is that on paper?
• What's expected of me once it's running, in time per week?

If a provider answers all five calmly and concretely, you're dealing with someone who knows the work. If they talk around it, you already have your answer without it being spoken.

This text was created with AI assistance and reviewed and approved by a human before publication.