Every month, our performance team produces a set of reports that track how key brands are performing across digital channels. It's important work. It informs decisions. And until recently, it was also a phenomenal waste of skilled people's time.
The process looked like this: download data exports from three platforms, copy numbers into a master spreadsheet, generate charts, paste those charts into a PowerPoint template, write commentary for each slide, format everything to brand guidelines, then send it out. Rinse and repeat for each market. Each brand. Every month.
I looked at this and thought: every single one of these steps is rule-based. There's judgment involved, yes — but it's bounded judgment. The kind an AI system can learn if you define the guardrails properly.
Building the pipeline
We started with a simple question: what if we broke this into discrete agents, each responsible for one step, and let them hand off to each other?
The result is a 7-agent pipeline:
- Data Ingester — reads Excel exports, normalises column names, validates data integrity
- Metric Calculator — computes period-over-period changes, flags anomalies, generates summary statistics
- Chart Generator — produces branded charts from the computed data using Python's matplotlib
- Narrative Writer — drafts slide commentary based on the metrics, using templates and conditional logic for different performance scenarios
- Slide Assembler — builds the PowerPoint deck, placing charts, text, and branding elements according to the template
- Quality Checker — validates the output against a checklist (correct date ranges, all brands present, no placeholder text)
- Distribution Agent — saves the final deck and triggers notifications
Each agent is relatively simple on its own. The intelligence is in the orchestration — how they pass data, how errors cascade, and where human checkpoints sit.
What surprised us
The quality bar was higher than expected. The narrative agent's commentary was consistently better than what we'd been writing manually. Not because it was smarter — because it was consistent. It never forgot to mention a key metric. It never got lazy on slide 30. It applied the same analytical framework to every brand, every time.
Error handling was the real engineering work. Getting the happy path working took about 40% of the effort. The other 60% was handling malformed data, missing columns, edge cases in the chart layout, and the dozen ways a PowerPoint template can be subtly broken.
The hardest part was defining "done." When a human makes a slide deck, they just... know when it's finished. Teaching an agent pipeline what "finished and correct" looks like required us to be far more explicit about our quality criteria than we'd ever been. That turned out to be valuable in itself.
Automating a process forces you to understand it. We found three redundant steps we'd been doing for years simply because nobody had questioned the workflow.
The business case
The numbers are straightforward. The manual process took roughly 40 hours per month across the team. The pipeline runs in under 10 minutes. Even accounting for the development time and ongoing maintenance, we broke even in the second month.
But the real value isn't time savings. It's what the team does with those 40 hours now. They're doing actual analysis — investigating trends, building strategic recommendations, having conversations with brand managers that go beyond "here's what happened last month" into "here's what we should do about it."
Lessons for anyone starting this
- Start with a process you understand deeply. You can't automate what you can't specify
- Build agents that are narrow and testable. One agent, one job. If an agent is doing three things, it's three agents
- Put human checkpoints at trust boundaries. Our quality checker flags issues, but a human reviews the final deck before distribution. That's intentional
- Version everything. Templates change. Data formats change. Your agents need to handle yesterday's version and today's
This project convinced me that the future of operational work isn't AI replacing people — it's AI handling the mechanical parts so people can focus on the parts that actually require thinking. The 7-agent pipeline doesn't eliminate the need for smart analysts. It gives them permission to actually be analysts.