Master Agency Projects with Intuitive Management Tools

The first 30 days of any engagement are about diagnosis, not delivery. Before any creative goes live or any spend is reallocated, we read the existing tracking, the historical performance, the campaign archive and — most importantly — the working assumptions that the in-house team has accumulated over the previous twelve months. A surprising amount of paid spend gets allocated against beliefs that were once true and quietly stopped being true. Naming those beliefs out loud is usually the most valuable single output of the diagnosis phase.

From there, we agree a written baseline on the metrics that actually move the business. Reporting against vanity metrics — total impressions, gross reach, post likes — is easy to produce and easy to ignore, and reporting against business metrics is harder to produce and impossible to ignore. We always pick the harder one. Each weekly note covers what shipped, what is being tested, what was killed, and what needs a decision from your side this week. Each monthly review compares the working metrics against the agreed baseline and proposes the next month's plan in a single working document, not a deck.

What we need from your team is small but non-negotiable: a single decision-maker available for a 20-minute weekly slot, prompt access to the analytics and ad accounts, and honest answers to direct questions during the diagnosis phase. Engagements that stall almost always stall on access, never on creative.

A working sprint is built around a single testable hypothesis and a single decision at the end. We open with a short written brief that names the hypothesis, the audience, the channels in scope, the budget envelope, and the criteria we will use to judge the result. Everyone on the engagement signs off on that brief before any production work starts, because the most expensive sprints are the ones where the criteria for success are only agreed in retrospect.

Production runs in weekly increments. Mid-sprint we share the assets, the tracking setup, and any unexpected friction with your team in writing — not in a meeting — so the working record is clear and the team can react asynchronously. Live testing happens in the second half of the sprint, with a defined window long enough to read signal but short enough that we are not just waiting for permission to make a decision.

At the end of the sprint we run a short review: what continues, what is killed, and what is iterated for the next sprint. The review is written before the meeting and circulated in advance, so the meeting itself can be 25 minutes of decisions instead of 60 minutes of reading. The output of every sprint is a one-page retro that lives alongside the working playbook for future reference.