Claude for absolute beginners, the Australian small business edition

Before we start, two honest things

First, the AI hype is overdone. You will not “10x your business” in a weekend. You will not “replace half your staff” in a month. The realistic version: AI saves most Australian small business owners 3-6 hours a week on writing, drafting, summarising and tedious admin. That’s worth doing. It’s not magic.

Second, you don’t need to learn anything technical. There are no terminal commands in this guide. No code. No “API keys”. If a word looks scary, we’ll explain it in plain English. If you can write a text message, you have all the skills you need.

Stop here if you handle regulated data. If your work involves patient records (allied health, dental, medical, vet), legal client files, tax / financial advice records, or anything subject to APP, AHPRA, TPB, or state Health Records Acts, this consumer-Claude guide is the wrong starting point for you. Read the Australian AI compliance landscape 2026 and the allied health practices guide (or your industry’s specific guide) before you paste a single piece of client data into Claude. The path for regulated work is Claude API, not consumer Claude.

Right. Let’s go.

What Claude actually is, in one sentence

Claude is a website (or app) where you type questions or requests, and an AI answers you in plain English. Like texting a very fast, very widely-read assistant who never sleeps.

That’s it. That’s the whole concept. The technical name for what powers Claude is a “large language model”, but you don’t need to know that to use it, the same way you don’t need to know how Google’s search algorithm works to Google something.

The 5-minute test

Before reading any further, do this. It’s the whole point.

Step 1: Open claude.ai

Go to claude.ai in your browser. Sign up with Google or your email. Free, no credit card needed.

If you’d rather, you can install the Claude app from the App Store or Google Play. The browser version does the same thing.

Step 2: Ask it one real question about your business

Pick the prompt below that’s closest to what you do, copy it, paste it into Claude, hit Enter:

If you run a cafe / restaurant / hospitality business:

“I run a cafe in [your suburb], [your city]. We’ve just put a new winter menu on, with mushroom toast, hot chocolate, and a dumpling soup. Write me three Instagram captions, each 40-50 words, with a hook line, mention the suburb, and end with a soft call to visit. Warm, slightly cheeky tone. No exclamation marks.”

If you’re a tradie (plumber, sparky, builder, chippy):

“I’m a [your trade] in [your city]. Write me a polite SMS to send to a customer 48 hours after I finish a job, asking for a Google review. The job was [describe what you did]. Don’t be pushy. Mention the work, make it sound like I wrote it. Australian tone, not American.”

If you run a service business (allied health, beauty, agency, consulting):

“I run a [your business type] in [your city]. Here are three customer enquiries I got this week, paste below. For each one, draft a friendly reply. Mention pricing for [your service], my availability this week, and a call to book a 15-minute call. Australian tone, not American. Don’t sound like a chatbot.

[paste your three enquiries]”

If you run a Shopify / online store:

“I run an Australian online store selling [what you sell]. Write me a product description for our [new product]. 120 words, conversational, mention the materials and a specific use case. Warm but not gushing. Don’t use ‘elevate’, ‘curated’ or ‘unleash’. End with a one-line shipping note (‘Free Australia-wide shipping over $80’).”

If you do something not on this list:

Make one up. The format that works:

“I am [your role + business]. Write/draft/summarise [the thing you need]. Tone: [your style]. Constraints: [word count, things to avoid, what good looks like].”

Step 3: Read what came back, and decide

If the output is something you’d actually use (maybe with a 30-second edit), congratulations. You’ve passed the test. AI is going to be part of how you work. Read on for the patterns that make it really useful.

If the output is rubbish, that’s almost always a prompting issue, not an AI issue. Read the “what good prompts look like” section below.

If the output is in American English (“color”, “favorite”, “z” instead of “s”), just reply “Use Australian English. Re-do.” Claude apologises and re-does it.

What good prompts look like

The single biggest unlock once you’ve passed the test. The pattern that works for any AI, for any task:

The four-part prompt

1. Who you are (your role, business, customer)
2. What you want (specific output, specific format)
3. Constraints (tone, length, things to avoid)
4. What good looks like (an example, a description of success)

Example of a bad prompt:

“Write me an email to my customers about our sale.”

Example of a good prompt (same task):

“I run an Australian women’s clothing boutique. We’re running a 25% off mid-winter sale, starting Friday, ending Sunday at midnight. Write a 100-word email to our customer list announcing it. Warm, friendly, not pushy. Mention that loyal customers get an extra 10% if they reply to the email. No exclamation marks, no ‘don’t miss out’, no ‘hurry’. Australian English. Subject line included.”

The second prompt produces something close to publishable. The first produces generic AI slop.

The trick: give Claude your stuff

The single fastest way to get great output is to feed Claude your actual material. Examples:

• Last 5 customer emails + “draft replies in my voice”
• Your menu + “write the Instagram caption for the dumpling special”
• Your last 3 blog posts + “write a new one in this voice on [topic]”
• A long email from your accountant + “summarise in 4 dot points, what action do I need to take?”
• A 20-minute meeting transcript + “summarise the key decisions and who’s actioning each one”

Claude reads what you give it, then works on it. That’s the difference between generic AI text and something that sounds like you.

Quick fixes for bad output

If the answer is meh:

• “Use Australian English.”
• “Make it half as long.”
• “Make it sound like a human, not a press release.”
• “Re-do, but in a more [your tone] voice.”
• “Don’t use these words: [list the ones it overused].”

You can keep replying. Claude doesn’t get frustrated. The conversation is the workflow.

What to actually use Claude for, day-to-day

The patterns that genuinely save time for Australian small businesses. We’ve seen all of these work in real client engagements.

1. Email triage

Paste 5-10 customer emails into Claude. Ask: “For each, give me a one-line summary, the customer’s intent (enquiry, complaint, booking, info-only), and a draft reply in my voice.”

Time: 1 minute. Replaces: 20-40 minutes of email writing.

2. Meeting summaries

After a Zoom or Teams meeting, copy the auto-generated transcript. Paste into Claude. Ask: “Summarise this in 4 dot points: key decisions, action items, who owns each one, deadlines.”

Time: 2 minutes. Replaces: writing meeting notes from memory.

3. Social media captions

Paste a photo description (or describe the product / dish / project). Ask: “Three Instagram captions, 40 words each, warm Australian tone, hook + body + soft call to action.”

Time: 30 seconds. Replaces: an hour of staring at a blank caption box.

4. Drafting hard messages

The polite-but-firm follow-up to the slow-paying customer. The apology email after you messed up. The “you’re no longer a fit for our service” email. Hard to write yourself, easy to draft with Claude.

“Draft a polite-but-firm follow-up to an Australian customer who is 30 days late on a $4,200 invoice. We’ve already sent two reminders. The customer is normally good. Don’t burn the relationship; do communicate urgency. Suggest a payment plan as an option. Australian tone.”

Time: 1 minute. Replaces: an hour of drafting and re-drafting because you don’t want to upset them.

5. Summarising long documents

You got a 30-page accountant’s report. A 50-page tender document. A 4,000-word contract. Paste it in. Ask: “Summarise in plain English. What does this mean for me? What do I need to action? What should I push back on?”

Time: 2 minutes. Replaces: 1-2 hours of reading, with better comprehension.

6. Brainstorming and ideas

You’ve run out of content ideas. New product names. Slogans. Subject lines. Ask Claude for 20. Pick the 3 you like. Refine them.

“I run a Newtown coffee roastery. Brainstorm 20 names for a new espresso blend made with Ethiopian and Brazilian beans. Tone: cheeky, Australian, slightly nerdy. No ‘rich’, ‘bold’, or ‘awakening’.”

Time: 1 minute. Replaces: an unproductive hour.

7. Categorising and organising

Got a messy list of 200 customers and want them sorted by region or product or status? Paste the list, describe the categories, ask Claude to sort.

“Below is a CSV export of my last 200 customers. For each, classify by region (Sydney, Melbourne, Brisbane, Perth, Adelaide, Regional VIC, Regional NSW, Regional QLD, Other). Return as a new CSV with a ‘region’ column added.”

Time: 1 minute. Replaces: a tedious afternoon in Excel.

Your first month, week by week

The single biggest failure mode for new Claude users is doing the 5-minute test, getting a “huh, that’s neat” feeling, and never going further. The 30-day plan below fixes that. Five small commitments, one per week.

Week 1: Pass the 5-minute test (this week)

• Sign up for the free Claude.ai account
• Run ONE prompt from the section above (cafe / tradie / service / store / your-own version)
• Notice what happened: did it sound like you or did it sound like AI

That’s the whole week. Don’t try to “use AI for everything” yet.

Week 2: Your top 3 recurring writing tasks

Pick the 3 writing tasks you do most often (email replies, social captions, quote follow-ups, product descriptions, whatever). For each:

• Write your usual version yourself first (so you have a baseline)
• Ask Claude to do the same task with the four-part prompt pattern (who you are / what you want / constraints / what good looks like)
• Compare side by side. Notice the gap.

Goal for the week: identify the ONE task where Claude is clearly faster and at least as good.

Week 3: Make Claude part of that one task

For the next 7 days, use Claude for that one task every single time. No exceptions. Notice:

• How much time you saved (be honest)
• How much editing the AI output needed (track it)
• Whether the output is getting closer to your voice as you refine your prompts

If after a week it’s saving you 30+ minutes a week on that one task, you’ve crossed the threshold. AI is now part of how you work.

Week 4: Add the second task and check whether to pay

You’re getting confident on task 1. Add task 2 from your shortlist. Same pattern: every time for 7 days. Measure.

At the end of week 4, ask yourself: am I hitting the free-tier “you’ve used your messages” limit? If yes, that’s the signal to pay $30 AUD/month for Claude Pro. If no, stay on free.

If you’ve made it through week 4 with AI saving you 1-3 hours a week and the output sounding like you, the basics are done. Time to read the not-quite-beginner guide for the next layer (Claude Projects, voice files, the compounding workflows).

If you’ve stalled, that’s useful information too. Either AI isn’t right for your specific work yet (rare, but happens for some hands-on trades), or your prompts are still too generic. The fix in both cases is to email Jenn (details at the bottom of this guide) and we’ll work out which.

When to pay for Claude Pro ($30 AUD/month)

You’re on the free tier. You start using Claude every day. You notice yourself hitting “you’ve reached your free limit, wait 4 hours” messages. That’s the signal.

What you get for $30 AUD/month:

• 5x the message volume (in practice, “as much as you’ll ever want”)
• Access to the most capable models (free tier uses smaller models; Pro uses the flagship Claude Opus when you ask for it)
• Claude Projects (folders that hold your business’s context: voice samples, brand guidelines, past emails. Claude reads them at the start of every chat. This is a killer feature.)
• Bigger file uploads (you can feed it longer documents, more transcripts, larger spreadsheets)
• Priority during peak times

For most Australian small business owners, $30 AUD/month is well under what you’d pay an assistant for an hour. If Claude saves you 3-5 hours a week, the math is obvious. Pay.

The trust shortcut: ask Claude what you should verify

When you don’t know if Claude’s answer is right, ask:

“How confident are you in this answer? What should I double-check? What did you make up or guess?”

Claude is quite good at flagging its own uncertainty if you give it permission to. It will say things like “the third statistic I quoted is from memory; verify against the ATO website” or “I’m extrapolating from US figures; the Australian numbers may differ”. Use this. Trust but verify.

Words you’ll keep hearing, in plain English

You don’t need these to use Claude. But they come up.

• LLM (large language model): the technical name for what powers Claude. “AI” in casual speech.
• Prompt: what you type into Claude. Better prompts = better output.
• Context window: how much information Claude can hold in working memory at once. Big enough for most documents you’d paste in.
• Token: roughly 3/4 of a word. It’s how AI providers bill (per million tokens). You don’t need to count them.
• Hallucination: when AI confidently states something wrong. Less common in 2026, still a real risk for niche facts.
• System prompt: instructions you give Claude at the start of a chat to shape every reply (your tone, business, what’s off-limits).
• Claude Projects: a Pro feature where you upload your business’s context once, and Claude reads it at the start of every chat. We use this with every paid client.
• MCP: how AI tools plug into other apps (Gmail, Xero, Shopify). Do you need this yet? No. Skip it until Claude tells you it does.
• Claude Code: the developer version of Claude that runs in a terminal. Do you need this yet? No, unless you write code or want AI editing files on your computer.
• Agent: an AI that takes actions on its own, not just chats back. Do you need this yet? Almost certainly not in your first 6 months. Stick with chat first.
• API: the developer way to plug AI into your own software. Do you need this yet? No. The chat interface is all you need.

Full glossary at /glossary/.

What you should not do

Avoid these patterns. They cause most of the bad-AI horror stories.

1. Don’t paste sensitive client data into the free tier without thinking. Patient records, legal documents, signed contracts, third-party personal details, full payment / banking combos, Tax File Numbers, Medicare numbers: never. For the full “never paste” list and the three-tier framework (free / paid / API), see our AI privacy guide for Australian business.
2. Don’t publish first drafts without reading. AI defaults to a generic, slightly-press-release tone. A 60-second edit fixes most of it.
3. Don’t ask Claude for medical, legal or financial advice and then act on it without checking the primary source. Same risk as Googling those things, except Claude sounds more confident.
4. Don’t fabricate testimonials with AI. Don’t fabricate reviews. Don’t use AI to write fake “as seen on” claims. This is fraud, and it’s increasingly detectable.
5. Don’t be vague. “Write something good” gets you “something generic”. Be specific about what good looks like.

What’s next

You’ve passed the 5-minute test. You’ve tried a real prompt. You know what good prompts look like. Now what?

Three honest paths:

• Keep going on your own. Bookmark this guide. Read our prompt engineering for non-developers piece. Try the seven daily-use patterns above for a fortnight. You’ll find your own.
• Step up to the intermediate guide. When you’re comfortable with the basics, Claude for the not-quite-beginner covers Projects, voice tuning, and the workflows that compound. That’s the next layer up.
• Get help. Book a free 30-minute audit. No slide deck, no pitch. Jenn walks you through your business, identifies the highest-ROI AI use cases, and gives you a written plan you can use whether you hire us or not.

If you’re stuck

The most common stuck-point for new Claude users is “it gave me a meh answer and I don’t know why.” Three things to try, in order:

1. Re-prompt with the four-part pattern (who / what / constraints / what good looks like)
2. Feed Claude an example of good output (“write more like this: [paste an example]”)
3. Email Jenn, jenn@onautopilot.com.au. We reply within one business day. No pitch, no charge, no obligation.

The 30-minute version starts at /start/ if you want a quicker doorway. This guide is the long-form version of the same idea: the 30-minute test, expanded to the patterns that compound.

See also

• Claude for the not-quite-beginner when you’re ready for Projects, voice tuning, and the compounding workflows.
• Claude vs ChatGPT for Australian small business for the comparison.
• How to write better AI prompts for the 10 prompt patterns that work for any task.
• Pick an industry guide for your specific business: tradies, cafes, allied health, real estate, accountants, and more.