AI personalization strategy is the set of decisions that sit above any personalization system: what the system is allowed to infer about a customer, what it may change for that customer, where the changing has to stop, and what an AI agent may do on a customer’s behalf. Vivaldi has advised on customer, brand and demand strategy since 1999, from ten offices on four continents.
These are governance and brand decisions wearing technical clothes. A recommendation engine does not decide whether it is acceptable to act on an inferred health condition, and a customer data platform does not decide whether an agent may cancel a subscription without asking. Someone has to, in writing, before the first model ships. That document is what this work produces.
- Since 1999customer, brand and demand strategy
- Über 200veröffentlichte Fallstudien
- 10 Niederlassungenauf vier Kontinenten
- 5xWirtschaftsWoche: Das Beste aus den Bereichen Beratung, Strategie und Innovation
Wenn Unternehmen uns beauftragen
- A personalization program is live, conversion is up, and complaints have started arriving that nobody can classify as a bug
- Legal or risk has stopped an agent deployment and no one can produce the document that would restart it
- Several teams are personalizing the same customer independently, and the customer is receiving the composite
- The board has approved AI agents that act for customers, and the question of what they may commit the company to has not been answered
- A platform vendor has been selected and the strategy is being reverse-engineered from the vendor’s feature list
Why treating personalization as a martech problem does not work
Personalization is usually owned by the team with the tooling, and that team is measured on conversion. Every decision then resolves the same way, because more inference and more automation reliably produce a better number this quarter. The costs land somewhere else and later: in trust, in churn among the customers who noticed, and in a brand that now reads as a company that watches you.
That matters financially rather than ethically. Our 2026 study of twenty-four years of stock market data (Joachimsthaler, Powney and Rolka) found that strong global brands beat the S&P 500 by 3.7 percentage points a year from 2001 to 2024, turning a dollar invested into $15.85 against $7.03 in the index. The asset being traded for incremental conversion is the one with the compounding return, which is why the limit on personalization belongs with the people accountable for the brand rather than with the people tuning the model.
The second failure is subtler. Teams debate how personal to get, as if the only axis were intensity. The real variable is what the personalization rests on and how much authority it has been given, and those two combine badly in exactly one corner.
What our AI personalization strategy services include
1. The inference boundary
The difference between what a customer told you and what your system concluded about them is the whole subject. An observed fact is defensible. An inferred claim is a guess the company is now acting on in public.
- A register of the inferences the system is permitted to draw, written as claims rather than as data fields, because “browsing history” is not the sensitive thing and “probably pregnant” is
- The inferences that are prohibited outright, including the ones a model can reconstruct from permitted inputs without ever being given the sensitive field
- Confidence thresholds per inference class, and what the system does below them, which is usually nothing rather than a hedged version of the same action
- Who reviews the register when a new data source is connected, since every new source silently expands what is inferable
Basis for the decision
Authority granted to the system
2. The personalization mandate
A mandate states what may vary between two customers and what must be identical for everyone. The second half is the one that gets skipped, and it is the half that protects you.
- What may vary: sequence, timing, emphasis, assortment, channel, level of support
- What may not vary without an explicit decision at the executive level: price, terms, access to redress, and what the company tells the customer is true
- The difference between personalizing the offer and personalizing the facts, which is where most reputational incidents in this field actually originate
- How the mandate holds across channels, since a customer meets one company and does not care that three teams own the touchpoints
3. Agent authority: what an agent may do on a customer’s behalf
Agents introduce a question personalization never raised. A recommendation can be ignored. An action cannot, and when an agent acts for a customer it is also acting for you.
- The mandate itself: which actions the agent may take unaided, which require the customer to confirm, and which require a named employee
- Value and reversibility thresholds, set as numbers rather than as principles, because a principle cannot be implemented
- The reversal path for every action the agent can take, defined before launch, including who is notified and how quickly
- Whose agent it is when the customer brings their own, and what your systems disclose, refuse or negotiate with a buyer’s agent that is not yours
4. Disclosure and customer control
Customers accept a great deal of personalization and almost no surprise. The variable you control is whether they find out from you or from the experience itself.
- What is disclosed, where, and in language that states the inference rather than hiding it behind “relevant to you”
- Which controls are real: the ability to correct a wrong inference is worth more to a customer than a blanket opt out, and is far cheaper for you
- What happens to personalization after a customer declines it, which should be a defensible default experience rather than a punitive one
- The escalation route to a person, which is the control that determines whether a bad automated decision becomes a complaint or a lawsuit
5. Governance and proof of value
Personalization programs are usually measured against the customers they worked on, which guarantees a positive result. The question is whether the program created value or moved it from one part of the base to another.
- A measurement design with a genuine holdout, so uplift is uplift rather than the customers who were going to convert anyway
- Counter-metrics that would show harm: complaint classes, unsubscribe composition, and churn among the customers who were personalized hardest
- A standing review that owns the inference register and the agent mandate, with the authority to withdraw a permission, not just grant one
- The audit trail that lets you answer, months later, why a specific customer saw what they saw
Not sure where your current line actually sits?
Start with a working session with one of our partners. We will take one live personalization or agent use case, place it on the two axes above, and establish which decisions have been made deliberately and which were made by a default setting.
How an AI personalization engagement works
- Establish. What is already being inferred and acted on, across every team that touches the customer. This is almost always wider than the executive sponsor believes, because the register has never been assembled in one place.
- Decide. The inference boundary, the personalization mandate and the agent authority thresholds, taken as business decisions with brand, legal, data and the commercial owner in the same room.
- Design. Disclosure, customer controls, escalation routes and the measurement design, including the counter-metrics that would tell you the program is working against you.
- Embed. The review body, its authority to withdraw permissions, and the trigger conditions that force a re-decision, such as a new data source or a new agent capability.
Why companies choose Vivaldi for AI personalization strategy
We are a strategy firm, not a platform partner and not an implementation vendor. We have no revenue tied to how much of your customer base gets personalized or to which system you buy, which matters on a question where every other adviser in the room has a position.
The work also starts from demand rather than from data. Vivaldi’s practice is built on understanding what customers are trying to get done, which is the only basis on which you can judge whether a given piece of personalization is a service to the customer or a service to your conversion rate. That distinction is the one a model cannot make for you.
How to evaluate an AI personalization consultant
- Ask what they would refuse to infer. A firm with no prohibited list has not done this work, only the parts of it that increase revenue.
- Ask for a threshold, not a principle. “Human in the loop for high-risk actions” is not an answer. The number at which the agent stops is.
- Ask who owns the limit after they leave. If the answer is the personalization team, the limit will move, because that team is measured on the thing the limit constrains.
- Ask how they measure harm. Any firm can show you uplift. Ask which metric would have told them to stop.
- Ask what they sell besides advice. A recommendation to personalize more is worth less from someone who also sells the engine.
Strategy consultancy vs personalization platform vendor vs privacy counsel?
| Kriterium | AI personalization strategy consultancy | Personalization platform vendor | Privacy and compliance counsel |
|---|---|---|---|
| Question it answers | What the system may infer, what may vary per customer, and what an agent may do for them | What the platform can execute and how fast | What the law permits in each jurisdiction |
| Typische Ausgabe | Inference register, personalization mandate, agent authority thresholds, measurement design | Use case library, segment builder, campaign throughput | Legal basis assessment, notices, records of processing |
| Where it stops | Does not build the system or run the campaigns | Does not decide what you should be willing to do | Does not decide what is commercially or reputationally wise |
| Wer gibt die Freigabe? | CMO, chief data officer and general counsel together | Marketing operations | Legal and the data protection officer |
| Am besten, wenn | The capability exists and nobody has decided how far it is allowed to go | The decisions are made and execution is the constraint | The exposure is regulatory rather than strategic |
Legal compliance and good judgment are not the same test. Most of what damages a brand in this field was lawful.
Verwandte Arbeiten
This page is the strategy layer. Two neighboring pages handle the layers beneath it, and the line between them is worth stating plainly.
- AI UX design consulting covers how an AI product behaves in the interface: where the model belongs in a flow and what the screen does when it is wrong. This page decides what the model is allowed to conclude in the first place.
- Dynamic customer journey strategy covers what a single journey may change for a given customer. This page sets the policy that holds across every journey, channel and agent at once.
- Machine learning, predictive analytics and AI strategy if the open question is whether the prediction is good enough to act on at all.
- AI strategy and new technology if no personalization program exists yet and the question is which workflows are worth changing.
Diese Arbeit ist Teil unseres Geschäftsbereichs „Business Technology Strategy “ bei Vivaldi, dem Strategieberatungsunternehmen, das hinter dem „Demand Landscape“ und dem „ Interaction Field “ steht.
AI personalization strategy in the US and worldwide
Our teams work out of ten offices on four continents, with the US team in New York. Personalization limits rarely translate across markets without inspection: an inference customers accept in one market reads as intrusive in another, and an agent mandate that is lawful in the US may be unlawful in the EU before it is ever unwise. We treat that asymmetry as a design input, which usually means one global mandate with a small number of documented market exceptions rather than a separate policy per country.
Write the limit down before the next model ships
In one working session we will take one live use case, separate what your systems observe from what they infer, and establish what your agents are currently permitted to do on a customer’s behalf. You leave with the decisions that have to be made and the names of the people who have to make them.
