COMMAND CENTER Streamlining Commerce with Shopify Migration and UX

80+

Custom AI agents deployed

25%

Time saved per workflow

33%

Faster time to completion

98%

Client satisfaction score

22%

Faster project delivery

40%

Reduction in AI operating costos YoY

18+

Months in continuous internal operation


  • THE CHALLENGE

Two years ago, our teams were running six different AI providers across isolated workflows. Project managers generated deliverables from OpenAI in one format while another team produced the same work from Claude in a completely different format. Lifecycle marketing ran Klaviyo automations through one pipeline and Bloomreach campaigns through another. Sales built agents nobody else could see. Every department was moving fast. Nobody was moving together.

The output was inconsistent. The governance was nonexistent. Sensitive client data was flowing through consumer-grade tools with no data protection guarantees. We tried buying our way out. We adopted every AI feature from every platform we used. Within months, the result was clear: a fragmented disaster. Each tool's AI worked in isolation. None of it talked to the rest. The build-vs-buy question answered itself. Buying AI tools is the easy part. Making them work together as a governed, organization-wide system is the hard part.

IM Command Center login screen with Google sign-in button, alongside a Vincent Van Gogh painting displayed in the interface
IM Command Center dashboard showing the main navigation, AI chat interface, and quick-access tools for the IM Digital team
IM Command Center showing the Confluence Agent detail page, with UX Helpers folder and agent list in the left sidebar

What We Built

Command Center is the AI operating platform we built for ourselves. Not as a product for market. We built it because we needed it. Every architectural decision was driven by an internal problem, not a feature someone thought would sell well.

The platform provides multi-model AI access (Gemini Pro, Gemini Flash, Claude Sonnet, and others) through a single governed interface running on Google Cloud enterprise infrastructure with Vertex AI. It connects to the systems our teams already live in through MCP integrations: Jira, Confluence, Klaviyo, Bloomreach, HubSpot, and Google Analytics. Knowledge bases built on RAG architecture through Llama Index Cloud allow agents to draw on document collections, call transcripts, and client data. Looker Enterprise dashboards are embedded directly in the platform, with data replicating into BigQuery. Role-based access control through Auth0 governs who sees what. The platform runs on Google's ADK framework with A2A protocol connectivity to Gemini Enterprise.

The most important capability: any teammate, regardless of technical background, can build and deploy custom AI agents. This moved the bottleneck away from engineering and put AI directly in the hands of the people closest to the work.

IM Command Center Agents Dashboard showing UX Research Assistant, Confluence Agent, IM Copywriter 2.0, and Sales Coach
IM Command Center Prompt Library with reusable prompts: Content strategy for LinkedIn, Shopify SOW, and Agent prompter
IM Command Center agent configuration for UX Research Assistant, showing safety settings and role-based access controls

What 80 Agents Taught Us

Over eighteen months, our team built and deployed more than 80 custom agents. Sales Ninja became the institutional knowledge layer for the entire organization, loaded with our service taxonomy, case studies, client history, and competitive positioning. Anyone can ask it who we are, what we do, and how we approach specific challenges. Brand voice agents built for specific clients generate on-brand copy across lifecycle marketing workflows. A project management agent connected to Jira lets PMs create and flesh out tickets using project documentation without switching tools. An internal knowledge agent answers routine operational questions from Confluence, reducing the load on leadership.

Deploying the technology was the straightforward part. Getting 100+ people to change how they work was the real project. Adoption was uneven. Some teammates went back to ChatGPT because the habit was already formed. We ran structured enablement sessions, assigned champions within each practice area, and tracked adoption metrics. We also learned what happens when AI adoption moves faster than AI literacy: some team members generated work from call transcripts without reviewing the output, producing results disconnected from the actual documentation. We built quality gates into every workflow. The AI produces a draft. The human reviews and validates. The output goes to the client.

The lesson we carry into every engagement: the technology is a prerequisite. The transformation is an organizational project.

Abstract close-up of smooth, flowing cream-colored sculptural forms with soft shadows
IM Command Center mobile Quick Add Prompt panel listing Agent prompter, Content strategy, and Shopify SOWIM Command Center mobile Save Prompt dialog with a sample urban planner prompt and tag fields for design and agent categoriesIM Command Center Archived Chats listing past sessions: UX Research Assistant, IM Copywriter 2.0, and Site Assessment

Our team reclaims a quarter of their time on every AI-integrated workflow. Project delivery accelerated by 22%. Strategy documents once taking a week now take days. Ticket creation once consuming an afternoon happens in minutes. Client satisfaction sits at 98% because the humans directing the work have more time to think, review, and refine. AI operating costs dropped 40% year over year even as token consumption doubled. And Command Center outperforms Gemini Enterprise on identical models for our use cases, because our architecture injects relevant documents and context directly into the prompt. Architecture matters more than model selection.

Explore with IMAI