Week one of a dedicated marketing team rarely ships a campaign, and it should not. It should ship a written plan you can hold the team to, and the first weekly review in the format you will read from then on. Below: the week-one checklist we work to, who owns each item, and what the first review contains.
Why week one produces a plan, not a campaign
Work started before the team has access and context tends to be redone. A campaign built without knowing what was tried last year, or an article written before anyone read the brand guidelines, looks like progress in week one and becomes rework in week four.
The faster route is a short, defined stretch of groundwork with a fixed output. Not open-ended discovery, and not a rushed first post to show momentum: a written plan on a named day, built from what the week found.
The week-one checklist we work to
Our delivery standard asks the coordinator and the service lead to confirm a set of items in the engagement record before work starts. In week one, those items are the work. The table lists them in the order we chase them, with the owner on each side.
| Item | What is confirmed | Owner on our side | Owner on yours |
|---|---|---|---|
| Named contacts | Primary contact and coordinator, specialist lead, escalation contact. One person may hold several roles | Coordinator | Decision-maker |
| Access | Analytics, ad accounts, Search Console, CMS, CRM where in scope, each tested working, not just granted | Specialist lead | Whoever administers each account |
| Deliverables and exclusions | What is in scope, what is not, and the acceptance check for each deliverable | Coordinator | Decision-maker |
| What already exists | Past campaigns and their results, content and its traffic, strategy documents, anything tried and dropped | Specialist lead | Whoever ran marketing before |
| How decisions get made | Who approves what, how long approvals take, any legal or brand review step | Coordinator | Decision-maker |
| Measurement | How success will be judged, including any baseline that does not exist yet and any figure that cannot be trusted | Specialist lead | Sales or finance owner of the numbers |
| Cadence | The weekly review slot, the update route and the escalation path | Coordinator | Decision-maker |
Access comes first because a missing permission found on day twelve is an avoidable delay. The “what already exists” row comes early because the plan should not repeat a failed test or drop something that was working.
- 01Named contactsCoordinator, specialist lead, escalation
- 02AccessEach account tested working, not just granted
- 03ScopeDeliverables, exclusions, acceptance checks
- 04What existsPast campaigns, content, anything dropped
- 05DecisionsWho approves what, and how long it takes
- 06MeasurementBaselines, and figures that cannot be trusted
- 07CadenceWeekly review slot, updates, escalation
- End of week oneA written plan and the first reviewSpecific enough to be wrong, on a named day
What lands in Prism by the end of the week
Where the engagement includes it, the plan and the first review live in Prism, the workspace you log into from kickoff. The plan names the first deliverables, their owners and their ship dates. The review is the format you will read every week:
- One row per channel: what it cost, fully loaded where you have shared the cost, and what it produced, counted in leads your sales team accepted.
- The state of each figure: measured, partial or unknown. Unmeasured spend shows as unknown, never as zero.
- A verdict per channel, recorded with what we expect to happen and the date we will check.
- Under the rows: decisions taken, tasks that moved, and caveats that need a decision from you.
In week one most rows will say partial or unknown, and that is the point. Our dashboard shows the last 90 days against the period before, so the first review also tells you which numbers you can plan on and which need fixing before anyone argues about them.
How to tell week one went well
Not by whether it felt busy. Check the plan for two things:
- It is specific enough to be wrong. “Focus on SEO and content” cannot fail. “Rebuild the category structure first, ship by a named date, because two near-duplicate pages are splitting one query” can be judged.
- It contains something the brief did not. An approval step nobody mentioned, a campaign that quietly failed, a stakeholder whose priorities differ. If week one only confirmed what everyone assumed, the questions were too polite.
If neither is true by the end of the week, say so in the first review. We recommend raising it there rather than waiting, because a vague plan compounds every week it runs.
When a full week of groundwork is the wrong answer
Some starts should be faster, and we say so before the engagement begins:
- Something is broken now. Tracking that has stopped recording, or a paid campaign spending on the wrong pages, gets fixed in the first days; the plan is written around the fix.
- The work is a small fixed scope. A one-off project with an agreed brief needs a kickoff, not a week of discovery. When a retainer is the wrong answer covers that choice.
- You already hold the groundwork. If access, history and decision rights are documented and current, the checklist takes a day, not five.
One more case: a single specialist starting on the 14-Day Risk-Free Trial. The week-one plan is what the trial is judged against.
For eligible managed specialists. Up to 14 calendar days or 80 logged working hours, whichever comes first. End within the trial and pay nothing for eligible trial hours. Continue beyond it and those hours are billed at the agreed rate. Unpaid trial work remains ours if you stop.
Written by
Parvessh Agarwal
Founder and Chief Executive, Vinove
Parvessh founded Vinove in 2004 with one idea: build focused technology companies that earn their place in real markets. His focus is on the long game, on companies that survive and serve real customers long after launch.
LinkedIn →
