I want to be upfront about who I am, because it matters for this article.
I'm a transport driver at a defence facility in Rockingham, Perth. I work rotating shifts — early mornings some weeks, afternoons others. I also run two businesses on the side: RJ Does AI, where I build AI automation systems for Perth clinics and law firms, and ronaldbasawil.com.au, where I show Perth professionals how to use Claude AI in their daily work.
I am not a developer. I don't have a computer science degree. I didn't grow up "technical." And I use Claude AI every single day — at home before shifts, during breaks, and late at night when the family's asleep.
This past week I tracked exactly what I used it for, how long each task took with and without Claude, and what the honest results were. No vendor sponsorship. No affiliate links. Just a real account from someone living it.
My week at a glance
This was a morning shift week — 5:30am starts Monday through Friday. That means I'm home by 12:30pm, which gives me a few hours before family commitments in the afternoon. Here's what I used Claude for across the week:
| Task | Context | Without Claude | With Claude | Saved |
|---|---|---|---|---|
| Building the RB Coaching website | Full site build — homepage, blog, DNS setup | Days (or hire a developer) | One afternoon session | Days of work |
| Writing LinkedIn post | Personal brand launch announcement | 45–60 min | 15 min | ~45 min |
| Researching SEO strategy | Reviewing YouTube video + verifying claims | 2–3 hours | 30 min | ~2 hrs |
| Planning the week's work | Prioritising tasks across two businesses + job | 30 min scattered thinking | 10 min | ~20 min |
| Drafting outreach emails | Cold email campaign for RJDA | 60–90 min per batch | 15–20 min | ~60 min |
Total time saved this week: conservatively 4–5 hours. For someone working shifts and running two businesses, that's not a small number. That's the difference between making progress and just keeping up.
Task 1: Building an entire website in an afternoon
Building ronaldbasawil.com.au from scratch
What I needed: A live coaching website with homepage, blog index, two SEO articles, DNS configuration, SSL certificate, Google Analytics, and Google Search Console.
What I knew going in: I'd done this once before with my other business site. I knew the tools but not the specific commands.
How Claude helped: I described what I needed at each step and Claude gave me the exact commands to run in my server terminal, the exact Nginx config to paste, and flagged a DNS conflict I'd missed that would have broken the site.
Honest result: The site went from nothing to fully live with SSL in one afternoon session. A developer would have charged $500–$1,500 for this. I did it myself with zero coding knowledge.
Task 2: Writing a LinkedIn post that actually sounds like me
Personal brand launch post
What I needed: An announcement post for the new coaching brand that was honest, personal, and didn't sound like a sales pitch or generic AI content.
What I did: I told Claude my background — shift worker, JW public speaker, AI practitioner — and asked it to write a post that used my real story rather than marketing language.
What I changed: One paragraph needed rewording because it overclaimed something I hadn't done yet. Claude actually flagged this when I asked it to double-check for honesty. I removed the line.
Honest result: The post I published sounded like me. Several people who know me personally commented that it felt genuine. That's the goal.
Task 3: Researching and verifying an SEO strategy in 30 minutes
Verifying YouTube SEO claims before applying them
What I needed: I watched a YouTube video about a "new SEO method" and wanted to verify whether the claims were accurate before changing my content strategy.
What I did: I extracted the video transcript, gave it to Claude, and asked it to identify which claims could be verified and which were overstated. Then I used Perplexity to run a deep research prompt Claude helped me write.
What we found: Most of the core claims were accurate and backed by Google's own documentation. Two specific examples in the video (certain ranking comparisons) couldn't be verified from current data. That nuance matters — it changed how I applied the strategy.
Honest result: Instead of blindly applying a YouTube strategy or spending hours researching it myself, I had a verified, nuanced breakdown in about 30 minutes — including specific action items for my own site.
Task 4: Planning my week across two businesses and a day job
Weekly priority planning
What I needed: A clear priority order for the week given I had limited afternoon windows, two businesses at different stages, and a cold email campaign running in the background.
What I did: I described my constraints — shift times, what was already in progress, what was time-sensitive — and asked Claude to help me sequence the week.
Honest result: This is one of Claude's most underrated uses. Not the flashy stuff — just thinking clearly about what to do first when everything feels urgent. It took 10 minutes and I stuck to the plan all week.
Task 5: Drafting cold outreach emails with personalised hooks
RJDA cold email batch
What I needed: Personalised email hooks for a batch of Perth clinic and law firm leads — each hook referencing something specific about their business.
What I did: I gave Claude the business names, websites, and industries. It researched each one and wrote a specific opening hook per lead.
Honest result: The hooks were 80–90% usable as-is. I edited maybe 20% of them. The batch that would have taken me 60–90 minutes to write took about 15–20 minutes to review and approve.
Where I used Claude this week
People assume AI tools are a desk-at-home thing. They're not. This week I used Claude:
- At home before my 5:30am shift — planning the day, drafting quick messages
- At home after shifts — building the website, writing the LinkedIn post, research
- On my phone during breaks — reviewing draft outputs, quick questions, checking progress
Claude's mobile experience is genuinely good. I don't need to be at a desk. I don't need a special setup. I need a phone and a Claude account.
What Claude couldn't do this week
I want to be honest about this because most AI content glosses over it.
- It couldn't replace judgment. When the LinkedIn post needed a line removed because it overclaimed, Claude flagged it — but I had to decide what the honest version was. That requires knowing your own situation.
- It needed context every time. Claude doesn't remember previous conversations by default. I had to re-explain my situation at the start of new sessions. This is a real friction point.
- First drafts still needed editing. Nothing went from Claude straight to publish. Everything needed a human pass — sometimes light, sometimes more significant.
- It made one DNS suggestion that needed correcting. A field label was slightly off in the DNS setup. I caught it because I was paying attention. If I'd copied blindly, the site might not have worked.
The honest summary: Claude makes me significantly faster and gives me capabilities I wouldn't otherwise have — but it works best when I bring my own judgment, context, and professional knowledge to every interaction. It amplifies what I already know. It doesn't replace knowing things.
My background — and why it matters
I've been a public speaker and teacher in a voluntary capacity for years — regularly presenting to groups of 50 to 150 people, explaining complex topics in plain language to people of all ages and backgrounds. That experience taught me something that's directly relevant to AI:
The person who can explain something clearly always gets more out of AI than the person who just types a vague request.
When I give Claude a well-structured brief — context, constraints, desired outcome, tone — I get something useful back. When I type "write me an email," I get something generic. The skill isn't technical. It's communication. And that's a skill experienced professionals already have.
What this week tells me about AI for Perth professionals
I work shifts. I run two businesses. I have family commitments. I have no technical background. And I saved at minimum 4–5 hours this week using Claude across tasks that ranged from building a website to planning my Thursday afternoon.
The professionals I talk to in Perth — lawyers, clinicians, migration agents, business owners — are managing far more complexity than I am in some respects. They have client work, staff, compliance, billing, correspondence. The potential time savings are significantly higher.
The barrier isn't technical. It's knowing where to start and having someone show you how Claude fits your specific work — not a generic tutorial, but your actual tasks.
That's exactly what the free 90-minute session is for.
Want to see what Claude can do for your work?
Book a free 90-minute session. We work through your actual tasks together — no slides, no jargon, no tech background needed.
Book your free session →