{"id":1853,"date":"2026-09-15T09:00:00","date_gmt":"2026-09-15T07:00:00","guid":{"rendered":"https:\/\/pletzenauer.com\/?p=1853"},"modified":"2026-07-27T17:48:54","modified_gmt":"2026-07-27T15:48:54","slug":"one-ai-tool-or-several","status":"publish","type":"post","link":"https:\/\/pletzenauer.com\/en\/2026\/09\/15\/one-ai-tool-or-several\/","title":{"rendered":"One AI tool or several? Why multi-tool setups usually fail"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>The short answer:<\/strong> one standard tool plus one deliberately permitted second tool. Anything beyond that costs more in coordination, training and data protection effort than it returns in quality. Not because variety is bad, but because the effort per additional tool does not grow linearly \u2014 it grows with the number of combinations in which people have to explain why they did what with which.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Last checked: September 2026.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Disclosure:<\/strong> I earn my living advising on and training people in Claude. An article arguing for monoculture would be in my interest \u2014 which is why I explicitly do not argue for it, and why the counter-position gets a full hearing in this text.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The short version<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>One standard tool<\/strong> for breadth \u2014 the one that gets trained, documented and reviewed.<\/li>\n<li><strong>One second tool<\/strong>, deliberately permitted for a named purpose, with a named group.<\/li>\n<li><strong>From the third tool onwards<\/strong> costs rise faster than value \u2014 and not in licence fees.<\/li>\n<li><strong>The power-user counter-argument is valid<\/strong>, but applies to individuals, not organisations.<\/li>\n<li><strong>The worst state<\/strong> is not variety but unregulated variety.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Why this becomes a question at all<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The question rarely arises at the start. It surfaces after about a year, when the situation in many businesses looks like this: management introduced a tool eight months ago. Marketing has been using a second one for four months because it produces better images. Development uses a third because it codes better. And part of the workforce still uses personal accounts, because they knew those before anything was introduced.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nobody decided this. It happened. And the question is no longer &#8220;which tool&#8221; but &#8220;how many of them can we afford&#8221;.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What an additional tool actually costs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The licence is the smallest item \u2014 for ten people we are talking a few thousand euros a year. Four other things are expensive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Training.<\/strong> Every tool needs its own two to three guided hours per person. Two tools do not mean two training sessions \u2014 they mean two sessions plus the explanation of when to use which. That third part is precisely the one missing in practice, and it accounts for most of the friction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Data protection.<\/strong> Every tool needs its own review, its own data processing agreement, its own line in your processing register, and its own answer to who removes which account when an employee leaves. That effort arises once per vendor, regardless of whether three or thirty people use the tool.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Knowledge that does not travel.<\/strong> The underrated item. What your marketing department builds in good templates and approaches does not transfer one-to-one into the specialist department&#8217;s tool. You pay for the same learning twice \u2014 and, more seriously, the two groups can no longer help each other.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Decision load in daily work.<\/strong> The item that never appears in a table. If someone has to pause before every task to consider which tool is right now, that costs little time \u2014 but it costs something on every single task. Across a year and a whole workforce it adds up to more than the second licence ever cost.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The counter-position \u2014 and what is right about it<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The most common argument against my recommendation runs: &#8220;Experienced users run two or three tools in parallel anyway and switch by task. That is the most productive way to work.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is true \u2014 for individuals. Anyone working with these tools daily develops a feel for which suits what, and genuinely gains from switching. I work that way myself.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The error lies in transferring it to an organisation. What works for one person, because they bear the cost of switching and collect the benefit themselves, works differently in a business: there the organisation bears the cost \u2014 training, coordination, data protection \u2014 while the individual collects the benefit. That is not a moral problem but a question of incentives. By the same logic, businesses do not run seven word processors, even though individual people are perfectly capable of using several.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So: a second tool, yes \u2014 but for a named group with a named purpose, not as a general permission.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What a sensible second tool looks like<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Three conditions, all of which in my view must be met:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>A named purpose.<\/strong> Not &#8220;for everything the other one does less well&#8221;, but &#8220;for visual material in marketing&#8221; or &#8220;for development&#8221;. If you cannot state the purpose in one sentence, you do not have one.<\/li>\n<li><strong>A named group.<\/strong> Four people in marketing, not &#8220;whoever wants it&#8221;. Otherwise you do not have a second tool; you have two standard tools.<\/li>\n<li><strong>A written demarcation.<\/strong> Three lines in the policy suffice: which tool is standard, which is the second tool, for what exactly. Without that sentence you get the friction described above.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Combinations that have worked in projects: Copilot or Gemini for breadth plus Claude for the department doing demanding text work. Or Claude as standard plus ChatGPT for marketing because of image generation. Both are clear divisions along the work, not along preferences.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The worst state<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Variety is not the problem; <strong>unregulated<\/strong> variety is. The state in which three tools are in use, none of them officially, nobody is responsible for any of them, and part of it runs through personal accounts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It looks harmless because it costs nothing. It merely costs elsewhere: you cannot say which company data was processed where. You cannot give auditors a defensible answer. And you cannot secure the knowledge built up, because it sits in personal accounts that disappear with the next departure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you are reading this and recognising the situation: the order is stocktake, then decision, then business accounts, then policy. In that order \u2014 a policy issued before the business accounts exist is a request, not a rule. More in the <a href=\"https:\/\/pletzenauer.com\/en\/2026\/09\/08\/ai-gdpr-vendor-comparison\/\">GDPR comparison<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What to do concretely<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Count<\/strong> how many AI tools are genuinely in use \u2014 including personal accounts. Ask without threatening sanctions.<\/li>\n<li><strong>Name a standard tool.<\/strong> The one training is built around and the policy points to.<\/li>\n<li><strong>Permit at most one second tool<\/strong>, with a purpose and a group.<\/li>\n<li><strong>End the rest<\/strong> \u2014 with a transition period and an explanation of why.<\/li>\n<li><strong>Secure the knowledge<\/strong> from the departing tools into your own store before you switch them off.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently asked questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Is this not simply convenience for the IT department?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Partly yes, and that is a legitimate objection. The difference lies in whether the limit is justified. &#8220;We permit only one because otherwise we cannot manage the data protection review&#8221; is a justification. &#8220;We permit only one&#8221; with nothing added is convenience \u2014 and will be understood as such.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What if a department rejects the standard tool?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Then listen before you decide. Often there is a genuine professional reason behind it \u2014 and that is exactly the case the second tool exists for. Sometimes, though, it is only habit, and then training helps more than a second licence.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">There are three of us. Does this apply to us?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In a weaker form. With three people the coordination effort is small and you can afford more variety. What remains is the data protection part: even with three people you need a contract per vendor and an answer to what happens to the data.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How often should we revisit the decision?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once a year is enough. More frequently and the workforce stops taking the decision seriously \u2014 and a tool change always costs more than the improvement initially promises.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What about specialist tools that are not assistants at all?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A transcription service or a translation tool is not a second assistant and does not fall under this rule. The data protection part applies unchanged, though: separate vendor, separate review, separate line in the register.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>One standard tool plus one deliberately permitted second tool. What each additional one really costs \u2014 and why the licence is the smallest item.<\/p>\n","protected":false},"author":1,"featured_media":1997,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[],"class_list":["post-1853","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-automatisierung"],"_links":{"self":[{"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/posts\/1853","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/comments?post=1853"}],"version-history":[{"count":1,"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/posts\/1853\/revisions"}],"predecessor-version":[{"id":1962,"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/posts\/1853\/revisions\/1962"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/media\/1997"}],"wp:attachment":[{"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/media?parent=1853"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/categories?post=1853"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pletzenauer.com\/en\/wp-json\/wp\/v2\/tags?post=1853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}