All guides

Path B - Builder · Guide · 15 min read

Claude for Beginners

Path B of the Soft Shift is the Builder path: turning your expertise into a product, such as a toolkit, a guide, a course, a template library or a small software tool. A few years ago that meant hiring designers, writers and developers. Today, an AI assistant can do much of the drafting, structuring, designing and even coding alongside you, while you supply the expertise and judgement. This guide introduces Claude, the AI assistant made by Anthropic, from the very beginning. You'll learn what it is, which plan to choose, how to ask for what you want, the features that matter most for Builders (projects, files, artifacts, research, skills and Claude Code), how to use it safely, and a one-week plan to build real confidence. No technical background needed. Features and plans change often, so we link to Claude's own help centre for the latest step-by-step instructions.

Key facts

$0
The Free plan includes chat on web, desktop and mobile, web search, file creation, memory, connectors, artifacts and up to five projects.claude.com/pricing (October 2026)
$20/mo
Claude Pro billed monthly, or $17 a month billed annually. It adds more usage, research, Claude Code, more models and Claude in Chrome.claude.com/pricing (October 2026)
74%
Of US independent workers used generative AI in 2025, most often for research, ideas and writing.MBO Partners, State of Independence 2025
3 surfaces
Claude runs in your web browser, as a desktop app and as a mobile app, with your work synced across them.Anthropic
Projects
Let you store files and instructions that Claude uses across every conversation in that project.Claude Help Center: What are projects?
Skills
Are reusable instructions that teach Claude how to do a task your way, such as your method, format or brand.Claude Help Center: What are skills?

Why AI changes the Builder path

The hardest part of building a product from your expertise has never been the knowledge. You have that. It's been everything around it: structuring ideas into a sequence, writing clearly at length, designing worksheets and slides, building a simple website or tool, and doing all of it in the evenings around a demanding job.

An AI assistant changes the economics. It can turn a voice note into an outline, a messy document into a clear framework, a rough idea into a working spreadsheet, or a description into a simple web app. You remain the author, the expert and the editor. AI becomes a tireless, fast collaborator who never minds a fifth rewrite.

That's why the Builder path is far more realistic for a busy professional now than it was even a few years ago. The goal of this guide is to get you from 'I've heard of it' to 'I use it every day to build'.

What Claude is

Claude is an AI assistant made by Anthropic, an AI safety and research company. You talk to it in plain language, by typing or by voice, and it responds by answering questions, writing, analysing documents, creating files, searching the web, building small apps and much more.

Claude is built on large language models: AI systems trained on large amounts of text to understand and generate language. Anthropic offers several models with different strengths. Larger models are more capable at complex reasoning, and smaller ones are faster. On paid plans you can choose which model to use for a conversation, but the default is a good starting point for most tasks.

You can use Claude in three main places: in your web browser at claude.ai, in the desktop app for Mac and Windows, and in the mobile app for iPhone and Android. Your conversations and projects follow you between them. There are also versions that work inside other tools, such as Claude in Chrome, Claude for Microsoft 365, and Claude Code for building software.

A few words you'll hear

TermWhat it means
PromptWhat you type or say to Claude: your request and its context.
ModelThe underlying AI system. Bigger models reason better; smaller ones are faster.
ContextEverything Claude can see in a conversation: your messages, files and project knowledge.
ProjectA workspace with its own files and instructions for one body of work.
ArtifactA standalone piece of work Claude creates, such as an app, page or document, that you can use and share.
ConnectorA secure link that lets Claude work with another app, like Google Drive.
SkillSaved instructions that teach Claude to do a task your way.
HallucinationWhen AI states something false with confidence. The reason you always verify.

Choosing a plan

You can start for free and upgrade when you hit the limits. Prices below are from Claude's pricing page in October 2026 and may change, so check claude.com/pricing for the latest.

For most women starting the Builder path, the Free plan is enough to learn, and Pro becomes worthwhile once you're using Claude several times a week to build your product.

PlanPriceGood for
Free$0Trying Claude: chat, web search, files, memory, connectors, artifacts, up to 5 projects
Pro$20/mo monthly, or $17/mo billed annuallyBuilders using Claude most days: more usage, research, Claude Code, more models, Claude in Chrome
MaxFrom $100/moHeavy daily use and large build projects
TeamFrom $20–25 per seat/moSmall teams that want shared projects and admin controls

How to ask for what you want

The single biggest difference between disappointing and brilliant results is how you ask. Claude can't read your mind, and it doesn't know your context unless you share it. Think of it as briefing a very capable new colleague on their first day. Use the five-part CRAFT approach.

  1. 1

    Context

    Who you are, what you're working on and why. 'I'm a former HR director building a toolkit for managers returning parents to work after leave.'

  2. 2

    Role and reader

    Who the output is for, and what they know. 'The reader is a busy first-line manager with no HR training.'

  3. 3

    Ask

    Exactly what you want. 'Draft a one-page checklist for the manager's first week after an employee returns.'

  4. 4

    Format

    How it should look. 'Use five headings, no more than six bullets under each, plain language, US English.'

  5. 5

    Tone and taste

    The voice and any examples. 'Warm, practical, not corporate. Here's a paragraph I wrote that sounds like me: ...'

Compare a vague request with a CRAFT request. 'Write a checklist for managers' will get you something generic. A CRAFT request gets you something close to usable on the first try.

Two more habits make a big difference. Give examples of what good looks like, because Claude is very good at matching a pattern. And ask Claude to ask you questions first: 'Before you start, ask me up to five questions you need answered to do this well.' Anthropic's own prompting guide at docs.claude.com covers more techniques if you want to go deeper.

Treat it like a collaborator, not a vending machine

Your first answer is a draft, not a verdict. The real value comes from iterating, just as you would with a colleague.

  • Be specific with feedback: 'Make section two half as long and more practical' beats 'make it better'.
  • Ask for options: 'Give me three different titles, each with a one-line rationale.'
  • Ask it to critique its own work: 'What's weak or missing in this draft? Then fix it.'
  • Change perspective: 'Review this as a sceptical CFO would.'
  • Build in steps: outline first, agree the outline, then draft one section at a time.
  • Start a fresh conversation when you switch topics, so old context doesn't muddy the new task.

Projects: give Claude your knowledge

A project is a workspace for one body of work, such as your product, your book or your client offer. Inside a project you can add files (your notes, frameworks, past presentations, brand guidelines) and write instructions that apply to every conversation in it, such as who your audience is, your tone and your formatting preferences.

For Builders, projects are transformative. Instead of re-explaining your method every time, you set it up once. Every new chat in the project already knows your frameworks, your audience and your voice. On the Free plan you can create up to five projects.

  1. 1

    Create one project per product

    For example: 'Returning Parents Toolkit'.

  2. 2

    Add your raw material

    Old slides, notes, articles, transcripts of talks, process documents and anything that captures how you think (removing confidential employer material).

  3. 3

    Write project instructions

    Your audience, voice, formatting rules and what to avoid. Keep them short and specific.

  4. 4

    Work inside the project

    Every outline, draft, worksheet and email for that product lives there, so the context builds over time.

Make real things: files, artifacts, docs, slides and design

Claude doesn't just write text in the chat. It can create finished work you can use, share or download.

  • Files: ask for a Word document, spreadsheet, PDF or presentation, and Claude can create it for you to download and edit.
  • Artifacts: interactive pieces such as a calculator, a checklist app, a quiz or a small website, which you can use and share by link.
  • Docs, Slides and Design: built-in tools for documents, presentations and visual designs, such as worksheets, slide decks and social graphics, that you can keep editing yourself.
  • Data analysis: upload a spreadsheet or survey results and ask for insights and charts.

For a Builder, this means you can go from idea to a prototype of your product in an afternoon: a sample worksheet, a first lesson, a pricing calculator for your landing page. Show it to five potential buyers before you build the rest.

Research with Claude

Claude can search the web to answer questions about current events, prices, competitors and markets, and cite its sources. On paid plans, the research feature carries out a deeper, multi-step investigation and writes up a report.

Use it to size your market, see what similar products exist and what they charge, find gaps in competitors' offers, and gather statistics for your content. Always click through to the sources for anything important. AI can make mistakes, and your reputation depends on accuracy.

Memory and connectors

Memory lets Claude remember useful context about you across conversations, such as your business, your preferences and your ongoing projects, so you don't have to repeat yourself. You can view, edit and turn memory off in your settings.

Connectors link Claude to tools you already use, such as Google Drive, Gmail, your calendar, Notion or Slack, so it can find and work with your files and information. Only connect what you're comfortable sharing, and review what each connector can access.

Skills: package your method

Skills are reusable sets of instructions, sometimes with templates and examples, that teach Claude to do a specific task your way, every time. Think of a skill as a standard operating procedure Claude can follow.

For a Builder, skills are powerful. You can turn your signature method into a skill (for example, 'how I run a pricing review' or 'my worksheet format'), so every output follows your structure and quality bar. Claude's help centre explains how to create custom skills, and you can ask Claude to help you write one.

Claude Code: when you want to build software

If your product is a tool rather than a document, such as a calculator, an app, an automation or a members' portal, Claude Code is Anthropic's tool for building software. You describe what you want in plain language, and Claude writes, runs and fixes the code with you. It's included with paid plans and works in the terminal, on the web, in the desktop app and on mobile.

You don't need to be a developer to start, but expect a learning curve. Begin with something small and self-contained, keep backups, and test thoroughly before you put anything in front of paying customers. For anything handling payments or personal data, get a developer to review it.

A worked example: from idea to first product in a weekend

Here's how one Builder might use Claude to go from idea to a sellable first version in two days. Imagine a former finance director who wants to sell a cash-flow toolkit for small business owners.

  1. 1

    Saturday morning: uncover and focus

    She asks Claude to interview her about her career, one question at a time. From the summary, she picks one product: a 13-week cash-flow forecast kit for owners of businesses with 5 to 50 staff.

  2. 2

    Saturday midday: research

    She asks Claude to research existing cash-flow templates and courses, their prices and the most common complaints in reviews. She notices buyers find most templates too complex, and checks the sources herself.

  3. 3

    Saturday afternoon: outline

    In a new project, she uploads her old training slides and notes, then asks for a product outline: a forecast spreadsheet, a short guide, and a 'weekly cash ritual' checklist. She edits the outline to reflect how she actually teaches it.

  4. 4

    Sunday morning: build

    She asks Claude to create the forecast spreadsheet with clear instructions on each tab, then the guide, one section at a time, in her voice. She tests the spreadsheet with real numbers from a past example and fixes two formulas.

  5. 5

    Sunday afternoon: package and test

    She asks for a one-page sales page and three pricing options, picks $47, and sends the kit to five business-owner friends for honest feedback before launching.

The expertise, the judgement and the final quality are all hers. Claude compressed weeks of drafting and formatting into a weekend.

Common beginner mistakes

  • Asking one-line questions and judging Claude by generic answers. Give context.
  • Accepting the first draft. The best results come from two or three rounds of feedback.
  • Pasting everything into one endless conversation. Use projects and start fresh chats for new tasks.
  • Publishing without checking facts, numbers and links.
  • Letting AI flatten your voice. Edit until it sounds like you.
  • Trying to learn every feature at once. Master briefing and projects first; add the rest later.
  • Giving up after one bad result. Rephrase, add an example, or ask what information it needs.

Which feature, when?

If you want to...Use
Think through an idea or get a quick answerA regular chat
Work on one product over weeksA project with your files and instructions
Get something you can download or shareFiles, artifacts, Docs, Slides or Design
Know what's happening in the market nowWeb search, or research for a deeper report
Work with your existing documents and emailConnectors
Get the same quality every time for a repeated taskA skill
Build a real app or automationClaude Code

Build on the go

Some of the best product ideas arrive on a walk or in the car. The mobile app lets you talk to Claude by voice, so you can capture ideas the moment they appear. Try dictating a stream of thoughts after a client call or a commute, then ask Claude to turn it into a structured outline inside your project. Many Builders find this is how they get their expertise out of their heads fastest, because speaking is easier than writing from a blank page.

Use Claude safely and responsibly

  • Check facts. AI can sound confident and still be wrong. Verify statistics, legal, medical and financial points against original sources before you publish or sell anything.
  • Protect confidential information. Don't paste your employer's or clients' confidential data into any AI tool unless you're permitted to, and review your privacy and data settings.
  • Keep your voice. Use AI to draft and structure, then edit so the final product sounds like you and reflects your real experience. That's what buyers pay for.
  • Respect others' work. Don't ask AI to copy someone else's course, book or design. Build from your own expertise.
  • Disclose where it matters. If a client or platform requires you to disclose AI use, do so.
  • Keep humans in the loop for decisions that affect people's health, money or careers.

Ten ways a Builder can use Claude this month

TaskTry asking
Find your product idea“Here's my career summary. Suggest 10 digital products I could build, ranked by demand and effort.”
Validate demand“Research what similar products exist, what they cost and what reviewers complain about.”
Outline the product“Turn these notes into a 6-module outline with outcomes for each module.”
Draft content“Draft module 1 in my voice, using the frameworks in this project.”
Design worksheets“Create a fillable one-page worksheet for this exercise.”
Build a tool“Build an interactive calculator that does [X] for my landing page.”
Write the sales page“Write a sales page for [product] for [buyer], with FAQs.”
Plan the launch“Create a 4-week launch plan for a $57 product with no paid ads.”
Create social posts“Turn this module into 8 LinkedIn posts in my voice.”
Answer customers“Draft friendly replies to these five customer questions.”

A starter prompt library

Copy these into Claude and fill in the brackets.

  • “I'm [role] with [years] years' experience in [field]. Interview me with one question at a time to uncover the expertise I could turn into a product. Ask 10 questions, then summarise what you learned.”
  • “Here are my notes on [topic]. Turn them into a clear framework with a name, 4 to 6 steps, and a one-line description of each.”
  • “Act as my target buyer, a [description]. Read this product outline and tell me honestly what's confusing, missing or not worth paying for.”
  • “Write three versions of a one-sentence product promise for [product], each for a different buyer motivation.”
  • “Create a checklist from this guide that someone could tick off in a week.”
  • “Before you start, ask me any questions you need answered to do this well.”

Your first week with Claude

  1. 1

    Day 1: Set up

    Create a free account, install the desktop and mobile apps, and spend 20 minutes chatting about anything to get comfortable.

  2. 2

    Day 2: Learn to brief

    Use CRAFT to ask for something real, such as an email you need to write. Compare it with a vague request.

  3. 3

    Day 3: Create a project

    Make a project for your product idea, add three documents of your raw material, and write short project instructions.

  4. 4

    Day 4: Find your idea

    Use the interview prompt to uncover your product options. Pick one to explore.

  5. 5

    Day 5: Make something

    Ask Claude to create one real piece: a worksheet, a one-page guide or a simple calculator.

  6. 6

    Day 6: Research

    Use web search to look at competitors and pricing. Verify the sources.

  7. 7

    Day 7: Review

    What saved you the most time? What needed the most editing? Decide whether to upgrade to Pro based on how much you're using it.

Setup checklist

Checklist0 of 7 done

Good habits checklist

Checklist0 of 8 done

Plans, prices and features change. Check claude.com/pricing and the Claude Help Center for current details. Vaantage is independent of Anthropic and isn't paid to recommend Claude.

Sources

  1. Claude pricing and plans
  2. Claude Help Center: What are projects?
  3. Claude Help Center: What are skills?
  4. Claude Help Center: What are artifacts and how do I use them?
  5. Claude Help Center: Create and edit files with Claude
  6. Claude Help Center: Use research on Claude
  7. Anthropic prompt engineering overview
  8. MBO Partners: State of Independence 2025 (SIA)