The artefact on my desk is a composite first-30-days Google Ads launch schedule, drawn from the week-by-week plan that appears in agency onboarding decks and public guides. This week-by-week version is the copy I worked from. I chose it because readers keep sending me plans like it with the same question: Is this normal? Yes. It bills you for a calendar instead of decisions.

The work that can decide the first month should happen early: verify conversion tracking before spend goes live, apply day-one negatives, inspect search terms as the campaign explores, and make sure the landing page fits the query. This schedule spreads those jobs across weeks and calls the gaps “learning” or “monitoring.” Say you spend $20k a month. A quiet fortnight is not neutral when the auction keeps spending.

Here is the plan as a client might receive it:

Week 1: Account audit and setup
Weeks 2–3: Campaign build and launch. Learning phase: no changes.
Weekly: Check-in call and performance report.
Week 4: Performance review and optimisation.

I’ll take each line in the order it appears, then look at the line it leaves out. Two instincts in this plan are worth keeping. The timing is not.

Line 1: “Week 1: account audit and setup”

This is the least offensive line, though “week” makes the work sound larger than it is. A useful audit checks whether conversion actions fire, whether campaign structure serves the business goal, and whether match types, negatives, geo settings, schedules and exclusions make sense. It also checks landing pages against the queries being bought, budget pacing and change history. The ten areas an audit should cover are a working day for someone experienced, perhaps two for an old, messy account. The rest of week one is often access and approvals.

That delay is real. The onboarding checklist behind this kind of schedule says onboarding “typically takes 2 to 4 weeks before campaigns go live,” notes a 10-to-14-day window elsewhere, and names approval latency as a common cause of delay. A client taking time to approve access is a scheduling dependency, not a week of account management. Put a buffer in the plan. Just label it honestly.

More important is what “setup” actually delivers. An audit of 100 agency-managed accounts identifies conversion setup as a recurring failure. That is why I want the conversion action checked before anyone congratulates themselves on the keyword list. Installed in a tag manager is not the same as verified through a real test submission and confirmed in the account. If week one ends without that check, the rest of the schedule rests on a signal nobody has tested.

Verdict: Keep the access buffer and the audit. Make verified conversion tracking a deliverable, not an implied part of “setup.”

Line 2: “Weeks 2–3: learning phase, no changes”

This is the expensive line. It treats two different things as one: Google’s bid-learning process and an agency’s chosen review cadence. The first is real. The second is a staffing decision. Calling both “learning” gives a two-week pause the sound of a platform requirement.

groas-image://generated/46ad64c2-3c22-4c26-98b1-bd6f13fb51b0

Google’s documentation on learning-period duration distinguishes the visible Smart Bidding “Learning” status from the longer time a strategy may need to settle, depending on conversion volume and conversion-cycle length. Its Demand Gen calibration guidance discusses roughly 50 conversion events or three conversion cycles and asks advertisers to aim for those conversions within two weeks. Those are reasons to watch the conversion signal and avoid impatient conclusions. They are not instructions to ignore search terms until a date on a project plan.

What deserves a quiet period, and what does not

Google’s performance guide identifies changing a live campaign’s conversion goal as a particularly disruptive change to learning. Repeated bid and structural changes can also make it harder to read what is happening. Protecting the model from unnecessary churn is sensible.

But “no changes” also forbids the basic housekeeping a launch needs. A negative keyword does not replace the conversion goal. Reviewing the search terms report does not require rebuilding campaign structure. In an r/PPC discussion of early account handling, one commenter argues for leaving the account alone on day two; a reply argues for checking search terms daily and building the negative list. The useful distinction sits between them: leave the bidding strategy room to gather signal; do not leave irrelevant queries room to spend.

New broad- and phrase-match campaigns can surface searches you would never have chosen to buy. One advertiser described spending $12k over three months for two leads while the agency defended the period as “learning.” The thread’s practical suggestions include negatives such as “jobs,” “employment,” “supplies,” “wholesale” and “how to.” Whether each belongs in your account depends on what you sell. The point is that obvious non-buyers should be excluded before launch, then the live search terms should be checked as they arrive. A quarter of neglect does not become a learning strategy because somebody put it on a slide.

Miniature desk diorama: three weeks torn from a calendar beside an idle figure and unread search-term reports.

Verdict: Keep the restraint around major bid and goal changes. Delete the blanket freeze.

Line 3: “Weekly check-in call and performance report”

A weekly call can be useful. A weekly look at launch search terms is too slow. Search-terms guidance recommends sorting the report by cost and notes that the first weeks are when exploration can produce the worst waste. My question for each costly query is simple: Would I pay for that search again tomorrow? During the first week, I want an answer tomorrow, not at the next Monday meeting.

A practitioner’s launch routine shared in r/PPC makes the same practical distinction: review search terms and add negatives daily in the early weeks, keep Display and Search Partners off until core search is profitable, and match landing pages to query intent. None of that requires a daily client meeting. It requires someone to do the work between meetings.

A thin first-week report also needs diagnosis, not a ceremonial explanation that “the algorithm is thinking.” Check whether the campaign is underspending, approvals are pending, settings restrict reach or an exclusion is catching the audience you meant to reach. A reporting cadence is not an optimisation cadence. The client can hear from you weekly while the account gets attention daily.

Verdict: Keep the weekly conversation if it helps. Do not make it the first time anyone inspects live spend.

Line 4: “Week 4: performance review and optimisation”

This line promises a payoff for three weeks of patience. Some conclusions genuinely need time: Smart Bidding needs conversion signal, and creative patterns take more than a handful of impressions to judge. But a week-four meeting is far too late to begin finding irrelevant searches or a landing page that does not answer the query in the ad.

Say the account spends $20k a month. If a fifth of three weeks’ spend goes to searches that were never likely to convert, that is a four-figure problem before the review arrives. The exact fraction will differ by account; the mechanism will not. Unpruned queries keep entering auctions while the calendar advances toward its first formal “optimisation” slot.

The week-four work listed on these plans is usually familiar: add negatives, adjust bids, refresh some copy. The negatives could have been handled as search terms appeared. Bid decisions may reasonably wait for more signal, but that does not justify waiting on everything else. groas’s CPOS account reports conversions up 135% and CPA down 48% within its first seven days; its Esmove account reports 28 conversions in its first four. Those results do not promise every launch the same pace. They do show why a plan should allow decisions before day 28.

Verdict: Keep the week-four review as a checkpoint. Stop treating it as the opening bell for optimisation.

Line 5 is missing: verify the conversion before spending

The schedule says “setup,” then moves on. It never explicitly promises that a real lead or purchase will trigger the intended conversion action before the campaign spends. That omission matters more than the spacing of the meetings.

If the action fails to fire, fires on the wrong event or double-counts, the campaign’s performance readout is wrong at the source. The bidding system may then optimise toward the wrong signal while the week-four report presents numbers that look tidy. This is why the conversion-setup problem in the agency-account audit belongs at the front of the plan, not in a troubleshooting appendix.

The test is plain work. Submit a real test lead or purchase, check the event and its trigger, then confirm the intended action is recorded in Google Ads once reporting and the attribution window allow it. Check that enhanced conversions and GA4 refer to the intended action rather than a convenient proxy. Do this before live spend. A weekly report cannot repair a month of decisions made from a broken conversion signal.

Verdict: Add this line ahead of launch. It is the prerequisite the other four lines assume.

What the schedule gets right

Access and approvals can delay a launch. The onboarding checklist says as much, and pretending every client will reply immediately helps nobody. I would keep the week-one buffer, clearly marked as a dependency. I would not present days spent waiting for a reply as days spent managing an account.

I would also keep the caution behind “no changes,” directed at the right objects. Google’s performance guidance warns against excessive modifications while a campaign builds its model, particularly changes to the conversion goal. That is a reason to resist restless bid tinkering. It is not a reason to buy the same irrelevant search again tomorrow.

Finally, a week-four review is worth having. By then you can discuss what the early decisions and accumulated conversion data show. The problem is not that the plan has a fourth-week review; it is that too much of the work waits for it.

Checklist: what a launch plan should promise by day 14

If an agency hands you a launch schedule, ask for dated decisions rather than phase names. This is the short version I would want attached to the plan. The bold items are especially easy to leave implicit.

Before launch or by day 3

  1. Verify conversion tracking: Test a real lead or purchase and confirm the intended action records correctly; a firing tag alone is not proof.
  2. Apply day-one negatives: Exclude clearly irrelevant job, supplier, wholesale or how-to queries where they do not fit the offer.
  3. Match each landing page to query intent: Do not send every ad to the homepage simply because it is convenient.
  4. Confirm geo, schedule and audience settings: Check exclusions and keep Display and Search Partners off until core search is profitable.

By day 7

  1. Review search terms daily: Sort by cost, ask whether you would buy each search again and negate the clear misses.
  2. Make the first wasted-spend cut: Investigate ad groups spending without conversions; pause clear losers rather than waiting for the week-four meeting.
  3. Protect the bid model: Avoid unnecessary goal, bid and structural changes while conversion signal accumulates.

By day 14

  1. Check conversion volume and cycle length: Judge progress against the bidding strategy’s needs; do not mistake a date for enough data.
  2. Read performance against the agreed target: Compare CPA or ROAS with the kickoff baseline, not “things are trending up.”
  3. Start landing-page and ad-copy iteration: Use the queries and early results to decide what needs changing before week four.

The item most often left implicit is number 1: verified conversion tracking. Skip it and the cost is not just a bad first report. You risk building the next round of bidding and optimisation on a signal you never checked.

groas-image://a07b25f9

The verdict: keep the buffer, move the work

I would keep the access-and-approval buffer, the caution around disruptive bid changes and the week-four checkpoint. I would cut “learning phase” as a blanket excuse for inaction, replace weekly-only launch inspection with daily search-term work, and put verified conversion tracking before live spend.

This schedule survives because it fits a familiar agency operating model. A senior person covering many accounts can hold weekly reviews more easily than they can inspect every new account each day. So the plan describes the review calendar, then uses platform language to make the gaps sound necessary. A calendar can tell you when someone intends to look. It cannot tell you what they decided.

That is the model groas’s Search Ads service is built to replace: around-the-clock work on bids, keywords, budgets and negative lists for a flat monthly fee, with a named account manager setting guardrails. It offers a live trial, no setup fee and logged actions with the reasoning behind them. Those logs make a better answer to “What happened on day four?” than “We were in a learning phase.”

My overall verdict on the artefact is simple. Keep its honest scheduling buffer and its respect for a model that needs time to learn. Move tracking verification, negatives, search-term pruning and landing-page checks into the first days. A launch plan should be busiest when the account knows least, then get quieter as the evidence improves. Not the other way around.