Claude Cowork · · 4 minute read

Claude Cowork Workshop Singapore: What You Actually Build in One Day

When people ask me what happens in a Claude Cowork workshop, I always give the same answer.

Soh Wan Wei speaking into a microphone during a Claude Cowork workshop

When people ask me what happens in a Claude Cowork workshop, I always give the same answer.

"You build something."

Not a concept. Not a mock-up. Not a practice exercise using someone else's made-up scenario.

You build a working Claude Cowork system around your actual recurring work task. And by the end of the day, it is running.

Let me walk you through exactly what that looks like.


Before the workshop

You do not need to prepare much. But you do need to come with one thing in mind.

A task you repeat every week.

It could be a report. A screening process. A research brief. A proposal structure. A client summary. A status update. Any task that:

  • Has a similar structure each time
  • Involves documents, information, or decisions
  • Takes time you would rather not keep spending

That task is your starting point. Everything else follows from there.


The morning: mapping your workflow

The first half of the workshop is about clarity.

Before you can build a working AI system, you need to understand your task well enough to explain it clearly. Not to code it. Just to describe it.

We ask questions like:

What is the first step? What information do you start with? What decisions do you make along the way? What does a good output look like? What do you always check before you sign off?

For most people, this is the most useful part of the workshop — even before any AI gets involved. Because mapping your work makes the inefficiencies obvious. You start to see where the real time is going.

Once the map is clear, we can start building.


The afternoon: building your Claude Cowork workflow

This is where it gets real.

We set up Claude Cowork around your workflow. We configure it with your context, your process, and your standards. We test it on actual inputs from your work.

Does it understand the task correctly? Does it follow your process? Does it produce the right kind of output?

We adjust. We refine. We test again.

By the end of the afternoon, most participants have a working Claude Cowork system that they have tested on real work.

Not a demo. A working system.


What participants have built in past workshops

These are real examples from real sessions.

A global mobility consultant built a daily briefing workflow. She reads updates from multiple sources every morning and synthesises them into a structured brief for her team. Before Claude Cowork, this took 45 minutes. After the workshop, it takes under 5.

An HR manager built a candidate screening workflow. She feeds in a set of CVs and her criteria. Claude Cowork produces a structured comparison and a draft recommendation. She still makes the final call — but the prep work is done.

A management consultant built a research synthesis tool. Before any client meeting, she uses it to compile and structure information from multiple documents into a readable briefing. Three to four hours of prep work is now a 20-minute task.

A marketing manager built a content brief workflow. She inputs a campaign goal and a few reference documents. The workflow produces a structured content brief in her team's standard format. Her writers now spend less time asking clarifying questions.

None of these people were technical. None of them wrote code. They just knew their work well — and that was enough.


The end of the day

At the end of every workshop, we go around the room.

Each person shares what they built, what problem it solves, and one thing they want to build next.

That last part — "one thing you want to build next" — is usually the most energising moment of the day.

Because once you have built one Claude Cowork workflow, you start seeing workflows everywhere. Every recurring task looks different. Every process you repeat looks like it could be better.

That shift in thinking is what I am most proud of.


Is one day enough to learn this?

Let me be honest.

One workshop will not teach you everything. AI tools are changing every few weeks. A one-day session is not going to cover everything Claude Cowork can do, and it is not going to turn you into an expert.

But it will give you one working system. And the confidence to build the next one.

That is the starting point. That is all you need.

For ongoing learning, participants can join the AI Native Circle — a monthly community where we share updates, troubleshoot workflows, and keep building together.


When is the next workshop?

Claude Cowork workshops run regularly in Singapore.

For private team workshops, see how ANCHR AI Labs trains. For open sessions and free resources, visit Cowork SG. For monthly follow-up and peer learning, explore the AI Native Circle programmes.


Wan Wei is the founder of ANCHR AI Labs and co-founder of Women in Claude. She trains non-technical professionals and corporate teams in Singapore and Malaysia to build practical AI workflows with Claude Cowork.

with careSoh Wan Wei