← All systems

Stanza Living · Operational AI

Operational Data Copilot

From business questions to operational clarity.

AI AgentsNL2SQLContext engineeringInternal tools
Role
AI Product Manager · Stanza Living
Setting
Production system
Delivery
Led with 2 developers, in collaboration with Data Science
Stakes

Business and Functional Heads needed operational answers they could use in decisions, alongside clearer updates from ground teams. A natural-language query interface addressed only part of that need: the system also had to carry relevant context through the interaction and fit the communication around the work.

Key decision

Build the harness around the operational workflow, with memory and context at its core.

Outcome

Shipped a React-based operational copilot for Business and Functional Heads, combining natural-language access to Redshift with a custom agent harness built around memory and context, while helping organize ground-team updates and communication.

Conceptual system overview
  1. 01Business and Functional HeadsOperational questions raised in the course of a decision
  2. 02React applicationThe interface leaders work in
  3. 03Agent harnessMemory and context engineering carry the workflow
  4. 04NL2SQL and RedshiftThe data capability, built with Data Science

Built for Business and Functional Heads at Stanza Living. It brought natural-language access to operational data into a React application, backed by Redshift and a custom agent harness. I led the work with two developers, collaborating with the Data Science team.

The obvious automation was not the whole problem.

The product needed to support more than a single question and answer. Leaders needed to explore operational information in context and keep track of updates from ground teams. The challenge was designing a system that could support those connected needs.

The interface made the system approachable. The harness made memory and context part of how it worked. That placed much of the product effort beneath the chat experience, in deciding what information the agent needed and how to carry it through the workflow.

Build the operating loop, not only the intelligent step.

  1. Anchor the experience in leadership workflows. Design for Business and Functional Heads asking operational questions and coordinating follow-up.

  2. Build the agent harness. Work with two developers on the infrastructure around the model, including memory and context engineering.

  3. Connect the data capability. Collaborate with Data Science on the NL2SQL capability and its connection to Redshift.

  4. Support operational communication. Include support for organizing updates and communication with ground teams.

Outcome

Shipped a React-based operational copilot for Business and Functional Heads, combining natural-language access to Redshift with a custom agent harness built around memory and context, while helping organize ground-team updates and communication.

What stayed after shipping.

The most substantial work sat beneath the interface. Building the harness around memory and context was central to making the agent useful within an operational workflow.