A Phased, Learn-as-You-Go Approach to Building Agents That Work the Way We Do
We approached this the same way we approach client campaigns: as a living system to iterate on, not a one-off project.
Across Q1 and Q2 2026, the team committed to weekly AI agent meetings, individual builds, and an internal philosophy that the goal isn’t to automate everything. The goal is to automate the parts of our work that should never have required a human in the first place.
This case study focuses on two of the agents that have made the biggest day-to-day difference. A daily app news agent built by Abbey, and a weekly Meta ads engine built by Rodrigo.
1. The Foundation: A Team-Wide Commitment to AI Fluency
Before writing a single agent, the team made a deliberate decision to treat AI fluency as a core skill, not a side project.
Weekly internal AI meetings became standing time on the calendar. Team members were encouraged to enrol in structured courses, including Anthropic’s Claude and AI Fluency certifications, and bring back what they learned to the rest of the team.
That commitment matters because it shaped everything that came after. The agents we built weren’t downloaded off a marketplace and configured to fit.
They were built by the same people who manage client accounts every day, which is why they actually solve the problems our team has, instead of the problems someone else thinks an agency should have.
2. Abbey’s Agent: A Daily Scan of the Mobile App Industry, Distilled
The first agent we want to highlight was built by Abbey, our Strategic Director.
Every morning, Abbey’s agent scrapes the web for what’s currently trending, important, and upcoming in the mobile app space. Algorithm updates from Apple and Google. Shifts in Meta and Google Ads policy. Breaking news from major app brands. ASO trends. New tools and platforms worth a closer look.
The output is a daily digest the team can read in minutes. What used to require an hour of scattered scrolling each morning, across blogs, newsletters, X, LinkedIn posts, and industry publications, is now consolidated into a single feed by the time the team logs on.
Three things make this agent useful in practice, not just in theory:
- It’s curated, not exhaustive. The agent prioritises items that are relevant to the kinds of work our team actually does, like paid acquisition, ASO, attribution, and creative trends. It doesn’t dump every mention of “mobile app” into our laps.
- It’s a starting point for client conversations. When Apple or Google ships something that affects how an app is marketed, our team is already aware of it before the client asks. That’s a small thing that compounds quickly.
- It runs every day without anyone managing it. Once the agent was tuned, the team got their mornings back.
See how we did it! Check out the results on our blog.
3. Rodrigo’s Agents: Closing the Gap Between Insight and Action
Rodrigo, our Marketing Specialist, has been focused on a different problem. The gap between knowing what to do and actually getting it into the workflow.
He has built two connected agents that we now treat as a single system.
The first is a weekly Meta ads trends and recommendations report. It pulls campaign-level performance signals across our Meta accounts and surfaces the patterns worth acting on. What’s slipping. What’s working. Where the next creative refresh should focus. It runs on a weekly cadence, in time for the team’s Meta optimization cycle.
The second is an automated ClickUp task creator. When the report (or the team) identifies a content idea, creative refresh, or follow-up, the agent creates a structured ClickUp task automatically. Categorised by format. Assigned to the right team member. Pre-populated with the source link and any context notes the team adds.
The connection between the two is the point. Insight without execution is just a report. By wiring the agent’s output directly into the system the team uses to manage their day, Rodrigo’s setup ensures that nothing falls through the cracks. The time the team would have spent translating findings into tasks gets redirected to actually doing the work.
4. The Operating Principle: Learn Day-by-Day, Improve Continuously
The most important part of how we build these isn’t the tools or the integrations. It’s the cadence.
Every week, the team reviews what each agent surfaced, what it missed, what it got wrong, and what should be added next. An agent that worked well in March is not the same agent that’s running in May. The prompts, the sources, the categorisation rules, the downstream actions all evolve as the team’s understanding of the work evolves.
This is the same iterative discipline we apply to client campaigns. Set a strong foundation, watch the data, refine relentlessly, never assume the first version is the final one.