How to connect client onboarding to strategy and reporting

From client onboarding to strategy and reporting: one connected workflow through Claude

A social media agency founder came to me looking for ways to automate parts of her business with Claude.

As I started asking how work moved through the business, I noticed something sitting just outside the original scope: the client onboarding process.

It worked. Sort of. There was a Google document with questions, then a trail of emails and separate links for the files, brand assets and other information the agency needed. Everyone could get there in the end, but it took a fair bit of passing things back and forth. Which tends to be the case a lot of the times. We think it’s easier if we just ping an email and ask for what we need.

But onboarding is one of the first experiences a new client has with your business.

Where was client onboarding getting tangled?

The questions lived in one place. The materials a client needed to share were uploaded elsewhere. The next steps were carried by emails and manual follow-up.

For the founder, that meant keeping track of what had arrived, what was still missing and where each piece of information had ended up. For the client, it meant figuring out which link to open and where to send each thing.
Then there is that awkward moment of trying to figure out where we put the thing in the first place. Which ultimately wastes our time and leads to small daily frustrations (I know I’ve done that to myself!).

I’ve seen plenty of small businesses with client onboarding held together this way. It’s easy to let it grow by accretion: one document, one more email, one extra folder. Suddenly a simple welcome takes a surprising amount of attention. I also think the welcome matters. It’s an early chance to show a client how the business works and what it feels like to work together.

Why use Google Workspace?

My first thought was to build the client-facing piece as a Claude Artifact, since we were already using Claude for other work with the team. But onboarding could involve client files and business information, and an Artifact would give us a public shared link. I didn’t want that to be the way this client information was handled, so I looked at the tools the agency already used.

The business ran mostly on Google Workspace. That made it a sensible place to build from, rather than asking the team to add another tool to the pile.

I used Google Apps Script to build the portal, with Claude Code helping me work through the build. The choice came from the way the business was already set up; the tool came second. It also let me connect onboarding with two recurring workflows the agency needed: social media strategy and reporting. The idea was to collect the source information once, then use it as a starting point for the related work.

What went into the portal?

Before building anything, I sent the founder a questionnaire about what happened from the moment a client said yes to the moment work began.

That gave me a clearer picture of the steps, the information to collect and what the client needed to experience along the way. Then I used those answers to plan the portal.

The client-facing page included the agency’s logo and onboarding questions. It also gave clients space to add files and links, and save their answers so they could come back and update them later.

While shaping the client onboarding questions, I looked at whether the information collected there could also support the social media strategy and reporting work that followed. The team had been gathering some of the same background again later. Some clients needed monthly reports; strategy work was also part of the service.

The portal also sets up the Google Drive folders the agency uses for strategy and reporting. That gives client information and client-facing documents a planned home, while onboarding answers can flow into the next steps.

Once the answers are in the client’s Google Drive folder, Claude pulls the relevant information, along with social media links and account handles, into Strategy Workbench. It is an interactive guide that takes the team through a strategy assessment. The team can start with information already gathered instead of searching for files or copying answers between sheets. A pre-built Claude workflow handles that hand-off; a similar workflow supports reporting. Passwords and logins are never collected or passed into these workflows.

The founder sends the same starting link to every new client. Their submission creates a client-specific portal link and folders for strategy and reporting, ready on the agency’s side. That gives each client a separate place for their onboarding information. The link is unique, but it is not a password-protected login by itself; access to files still depends on the relevant Google Drive permissions.

What changed for the agency?

The client onboarding process now gives clients one place to answer questions, add files and links, and return to update their responses. On the agency’s side, the same information can feed into strategy and reporting rather than being found and entered again by hand.

These workflows give the team a shared starting point for recurring work. The strategy assessment guides what to cover, while reporting follows a consistent structure and language. Presentations can use the same design standards. That gives each team member a clearer idea of what belongs in each deliverable and reduces the need to begin from a blank page.

I haven’t measured the hours saved, so I won’t put a number on it. The practical change is that client information is gathered once, then reused through more of the work; the team has fewer details to chase, locate or copy between documents.

What can connected automation make easier?

An improvement to client onboarding can help with more than the first welcome when the information gathered there has a clear next use. In this project, answers collected at the start can feed into strategy and reporting work, giving the team a shared starting point for ongoing client work.

When you spot a repetitive task, look at what happens before and after it. Is the same information being gathered twice, or moved manually from one place to another? Map that hand-off first; then see whether a tool you already use can take some of the carrying.

I began by looking for places to use Claude. The more useful question was how the onboarding information could support the strategy and reporting work that came after it.

If you’d like more thoughts on making a business easier to run, subscribe to my Substack.

And if client information is scattered across emails and folders, you can book a chat with me to talk through what process would help.

About the author
Jagoda Puczko is a business operations partner who helps growing founders close their laptop at 6pm. She has run operations for teams of more than 100 people at Apple and Little Dot Studios, directed award-winning films, and once had a headshot photography business with a very sophisticated pricing strategy.