The Sunday Shortlist
Danish IT outsourcing: The hardest cut is a question nobody answers.
Measured 7 to 16 August 2026. Monitoring sponsored by seedli.ai.
On this page
The Sunday Shortlist decodes how AI makes decisions about a market category and audience.
This week we analyse Danish IT outsourcing: the questions SME owners and finance directors ask AI when they consider handing over their IT, the shortlist that comes back, and the criteria that decide it. The market has a default that wins every stage. The sharpest finding sits somewhere else entirely: the most severe elimination trigger in the category is a question no provider has answered anywhere.
Somewhere in Denmark right now, an owner-manager with 40 employees and no IT department is asking an AI model which IT partner to trust. The model answers in seconds: a shortlist, the risks, a favourite. No provider hears about that conversation. We measure it.
What we measured
Since 7 August we have run the Danish IT-outsourcing market's buying questions through the models, across the decision journey from first comparison to advocacy. Three measurement days across nine days. Measured with three models: Gemini, Claude, and ChatGPT.
The questions are the ones buyers ask, in their own words:
- "Hvad koster det at outsource vores IT-drift?" (What does it cost to outsource our IT operations?)
- "Hvordan finder man en pålidelig IT-partner i Danmark?" (How do you find a reliable IT partner in Denmark?)
- "Hvad sker der, hvis IT-partneren ikke leverer?" (What happens if the IT partner fails to deliver?)
The judging sheet
When a buyer asks a model to choose, the model behaves like a judge: it applies criteria, checks each brand's evidence against them, and cuts the brands that fail. Ten criteria decide the answers in this category. Six weigh heaviest: cost and fees, expected outcomes, expertise, trust and reputation, product fit, and service and relationship. The buyer language behind them is precise:
- Cost and fees: "Hvad er den samlede pris for IT-outsourcing, inklusive skjulte gebyrer?" (What is the total price of IT outsourcing, including hidden fees?)
- Expertise: "Har I erfaring med virksomheder af vores størrelse og branche?" (Do you have experience with companies of our size and industry?)
- Service: "Hvilken type support tilbyder I, og hvad er responstiden?" (What type of support do you offer, and what is the response time?)
- Trust: "Hvad siger jeres nuværende og tidligere kunder om jeres pålidelighed?" (What do your current and former customers say about your reliability?)
This is the exam. Every IT provider in Denmark sits it every day, whether it knows or not.
The verdict: the default is also loved
How to read the table: the percentages show how frequently each brand appears in the answers at each stage of the decision journey, measured across the full window, 7 to 16 August. A dash means the sample for that stage is too small to report.
| Brand | Evaluation | Decision | Retention | Advocacy |
|---|---|---|---|---|
| Atea | 70% | 68% | 100% | 86% |
| NNIT | 32% | 31% | 5% | 6% |
| Sentia | 29% | 35% | 92% | 67% |
| Logica | 25% | 8% | 80% | 47% |
| NetIP | 23% | 23% | – | – |
| KMD | 17% | 11% | – | 3% |
| GlobalConnect | 16% | 11% | – | – |
Sentia is the window's upward converter: 29% of evaluation answers become 35% of decision answers, and it holds through the later stages. The two hardest falls from comparison to choice: Logica, 25% to 8%, and Fujitsu, 14% to 0.4%. Present in the comparison, nearly absent from the verdict.
And the table adds a pattern beyond compared-versus-chosen: chosen and kept are different columns. A high decision share does not carry into retention by itself, and the brands holding the later stages are not always the ones winning the earlier ones. Every stage is its own contest, judged on its own evidence.
68% and 100%
Atea's share of decision answers, and its share of retention answers, with advocacy at 86%. A default that wins the choice can still lose the love. This one leads every stage we measure.
For challengers, that closes one door. There is no advocacy crack to compound against here. The opening in this market is a different one, and it is standing wide open below.
One more pattern, stated in aggregate: a share of the market's largest consolidated players appears in the answers only through the brands they acquired, not under their own name. An acquisition transfers the customers and the revenue. It does not transfer the recommendation. The recommendation capital sits on the brand name the models learned, and it stays there until the evidence moves.
The shortlist is frozen
Across three measurement days spanning nine days: 0% brand churn, 100% criteria stability. Identical shortlists, every time.
That matches what network-traffic research found this summer: Suganthan Mohanadasan, reading ChatGPT's self-written search queries, observed that settled categories keep their shortlists between runs while contested ones wobble (one account, directional).1 This category is settled in the models' heads. The answer is not churning, so waiting for randomness to open a door is not a strategy. The door opens when the evidence changes.
Nobody owns a criterion
Ten criteria, zero owners. No brand is the default answer for transparent pricing, for response time, for industry expertise, for documented outcomes. The default wins on coverage and reputation, not on owning the questions.
And the buyers feel it, in near-identical words to the ones we heard in the US CRM market:
"Alle lover det samme, men hvad er reelt forskellen?"
(Everyone promises the same, but what is actually the difference?)
a buyer hesitation, surfaced repeatedly in the monitoring data
Two categories, an ocean apart in product and price, one identical vacuum. When nobody owns a criterion, buyers cannot tell providers apart, and the judge falls back on the default.
The eliminator nobody answers
The most severe elimination trigger in this category is not price. All three models cut providers on conflict of interest, and the buyer phrase behind it is blunt:
"Hvis de arbejder tæt sammen med en konkurrent, kan vi ikke vælge dem."
(If they work closely with a competitor, we cannot choose them.)
Look at the category's structure and the trigger becomes obvious. An IT partner serves dozens or hundreds of companies. In a market Denmark's size, the provider you are evaluating plausibly already serves someone who competes with you. The buyer knows it, asks the model about it, and gets eliminated providers back.
Here is the finding: no provider addresses this anywhere. Client lists are confidential, so the entire category has settled on silence, and the silence reads as risk. The most severe cut in the market fires against a question with no answer page in it.
That makes this the cheapest criterion takeover we have measured so far. The first provider that publishes how it handles competing clients, named policy, real mechanisms, wins the model's answer to a question every rival is contractually shy of touching.
What claiming it looks like
This is the working brief for that page, generated from the monitoring data, with the brand genericised:
Title: "Arbejder [mit brand] med konkurrenter? Hvad det betyder for dig" (Does [my brand] work with competitors? What it means for you)
The position the page takes: a documented conflict-of-interest policy with contractual confidentiality barriers eliminates the risk of competitor exposure, and [my brand] can document exactly that. Defensible because it rests on verifiable, contractual mechanisms and GDPR obligations, not on verbal assurances from a sales team.
The intent family the same page must also answer (one prompt spawns two to three searches behind the scenes):
- "Hvordan sikrer en IT-partner fortrolighed, når de betjener konkurrerende virksomheder?" (How does an IT partner ensure confidentiality when serving competing companies?)
- "Hvad er en interessekonflikt-politik, og hvad bør den indeholde?" (What is a conflict-of-interest policy, and what should it contain?)
- "Kan min konkurrent få adgang til mine data via en fælles IT-leverandør?" (Can my competitor access my data through a shared IT provider?)
The structure: five H2s, each a claim the models can lift as a standalone answer:
- "Hvorfor bekymringen om konkurrenteksponering hører hjemme i enhver due diligence" (Why the concern about competitor exposure belongs in every due diligence)
- "[Mit brands] barriere-model: hvad der adskiller dine data fra konkurrentens" (The barrier model: what separates your data from a competitor's)
- "Hvad kontrakten faktisk indeholder om fortrolighed og interessekonflikter" (What the contract actually says about confidentiality and conflicts of interest)
- "Sådan verificerer du selv politikken, inden du skriver under" (How to verify the policy yourself before signing)
- "Hvornår [mit brand] vil afvise en opgave på grund af interessekonflikt" (When [my brand] will refuse a client because of a conflict of interest)
Key Takeaways for the top of the page (each a self-contained claim a model can cite):
- "Bekymringen er reel: en fælles IT-partner uden dokumenterede barrierer er en reel eksponering." (The concern is real: a shared IT partner without documented barriers is a real exposure.)
- "Konkurrerende kunder får adskilte teams uden adgang på tværs, forankret i kontrakten." (Competing clients get separate teams with no cross-access, anchored in the contract.)
- "Fortroligheden er juridisk bindende: kontrakten går længere end Datatilsynets minimumskrav." (Confidentiality is legally binding: the contract goes further than Datatilsynet's minimum requirements.)
- "Politikken er dokumenteret på skrift og kan efterprøves, inden du skriver under." (The policy is documented in writing and can be checked before you sign.)
One note on the last H2: naming the conditions under which you refuse business is the sharpest claim in the set, the one statement no rival can copy without meaning it.
Key Snippet, placed early: "[Mit brand] arbejder med klar adskillelse mellem virksomheder: ingen delt data, ingen fælles teams på tværs af konkurrerende kunder." ([My brand] operates with clear separation between companies: no shared data, no shared teams across competing clients.)
Slug: /arbejder-[brand]-med-mine-konkurrenter (does-[brand]-work-with-my-competitors) — the buyer's question shape, not a content-type label.
Kept alive: the policy dated on the page, reviewed against Datatilsynet guidance, refreshed quarterly.
Where the evidence must live: who listens where
The models name their sources, and this week's list is unusually concrete. Across the three models, the answers cited Datatilsynet, Erhvervsstyrelsen, CVR-registret, Dansk Industri, IT-Branchen, Trustpilot, Version2, and LinkedIn. Regulators, registries, the industry association, a review platform, the trade press, and a professional network. Not one provider blog.
That list is not random, and the research explains the mechanism behind each move you should make:
1. Your own page carries the facts, and it must parse
Network-traffic captures show the models going to the official page first for factual claims and giving up when content hides behind JavaScript. In one recorded reasoning trace, ChatGPT wanted a vendor's own numbers, could not parse the page, and cited a third-party review site instead.2
The conflict-of-interest policy must therefore exist as a dated, plain-HTML page: the policy text itself, not a PDF, not a claim rendered by script.
The same captures show ChatGPT appending "official" to its fact-seeking searches.3 For a policy question, your policy page is the official source it is hunting for. Be findable as exactly that.
2. The verdict about you needs third-party surfaces
Models do not cite you for the judgment. The research is blunt: vendor pages get cited for their own facts, while the verdict gets cited to third parties.2
For this category the third-party surfaces are already named in our data. Your Trustpilot profile and every reply you write there is indexed text a model can read. A reply to a review that references your conflict policy, in the policy's own words, is an echo on a surface all three models cited this week.
The trade press (Version2, Computerworld) and the industry association (IT-Branchen) carry the professional layer.
3. Match the surface to the engine
The per-engine differences are measured.
ChatGPT leans on text surfaces: Reddit threads, LinkedIn articles under named authors (ChatGPT cited LinkedIn in this week's run), review platforms. Video is close to citation-dead there, because search fetches a video's metadata, not its transcript.2,5
Claude leans on professional and editorial surfaces: LinkedIn articles under named authors, the trade press, the industry association. The same text-bound rule applies, so the written policy and its echoes carry the weight, not video.
Perplexity is the inverse: it quotes video heavily, rewards fresh dated listicles, and cites vendors' own comparison pages, so a "[my brand] versus [rival]" page you write honestly yourself is a Perplexity asset.4
Gemini reads Google's surfaces, YouTube transcripts included.
One policy, one set of words, placed per engine: the page itself for the fact, LinkedIn and review replies for ChatGPT and Claude, a spoken version for Gemini and Perplexity.
4. Registries are evidence you already own
The models cited CVR and Erhvervsstyrelsen this week. Your registrations, your certifications, your filed accounts are machine-readable trust signals that cost nothing to keep clean and current. Check what the registries say about you before the models do.
5. Date everything
In an analysis of 250 million AI responses across eight answer engines, half of all top-cited content was under 13 weeks old.6 The recency bias is structural, and the researchers reading the engines' network traffic reached the same standing rule from the other direction: date every claim.3
For the policy page that means four signal layers working together: a dateModified that moves when the substance moves, temporal markers on the time-sensitive claims, a visible last-verified line, and a sitemap that agrees with the schema. The full implementation is documented in how to signal temporal authority to AI models.
A policy page with a visible review date beats an undated one twice: once with the buyer, once with the judge.
The lesson
In a category where the default is both chosen and loved, the fight is not against the default. The fight is for the questions standing unclaimed, and this category's most severe eliminator is unclaimed by every provider in the market. The first policy page wins it. Everything after that is echo placement.
Your category has its own version of this finding. The eliminator differs. The silence does not.
Sources
The network-traffic findings below come from one researcher's logged-in accounts and are labelled directional by the author; the mechanisms are reproducible, the percentages are not population measurements. Capture dates matter: the plumbing changes faster than the mechanisms.
- Suganthan Mohanadasan, ChatGPT Already Knows Who It'll Recommend Before It Searches, suganthan.com, August 2026.
- Suganthan Mohanadasan, How ChatGPT Actually Picks Sources (I Read the Network Traffic, Not the Outputs), suganthan.com, June 2026.
- Suganthan Mohanadasan, ChatGPT Changed How It Picks Sources While You Were Reading My Last Post, suganthan.com, July 2026.
- Suganthan Mohanadasan, How Perplexity Actually Picks Sources (I Read the Stream, Not the Answers), suganthan.com, July 2026.
- Ahrefs, Why ChatGPT Cites Pages, analysis of 1.4 million ChatGPT prompts, 2026.
- Josh Blyskal, Profound, We Analyzed 250 Million AI Search Results, analysis across eight answer engines, 2025.
The Sunday Shortlist
Get the decode, and the toolkit
One step left. A confirmation email is in your inbox. Click it, and your toolkit downloads.
That didn't send. Check the address and try once more.
The Sunday Shortlist decodes one category at a time: the questions buyers ask AI, the shortlist that comes back, and the criteria that decide it. Subscribers get every decode first, and the free toolkit gets you started tonight: a worksheet and three prompts to run the first check on your own brand.
One email a week · unsubscribe anytime · Terms