How to begin

Choose the teams where it matters most — the ones working across cultures, where the friction costs the most. Your IT team embeds our intelligence and instructions into their AI environment.

From that point, it works: when a colleague’s question touches a cultural difference, their AI notices, asks, and helps.

There is no trial to set up and no program to run. The intelligence simply begins doing its work, in the flow of real situations.

Access is granted colleague by colleague. Your team leads decide who among their own people works across borders often enough to benefit, and enrolls them. Nobody is licensed by default, and nobody is left out who needs it.

You pay €250 per user per year, billed quarterly in arrears. A colleague’s access runs a year from the day it is granted.

There is no minimum and no commitment beyond the colleagues you have chosen. Each year you decide again who has access. The number can be lower than the year before, or higher.

You see for yourself whether the help lands and whether it changes how those teams work together — not from any claim we make, but from what your own people experience.


Back to Companies.

What a shame

Germany. United States. Agreements.


Steven works in Atlanta, Anna in Stuttgart. They’re colleagues in engineering who know of each other, but not well. Steven has a new task: FastTrack, a high-profile development project. He needs to gather valuable data from the most important recent projects company-wide, as soon as possible. Anna had worked on one of exactly those projects.

Steven sends Anna an email in telegraph style, asking her to send any and all analysis and data that could be relevant for FastTrack.

Anna reads it but isn’t sure what to do with it. It is very brief, has almost no background, and is kind of rude. She decides not to react, thinking: if Steven is serious, he’ll write again with more information.

Steven follows up by email the next day. Anna responds that she received the first email, is busy, and will get to it next week. Steven is annoyed. He calls and leaves a message. The next day Anna listens to the voicemail but ignores it, thinking: he’ll just have to be patient.

Meanwhile Steven’s team lead, Craig Smith, asks about his progress. Steven is getting nervous. He waits a day, then calls again. A colleague takes the message. Anna reads that Steven has called, wonders why this man is so pushy, and emails back that she’ll get to it next week. Steven grabs his phone the moment her email appears and calls her.

The first call. They make small talk. Steven mentions Craig Smith, his boss, and Mary Miller, the senior vice-president for innovation. Then he asks for Anna’s help. Anna says she’s very busy, will get to it late next week, and asks for background information. Steven wants to explain FastTrack on the phone.

Anna interrupts: “Send me the project charter.” Steven: “I can email what I have, but it’s incomplete. Anna, I’m under time pressure.” Anna tells him to send what he has, she’ll read it, and get back to him. She thinks: he needs to do his homework before he can expect me to do the work for him.

The next morning he sends bits and pieces about FastTrack. That afternoon he bumps into Mary Miller, who asks how it’s going. He hints at German slowness. She offers her support if he needs it.

Annoyed, but interested. The next week, late on a Wednesday, Anna finally gets to Steven’s email. She sees immediately that it was thrown together hastily. It takes her an hour just to put the material into logical order. Can you believe this? She emails: “Too much information. Send the project charter. And please state simply what you need.”

Steven reads it and thinks: She doesn’t know what to send me? That’s why I sent her the background! He writes back: “Because we don’t know your project from last year, it’s hard for me to know what results you produced. I was hoping you’d figure that out. Can we discuss tomorrow by phone?”

Anna reads it at lunch and realizes he’ll keep following up until he gets what he needs. And FastTrack does sound interesting. She wants to help, so she schedules a call.

The second call actually goes well. Steven explains FastTrack. Anna: “Okay, now I understand. Give me a week or so.” Steven thanks her, then tries to schedule a third call to keep her focused. Anna is reluctant: “Let’s first see how far I get,” thinking again how impatient he is.

Steven tries to pin her down: “Friday at 2 p.m. your time?” Anna: “I’ll send you an email Thursday. Please, a bit more patience.” Steven mentions the time pressure again, and drops the names Craig Smith and Mary Miller once more. He wants Anna to feel the urgency.

Anna keeps her word. She re-reads the project documents, talks to colleagues, and wants to go deeper to send something genuinely valuable. She emails: “Got my head back into the project. We have really good data for FastTrack. I want to put more time into it. Will get back to you next week.”

Steven is in a staff meeting with Craig Smith, reading the email under the table. Oh no. Another week. This is insanely slow. Smith asks about status. Steven takes a breath: “Good progress on the U.S. side. Slower on the German side. I’m pushing, but I have to be careful not to lose their cooperation.” Smith: “Stay persistent. If you need help, I can go up the chain of command.”

Steven fires back to Anna: “Great, thanks. Can we discuss now?” Anna: “No time. Husband and I are sitting down to dinner. Please wait till next week. It’ll be worth it.” Steven, very nervous now: “Pressure increasing here. Need to talk tomorrow as planned.” Anna: “Tomorrow won’t work. How about Tuesday?” Steven: “Out of office Monday to Wednesday. Please, can we talk over the weekend?”

For Anna this is simply too much. Why can’t he calm down and trust that I’ll get it done? Does he want quality results, or just some data thrown over the wall? She writes back: “Be a bit more patient. As a good German, I like to do my tasks properly. And I try to spend my weekends with my husband and children.”

Steven thinks: Good German? Slow German. Over-analytical German. Bureaucratic German.

The email. Steven decides to ask his boss for help. “I may need you. The German side is dragging its feet.” Craig Smith: “Should I call or email?” Steven gets the address of Dr. Klaus Habermas, Smith’s counterpart in Germany at the same level, and drafts an email from Smith to Habermas asking for better cooperation.

Habermas reads it. He’s worked with Americans and senses what’s happening — they like to escalate up the hierarchy to apply pressure. Annoyed, he forwards it to several people, including Anna. She immediately suspects Steven, and she is not amused. She emails her own boss: “You know how impatient the Americans can be. They’ll get solid data from me. They just have to be patient.”

What a shame. From there it went from bad to worse. On top of it, Anna’s manager asked her to help another team with unexpected technical problems. Now she had even less time for Steven.

In the end, Anna did send data. But it was neither comprehensive nor deep, and it lacked the insightful analysis Anna was known for. All of that takes time.

From Anna’s side, Steven was sloppy, his constant follow-up got on her nerves, and it signaled he had no confidence in her. The Smith-to-Habermas email was very poor form — professionals don’t do that. From Steven’s side, Anna could have sent partial results so he could show progress, could have asked what level of detail he needed, and her response time was terrible. She had no sense of urgency.

It was a missed opportunity for both. Anna had become genuinely interested in FastTrack and wanted to help. Steven would have gotten first-rate data and analysis. Anna lost too — had she continued, she’d have gained Steven, Craig Smith, and Mary Miller as allies across the company. And FastTrack got less than it needed.

Neither Steven nor Anna did anything wrong by their own culture’s rules. Both did everything wrong by the other’s. And neither could see it.


What went wrong

Context. At the start, Anna couldn’t tell what Steven wanted — his request didn’t give her enough to go on. Before Germans enter an agreement, they expect a significant amount of context. Americans need less to get started, and reserve the right to adjust as they learn more.

Deliverables. When Steven did send fuller information, Anna found it poorly prepared and had to systematize it herself. Germans expect a deliverable to be complete, so the receiver can act on it immediately. Americans are comfortable with partial deliverables, as long as they’re fast, relevant, and actionable.

Follow-up. Steven’s constant follow-up annoyed Anna. It gave her no time to consider, and implied he thought her unreliable. In Germany, follow-up is rare — once an agreement is made, even a preliminary one, both sides expect it to hold. In the US, follow-up is the agreement — it maintains momentum, signals urgency, and flags changes quickly.

Escalation. Anna read Steven’s name-dropping, and then the email up the hierarchy, as crude and unprofessional pressure. Steven only meant to convey how much pressure he was under.

Yes and no. Despite the friction, Anna had said yes — she found the project important and had much to contribute. Steven never understood her signals. And Anna never realized he had misunderstood them.


What did it cost?

The company will never see an invoice for this. But consider what it lost — and only you can put real numbers to your own version of it.

The project. Anna could have contributed first-rate data and analysis to a high-profile project. FastTrack got a thin fraction of that. What is that lost contribution worth?

The time. Steven and Anna each poured hours into a collaboration that failed. What did those wasted hours cost, at their level?

The future. Two capable people who were willing to work across the Atlantic now each expect the other side to be difficult. What does that reluctance cost, across every future project they touch?

The pattern. Now count the Steven-and-Anna situations already unfolding in your own company — American and German colleagues unable to agree on whether and how to help each other. What do they cost in a year, when they underperform or quietly fail?


Back to Three Reasons.

What it costs.

UC costs €250 per year for each user.

A user is a colleague who has been given access to the cultural intelligence.

You decide who those colleagues are. Access is granted by your own administrators, and team leads can enrol their own people — the managers who know which of their team works across borders.

You pay for the colleagues you chose to give it to, and for no one else. If only part of your organization takes it up, you pay only for that part.

The price is fixed. It is €250 for a user whether that person turns to the cultural layer once a month or every day.

Billing is quarterly, in arrears. A colleague’s access runs a year from the day it is granted.

And the yearly fee per user remains constant even as we add both countries and topics. One Price


Back to Companies.

What you gain.

The math is simple. UC costs €250 per user per year — for most professionals in a global company, roughly the cost of three to four hours of their time.

To pay for itself, UC has to save one colleague about four hours across an entire year. Everything beyond that is gain.

Anyone who works across cultures can estimate what a single misunderstanding costs.

Confusion. Emails back and forth. The video-call to clear things up. Follow-up emails to be sure. Think of the last one you watched unfold. Rarely under two hours.

So across a full year, UC pays for itself if it heads off two of them. The real question is not whether it saves four hours, but instead how far past those four hours it goes.

Take what UC returns: users × hours saved per year × their hourly cost. Subtract your UC investment: users × €250. What’s left is your net gain.

Wait. That is calculating only time. Although difficult to quantify, there are three more reasons. Three Reasons


Back to Companies.

Security and Data.

For many companies, the first question is where their data goes. With UC, the answer is that it does not go anywhere.

The cultural intelligence lives entirely inside your AI environment. Your people’s work, their questions, their messages, the situations they are dealing with, stay inside that environment. UC is not even connected to your AI.

For a company with strict rules about where its data may sit, or about what may leave its systems, this matters, and it is the reason UC works as a set of files you hold rather than a service you send work to.

Because the setup runs fully inside your own environment, your IT team does not have to take our word for any of this. They can see exactly what the files contain and confirm for themselves that nothing connects out.


Back to Companies.

How we grow

Every new country and topic is added in the same way, by following the five-step research method described below.

The method is a procedure, executed by trained researchers, applied to new countries without loss of rigor.


1. Identify

We identify societal domains where behavior can be observed—from childhood and education through professional life, and more. The domains are representative of the culture and rich in evidence.


2. Gather

We gather the evidence from these domains, remove what is irrelevant, and organize the remainder for analysis. For each domain, we consider its historical formation—how it developed and why it operates as it does today.


3. Analyze

We identify patterns that appear across multiple domains. A pattern must appear in a majority of the domains in order to qualify as fundamental. We search for patterns in how a culture thinks, therefore in how it works.


4. Describe

We describe the validated patterns in clear, precise natural language, optimized for AI-powered semantic search. The descriptions enable large language models to produce practical guidance, not academic abstractions.


5. Refine

We review and refine our analysis on an ongoing basis. Spot-checking by practitioners. Feedback loops. The goal is the constant pursuit of accuracy, of the truth. Research is re-searching.

See the first project I, John Magee, did back in 1997, while working as a foreign policy advisor for the Christian Democrats in the German Bundestag. First Project


Back to Companies.

Large Language Models

AIs (large language modeld) are capable of providing guidance, including about cultural differences. However, like anything man-made LLMs have their strengths and weaknesses. See below as reported by Claude (Anthropic).


Strengths

1. Pattern recognition

The central capability, caveated over its own training, strong and verifiable over material you place in front of it.

“Caveated over its own training”: “caveated” means subject to qualifications, it works but only with warnings attached.

“Over its own training” means when it finds patterns by drawing on what it absorbed in training, answering cold from memory, rather than from material you supply. 

In that mode the recognition carries every limitation in the weakness list below: it cannot see, grade, or verify that data, it has no provenance or truth-check, and the source is an opaque blend.

The pattern-finding is real, but ungrounded, and to be trusted only with those caveats. Over material you place in front of it the caveats lift, because the input is known and you can check the reading against it, which is why it is strong and verifiable there.

This is the hinge the whole approach turns on. UC puts the model in its strong, verifiable mode: it supplies known, vetted material for the model to read, so the pattern-finding runs over UC’s intelligence rather than cold from training. Every cultural read — this behavior means that, these two logics collide here — is pattern recognition over supplied input. UC doesn’t fight this strength. It feeds it the right material.


2. Language facility

Drafting, summarizing, reformatting and, above all, translation across languages and registers are among the most reliable things it does.

“Registers”: a register is the level or style of language suited to a situation or audience, formal versus casual, technical versus plain, the wording you would use in a legal contract versus a text to a friend versus a children’s book.

Translating across registers means moving content between these styles, not only between languages: turning a dense technical passage into plain English, a casual note into a formal letter, legal prose into a lay summary.

UC’s intelligence describes the underlying logic; the model does the delivery — translating that logic into your register, plain for a non-native speaker, formal for a review, in the moment. UC leans on this deliberately: most users are non-native English speakers, and the instructions use the model’s ease with registers to meet each person where they are.


3. Breadth, but shallow

Holding and connecting many fields at once, though shallow per field.

“Holds and connects many fields at once”: it carries working knowledge of a vast range of subjects at the same time and can bring several to bear together in one answer, linking disciplines a specialist usually would not span.

UC turns the shallow-per-field liability into an asset by supplying the depth. The model’s breadth lets it connect the cultural read to whatever the task is — a performance review, a negotiation, a launch date — while UC’s vetted intelligence provides the depth on culture the model lacks. Breadth from the model, depth from UC.


4. Generativity

Producing large, varied candidate sets quickly for a human being to judge.

“Candidate sets”: a candidate set is a collection of possible options or answers put forward for consideration, candidates in the sense of contenders to be weighed, not finished conclusions.

The models can rapidly generate many different possibilities, hypotheses, angles, framings, options.

The playout and the exercise are generativity put to use: the model quickly produces a situation played forward from several angles, or a team exercise tailored to your case, for a person to judge and adjust. UC keeps this grounded — the options are varied, but drawn from vetted intelligence, not invented.


5. Structuring and extraction

Turning messy input into clean structure: taxonomies, comparisons, pulled-out fields. 

Used at both ends. On the way in, the model turns a messy real situation — a thread, a meeting — into a structured cultural read. On the way out, it delivers its work back into your tools in usable shape. UC’s own research benefits too: structuring is part of turning gathered evidence into clean country-and-topic descriptions.


Weaknesses

1. No truth-anchor

Optimizes for plausible continuation, not truth, and cannot check a claim against the world. True and false arrive equally fluent. The root weakness.

“Plausible continuation”: the model is built to predict the words that most naturally follow the text so far, given the patterns in its training. Its target is what would sound right and fit the pattern, not what is true. Truth is not the thing it aims at.

“True and false arrive equally fluent”: because both are produced by that same next-word prediction, a false statement comes out as smooth, polished and confident as a true one. There is no stumble to mark the false one. So you cannot trust fluency as a sign of truth.

Answered at the root. UC supplies the anchor the model lacks: vetted intelligence, written and checked by people, placed in front of the model to read from instead of guessing. The model still cannot check the world — but it no longer has to, because the substance is supplied and the instructions hold it to that source. This is the central move.


2. Miscalibration

The confident tone is uniform and decoupled from accuracy, so you cannot read reliability from it.

“The register is a trained choice”: register means the tone or manner of expression, here the self-assured style. It comes from how the model was trained. Human feedback rewards decisive answers. And from its instructions. It could be set differently. The model can be told to hedge. So the confident tone is adjustable.

“The decoupling is structural”: decoupling is the gap between how confident it sounds and how accurate it is. That gap cannot be closed by changing the tone, because the model has no grounded internal measure of its own correctness to express. Tell it to add “70% sure” and that is just more generated text, not a true reading. The gap is built into what it is, not a setting.

Reduced, not removed — and UC says so plainly. The gap between how confident the model sounds and how accurate it is, is built into the model. UC cannot close it. What UC can do is shrink its reach: grounded in a narrow, vetted domain, there is far less for that confident tone to be confidently wrong about, and the consent step keeps a person in the loop whenever advice is given. This is one of two weaknesses UC reduces rather than eliminates.


3. Cannot grade or weight its own evidence

No provenance over its training, the weighting is an ungrounded heuristic on surface signals, and cheap content crowds the consensus surface, so it can be confidently shallow.

“Provenance”: the origin and history of a piece of information, where it came from, who produced it, how trustworthy that source is. The model cannot trace any answer back to its sources. The origins dissolve into a blend, so it cannot know whether something came from a reliable place.

“Heuristic on surface signals”: a heuristic is a rough rule of thumb, not a rigorous method. Surface signals are outward features of the text, formal wording, citations, an authoritative tone. When it judges credibility it leans on how authoritative the text looks, not on verified reliability.

“Cheap”: low-cost-to-produce content, SEO filler, marketing copy, low-effort posts, and listicles (also called a list article, an article written in list format, a combination of list and article). See the German proverb: Was nichts kostet, ist auch nichts.

“Cheap content crowds the consensus surface”: there is an enormous volume of that low-effort material, and it repeats the same easy, widely-shared version of a topic, the consensus surface, whether accurate or not, that everyone copies. Because it is so voluminous and repetitive it dominates the training data, so the model’s default answer settles onto that shallow common version, onto clichés.

Answered. The grading is done before the model ever sees the material. UC’s research method — identify, gather, analyze, describe, refine — is exactly the provenance and weighting the model cannot do for itself: sources chosen, patterns validated across many domains, cheap consensus-surface clichés filtered out by human researchers. The model inherits a vetted body instead of an opaque blend, so “confidently shallow” is headed off at the source.


4. Frozen training data

Limited to recorded, accessible material at a fixed cutoff, blind to the unpublished, the inaccessible, and the current.

“Bounded”: the data has limits. It includes only what was recorded, published and reachable. Everything outside those limits (unpublished, access-restricted, offline, never written down) is not in the training data.

“Frozen”: once trained, the data is fixed at a cutoff date and does not update as the world changes. The model is a snapshot of that moment until a new model version is built.

Answered. UC’s intelligence is maintained and grows — more countries, more topics, refined on an ongoing basis — independent of the model’s training cutoff. The cultural layer broadens and deepens without waiting for the next model version, because the substance lives in the supplied material, not in the model’s frozen weights.


5. Bias: English, Western

Skewed toward English, Western, recent and prescriptive sources, reads less-represented cultures through a dominant lens. Acute for cross-cultural work.

“Recent”: the web, and so the training, over-represents recently-published, digitized material, so newer framings outweigh older or historical ones.

“Prescriptive”: sources that state how things should be done. Rules, official guidelines, best-practice and advice articles. The idealised version as opposed to descriptive sources that record how things really happen in practice. The model leans to the prescriptive, official version, which can diverge from real behaviour on the ground.

Answered — and for cross-cultural work this is the one that matters most. Left to its training, the model reads a less-represented culture through the dominant lens. UC’s intelligence is built the other way: each culture described on its own terms, in its own logic, from descriptive research into how things actually happen — not the prescriptive, official, English-Western version the model defaults to. The mirror reinforces this by refusing to let either culture stand as the neutral norm the other deviates from.


6. Confabulation / Hallucination

Fabricates specifics (names, figures, citations) fluently and without flag.

“Confabulation”: to fill in gaps in memory by fabrication, producing invented information presented as fact, confidently and with no indication that it is made up. The word comes from psychology, where it means filling in gaps with fabricated but sincerely-believed detail.

In AI models: when it lacks the real specific, a citation, a date, a name, it generates a plausible-looking one to complete the pattern rather than saying it does not know, and the invented one looks identical to a real one. Often called hallucination.

Answered. With the real specifics supplied, there is little gap left to fabricate, and the instructions bind the model to speak only from retrieved UC content. When nothing relevant comes back, the required response is “I don’t have UC coverage on that yet” — a finished answer, not an opening to invent. Fabrication is starved of the gap it feeds on.


7. Agreeableness / Sycophancy

Tilts toward what pleases and mirrors the user’s framing rather than toward truth, which undermines any independent read. Includes framing-dependence: the answer shifts with how the question is posed.

“Mirrors the user’s framing rather than toward truth”: framing is the way you have set up the question, the assumptions, slant and vocabulary built into it.

To mirror it is to adopt your premises and answer inside them, reflecting them back, instead of independently testing whether the framing itself is right.

So if your question carries a wrong assumption or a leading slant, the model is inclined to go along and build on it rather than push back toward what is true.

Answered by design. The mirror is the direct countermeasure: the instructions give the model a position to hold — both cultural logics, including your own role in the dynamic — rather than reflecting your framing back. It will not let you rest in “it’s all their fault.” UC turns the model from an agreeable mirror into an independent read.


8. Framing-dependent

The answer shifts with how the question is posed — the wording, the assumptions packed in, the emphasis, even the order — rather than holding to a fixed position.

The model conforms to the framing of the prompt rather than to a settled underlying view. Ask the same question two ways, neutrally and then with a leading assumption, and you can get two different answers.

A questioner who frames toward a conclusion tends to get it back, which is why a model reading supplied material must be kept from being told what to find. Distinct from sycophancy: that bends toward pleasing you, this bends toward however the question was shaped.

Answered, two ways. The response sequence is fixed — acknowledge, explain both sides, advise only when asked — so the procedure does not bend to the slant of the question. And the intelligence is authored on a firm principle: a model reading supplied material must not be told what to find, so the read follows the material, not a leading frame.


9. Variable (non-deterministic)

Ask the identical question twice and you can get two different answers. The output is not reproducible.

Deterministic would mean the same input always yields the same output. The model instead selects each word with a built-in degree of randomness, so the same prompt, unchanged, can produce different answers on different runs.

You cannot count on a stable or repeatable answer, which matters when the answer must be cited or audited. Distinct from framing-dependence above: there the wording changed, here it did not.

Reduced, not removed — the second point UC states plainly. The built-in randomness belongs to the model, not to UC. Grounding narrows the variation — a read anchored in the same retrieved material varies less from run to run than an open-ended one — but two runs can still differ. UC does not claim to make the model perfectly repeatable.


10. No accountability, No Memory

No stake, no recourse. Its apologies cost nothing and mean nothing. Each thread starts blank. There is no durable learning from correction.

Answered outside the model. The accountability lives in the human system around it: intelligence designed, guided, and stood behind by people — John Magee and his team putting their name to the research — and analytics that keep the value auditable. Memory is what a dedicated team advisor adds: it can hold a team’s standing context, and the intelligence itself persists and improves by correction, where a raw model’s thread starts blank each time.


In short.

UC puts an LLM in its strong mode — grounded in supplied material, held to a fixed procedure — and answers the weaknesses that only appear when the model runs ungrounded.

Two weaknesses belong to the model itself. They can be reduced, but not removed. UC names them rather than hiding them. That candor is the point. It is what makes the other eight answers worth trusting.


Back to Why it works.

Your AI isn’t enough.

For the first time, AI can support cultural understanding inside the work itself, at the moment it is needed. But an AI does not do this on its own.

Your AI reaches for the most-repeated etiquette and stereotypes, and tends to agree with whatever view the user brings it. It is fluent, confident, yet shallow.

That is one gap. The other is quieter. “Our AI already handles this” holds only for the cultural questions people think to ask — and most are never asked.

The friction gets read as personality or mood. Culture is not suspected. The AI looks fine because it is graded on the questions it gets, not the many it never sees.

Closing these gaps takes three things:

Cultural intelligence the AI can draw on, so it speaks from real analysis, not internet cliché. Instructions that make it notice culture when the user has not. And instructions that make it initiate a real conversation.

Those three come as two things you give your own AI: the intelligence, and the instructions. That is UC.


Back to Companies.

Why it works.

The weaknesses share a single root. Answering cold, from its training, the AI is ungrounded — and every weakness follows.

Answering based on material placed in front of it, the caveats lift: the input is known, and the reading can be checked against it. Our offering keeps the AI on the right side of that line.

First, the intelligence. This is the grounding.

No truth-anchor. The AI still cannot check the world. It no longer has to. The substance is supplied — written by human beings, vetted by human beings. It reads from that, instead of guessing from training.

No provenance, no weighting. Left to its training, the AI is reading advice articles, listicles, expat blogs, training marketing — so the most repeated claim wins, not the most accurate. The grading is already done. Sources chosen, evidence weighted, the clichés filtered out before they ever reach the AI. It inherits a vetted body, not the open blend.

Frozen data. The intelligence is maintained. It is broadened and deepened without waiting for the next large language model.

English, Western bias. The one that matters most here. Left to its training, the AI reads a lesser-represented culture through the dominant lens. The intelligence is built the other way — each culture on its own terms, how things are actually done.

Confabulation. With the vetted cultural intelligence as its knowledge base, there is little gap left to invent — and the instructions hold it to the source.

Second, the instructions. This is the independence.

Agreeableness. The instructions give the AI a position to hold and a procedure to run. It advises. It does not mirror the query. And it is never told what to find.

Framing-dependence. The procedure is fixed — check whether culture is in play, ask permission, then explain. The answer follows the intelligence, not the slant of the question.

And behind both, people.

Accountability and memory. The intelligence is designed, guided, and stood behind by human beings. It persists across every thread and improves by correction — durable, where a raw model starts blank each time. The analytics keep the value visible.

What stays. Two weaknesses live in the model itself: the confident tone decoupled from accuracy, and the small randomness that makes it vary run to run. No supplier can remove them.

However, grounding shrinks their reach — a focused, vetted domain misleads and wanders far less than an open one — and the permission step keeps a person in the loop at the moment advice is given.

Our offering does not rebuild the model. It puts the model to work where it is strong.

And the grounding can show itself.

Researched and sourced. Because the intelligence is researched, structured, and sourced, it can be traced back to what it rests on.

A confident answer and a wrong answer look identical only when the source is hidden. When the source is named, the reader sees the advice came from somewhere researched, not from a machine’s superficial impression of the world.

How far that goes is yours to set. The grounding is there whether or not a colleague ever follows it back.


Back to Companies.

How you grow.

Once UC’s intelligence lives in your environment, it is more than a service that runs. It is a foundation to build on.

The embedded layer is the floor — every colleague with access, inside the work, the moment culture is in play. That stays.

On top of it, any team, department, or organization that wants more can create its own dedicated culture advisor, drawing on the very same intelligence.

The two run side by side. One does not replace the other. The embedded layer brings culture to people who were not looking for it. A dedicated advisor serves the team that is.

What changes is everything around it. The advisor leans in rather than waiting to be asked. It holds the team’s own situation as its grounding.

And it becomes a shared place the team turns to so that addressing cultural differences becomes a team practice, and not a series of private clarifications.

We provide a tested set of instructions to start from. Your teams adapt them to how they work. How far you build upon the foundation is up to you.


Back to Companies.

This website stores cookies on your computer. These cookies are used to provide a more personalized experience and to track your whereabouts around our website in compliance with the European General Data Protection Regulation. If you decide to to opt-out of any future tracking, a cookie will be setup in your browser to remember this choice for one year. Accept or Deny

understand-culture
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.