Claude workshop
Learn to take recurring work off your plate and build useful tools with Claude. You don’t need to be a developer.
Book a free 20-minute call
Turn business signals into a tool the team can review.
Imagine a service team sees the same customer issue each week. Claude brings the numbers and feedback together, sketches a better response and helps explore a small tool the team can keep using. This example is illustrative.
Does this pattern appear in the sample?
In a reviewable team draftThe draft pairs each possible pattern with its source rows and comments. It names the sample’s limits and marks gaps.
What the team decidesDo the sources support this interpretation, or does the team need more information?
What would help the team review it again?
In a reviewable team draftA rough triage screen brings the measures, feedback and open questions together. Claude Code could help prototype a small tool if it fits the task and account.
What the team decidesWhich details belong in the team’s view, and which question is still unanswered?
What should happen next?
In a reviewable team draftA draft list of possible follow-ups, with no customer messages sent or shared records changed.
What the team decidesWhich issue is worth addressing, who owns it, and who approves a real action?
The fictional inputs: Sample export: category, status and age. Six fictional comments. Team goal: choose one recurring issue to review. No live system is connected.
Keep each interpretation beside its source, test the view on fresh material, and let the people closest to the work set priorities and approve action.
Try this workflow yourself
Start with a safe sample
Use a small approved export and redacted or fictional comments. Pasting or attaching a sample is enough for the first exercise; no business-system connection is required.
Hello Aristotle
Explore a workflow you repeat
Help me plan a reviewable first version of a tool for a recurring team decision.
The decision we want to make: [goal].
The business data I can share: [approved, redacted or fictional export; name the fields, time period and source].
The feedback I can share: [approved or fictional excerpts].
The people who will use the result: [roles and what they need to decide].
The actions allowed: [state explicitly; default to a read-only draft].
First confirm which sources you can actually access. Ask about definitions, time periods or missing sources if they could change the conclusion. Keep the sample’s limits visible. Do not infer a trend, cause or customer motive beyond the material.
Then:
1. Pair each useful pattern with its supporting data rows or comments.
2. Separate direct evidence, interpretation and unknowns.
3. Sketch a simple team review view. If a small tool might help, explain its inputs, output, location and setup in plain language. Do not assume Claude Code, Cowork or a connector is available.
4. Test the draft on one ordinary and one unusual case.
End with the choices a person still needs to make. Keep everything as a draft. Do not message customers, update shared records, publish or schedule work. Ask before using a connector, reading other files or taking any action outside the material I named.Make a repeated team decision easier to handle.
You bring the business goal. We work through where the right context lives, what Claude can prepare and what the team should decide.
Name the decision and the sources
Choose one recurring team task, who uses the result and the small data or feedback sample available. Say what Claude may read and what it should leave alone.
Pick the Claude setup that fits
Use chat for a conversation, Projects to keep related guidance and sources, Cowork for multistep work where available, or Claude Code to build or revise a small tool. Anthropic is rolling out a unified chat and Cowork experience and a new Projects version, so we’ll check your account.
Prepare a team-readable first pass
Pair possible patterns with supporting feedback, keep assumptions visible and sketch a triage view or first tool draft if it fits the task and account.
Test it, then decide what repeats
Try fresh input and inspect what changed. Confirm access, schedule and approval steps before setting up a recurring task. Keep team priorities and meaningful actions with the people responsible.
Bring a task your team wants to improve.
We’ll start from the work your team already does and the information Claude could use. Ask questions, steer the draft and decide whether a chat, Project, Cowork task or Code helper fits.
Practice keeping evidence visible, testing a fresh example and choosing what deserves action. Your team keeps the decision and approves any real follow-up.
Meet Sydney Liu →What our learners say.
Nick on gaining confidence with AI after an individual session with Sydney.
“I work in finance and felt like I was falling behind. After one short session with Hello Aristotle, I had real ways to improve my workflows and the confidence to keep exploring. Sydney breaks things down in a way that’s easily digestible!”
A few practical questions.
Do I need a technical background?
No. Start by describing a process you know and the result you want. We can explore whether a Project, Cowork task or Claude Code helper fits. Some ideas need more setup or a technical partner; we’ll be clear about that before proposing one.
What’s the difference between a chat, a Project, Cowork and Code?
A chat handles a conversation, a Project keeps related context together, Cowork can take on a multistep task, and Claude Code can help build or revise a small tool. Anthropic is rolling out a unified chat and Cowork experience, so some accounts no longer show separate options. A new Projects version is also in beta. We’ll check what your account supports.
I already use Claude. What would a workshop add?
Bring a task your team repeats. We’ll look at the useful context, what Claude can prepare and where a small tool might help. Then we’ll test a fresh example so you can see what still needs your judgment.
Can Claude work with our business data?
Only when your plan and workplace settings allow it and the needed source access is approved. We can start with a permitted export or fictional sample; a connected app or folder is optional and needs its own setup.
Can it run this on a schedule?
Some paid Cowork setups support scheduled tasks. Available sources, local-file access, where a task runs and workplace controls depend on your account and setup. We’ll test a low-risk draft and confirm permissions first. You remain responsible for reviewing results and consequential actions.
How does this compare with a free Claude course?
Free courses are useful for learning the product. A workshop gives you space to examine your team’s own task, practice with the material you can share and get feedback on what Claude prepares. This is independent Hello Aristotle training with Sydney as instructor.
Can I join on my own or with colleagues, and what does it cost?
Yes to both! Tell us what you want to work on and where you’re starting. We’ll agree the scope, format and price with you before you book. For a group, we’ll also work out the participant count; initial paid group sessions start at one hour. The free 20-minute call is a separate conversation to explore fit.
Will I receive a certificate?
We offer Aristotle Certificates for proficiency milestones connected to practical work. They aren’t accredited qualifications or employer certificates. What matters most is that you can apply the learning to another task.
What should I have ready?
One repeat task, a clear outcome and a small safe sample are enough to start.
The team decision. Name the work you repeat, the question it supports and who will use the result. A small first task is best for exploring fit.
Material you can share. Use an approved export and fictional or redacted feedback. A pasted sample is enough for the first exercise; no connection to a business system is required.
Your Claude setup. Tell us whether you have Projects, Cowork or Claude Code access and whether your organization manages the account. Features and permissions vary by plan, app and workplace; we’ll check before an exercise depends on them.
What repeated work could use a better tool?
Bring a recurring task, a safe data sample and a question about Projects, Cowork or Claude Code. We’ll talk through what may help your team and what should stay under your review.
Book a free 20-minute call