Case studiesAgency operations software

Waltz AI: connected page, email and knowledge workflows for agencies

Waltz AI brought creative production, campaign execution and agency context into one workspace. Ego Eimi built the platform with Afaq Jamshad, connecting four AI systems to the work around a campaign.

Business
Waltz AI
Sector
Agency operations software
Scope
Pages, campaigns, forecasting and retrieval
Contributor
Afaq Jamshad
Editorial illustration: interlocking metal ribbons joined by one orange strip
AI-generated editorial illustration of the project’s domain.

Campaign information was recreated at every tool boundary.

A campaign moves from a brief to a page, an email, analytics and a report. When those stages live in unrelated systems, the team repeatedly carries the same information between them.

The product needed to connect those workflows while keeping agency knowledge available. Each AI capability had a defined role in the wider application.

Give creation, execution and analysis a shared workspace.

A page orchestrator used GrapesJS Studio with output purification to generate and edit landing pages and brand assets. The email suite handled campaign variables and lead tagging.

Prophet-based forecasting supplied trend projections. Walter, a retrieval-augmented assistant, used agency context to answer questions. The platform connected these systems to campaign execution and knowledge management.

What the workflow includes

  • Generate and edit pages through a GrapesJS integration.
  • Run email workflows with variables and lead tagging.
  • Use forecasting as an input to campaign planning.
  • Retrieve agency knowledge through the Walter assistant.

Project details

Waltz AI product page with the Walter design prompt entry point

Project materials showing the workflows and interfaces described in this case.

Product walkthrough

Pages, campaigns, forecasting and retrieval. The delivery section explains the workflow demonstrated here.

The application carried context across the campaign workflow.

The delivery brought several campaign tasks into one connected application. Page creation, email, forecasting and knowledge retrieval could use the context held by the workspace rather than requiring a fresh handoff at every step.

What this means for the technology owner.

A connected workspace needs an owner for the relationships between its tools. Generated pages, email permissions, forecast assumptions and retrieval sources each change on different schedules. A handover should explain those dependencies and the review step before a customer-facing action.

Tech Team: ongoing technology responsibility →

PythonGrapesJSRAGProphetLLMsWeb app

Project contribution: Afaq Jamshad. The scope described above identifies the work behind this case.

Waltz AI — project link

Editorial review: Ego Eimi · Updated September 6, 2026 · About the team

Your technology

Start with the business

Your business depends on it.

Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.