Hi {{ first_name | there }},

Recently, I’ve been heads down in Claude Code. I wanted to share a practical workflow you could implement in your business today.

Let’s dive in!

Today, in 10 minutes or less, you’ll learn:

SPONSORED

Ready to grow your portfolio career with like-minded peers?

If you have 5+ years of working experience, join our invite-only community.

🚀 Why join the community: Accelerate your learning, grow your revenue, and build genuine relationships with an exclusive group of portfolio professionals

🎯 What you get:

Apply now - we'll notify accepted applicants within the next couple weeks:

To get your brand in front of 7k+ professionals, founders, and consultants, fill this out and let's chat.

You’ve gotten your first clients. You’re finally scaling up.

But now you’re drowning in service delivery. Overwhelmed.

You absolutely don’t have time for customer research, when you barely had time to do your own laundry yesterday.

However, you just know your 14 recent client calls must contain nuggets of insight that can help level up your service quality or grow your business faster.

So how do you unlock these insights without overburdening yourself?

Previously, I showed you how to use AI prompts for customer research.

An obvious solution: Dumping your client meeting notes into a Claude Project, then running an effective prompt over them. I still do this a lot. It’s fantastic.

But sometimes it’s not enough.

In these cases, I bring out the heavy artillery - Claude Code.

While it looks intimidating at first, I’ve found it extremely powerful even as a non-technical person.

Today, I’m going to show you how I leverage Claude Code to accelerate my client research workflow in 15 minutes.

I still use Claude Projects a lot, but have run into several pains:

Not to mention - that feeling of horror when I see my Claude Desktop app freezing yet again.

Claude Code emerged onto the scene this spring.

At first I was skeptical. But then I tried it after hearing so much hoopla about it - and was blown away. Using it was the first time I felt a visceral “agentic AI” moment.

Now I’m leveraging the tool not only for coding, but also business workflows.

Hopefully this client research walkthrough can show you how Claude Code can help you too.

First things first. To get Claude Code running, I whipped up the ol’ Terminal:

Next, I downloaded Claude Code by entering this command into terminal (Anthropic’s full instructions). Here it is for Mac:

And for Windows:

Then, I created a “customer_research” folder in my Finder and navigated to it using the command “cd customer_research” (quick instructions).

Once I was there, I typed “claude” in the terminal to open Claude Code:

Boom. You’re in.

Now for the exciting part - building your own analyst.

Now that we’re in Claude Code, I’m going to show you how I setup my research analyst.

I created a sub-folder meeting_notes and uploaded all my meeting notes, transcripts, and documents as markdown files.

Afterward, to avoid having to copy-paste prompts, I created a Claude Slash Command. To do this, I created two prompt files in the folder .claude/commands:

This basically saved my prompts as markdown files in a folder, which is pretty convenient. No more losing track!

Next, I prompted Claude Code to run the topic analysis and save the output in a markdown file called topic_analysis_output.md

Then, I fed this output into the insight generation prompt to created the final synthesized insights.

Voila! I got a research summary of client insights, supporting quotes, actionable recommendations grouped by the topic.

The actual research output was a great starting point:

I’ve been impressed by how Claude Code manages context more smoothly than Claude Projects, producing higher-quality outputs IMO.

In particular, these insights helped me answer questions like:

Separately, I’ve also built a web dashboard to visualize this data with charts and a structured UI. (Not covering this today, but so much easier to create than before with Claude Code.)

From here onwards, I can see tons of possibilities.

I can use this research output to do things like:

All within Claude Code. And that’s just the tip of the iceberg.

So would I recommend Claude Code?

It might seem intimidating as a non-dev, but I’d recommend trying it out if you’re feeling inspired and not afraid to get your hands dirty.

And if you do, building your own customer research analyst could be the perfect weekend project. Let me know how it goes.

🤯 Shorting the AI jobs apocalypse (David Deming)

🧠 On the Reverse Flynn Effect (Cal Newport)

💵 How to Keep This Hot Stock Market From Melting Your Retirement Dreams (WSJ)