Claude for the not-quite-beginner, the Australian small business follow-up

The honest checkpoint: are you ready for this?

This guide assumes:

• You have a Claude account (free or Pro, either works)
• You’ve used Claude at least 5-10 times for real-business prompts
• You know what a “prompt” is and roughly what good prompts look like

If you’re not there yet, do the absolute beginners guide first. Come back when you’ve passed the 5-minute test and used Claude for at least a week.

If you’re there, let’s compound.

The 80/20: Claude Projects

If you only read one section, read this one. Claude Projects is the single biggest unlock for paying users and it’s the feature most people never touch.

What it is, in plain English

Imagine if every new staff member you hired could read a folder called “everything about how we work” on their first day, and would re-read it before every conversation with you. They’d know your tone, your products, your customer base, your no-no words, your style. They’d never have to ask.

Claude Projects is exactly that, but for AI. You make a Project, upload (or paste) the business context, and from then on every chat inside that Project starts with Claude already knowing all of it. You don’t have to re-paste your menu, your voice samples, your style guide every single chat. It just knows.

How to set it up (10 minutes, one-time)

1. Open Claude.ai. Sign in to your Pro account.
2. In the left sidebar, click Projects → Create Project.
3. Name it after your business: “Marlowe’s Cafe”, “Bennett Plumbing”, “Northcote Physio”.
4. In the Project’s Instructions field, paste a 200-500 word “voice file” (we’ll cover that in the next section).
5. In the Project’s Knowledge area, upload supporting files: your product list, your menu, your FAQs, your past blog posts, your last 10 customer reply emails, your brand style guide. Anything Claude would benefit from knowing.
6. Save.

Done. Now every time you start a chat inside that Project, Claude reads all of it before replying. You’ll feel the difference within 2 prompts. Output suddenly sounds like you.

The “knowledge” you want in there

The Knowledge area takes documents (PDF, DOCX, TXT, MD) and links them to every chat in the Project. The most valuable things to upload, for most small businesses:

• Brand voice guide (your written tone rules)
• Product / service list (with descriptions, AUD pricing, common questions)
• 5-10 past customer reply emails you were proud of (Claude learns your reply voice)
• 2-3 past blog posts or social captions you liked (voice samples)
• Your “about us” page (so Claude knows the business’s mission and history)
• Your FAQ document (so Claude can answer customer questions in your voice)
• A list of words and phrases you NEVER use (the no-no list)

That’s it. Don’t upload your entire Google Drive. The Project gets bloated and Claude’s responses get slower and less focused. 5-15 well-chosen files is the sweet spot.

The voice file that pays off forever

Inside every Claude Project, the Instructions field is where you write the most important 200-500 words of your year. It’s read before every reply, every time. Write it once, edit it twice over the next two months, and Claude will sound like you for as long as you use it.

The voice-file template

Copy this. Edit the bracketed bits. Paste into your Project’s Instructions field.

WHO I AM
I run [BUSINESS NAME], a [TYPE OF BUSINESS] in [CITY/SUBURB], Australia.
We sell/offer [WHAT YOU DO IN ONE SENTENCE]. Our customers are mostly
[WHO YOUR CUSTOMERS ARE: age range, situation, vibe].

WHO I'M WRITING TO
Most of my writing (emails, social, blog, ads) is aimed at [PRIMARY
AUDIENCE]. They know [BACKGROUND]. They don't know [THINGS YOU SHOULDN'T
ASSUME]. They care about [WHAT MATTERS TO THEM].

TONE
We sound [3-4 ADJECTIVES: warm, dry, slightly cheeky, professional, etc.].
We don't sound like [3-4 NEGATIVES: corporate, salesy, gushing, American, etc.].

RULES
- No em-dashes
- Australian English (organised, colour, centre, analysed)
- AUD currency unless I say otherwise
- DD/MM/YYYY dates
- Banned words: the standard AI-tell list (the L-word, the E-word, the U-word, the D-word) plus any you've personally noticed Claude overusing
- Never use exclamation marks except in [SPECIFIC CASES, if any]

VOICE SAMPLES
Here are 3-5 sentences that sound exactly like me:
1. [paste one]
2. [paste one]
3. [paste one]
4. [paste one]

WHAT'S OFF-LIMITS
- [Topics, claims, or angles you don't want Claude to ever touch]
- [Competitor mentions, if relevant]
- [Confidential things]

OUTPUT DEFAULTS
- Unless I say otherwise, default to [SHORT/MEDIUM/LONG] length.
- Default format: [paragraphs / dot points / structured headers].
- Always ask me [SPECIFIC CLARIFYING QUESTIONS] if I haven't given them.

Spend an hour on this. Edit it twice in the next month as you notice patterns (“Claude keeps using ‘delight’ even though I never do, add it to the no-no list”). After a month, it’s a finely-tuned filter. Output sounds like you wrote it.

Five compounding workflows

The patterns that turn occasional Claude use into a daily habit. Pick two for the first month. Add the others as the habit forms.

Workflow 1: Morning planning (10 minutes)

Every morning, before opening email, open Claude.

“Good morning. Here’s my schedule for today: [paste it]. Here are the three biggest open threads in the business: [paste them]. Here’s what I want to ship by Friday: [paste it]. Help me prioritise the day. Flag anything I’m forgetting. Suggest the order I should tackle things to maximise momentum.”

You get an honest second brain on your morning. Claude’s reordering of your day is usually 80% sensible; the act of articulating the day clarifies your own thinking. Replaces journaling, replaces the productivity coach, costs nothing.

Workflow 2: End-of-day journal (5 minutes)

Last thing in the work day.

“Quick end-of-day journal. Today I: [3-5 bullet points of what you did]. Today I felt: [a sentence]. Tomorrow I need to: [3 bullet points]. Anything I’m avoiding: [a sentence]. Reflect back: what’s the pattern this week, what should I notice, what’s the one thing I should fix tomorrow?”

The pattern-spotting is what makes this valuable. After two weeks Claude will start pointing out things like “this is the third time you’ve mentioned the supplier issue without dealing with it” or “you’ve talked about hiring a VA for six weeks, why are you stalling?” Useful, and free.

Workflow 3: The draft factory

Every email, every social post, every quote, every reply is a Claude draft first. Not because Claude writes them better than you (it doesn’t). Because Claude writes a first draft faster than you, and the editing is where the quality comes from.

The rule: never start from a blank page when Claude can give you a draft in 30 seconds.

Workflow 4: Weekly research desk (30 minutes)

Once a week, dump every research question you’ve accumulated into Claude.

“Weekly research roundup. Five questions I need quick answers to:

1. [your question]
2. [your question] …

For each: 2-3 paragraph answer in plain English, with ‘what should I verify’ notes.”

In 30 minutes you cover what would have been 5-10 ad-hoc Googling sessions across the week. Better, because Claude joins dots Google doesn’t.

Workflow 5: Monthly retrospective

Last day of the month.

“Monthly retrospective. The wins this month: [list]. The misses: [list]. The patterns I noticed: [list]. The decisions I’m still putting off: [list]. Now: what’s the honest read? What should I start doing in [next month]? What should I stop?”

The “stop” list is the gold. Most small business owners are great at adding new things and terrible at stopping old ones. Claude’s pattern-recognition (across the journals and retros you’ve been writing) makes it surprisingly good at flagging the stop list.

When you’re ready for the next thing

Three honest signals.

Signal 1: Ready for Claude Code

If you’ve started wishing Claude could:

• Touch your files directly (instead of you copy-pasting)
• Edit your spreadsheets in place (instead of describing changes)
• Run scripts on data (instead of you doing it manually)
• Read your codebase (if you have one)
• Write code that actually works

…you’re ready for Claude Code. It’s the same Claude, running in a terminal where it can read and write files on your computer. For non-developers we have a getting-started piece for non-developers.

If you’ve never opened a terminal and don’t have files / code / spreadsheets you want Claude touching, skip this. You’re not ready yet, and that’s fine.

Signal 2: Ready for an agent

If you find yourself asking Claude to do the same thing every day (read these emails, draft these replies, summarise these meetings, send this report), an agent might be next.

An agent is an AI that runs the workflow on its own, in a loop, without you typing each time. It checks inputs, takes actions, makes decisions inside a defined scope.

Two honest signals you’re ready for an agent:

• You’ve been doing the same Claude prompt 5+ times a week for a month
• You know exactly what “good” looks like for that task

If both are true, an agent will save you the time and improve the consistency. If either’s false, build the manual habit longer.

We build agents as part of our productised services. The most common ones we ship: after-hours customer triage, inventory monitoring, lead enrichment, content factory, weekly briefings. Each one is a specific named pattern, with a fixed AUD price.

Signal 3: Ready for Projects-of-Projects (multi-business)

If you run more than one business (or wear more than one hat: founder, parent, side hustle, board role), make one Claude Project per identity. Don’t mix them. The voice file for “Founder of Marlowe’s Cafe” is not the same as the voice file for “Board member of Bennett Trust”. Separate Projects keep the voices clean.

We do this internally: separate Projects for Boring Ventures (the parent co), DotVA (the VA agency), Lead Gen Empire (the comparison network), and the consulting work. Each has its own voice file, its own customer list, its own no-no words. Switching is one click.

The intermediate mistakes (and how to avoid them)

The four most common intermediate-user pitfalls.

Mistake 1: The 3-page mega-prompt

New users err on the side of vague. Intermediate users overcorrect by writing prompts that ask for 15 things at once. Output gets generic again.

Fix: one prompt = one focused outcome. Chain prompts when you have multiple goals. Use the conversation, don’t try to one-shot everything.

Mistake 2: Not refreshing the voice file

You wrote the voice file in week one. You haven’t touched it. Three months later your business has evolved and Claude is still writing in your week-one voice.

Fix: monthly 10-minute review. Read your voice file. Edit the bits that no longer match. Add the words you’ve added to your no-no list since.

Mistake 3: Using Claude as Google

Asking Claude factual questions about recent events, niche regulations, or specific people is the highest-hallucination risk pattern. Claude is excellent at synthesis, generation, drafting, and reasoning. It’s not a search engine.

Fix: for facts, use Perplexity (which actually searches). For drafts, summaries and synthesis, use Claude.

Mistake 4: Not measuring whether it’s saving time

You feel busy. You’re using Claude every day. But is it actually saving time, or are you just doing more (without realising you’re doing more)?

Fix: pick two weeks. Track what you handed to Claude, how long each task took including editing, and what you would have done in that time before AI. Real savings emerge clearly. So do the cases where AI added busywork instead of removing it.

What’s next

You’ve got Projects set up, a voice file in place, and at least two compounding workflows running. From here:

• Read the voice-tuning deep dive. How to fine-tune AI for business voice covers the next level of voice work, including handling multiple brands and seasonal tone shifts.
• Pick an industry guide. All 18 of our industry-specific playbooks build on this foundation. Apply the patterns to your specific business.
• Consider Claude Code or an agent. If signals 1 or 2 above apply, take the next step.
• Book a free audit. If you’re stuck on workflow design, book 30 minutes with us. We’ll map your week against the AI patterns and tell you which one to automate first.

See also

• Claude for absolute beginners if you skipped ahead or want to send someone the starter.
• How to write better AI prompts for the 10 prompt patterns that work for any task.
• Custom GPTs vs Claude Projects for the platform comparison.
• Free 30-minute audit if you want help designing your weekly workflow.