A Week with AI
Two real-shaped households, Monday to Sunday, with the actual prompts they used and what came back. The cumulative case for AI is not about one clever trick. It is what the small wins look like over seven days.
Most reviews of AI tools focus on the impressive single demo: the resume rewrite, the photo-to-recipe trick, the holiday itinerary. The honest case for AI is quieter. It is what happens across a normal week of normal life, where small bits of friction get smoothed out one after the other. Two scenarios below. Names changed; situations are the kinds of things real people I know have used AI for.
Scenario one: a retired couple managing a busy week
Margaret and David are both 67, recently retired, living in a townhouse in suburban Adelaide. Margaret has used a chatbot a few times. David is sceptical and has not. They have access to Claude on Margaret's laptop and the free ChatGPT app on David's phone. Their week looks like this.
Monday: a medical appointment to prepare for
David has a follow-up appointment with a cardiologist on Wednesday. Last visit, he forgot most of the questions he meant to ask and came home frustrated. Margaret opens Claude.
What came back was a clean one-page summary, organised by topic, with sensible questions about whether the dizziness might be the beta-blocker, whether the bruising could be related to the statin, and what symptoms would warrant an urgent call rather than waiting. David printed it.
Watch-out. AI does not diagnose. The sheet is a preparation aid for the actual conversation with the cardiologist, not a second opinion. Margaret made a point of not asking "what is causing the dizziness". The longer story is on the How to Check What AI Tells You page.
Tuesday: a family birthday and a tradesperson dispute
Their daughter Anna turns 40 on Saturday. Margaret wants to write something for the speech and is dreading it. She gives Claude four sentences about Anna ("first child, midwife, two girls of her own, has a way of making everyone feel important") and asks for a 90-second speech draft to read at the dinner.
What came back is not the speech she ends up giving. It is something better: a structure with three good lines and a way to land it. Margaret rewrites it in her own voice, keeps two of the lines, and cuts the rest. The version she will say on Saturday took her twenty minutes instead of two hours of staring at a blank page.
Meanwhile, the plumber who fixed the hot water service in March has invoiced for work he did not do. David is furious. Margaret asks Claude to help draft a polite-but-firm email to dispute the charges.
The email comes back well-pitched: firm, references the consumer guarantees, leaves him a way to fix it without losing face. They send it. By Thursday morning he has corrected the invoice.
Watch-out. They read the email out loud before sending. It tightened up two slightly stiff phrases. Reading drafts aloud is the single most useful editing trick on this site.
Wednesday: a body-corporate notice and the cardiology appointment
A two-page body-corporate circular has arrived proposing a special levy of $4,200 per unit for waterproofing repairs. Margaret photographs it and uploads it to Claude.
The summary flagged that the notice did not include three written quotes (which the regulations in their state require) and that the proposed timeline gave less notice than the minimum. Margaret raised both at the meeting on Friday. The committee deferred the vote.
The cardiology appointment goes well. David takes the printed sheet. The cardiologist says the dizziness is almost certainly the beta-blocker timing and adjusts the dose. He thanks David for the bruising question, which he says he might not have probed otherwise.
Thursday: planning a holiday
They have been talking about a fortnight in Tasmania for months and have done nothing about it. Margaret asks Claude to draft a 14-day itinerary on a real budget.
The itinerary is solid. Devonport, Cradle Mountain (with an honest note that the steeper walks would not suit them), Strahan, Hobart, Bicheno, Launceston. They book the flights that night.
Watch-out. AI happily produces accommodation names and prices that sound real and sometimes are not. Margaret takes the suggested towns and checks accommodation directly on the venue's own website before booking. Half of the suggested places existed; the others were close but slightly off (one was a cafe, not a hotel).
Friday: a difficult email about Anna's birthday
David's brother lives interstate and was vaguely promising to come for Anna's birthday for weeks. He has now said he is not coming, with a long, slightly hurt-sounding email. David wants to reply without escalating it.
Margaret asks Claude for two versions: a slightly warmer one that lets it lie, and a slightly firmer one that says clearly that they wish he would come. David reads both, takes one paragraph from one and one from the other, and writes the rest himself. The brother replies three hours later saying he has changed his mind. He comes.
Saturday: the birthday, and Sunday: a recipe from the fridge
The birthday goes well. The speech lands. Sunday morning Margaret takes a photograph of the inside of the fridge and sends it to ChatGPT on her phone with the prompt: "Five real dinners I can make this week with what is in here, plus what I would need to add from the supermarket. Cooking is for two, and we eat plain food."
The five suggestions are sensible. Three become dinners. The grocery list at the bottom shaves twenty minutes off the Sunday afternoon shop.
What the week added up to
None of these are revolutionary. A speech that took twenty minutes instead of two hours. A body-corporate vote that was deferred because the right question got asked. A medical appointment that came home with a useful answer. A holiday that finally got booked. An invoice corrected without a fight. A speech that landed. Maybe nine or ten hours of friction removed across the week, and a small handful of decisions made better. The cumulative case for AI is this, not any one clever trick.
Scenario two: a working parent with two school-age kids
Priya is 41, a logistics manager in Sydney, two kids (10 and 13), husband works shifts. She uses ChatGPT Plus on her phone, which her workplace pays for, and has Claude on her laptop. Her week is perpetually full. AI is not optional; it is the only way her week fits into the hours available.
Monday: school newsletter and an awkward email to a teacher
Monday morning the school newsletter lands in her inbox. Six pages of dense PDF, of which roughly two paragraphs apply to her family. She forwards it to ChatGPT and asks it to pull out the items relevant to a Year 5 and a Year 7. Forty seconds later she has a list: a Year 5 excursion that needs payment by Wednesday, a Year 7 elective form due Friday, a working-bee on the 18th. She marks the dates and moves on.
The Year 7 maths teacher has emailed about her son's recent test, which was "below where we would expect". She wants to reply without sounding defensive but also wants to know what is going on.
The draft was almost there. She tightened two phrases, added a sentence about her son's own reading of the situation, and sent it. The teacher replied the next morning with specific topics he was struggling with. Useful.
Tuesday: dinner-plan rescue and a homework topic
Priya forgot to think about dinner before leaving for work. At 4pm she opens ChatGPT on the bus and types: "What is in the fridge based on my Sunday shop: chicken thighs, broccoli, spring onions, ginger, half a packet of egg noodles, leftover rice, two limes, eggs, soy. Dinner for four in 25 minutes. Kids eat most things but not chilli."
Stir-fried chicken with noodles, broccoli on the side, lime slices to squeeze. Twenty-eight minutes including the chopping.
That night her daughter asks for help with a Year 5 history topic on the gold rush. Priya does not remember Australian history clearly enough to be useful. She opens Claude and asks for a kid-pitched explanation with three good questions her daughter could think about herself.
The explanation is solid. The questions are good. Priya reads it with her daughter, who then writes her own paragraph for the homework. Priya does not type a word of it.
Watch-out. The line in this house is the one on the When Not to Use AI page: AI is allowed to teach. AI is not allowed to do. Priya was clear with her daughter about which side of the line they were on.
Wednesday: a complaint to a telco
The mobile bill is wrong again. Third month running. Priya asks Claude to help draft a complaint that goes one rung higher than usual.
The draft was good. She added a paragraph with the dates of her two earlier calls and the names of the people she spoke to, then sent it. The refund hit her account on Friday.
Thursday: prepping questions for a GP visit
Her younger son has been getting headaches. Their GP appointment is Friday afternoon. Priya gives ChatGPT a short, accurate summary of the symptoms, frequency, what makes them better and worse, and asks for a list of the questions a sensible parent would want to ask, plus what symptoms would be worth flagging clearly.
She does not ask "what could it be". She asks "what should I make sure to bring up". The difference matters. The list keeps her organised on the day.
Watch-out. The GP visit was the one that mattered, not the chat with the AI. The longer rule on this is on Rules That Matter: medical decisions of any consequence get made by the qualified person, not by the chatbot.
Friday and the weekend: weekend admin
Friday evening Priya runs through three weekend errands with Claude in voice mode while doing the dishes. Comparing two extracts plans for the family's health insurance, drafting a reply to a relative on a delicate matter, working out what to do about the leaking dishwasher (call the service guy from Tuesday's email; do not start with the warranty page).
Saturday morning her son's headaches turn out to be screen time and dehydration, mostly. The GP suggested a couple of small changes; both seem to be working. Sunday afternoon she uses ChatGPT for a Sunday-meal-prep list to cover three weekday dinners, total cost roughly A$60.
What the week added up to, again
None of this is impressive on its own. The cumulative case is the same as scenario one: maybe ten hours saved across the week, three or four small decisions made better, two tricky messages sent that would otherwise have sat in her drafts for a week. The point of these worked examples is not to show off. It is to show what AI looks like as a quiet helper, in the actual texture of an actual week.
If you want to try this yourself, start with Your First Week with AI for a seven-day plan. The topic-by-topic pages on Everyday Life are next. The hard rules and verifying habits sit on Rules That Matter and How to Check What AI Tells You.