Learn what Claude AI can do for your specific job. One simple prompt turns your role and documents into a personalized guide with 5 examples to try today.
Most people’s first conversation with Claude looks the same: a random question, a decent answer, and no real sense of what else the tool can do. Claude has a simple fix for that problem, and it starts with a single prompt.
The idea, laid out in Claude’s guide “Explore What Claude Can Do for You,” is that the most useful capabilities for any person depend entirely on what they actually do every day. A teacher, a product manager, and a butcher (yes, Claude tested that one) need completely different things from the same tool. So instead of guessing, you tell Claude your role, and it works out the rest.
The One Prompt That Starts Everything
The approach begins with a short prompt describing your job and what you spend your time on. Claude own example, written from the perspective of a product manager at a B2B SaaS startup, looks like this:
“I’m a product manager at a B2B SaaS startup. I mostly work on roadmap prioritization and customer research. I’m new to Claude. How can I use you most efficiently? Can you give me 5 examples I can try right now, ideally things that would actually make a difference in my daily work. Surprise me with one of them!”
That’s the entire starting point. No special setup, no advanced prompt engineering, just a clear description of the work.
Context Turns Generic Advice Into Specific Advice
A role description alone gets you useful, if somewhat generic, suggestions. What changes everything is giving Claude access to your actual working documents, for example by connecting Google Drive or uploading files directly into the conversation.
With real documents in hand, Claude stops describing hypothetical capabilities and starts referencing your actual projects. In this example, Claude finds the product manager’s real interview notes and roadmap, and comes back with genuinely specific ideas: spotting friction points across real customer interviews, stress-testing a real prioritization decision between three named features, and turning messy meeting notes into a clean one-page decision document.
Five Examples, Grounded in Real Work
The five example capabilities Claude walks through aren’t abstract feature descriptions. They’re built around what a product manager’s actual week looks like:
Synthesizing customer interview themes, by pasting a batch of interview notes and asking Claude to find the top friction points with direct quotes as evidence. Stress-testing a prioritization decision, by asking Claude to poke holes in a roadmap choice and flag what’s being underweighted.
Drafting a competitive teardown, by sending a competitor’s marketing site or screenshots and asking how their approach compares. Turning rough notes into a one-page decision document with a clear problem, options considered, recommendation, and risks. And, as the “surprise” example, having Claude go find and analyze a specific document, like customer interview notes, and surface patterns or contradictions on its own.
It Doesn’t Stop at the First Answer
Claude’s guide treats the first response as a starting point, not the end of the exercise. It suggests three natural follow-ups: bringing Claude a real deliverable you’re currently stuck on rather than a hypothetical example, and asking Claude to interview you with questions when you’re not even sure how to frame a problem yourself.
The third follow-up is asking directly what features beyond plain chat, such as Projects for persistent context, web search, file creation, or connectors to other tools, might be useful for your specific role.
Claude as a Thinking Partner, Not Just a Task-Doer
One tip from the guide is easy to overlook: some of the most valuable ways to use Claude aren’t about getting it to produce a document at all. Prompts like “Help me think through this decision” or “What am I not considering?” turn Claude into a sounding board for a problem you haven’t fully worked out yet, rather than a tool you hand a finished task to.
Claude also points people toward two practical habits that make the whole approach work better. The first is sharing documents instead of just a job title, since “product manager” alone produces far more generic suggestions than an actual roadmap or set of interview notes would.
The second is being specific about where time actually goes, since a detail like “I spend hours on status updates” helps Claude prioritize the capabilities that address a real, recurring pain point rather than a generic one.
Try It Yourself
The whole approach reduces to one move: open a new conversation, describe your actual job and what eats up your time, and optionally hand over the documents you already work with. That’s usually enough to get a personalized guide to the features that matter most for your specific work in under a minute.