Advanced26 min read

Claude 101(17) — 10 Real Things Normal People Are Doing With Claude (Case Studies)

Learn from 10 real-life case studies showing how everyday people — students, parents, small business owners, retirees — use Claude in their daily lives. From exam prep to wedding planning to memoir writing.

Claude 101(17) — 10 Real Things Normal People Are Doing With Claude (Case Studies)

Overview

By now you've seen the tools — Projects, Styles, Skills, Connectors, Cowork, Code, Computer Use. The question that matters most isn't "what can Claude do?" — it's "what would I actually do with it?" This article answers that with 10 short case studies of normal people using Claude in their real lives. Each one shows the person, the problem, the tools they used, and a sample prompt or workflow. Read them like inspiration, not instructions. Pick the 2 or 3 that resonate, copy what's useful, ignore the rest.

Who This Is Useful For

  • People who learned the tools in earlier articles but aren't sure how to put them to work
  • Anyone who wants permission to use Claude for "non-professional" everyday life — not just office tasks
  • Folks looking to convince a family member or friend that AI is for them too
  • Case Study #1 — The High School Student Preparing for College Exams

    Mei, 17, Taipei. Studying for her college entrance exams while juggling part-time work and three after-school clubs.

    What she does:

  • Built a Project called "Exam Prep" with all her course notes uploaded
  • Created a Skill called /quiz-me that pulls questions from any chapter on demand
  • Set up a scheduled task that emails her one practice essay prompt every morning at 6:30 AM
  • Uses Claude Artifacts to make herself custom flashcards
  • Sample prompt she runs daily:

    
    /quiz-me Chapter 8 — give me 5 multiple-choice questions with
    explanations for the wrong answers.
    

    Outcome: She studies 30 minutes more efficiently each day and feels less overwhelmed because Claude generates the practice questions she'd otherwise spend an hour finding.

    Case Study #2 — The New Parent Drowning in Baby Information

    David, 34, Singapore. First-time dad with a 6-month-old. Drowning in pediatrician notes, vaccination schedules, feeding logs, and "is this normal" questions in the middle of the night.

    What he does:

  • Built a Project called "Baby" with his daughter's medical history, allergies, and pediatrician's name uploaded
  • Connected Notion so he can save chat snippets to a "Baby Logs" page
  • Built a Skill called /baby-fever that runs a triage checklist when she has a temperature
  • Uses Claude in Chrome to summarize long parenting articles in 30 seconds
  • Sample prompt at 3 AM:

    
    /baby-fever — temp is 38.4, she's still feeding, slightly fussy.
    Last vaccine was 2 weeks ago. What should I check before
    calling the doctor?
    

    Outcome: He sleeps better. The 3 AM panic moments are 90% lower because Claude pre-filters the "is this an emergency?" question with his daughter's actual context in mind.

    Case Study #3 — The Retired Grandfather Writing a Memoir

    Mr. Lin, 71, Kaohsiung. Always wanted to write his life story for the grandkids but doesn't know where to start.

    What he does:

  • Built a Project called "My Story" with photos, old letters, and a 2-page bio of himself
  • Custom Style trained on letters he wrote in his 30s, so Claude writes in his voice, not generic AI prose
  • Uses voice input to dictate stories for 20 minutes at a time, then has Claude clean them up
  • Asks Claude to interview him with one new question every Sunday
  • Sample prompt:

    
    Ask me one specific question about my life as a young man
    that you don't know the answer to from what I've shared so
    far. Make it the kind of question that would surface a story
    worth writing down.
    

    Outcome: After 5 months he has 80 pages of stories — more than he'd written in the previous 50 years combined.

    Case Study #4 — The Small Café Owner Tracking Daily Inventory

    Sara, 38, Taichung. Owns a 25-seat café with two part-time staff. Inventory used to be a Sunday-night spreadsheet panic.

    What she does:

  • Uses Cowork to read photos of her stockroom and produce an inventory sheet
  • Built a Skill called /order-coffee that drafts the weekly order email to her supplier based on current stock + past 4-week patterns
  • Scheduled task every Friday afternoon: "Look at this week's sales CSV, suggest what to order more or less of next week"
  • Uses Claude Design for new specials posters and Instagram posts
  • Sample prompt for the order email:

    
    /order-coffee — I just took photos of the dry goods shelf and
    the fridge. Compare to last week's order, factor in this week
    being a school holiday, and draft the email to Lin from Café
    Supply Co.
    

    Outcome: Saves about 4 hours every week. More importantly, she's stopped running out of milk during Saturday rushes.

    Case Study #5 — The Freelance Designer Onboarding Clients

    Kenji, 29, Osaka. Solo designer juggling 6–8 active clients. Onboarding new ones used to take a full afternoon.

    What he does:

  • Project per client — each one has the brief, brand guidelines, and meeting notes
  • Skill called /onboard-client that generates the first-week email sequence, the welcome doc, and the project kickoff agenda
  • Uses Claude Artifacts to mock up first drafts of brand explorations live during client calls
  • Connector to Notion so each client's docs auto-save to the right page
  • Sample workflow: A new lead emails him. He runs /onboard-client with the lead's name and their initial brief. Within 90 seconds he has a personalized welcome email, a starter brand questionnaire, and a folder ready in Notion. He sends, the client thinks he's hyper-organized.

    Outcome: Onboarding went from "half a day" to "fifteen minutes". He's taken on two more clients without working more hours.

    Case Study #6 — The University Student Doing Literature Reviews

    Anya, 24, doing a non-CS master's degree. Has to read 30+ academic papers per semester and synthesize them into reviews.

    What she does:

  • Project called "Thesis" with her topic and methodology uploaded
  • Drops each PDF into the chat, asks Claude to extract: argument, methodology, key findings, limitations
  • Uses Claude + Web Search to find related papers she may have missed
  • Saves all summaries to Notion via connector — searchable for later
  • Sample prompt for each paper:

    
    Summarize this paper for a literature review. I need:

    1. Core argument in 2 sentences
    2. Methodology — strengths and weaknesses for my topic
    3. Findings most relevant to my research question (which is
    in this Project's instructions)
    4. How this paper connects or contradicts the others I've
    already saved to Notion under "Thesis Sources"
    5. The 1 question this paper opens that I should think about

    Outcome: Cuts her literature-review prep time roughly in half. More importantly, she catches connections between papers she would have missed reading them in isolation.

    Case Study #7 — The Wedding Planner Managing Seating Charts

    Priya, 41, organizing her own wedding for 180 guests. Three months out, the seating-chart anxiety hit.

    What she does:

  • Built a Claude Artifact seating-chart tool — drag and drop, with capacity warnings per table
  • Skill called /seating-conflicts that takes the guest list and flags potential conflicts (divorced couples, family feuds, dietary issues by table)
  • Uses Claude Design to make custom name cards and table numbers
  • Connector to Google Sheets — RSVP sheet auto-syncs into her chart
  • Sample prompt before each round of changes:

    
    /seating-conflicts — given the current seating, flag any
    issues based on the notes I've added to each guest. Especially
    check: gluten-free guests are at tables with gluten-free
    options, no exes at the same table, and elderly relatives
    have aisle seats.
    

    Outcome: What was supposed to be a multi-week stress turned into 4 evening sessions. The day-of seating ran without a single complaint.

    Case Study #8 — The Travel Blogger Translating and Localizing Posts

    Tomás, 33. Writes a small travel blog in English; readers in Asia keep asking for 繁體中文 versions.

    What he does:

  • Skill called /translate-blog that not only translates but also adapts cultural references (replaces a baseball metaphor with a basketball one when the audience changes regions)
  • Custom Style for "blog voice" trained on his own posts
  • Uses Claude Artifacts to generate post-specific maps and itinerary widgets that work in both languages
  • Schedules a weekly task to draft the next week's blog calendar
  • Sample prompt:

    
    /translate-blog — target language: Taiwan-style 繁體中文.
    Adapt food references, cultural touchstones, and currency.
    Keep my tone (slightly self-deprecating, story-driven).
    Add 2-3 phrases that would resonate specifically with Taiwan
    readers — but don't overdo it.
    

    Outcome: His Taiwan readership tripled in 6 months. The localized posts feel like they were written by a local — because Claude is doing real adaptation, not just translation.

    Case Study #9 — The Person Managing a Chronic Health Condition

    Elena, 52. Diagnosed with type 2 diabetes 3 years ago. Tracks blood sugar, food, exercise, and medications across 4 apps.

    What she does (with her doctor's awareness):

  • Project called "Health" with her medical history, current medications, doctor's instructions
  • Daily journal entry — paste the day's readings, food, and mood; ask Claude to flag patterns
  • Uses Claude Artifacts to build a custom mood-and-glucose tracker beyond what her apps allow
  • Brings monthly Claude-generated summaries to her doctor visits
  • Sample weekly prompt:

    
    Look at the past 7 days of readings, food entries, and exercise.
    Flag any patterns — especially: meals that consistently spike
    my glucose, days my mood was low after specific foods, and
    whether my evening exercise actually helped morning numbers.

    Write a one-page summary I can show to my doctor.

    You are not a medical professional. Add a line at the top
    reminding me that what you find should be reviewed with my
    doctor before I change anything.

    Outcome: Her appointments are dramatically more productive — instead of pulling up 4 apps and trying to explain, she walks in with a one-page Claude-generated trend report. Her doctor reads it in 30 seconds and they spend the rest of the time on actual treatment decisions.

    Case Study #10 — The Person Job Hunting in a New Field

    Marcus, 29. Switching from finance to UX design. Has to write a different cover letter for every application without sounding generic.

    What he does:

  • Project called "Job Search" with his master CV, the brand voice he wants ("curious-rigorous-collaborative"), and notes on each company he applies to
  • Skill called /cover-letter that takes a job posting and generates a tailored cover letter using his voice
  • Uses Claude + Web Search to research the company before applying
  • Style called "Marcus Voice" trained on his actual writing
  • Connector to Gmail so Claude can review his outbox and improve drafts
  • Sample prompt:

    
    /cover-letter — paste the job posting below. Use my master CV
    and Marcus Voice. The cover letter should:

    1. Open with a specific reason this company appeals to me
    (research them via web search if needed)
    2. Connect 2 things in my CV to specific lines in the job
    posting
    3. Address the obvious "but you're from finance" question
    honestly, in 2 sentences
    4. Close with a specific next step

    Max 250 words. Sound like I wrote it after 30 minutes of
    thinking, not 5 seconds of AI generation.

    Outcome: Got 3 interviews from his first 12 applications. The "honest 2-sentence career-switch line" turned out to be the thing every interviewer commented on.

    Going Further

    Pick 2 cases that resonate. Not 10 — two. Set yourself a goal: build the same setup for one of them this week, the other next week. By month 2 you'll have your own pattern.

    Write your own case study. After 3 months of using Claude consistently, write a "what I'm doing with Claude" page in your Notion. Even just for yourself. It clarifies your own setup, and helps you spot what's working from what's just sitting unused.

    Share with one person. The biggest unlock for most non-technical users isn't reading another tutorial — it's having one friend show them their actual setup. If a case study above looks like a friend's situation, send it to them.

    Key Takeaways

    Here's what you learned from these 10 case studies:

  • The same tools, used in different ways. Projects + Skills + Connectors form the spine of almost every setup. The variation is in what you put inside them.
  • Personal context beats clever prompts. Mei's exam prep, Elena's health summaries, and Mr. Lin's memoir all work because the Project has rich personal context — not because the prompts are unusual.
  • The biggest wins are recurring. One-off Claude use saves you minutes. Recurring setups (daily, weekly, monthly) save you hours.
  • Cross-tool combinations are the magic. Almost every case study above uses 3+ Claude tools layered together. None of them use Claude in isolation.
  • The setup pays for itself fast. Most case studies above describe 2-4 weeks of "play and tweak" before things clicked. After that, the time savings compound forever.
  • You don't need to be technical. None of the people in these stories had any programming background. They described what they wanted; Claude built it.
  • The pattern across all 10: figure out one repeating thing in your life that wastes time or causes stress. Build for that. Once it works, build the next one. After 3 to 5 such builds, your relationship with daily life is meaningfully different.

    Learn AI, after work

    Track your progress, earn XP, and unlock more free tutorials in the AfterWork Bytes app.

    Open this tutorial in the app