Every agency has a "first 90 days" deck. Most of them are aspirational. They describe an idealised path where data is clean, stakeholders are aligned, access is granted on day one, and the work starts producing results in a fortnight.
Real engagements are messier. Below is what we typically see, week by week. The shape is reliable enough that we can predict what week 4 will look like before week 1 starts. The shape doesn't make the work easy — it makes it manageable.
Weeks 1–2: discovery and access
The single biggest determinant of how well the engagement runs over the next twelve weeks is what gets resolved in the first ten days. Specifically:
- Platform access (paid media accounts, CRM, analytics, CDP if any) requested and granted.
- The data-sharing agreement and PDPL compliance posture nailed down.
- The five questions from our brief framework answered concretely.
- The decision-making structure on the client side mapped — who decides on creative, budget shifts, and strategic pivots, and how fast.
The thing nobody warns clients about: in many engagements, at least one of the four lines above stalls in the first two weeks. Usually access. The platform admin is on leave, the IT team requires a security review that wasn't scoped, the parent company has a global account governance rule that nobody surfaced. We plan for this — the Day-30 milestone is set assuming an access delay.
VIMS01 produces a discovery deck at the end of week 2: a baseline diagnostic of where the brand currently is, with an emphasis on the gaps that will block agent activation if not fixed.
Weeks 3–4: instrumentation
This is the unglamorous, high-leverage work. The agents are only as good as the data they read. Most marketing data we inherit is broken in at least one of these ways:
- Conversion events are double-firing or under-firing depending on platform.
- The CDP (if there is one) has identity stitching gaps that hide part of the cross-device journey.
- UTM hygiene is inconsistent across channels — different naming conventions per platform, templates that drift, paid social campaigns that don't tag.
- The CRM-to-platform conversion API integration is half-built or stale.
VIMD01 reads the existing measurement layer and states every gap, so the fixes are clear before activation. We don't bolt on a new measurement layer; the work is to make the existing one reliable. By end of week 4, the data layer should be reliable enough that any future analysis or optimisation we run on it doesn't have to ask "is this real or is this a measurement artefact?"
This is the week where clients sometimes get nervous because the visible output is low. There's no creative running yet. There's no campaign restructure visible. The dashboard doesn't show wins. Progress is easy to miss during this phase, because the work being done is structural and the client can't see it yet.
Weeks 5–6: architecture and baseline
With clean data, VIMS01 produces the campaign architecture: how the channels, audiences, and creative streams will be organised over the next ninety days. For multi-property or multi-product clients this is the most consequential single deliverable of the engagement — the architecture decides what's possible.
In parallel, VIMD01 publishes the baseline: the honest pre-engagement performance numbers, each sourced and dated. This is the number against which everything that follows is measured. We sometimes get pushback on the baseline because it's lower than the platform-reported numbers the client was used to — that's almost always because the platform numbers were inflated by the issues fixed in weeks 3–4.
The architecture and baseline are locked at the end of week 6 and become the reference for everything that follows. This is a hard checkpoint. Agent activation is built on them.
Weeks 7–8: activation
VIMP01 and VIMC01 begin work. The campaigns under the new architecture launch. The creative pipeline produces its first archetype packs.
The first two weeks of activation often have a performance dip. The reasons are well-understood — audiences are being routed for the first time, and the creative pipeline is producing initial variants that haven't yet been pressure-tested. The plan sets this expectation up-front and states its stop rules in advance.
The work in this period is operational: monitoring and exception-flagging against the plan. The agents build and read the work against the plan, and any campaign built here that goes quiet or off pace is flagged on the next daily read, against the stop rules the plan states. Brand judgement and business context outside marketing come from the brief you give during discovery, so they shape the plan before activation.
Weeks 9–10: first optimisation cycle
By week 9, there's enough data on the new architecture to run the first proper optimisation cycle. VIMP01's performance analysis runs on the new structure. VIMC01's creative win-rate is identifying which archetypes deserve scaling and which to retire. VIMD01 publishes the first proper performance read, decomposed by audience cohort and channel.
The optimisations are not heroic moves. They're a series of small, evidence-backed decisions: shift 8% of spend from this audience to that one, retire these three creative archetypes, scale this one, expand into this previously-excluded geo segment. The compounding of small good decisions across a quarter is what produces the headline ROAS numbers most case studies report.
Weeks 11–12: first reporting cycle and forward plan
Week 12 ends with the formal Day-90 report, a single document with three sections:
- What happened. Performance against the baseline, decomposed by the metrics that matter (the four metrics covered in a previous piece).
- What we learned. Specific findings about the brand, the audience, the channels, and the creative archetypes that work. These compound into the next quarter's strategy.
- What's next. The 90-day plan for the following quarter, with explicit hypotheses and the metrics that will validate or kill them.
If the engagement is working, the report is detailed and forward-looking. If it isn't working, this is where the structural reasons surface and the report gets harder to read. We've had both. The latter reports are the ones that show whether the engagement is salvageable or should be unwound — and the report is as direct about that as it is about the wins.
What we don't do in the first 90 days
To set expectations correctly, here's what is not in scope for Day-1 to Day-90:
- A brand repositioning. If the brand needs repositioning, that's a separate workstream. The first 90 days operate within the existing positioning.
- A full creative refresh of all evergreen assets. We refresh the assets that move the metric. The full library refresh is a Day-90+ project.
- A platform consolidation. If the brand is on six tools and should be on three, that's a separate procurement and migration project. The agents work with the current stack.
- An organisational change on the client side. Reorganising the marketing team is outside the scope of the first 90 days.
The discipline of staying in scope for the first 90 days is what makes the next 90 days possible. The engagements that try to do everything at once are the ones that don't make it past the first quarter.
The version of this that is honest
The 90-day plan above is real. It is also imperfect. Engagements miss milestones. Some weeks the work is harder than the plan suggests. Some clients have business realities that compress or extend particular phases. We've had engagements where week 4's instrumentation work took eight weeks because the data layer was worse than initial discovery surfaced. We've had engagements where week 7's activation produced clean wins inside a fortnight because the brand was strong and the architecture was the one blocker.
The shape is the right reference. The dates flex with reality. What VIMDRIVE commits to is the shape, and a clear read on where you stand against it for ninety days, on a dashboard refreshed daily and in a Day-90 report that is candid about the result. After that, the cadence is whatever the engagement actually needs.