Lo que mas me ha resultado es primero armar un design system bien documentado (lo haces con claude design), que te baje todos los tokens a css, y luego te armas un skill que sea “experto” en ese design system. Despues combinar con otros skills de ux. De esa forma logras consistencia en cada nuevo feature.
The CDP-as-product is dying.
The seam between customer data and the system that acts on it was always artificial — an architectural artifact nobody questioned.
Whoever owns the system that acts owns the data. Loyalty is next.
If your loyalty program isn't callable by an agent, it isn't loyalty.
It's a coupon database with a UI nobody visits.
Chipotle's strategy chief just named the era loyalty 4.0. The definition is architecture, not feature.
https://t.co/xWBlRSJjyu
Stored-value loyalty is repricing in public.
Hyatt: top redemptions up 67%. American: partner bonuses capped.
Two flagship programs said the quiet part the same quarter. The balance isn't the moat. The relationship is. And the relationship lives at the moment, not in the spreadsheet.
Banks used to report AI as deflection rate.
Nubank just disclosed 15M monthly active users on an AI advisor.
That's not a deflection number — it's a habit number. The conversation moved from "we saved tickets" to "we own a relationship slot."
Esto no va de seguridad. Va de quién tiene el kill switch.
Una agencia del gobierno de EE.UU. obligó a Anthropic a retirar del mercado Fable 5 y Mythos 5 por un "jailbreak"
En el contexto LLM, un jailbreak es un prompt (o secuencia de prompts) que logran generar una respuesta que supuestamente el entrenamiento de seguridad debiera haber bloqueado (ej. como hacer una bomba).
El laboratorio más alineado con la narrativa de "AI safety" está argumentando públicamente que un jailbreak puntual no debería retirar un modelo a cientos de millones de usuarios.
El argumento es esencial: el indeterminismo de los modelos hace matemáticamente imposible garantizar la inexistencia de jailbreaks menores en un modelo de frontera
Si un "jailbreak puntual" justifica retirar un modelo en producción, todo modelo frontera es retirable para siempre. La resistencia perfecta a jailbreaks no existe.
Cada producto AI-native ahora carga riesgo de recall gubernamental en su diagrama de arquitectura. Multi-proveedor dejó de ser paranoia esta mañana. Es el nuevo mínimo viable de cobertura.
Esa carta es el precedente que va a citar todo founder construyendo sobre rails de IA.
The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees.
The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance.
Access to all other Claude models is not affected.
We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible.
Read our full statement: https://t.co/bwn0sximKZ
The role is real. The output ceiling is set one layer down.
The marketing engineer's leverage caps at whatever the underlying platforms (CRM, loyalty, segmentation) expose. Click-the-UI software hits the ceiling fast — the engineer can't delegate what the platform won't expose to an agent. Only platforms built to be operated by agents let the role compound.
The cert is what the moat looks like before it's named.
Regulated CX — federal, financial, healthcare — needs typed surfaces, full audit trails, and reversible permissioned agents. Most "AI chatbot on CRM" stacks can't pass that bar because the architecture wasn't built for it. Sierra's FedRAMP High is the first public proof that agentic CX is leaving the SMB sandbox
I am proud to announce that Sierra has been certified FedRAMP High — the standard for cloud companies working with U.S. federal agencies.
Hundreds of millions of people rely on the U.S. federal government for services — from navigating Social Security, Medicare, and Veterans Affairs to filing their tax return or renewing their passport. AI agents built on Sierra can help make them simpler and faster. https://t.co/u2qfyA0wnH
Ulta has 46M loyalty members. They drive 95% of US sales.
At that ratio, "loyalty program" is the wrong noun. It's the operating system.
Same week: Sephora links 80M Beauty Insider members into ChatGPT as a storefront. The agentic discovery surface sits on top of the loyalty graph, not separate from it.
Read the two together. The loyalty graph isn't a CRM module bolted onto the retail stack — it IS the retail stack, with merchandising, personalization, and the agentic surface all plugging into it.
The procurement question for any retail CMO in H2 2026 has shifted. Not "do we have a loyalty program?" but "what runs on top of it?"
Most LATAM retailers still treat loyalty as a CRM module. The gap between that and Ulta isn't a feature gap. It's years of compounded loyalty-graph data acting as the operating layer.
The retailers that win the next decade will be the ones whose loyalty layer is callable by every other system — including the agent the customer hasn't met yet.
Pensar problemas en formato solución era un error caro. Ahora es uno absurdo.
Las soluciones están a n-tokens. Entender el problema cuesta todo lo demás.
Extending this: the moat isn't just the context. It's how the context is callable. Every vertical with applied-AI ambition will accumulate similar context. The differentiator is whether the next agent can fetch it in one typed call or has to rebuild it from logs each time.
The lock-in lives one layer below where most people are looking.
@gabriel1 The marketing equivalent is already running.
Every loyalty rule, every campaign brief, every personalization edge case — those are intent specs written in slack threads instead of typed contracts. Coders are 18 months ahead of marketers on figuring out the cost.
Ocho proveedores en una sola línea de presupuesto.
Carrefour comprometió €3.000 millones a su transformación digital y de IA bajo su hoja de ruta 2030. Los socios nombrados: OpenAI, Google Cloud, Microsoft, Bain, Capgemini, Publicis Sapient, Artefact, Centric. Cada uno entrega una pieza. El trabajo de Carrefour es la integración.
Pueden pagarlo: €21.100 millones de facturación trimestral, 50 millones de socios de fidelización hoy (meta de 60 millones a 2030), Hopla — su asistente sobre OpenAI — ya en producción, y el catálogo del supermercado disponible dentro de ChatGPT como punto de venta. La tesis es correcta. El costo de armarla es enorme.
Cualquier retailer Tier-2 que esté mirando esto tiene una alternativa más limpia. Comprar una sola plataforma AI-native donde fidelización, mensajería, segmentación y la capa agéntica viven en un solo esquema, no en siete contratos. Saltarse el armado. Llegar al mismo destino en un trimestre, no en dos años.
El costo de integración era un feature de la década SaaS. En la era AI-native es un bug.
@nikitabier Same dynamic on the loyalty side. The most impactful rewrites — callable layer, eval gates, data model — never show up to the end user directly. What ships visible is "the app got faster, the offers got smarter."
The substrate change is invisible. The surface compounds.