The data behind the design: How Pantone built agentic AI with an AI-ready database
Pantoneโs example is useful because it shows agentic AI as an application architecture problem, not just a model-selection exercise. The core dependency is a low-latency data layer that can persist prompts, chat history, and interaction state fast enough to keep a conversational workflow coherent across turns, sessions, and geographies. That makes the database part of the user experience, not just a back-end store.
The trade-off is that richer agent behavior increases the burden on persistence, retrieval, and observability. Once an assistant depends on conversation memory and interaction telemetry, teams need to think about schema evolution, data retention, and operational cost alongside response quality. Pantoneโs move toward vector-based workflows reinforces a common pattern: AI systems often begin with text, then need a path to semantic retrieval without rebuilding the entire platform.
For technical teams, the architectural lesson is that AI readiness depends on integration discipline. Agent orchestration, embedding models, analytics, and database services must line up cleanly so the system can improve iteratively. That has practical implications for platform engineering: choose components that support rapid prototyping, then can absorb production workloads, instrumentation, and future retrieval methods as usage grows. The most durable AI experiences are usually the ones designed for change from the start.
The challenge: Scaling color expertise in a real-time, interactive world
Pantone is widely recognized as a global authority on color. For decades, their teams have combined human expertise, color science, and trend forecasting to help designers and brands define, communicate, and control color across industriesโfrom fashion and product design to packaging and digital experiences. But as Pantone explained in the webinar, translating that depth of expertise into a modern, conversational AI experience came with real challenges. Creating color palettes is both time consuming and critical to the design process. Designers often gather inspiration by navigating between tools, color pickers, and trend reports before they ever land on a usable palette.
Pantone saw an opportunity to rethink that workflow entirely: What if designers could interact with decades of Pantone research, trend data, and color psychology through a chat-based interfaceโand generate curated palettes instantly?
Introducing the Palette Generator: An agentic AI experience
The result is Pantoneโs Palette Generator, an AI-powered experience launched as a minimum viable product to gather real user feedback and iterate rapidly. Rather than offering static recommendations, the Palette Generator uses multiagent architecture to respond dynamically to user intent, conversational context, and historical interactions.
In the webinar, the Pantone team described how they designed the system to include specialized agentsโsuch as a โchief color scientistโ agent and a palette generation agentโeach responsible for different aspects of reasoning, context retrieval, and response generation. These agents work together to deliver curated color palettes that reflect Pantoneโs proprietary data and expertise.
What stood out to me was not just the sophistication of the AI, but the architectural discipline behind it. Agentic AI isnโt just about modelsโitโs also about data.
Why Azure Cosmos DB was foundational
At the heart of Pantoneโs Palette Generator is Azure Cosmos DB, serving as the systemโs real-time data layer. Azure Cosmos DB is used to store and manage chat history, prompt data, message collections, and user interaction insightsโall of which are essential for responsive, fast, context-aware agents.As we did our research to find the best persistence storage, we explored different databases. What we found for Azure Cosmos DB was how easy it was to integrate it into our systems. We were able to make our initial proof of concept with a few lines of code and retrieve all the data very, very fast, like in a few milliseconds. Kristijan RisteskiAzure Cosmos DB was also chosen because of its scale, allowing Pantone to serve users all over the world with fast data retrieval. This is a critical point. As applications shift from โdoingโ to โunderstanding,โ databases must support far more than simple transactions. They need to handle massive volumes of operational data, adapt as AI workflows evolve, and support advanced scenarios like conversational memory, analytics, and vector-based search. Pantoneโs architecture demonstrates what it means to be โAI-ready.โ Azure Cosmos DB provides the scalability and flexibility needed to track user prompts and conversations across sessions, along with analytics that help Pantone understand how customers interact with the Palette Generator over time.
From text to vectorsโand what comes next
Another insight Pantone shared during the webinar was how their architecture is evolving to improve relevance, accuracy, and contextual understanding. While the current system already supports rich conversational experiences, the team outlined next steps that involve moving from traditional text storage to vector-based workflows. This includes embedding user prompts and contextual data, allowing for vector search, and enriching responses with deeper semantic understanding. Azure Cosmos DB plays a role here as well, supporting vectorized data, integrating with agent orchestration, and embedding models deployed through Microsoft Foundry. This allows Pantone to iterate without rearchitecting the entire systemโan essential capability when working in a fast-moving AI landscape.Real-world results from agentic architecture
Pantone didnโt just talk about visionโthey shared concrete results from real usage of the Palette Generator. According to the webinar data, users across more than 140 countries engaged with the tool, generating thousands of unique chats within the first month of release and interacting in dozens of languages. The system observed multiple queries per user session, indicating that designers were actively experimenting, refining prompts, and exploring ideas conversationally. Just as importantly, Pantone emphasized how rapidly theyโve been able to learn and adapt. Prompt sensitivity, user behavior, and architectural tradeoffs around speed, cost, and reliability all informed ongoing refinements. Azure Cosmos DBโs flexibility made it possible to capture these insights and evolve the experience without slowing innovation.Lessons for anyone building agentic AI
Pantoneโs journey reinforces several lessons I see repeated across customers building AI agents on Azure:- Agentic AI is inherently data driven. Without a real-time, scalable database layer, even the most advanced models struggle to deliver consistent, context-aware experiences.
- Feedback loops matter. By capturing prompts, responses, and user interactions in Azure Cosmos DB, Pantone can continuously improve both the AI and the product experience itself.
- Flexibility is nonnegotiable. AI architectures evolve quicklyโfrom orchestration patterns to embedding strategiesโand databases must evolve with them.
The data behind the design: How Pantone built agentic AI with an AI-ready database
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.
