Why Most Business Owners Only Use 5% of Claude

This is Farah’s story, more or less. Some details are changed, but the pattern isn’t — I’ve watched it repeat across dozens of SME owners in the Club. If you’ve ever closed a Claude chat feeling underwhelmed, you’ll probably recognise yourself somewhere in it.

The tab she kept closing

Farah runs a small event styling business out of Petaling Jaya — mostly weddings and corporate launches, mostly booked through Instagram DMs and WhatsApp. Like a lot of the owners I work with, she’d heard enough about AI to feel behind, and enough about Claude specifically to give it a try.

Her first few weeks looked like this: open Claude, ask for a caption, get something serviceable but generic, rewrite half of it herself, close the tab. Ask for a client follow-up message, same thing. Ask for help pricing a package, same thing again. Useful, technically. Never quite worth building a habit around.

“It felt like talking to someone smart who’d never met me,” she told me. That line stuck, because it’s exactly right — and it’s the whole problem in one sentence.

One question, one answer

Here’s what I mean when I say most business owners use less than five percent of what Claude can do. Treating it like a search box — one question in, one answer out — is like hiring a strategist and only ever asking them to confirm today’s date. The capacity is sitting there unused, and it stays unused for one simple reason: nobody ever gave it anything to work with.

Claude has no memory of your business, your brand, or your customers unless you tell it — or unless you ask it to ask you. That second option is the one almost nobody tries first.

I need help with [a task — e.g. a follow-up message to a client who hasn't confirmed their booking].

Before you answer, ask me any questions you need to do this well.

The second habit worth building alongside it: ask Claude to check its own work. It’s a strange thing to have to request — of course it should check its own work — but it does catch gaps a rushed first draft leaves behind, and it costs nothing but one extra sentence.

A workspace, not just a chat

Farah’s second shift came about two weeks later, once the novelty of better one-off answers had worn off and a new frustration set in: she was retyping the same context every single time. Her brand tone. Her pricing structure. The three package tiers she offered. Every new chat, from scratch, again.

This is where Claude Projects earned their keep. Instead of one long, cluttered conversation — or a dozen separate ones, each starting cold — she built a single workspace for her business, with:

• A master prompt describing how she works, who her clients are, and what she’s usually trying to achieve
• Her actual brand voice and past captions, so new drafts sounded like her, not like a template
• Her pricing tiers and package details, so she never had to restate them

Interview me to build a master prompt for my role as [your role — e.g. owner of a small event styling business].

Ask me about how I work, who my customers are, and what I'm usually trying to get done.

She also connected her Gmail and Google Drive not long after — a smaller shift, but a meaningful one. Instead of copying client emails into the chat by hand, she could ask Claude to pull the thread directly. Small friction removed, repeated dozens of times a week, adds up faster than it sounds.

What would change about your week if Claude already knew your business the way a long-time employee does?

The week she stopped doing it herself

By week five, Farah noticed something that surprised her more than any single answer Claude had given: she was still the one doing all the work. The context problem was solved. The workspace was solid. But every task still needed her to sit down, open the chat, and press go.

This is the quiet ceiling a lot of business owners hit without naming it. The tool is capable. The bottleneck has just moved — from “Claude doesn’t understand me” to “I’m still the one directing every single thing.”

The fix wasn’t complicated. She picked her single most repeated task — a weekly update she sent to her two subcontractors — and instead of writing it fresh each time, she asked Claude to help her turn it into a documented, repeatable process.

I do [a task you repeat weekly or more] the same way most times.

Interview me about how I currently do this, then write it up as a clear, repeatable set of instructions I can reuse.

The recipe book moment

What Farah built in the last section was really an early version of a Claude skill — she just didn’t have the word for it yet. Once she did, the idea clicked faster than anything else in this story.

Think of a skill as a recipe you write once. Instead of re-explaining the full method every time you want to cook the dish, Claude opens that recipe only when it’s needed and follows it the same way, every time. Not loaded into every conversation by default — just there, ready, when the task calls for it.

Farah’s first skill scored and ranked new enquiries by budget and event date, so she could see at a glance who to follow up with first. It took her one afternoon to set up. She’s used it every week since.

Six weeks later

None of this made Farah’s business unrecognisable. That was never the promise. What changed was smaller and more durable: she stopped dreading the admin side of her work, because most of it no longer landed entirely on her.

• Client follow-ups went from a dreaded backlog to a five-minute task, because Claude already knew her tone and her packages
• New enquiries were scored and sorted automatically, so she called the right people first
• Her weekly subcontractor update took two minutes instead of twenty, because the process was already written down

“It’s not that Claude got smarter,” she said. “I just finally told it who I was.”

Your turn

If any part of Farah’s early weeks sounded familiar, the fix isn’t a bigger tool or a longer prompt. It’s one small shift, used consistently, before you move to the next one.

1. This week: let Claude interview you before it answers, on one real task.
2. Next week: build one Project with your business context and brand voice.
3. The week after: pick your most repeated task and write it up as a process.

Small, consistent use beats one big setup you never return to.

FAQ