Onboard a new client in the first 30 days

This page shows how I take a new client from a signed agreement to a working engagement in 30 days: access to every account without handling a password, a kickoff call that ends in writing, a baseline recorded before anything changes, and something visible shipped by day 14. Agencies can copy it. Owners about to hire one can hold them to it.

The rule under everything: the client owns every account

Every account the business pays for or builds history in belongs to the business: analytics, Tag Manager, ad accounts, the Meta business portfolio, the Business Profile, the domain, hosting, the CRM, and email and SMS tools. The business is the owner and pays the bills. I work through my own access, granted by invite and removable at any time.

When an agency owns the accounts, a business that parts ways with it can lose control of its ad history, its analytics data, its reviews, and sometimes its own domain. Client ownership protects the agency too. If you never hold a password, you are never the suspect when something changes, and ending the engagement means removing a user.

Before you begin

• A written agreement covering scope, price, start date, and how either side ends it. At minimum, an email stating the terms and a reply confirming them. See discovery and proposals.
• The first invoice paid, or payment terms agreed in writing. See billing.
• One agency identity per platform, reused for every client: a Google account on your business email with two-step verification, a Google Ads manager account, and a Meta business portfolio.
• A password manager that can share a single item, for the rare login that cannot be delegated.
• A short intake form, a project folder for the client, and an empty access log.

The 30-day plan at a glance

The client sees a welcome email, one short form, a good call, and finished work inside two weeks. Behind that is a fixed schedule, and everything they hand over turns into something they get back.

Day 0: Send one welcome email

1. Set up your side first

   The same day the agreement comes back, create the project and access log, and move the client from your pipeline to your client list so your records are true.

2. Give them three things to do, in order

   The intake form (what they sell, how customers find them, every tool they use, who handles leads, their goals, and brand assets), an access guide listing only the accounts their scope needs, and a link to book the kickoff. Anything they get stuck on gets finished together on the call.

3. Attach a roadmap with real dates

   The next 30 days, what you need from them, and what each item becomes. The dates are promises. If one will slip, the client hears it from you before it passes.

4. Put the communication cadence in writing

   Tell them how and when they will hear from you, before they have a reason to wonder.

Only promise what you already have a routine to deliver. A promise with nothing behind it is a future apology. See the monthly report guide for the report itself.

Days 0 to 3: Get access without collecting passwords

Use delegated access by default: the client invites your agency identity inside their own account, you never see a password, and they can remove you in one click. For the rare system with no invite option, use a shared password manager item. Passwords never travel by email, text, chat, or screenshot. Request only what the scope uses; unused access is still risk you carry.

Keep an access log

Record every grant the day it lands: system, level, method, date, and a note. For a password manager item, record the item name, never the password. The log proves you never held credentials and becomes your revoke list when the engagement ends.

System                   Level          Method            Granted     Note
Google Business Profile  Manager        Invite            2026-09-15  Business is primary owner
Google Ads               Manager link   Link request      2026-09-15  Billing on client's card
Booking tool             Shared item    Password manager  2026-09-17  Item: "Booking tool (client)"

Days 3 to 7: Run the kickoff call

Beforehand, read the intake form, pick the three or four answers worth digging into, and check which grants have landed.

Before the end of that business day, send a recap: access still pending, the 30-day deliverables and dates, the headline number, and the next check-in. Every call ends in writing, because memory is not a system.

As access lands: capture a baseline before changing anything

Before changing a single setting, record how everything stands. The baseline makes every improvement provable and protects you when someone later says a thing used to work.

• The Business Profile is saved as it stands: info, review count and rating, photos, and last post date.
• The homepage and key pages are saved as full-page screenshots.
• The last 90 days of Analytics and Search Console are exported: traffic, sources, key events, clicks, and top queries.
• Every tag is mapped: which container loads, which measurement ID it sends to, and which property owns that ID.
• Every phone number and form on the site is listed, with where each form actually sends.
• Ad campaigns, social profiles, and the CRM's pipeline and automations are recorded, where they exist.
• Current lead volume and source mix are written down from whatever the client can show you.

Day 14: Ship the first quick win

The first visible deliverable is the most important date of the month. It is the client's proof that hiring you was right, so protect it above everything else.

1. Pick it at kickoff

   Something the client can see working, not a plan: a Business Profile cleaned up with new posts live, a homepage fix, every lead landing in one inbox, or tracking confirmed end to end. Visible beats perfect.

2. Check it against the access log

   The quick win cannot depend on an account that is still locked.

3. Show the before and after

   Send a short note with the baseline screenshot beside the change. Work the client never sees is worth nothing to them.

Day 30: Review the month and write down what was set up

Review what got done, what the early data shows, and whether the plan still fits. Book the monthly check-in, move the client into your normal operating rhythm, and write the setup record where the client can reach it:

An ID map that lives only inside the platforms is how data ends up in the wrong place. The same record is your checklist when the engagement ends; see offboarding and data handover.

Verify it works

• The price and scope were in writing before delivery work started.
• Every account is owned by the business, and your access is a named user or partner link.
• No password was sent by email, text, or chat, and the access log shows how each grant was made.
• The baseline was saved before the first change.
• Something the client can see shipped by day 14.
• The setup record matches what is actually configured.

Troubleshooting