Most people who start using Claude think of it as a smarter search engine or a fancy chatbot. Ask it a question, get an answer, move on. That’s fine. But it’s also like buying a Swiss Army knife and only ever using it to open bottles.
I’ve been using Claude daily for a while now, across work, writing, training, parenting, and just about every other corner of my life. The honest answer to “what can I use Claude for” is: a lot more than you’re currently using it for, and probably in ways that would actually save you meaningful time every week. Let me break down the categories that matter and give you real examples of each.
Creating Documents, Spreadsheets, and Presentations
This is my most-used category by a significant margin and the one I recommend to people first. Claude can generate actual downloadable files, not just text you copy and paste somewhere. Word documents, Excel spreadsheets, PowerPoint presentations. Real files, properly formatted, ready to open.
What this looks like in practice: I describe what I need, Claude builds it, and I download it. A project proposal with headers, sections, and formatted content. A training log spreadsheet with the right columns and formulas already built in. A slide deck for a presentation I need to give, structured and designed. Tasks that used to take me an hour of starting-from-scratch formatting now take ten minutes of describing what I want and reviewing the output.
The Excel piece is where this genuinely surprised me. I am not an Excel person. I know how it works, I resent using it. Claude removes most of the friction. Tell it what the spreadsheet needs to do, what columns you want, what calculations matter, and it builds the thing. I’ve used this for budget trackers, training plans, grocery cost comparisons, and a race log that normalizes all my finish times into a consistent format. Stuff I would have manually built in a resentful hour now gets done in five minutes.
Same story with PowerPoints. Describe the topic, the audience, how many slides, the tone you’re going for. Claude builds a structured deck. You customize from there. It’s not going to win design awards but it’s a legitimate starting point that’s miles ahead of a blank slide.
Writing and Communication
Email drafting is one of those use cases that sounds small and quietly saves you a surprising amount of time. The emails that take the longest aren’t the quick replies. They’re the ones where you need to say something delicate, push back on something, follow up for the third time without sounding passive-aggressive, or deliver news that someone isn’t going to love. I describe the situation and what I’m trying to accomplish, Claude drafts it, I tweak the voice and send it. The blank-page problem disappears.
Beyond email, Claude is useful for anything that involves turning rough thinking into polished writing. Blog posts (you’re reading one). Performance reviews. Job descriptions. LinkedIn bios. Cover letters. Project briefs. Meeting agendas. The use case is always the same: you have a general idea of what needs to be said, Claude helps you say it clearly and in the right format.
It also works in reverse. Paste in something someone else wrote and ask Claude to summarize it, extract the key points, or identify the action items. I do this constantly with long email threads, dense documents, and meeting notes that need to be turned into something a normal human would actually read.
Summarizing and Organizing Notes
This one is criminally underused. If you’ve ever finished a meeting and stared at a page of half-sentences and bullet points that only made sense in the moment you wrote them, Claude fixes that. Paste in the mess, tell it what you need out the other side (action items, a summary for stakeholders, a cleaned-up set of notes you can actually reference later), and it does the work.
I use this for brain dumps constantly. I’ll capture a half-formed idea in my notes app while I’m running, come back to it later, paste the chaos into Claude with a one-line brief about what it’s supposed to become, and get back something structured and usable. The thinking is mine. The organization is Claude’s. That division of labor works well.
It’s also useful for research. Paste in several articles or documents on the same topic and ask Claude to synthesize the common themes, identify where sources disagree, or pull out the most relevant information for a specific decision you’re making. You still have to read the things that matter, but Claude can tell you which things matter before you read all of them.
Writing Documentation
As a software developer, this is one of the highest-value use cases on my list. Documentation is the thing everyone knows needs to exist and nobody wants to write. Claude makes it fast enough to actually do.
Give it a function, a module, an API endpoint, a process you’ve built, and ask it to write the documentation. It’ll produce READMEs, inline code comments, API docs, runbooks, and technical guides. Not perfect first drafts, but solid starting points that you edit rather than create from scratch. The time difference between editing and creating is enormous when you’re doing this repeatedly.
It works for non-technical documentation too. Standard operating procedures, onboarding guides, process docs, employee handbooks, workflow explanations. Anything where the goal is explaining how something works to someone who wasn’t in the room when you built it.
Coding and Technical Work
If you write code, Claude is useful in ways that go well beyond autocomplete. Debugging is the obvious one. Paste in the error, describe what you were trying to do, get a diagnosis and a fix. It doesn’t always get it right on the first try, but it narrows the problem space fast.
Code review is another good one. Paste in a function or a block and ask Claude to look for bugs, edge cases, performance issues, or anything that doesn’t follow the conventions you describe. It’s not a substitute for a real code review, but it’s useful for catching things before the real review happens.
For small utility scripts, the use case is even cleaner. Describe what the script needs to do, what the input looks like, what the output should be. Claude writes it, you test it, you tell it what broke. Most small tools are three or four iterations from working. This is fast enough to be worth doing for scripts that save you only a few minutes a week, which changes the math on what’s worth automating entirely.
Planning and Decision-Making
Claude is a useful thinking partner for decisions that have a lot of variables. Not because it tells you what to do, but because explaining a problem to it forces you to articulate the relevant factors, and then it can help you think through them systematically.
I’ve used it to plan training blocks around race schedules, work out meal plans against a week of calendar commitments, think through how to structure a difficult conversation with someone at work, and evaluate whether a purchase actually makes sense against my actual usage patterns. The format is always the same: here’s the situation, here are the constraints, help me think through this. It’s faster than staring at a blank page and more structured than thinking out loud.
It also works for research on decisions you haven’t made yet. Comparing two approaches to something, understanding the tradeoffs between options, getting a quick overview of a topic you don’t know well enough to evaluate options in. Claude can give you a usable mental model fast, with the understanding that you should verify anything important before acting on it.
Connectors: When Claude Connects to Your Actual Tools
This is where Claude moves from being a useful standalone tool to being genuinely embedded in how you work. Claude supports connectors that let it talk directly to the apps you’re already using: Google Calendar, Gmail, Notion, Slack, Google Drive, and others depending on your setup.
What this unlocks is context. Instead of describing your situation to Claude, it can see it directly. I use the Google Calendar connector so Claude can read my actual week before helping me plan meals or training. It knows Tuesday has a late call, Thursday ends with rugby, and Saturday is a long run, so the plan it builds accounts for the real week instead of an idealized one. The difference between a plan built on your actual schedule and one built on a generic template is the difference between a plan you follow and one you abandon.
The Notion connector means Claude can pull from your existing notes and documents instead of starting from scratch every conversation. The Gmail connector means it can draft emails with full context about the thread. The Google Drive connector means it can read a document you share instead of making you copy and paste the contents.
Use connectors when the task requires context that lives in another tool and would be annoying or impractical to manually describe. Use Claude without connectors when the task is self-contained and you can give it everything it needs in the conversation. The connectors aren’t always necessary but when they are, they close the gap between “Claude as a tool I use” and “Claude as something that actually knows my situation.”
Skills: When You Need Claude to Do Something Specific, Every Time
Skills are reusable instructions you give Claude that change how it behaves for a specific type of task. Think of them as custom modes you can invoke instead of re-explaining what you want every time you need the same kind of output.
If you run keyword research for a blog and you want it done the same way every time, with the same sources checked and the same output format, you build a skill for that. If you write code in a specific style with specific conventions and you want Claude to follow them without being told every session, that goes in a skill. If you have a particular way you want meeting notes formatted, a particular structure for performance reviews, a particular voice for customer communications, skills are how you make that consistent without repeating yourself.
The practical rule: use skills when you’ve done the same type of task with Claude more than a few times and found yourself giving the same setup instructions each time. That repetition is a signal that the instructions belong in a skill rather than in the conversation. Skills make Claude feel less like a tool you configure each time and more like a workflow that already knows what you need.
Everyday Stuff That Adds Up
Beyond the big categories, there’s a long tail of smaller use cases that don’t fit neatly into a bucket but collectively save real time. A few from my own regular rotation:
Proofreading and editing anything I write before it goes anywhere. Translating something into plain language when I need to explain a technical concept to a non-technical audience. Generating checklists for recurring processes so I don’t have to rebuild them from memory every time. Getting a quick explanation of something I don’t understand well enough to Google effectively. Brainstorming names, titles, or ideas when I’m stuck and need options to react to rather than a blank page to fill.
The pattern across all of it is the same. Claude is most useful when the task has a clear output you’re trying to reach, some friction standing between you and that output, and enough context that you can describe the situation clearly. Those three conditions cover a lot of ground in a normal week.
Where to Start
If you’re new to Claude or haven’t pushed past basic Q&A, start with the document creation use case. Find something you need to produce this week, a report, a spreadsheet, a presentation, and describe it to Claude instead of building it from scratch. That single use case tends to immediately demonstrate the time savings in a concrete enough way that everything else clicks into place.
From there, try the email drafting. Find the email you’ve been putting off because you’re not sure how to say the thing, describe the situation to Claude, and see what it comes back with. You’ll edit it. But you won’t be starting from nothing.
The connectors and skills come later, once you have a sense of where Claude fits in your workflow and which tasks you’re doing repeatedly enough to be worth automating. Don’t set them up on day one. Set them up when you notice yourself doing the same setup steps over and over and think “there has to be a better way to handle this.” There is. That’s what they’re for.
Take what’s useful. Leave the rest.